After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 584953 - crash in Home Folder:
crash in Home Folder:
Status: RESOLVED DUPLICATE of bug 584745
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-06-05 19:31 UTC by meier
Modified: 2009-06-06 03:12 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26



Description meier 2009-06-05 19:31:41 UTC
What were you doing when the application crashed?



Distribution: Debian squeeze/sid
Gnome Release: 2.26.1 2009-04-14 (Debian)
BugBuddy Version: 2.26.0

System: Linux 2.6.26-1-686 #1 SMP Fri Mar 13 18:08:45 UTC 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: gnome
GTK+ Modules: gnomebreakpad, canberra-gtk-module

Memory status: size: 86306816 vsize: 86306816 resident: 18526208 share: 13340672 rss: 18526208 rss_rlim: 18446744073709551615
CPU usage: start_time: 1244218173 rtime: 432 utime: 402 stime: 30 cutime:0 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/nautilus'

[Thread debugging using libthread_db enabled]
[New Thread 0xb6de8760 (LWP 379)]
[New Thread 0xb4afab90 (LWP 383)]
0xb7f27424 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6de8760 (LWP 379))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 IA__g_spawn_sync
    at /build/buildd-glib2.0_2.20.3-1-i386-o59wJY/glib2.0-2.20.3/glib/gspawn.c line 382
  • #3 IA__g_spawn_command_line_sync
    at /build/buildd-glib2.0_2.20.3-1-i386-o59wJY/glib2.0-2.20.3/glib/gspawn.c line 694
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 ??
  • #7 exit
    from /lib/i686/cmov/libc.so.6
  • #8 __libc_start_main
    from /lib/i686/cmov/libc.so.6
  • #9 _start
    at ../sysdeps/i386/elf/start.S line 119
  • #0 __kernel_vsyscall


----------- .xsession-errors (1804151 sec old) ---------------------
open uri = file:///home/shared/Eigene Bilder/2009/04/04/DSC00074.JPG
open uri = file:///media/cdrom0/DSC00075.JPG
cleanup context
cleanup context
open uri = file:///media/cdrom0/DSC00075.JPG
open uri = file:///home/shared/Eigene Bilder/2009/04/04/DSC00074.JPG
open uri = file:///home/shared/Eigene Bilder/2009/04/04/DSC00074.JPG
open uri = file:///home/shared/Eigene Bilder/2009/04/04/DSC00075.JPG
open uri = file:///media/cdrom0/DSC00076.JPG
open uri = file:///media/cdrom0/DSC00076.JPG
open uri = file:///home/shared/Eigene Bilder/2009/04/04/DSC00076.JPG
open uri = file:///home/shared/Eigene Bilder/2009/04/04/DSC00075.JPG
open uri = file:///home/shared/Eigene Bilder/2009/04/04/DSC00075.JPG
Syncing metadata to file...
open uri = file:///home/shared/Eigene Bilder/2009/04/04/DSC00073.JPG
old = "" new = "" heading = "ASCII
--------------------------------------------------
Comment 1 Fabio Durán Verdugo 2009-06-06 03:12:59 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


*** This bug has been marked as a duplicate of 584745 ***