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 601027 - crash in File Manager:
crash in File Manager:
Status: RESOLVED DUPLICATE of bug 595804
Product: nautilus
Classification: Core
Component: general
2.26.x
Other All
: Normal critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-11-06 22:31 UTC by lajos-herpai
Modified: 2009-11-07 14:44 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28


Description lajos-herpai 2009-11-06 22:31:21 UTC 
Version: 2.26.3

What were you doing when the application crashed?



Distribution: Debian squeeze/sid
Gnome Release: 2.28.0 2009-09-27 (Debian)
BugBuddy Version: 2.28.0

System: Linux 2.6.26-2-686 #1 SMP Wed Nov 4 20:45:37 UTC 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10605000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Nuvola
GTK+ Modules: gnomebreakpad, canberra-gtk-module

Memory status: size: 72998912 vsize: 72998912 resident: 24342528 share: 19283968 rss: 24342528 rss_rlim: 18446744073709551615
CPU usage: start_time: 1257546661 rtime: 224 utime: 208 stime: 16 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb4788b90 (LWP 3777)]
[New Thread 0xb520cb90 (LWP 3764)]
0xb7fc1424 in __kernel_vsyscall ()

+ Trace 218890

Thread 2 (Thread 0xb4788b90 (LWP 3777))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 IA__g_spawn_sync
    at /build/buildd-glib2.0_2.22.2-2-i386-R8GTDn/glib2.0-2.22.2/glib/gspawn.c line 386
  • #3 IA__g_spawn_command_line_sync
    at /build/buildd-glib2.0_2.22.2-2-i386-R8GTDn/glib2.0-2.22.2/glib/gspawn.c line 700
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 ??
  • #7 g_local_file_enumerator_next_file
    at /build/buildd-glib2.0_2.22.2-2-i386-R8GTDn/glib2.0-2.22.2/gio/glocalfileenumerator.c line 345
  • #8 next_files_thread
    at /build/buildd-glib2.0_2.22.2-2-i386-R8GTDn/glib2.0-2.22.2/gio/gfileenumerator.c line 641
  • #9 run_in_thread
    at /build/buildd-glib2.0_2.22.2-2-i386-R8GTDn/glib2.0-2.22.2/gio/gsimpleasyncresult.c line 676
  • #10 io_job_thread
    at /build/buildd-glib2.0_2.22.2-2-i386-R8GTDn/glib2.0-2.22.2/gio/gioscheduler.c line 182
  • #11 g_thread_pool_thread_proxy
    at /build/buildd-glib2.0_2.22.2-2-i386-R8GTDn/glib2.0-2.22.2/glib/gthreadpool.c line 265
  • #12 g_thread_create_proxy
    at /build/buildd-glib2.0_2.22.2-2-i386-R8GTDn/glib2.0-2.22.2/glib/gthread.c line 635
  • #13 start_thread
    from /lib/i686/cmov/libpthread.so.0
  • #14 clone
    from /lib/i686/cmov/libc.so.6 

	Inferior 1 [process 3763] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]


----------- .xsession-errors ---------------------
** (gnome-volume-control-applet:3423): WARNING **: Connection failed, reconnecting...
** (gnome-volume-control-applet:3423): WARNING **: Connection failed, reconnecting...
** (gnome-volume-control-applet:3423): WARNING **: Connection failed, reconnecting...
** Message: Initializing gksu extension...
** (gnome-volume-control-applet:3423): WARNING **: Connection failed, reconnecting...
** (gnome-volume-control-applet:3423): WARNING **: Connection failed, reconnecting...
** (bug-buddy:3778): WARNING **: Couldn't load /usr/share/applications/openoffice.org3-startcenter.desktop: Datei oder Verzeichnis nicht gefunden
** (gnome-volume-control-applet:3423): WARNING **: Connection failed, reconnecting...
--------------------------------------------------
Comment 1 Akhil Laddha 2009-11-07 04:07:27 UTC 
dupe of bug 595804 ?
Comment 2 Cosimo Cecchi 2009-11-07 14:44:59 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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