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 598127 - crash in File Manager: I just had a few folders...
crash in File Manager: I just had a few folders...
Status: RESOLVED DUPLICATE of bug 554550
Product: nautilus
Classification: Core
Component: general
2.28.x
Other All
: Normal critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-10-12 00:50 UTC by timmazid
Modified: 2009-10-12 05:48 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28


Description timmazid 2009-10-12 00:50:34 UTC 
Version: 2.28.0

What were you doing when the application crashed?
I just had a few folders open. That's all, I think.


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

System: Linux 2.6.30-1-amd64 #1 SMP Sat Aug 15 18:09:19 UTC 2009 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10604000
Selinux: No
Accessibility: Disabled
GTK+ Theme: SphereCrystal
Icon Theme: SphereCrystal
GTK+ Modules: gnomebreakpad, canberra-gtk-module

Memory status: size: 740478976 vsize: 740478976 resident: 61509632 share: 22011904 rss: 61509632 rss_rlim: 18446744073709551615
CPU usage: start_time: 1255171844 rtime: 13420 utime: 9145 stime: 4275 cutime:1474 cstime: 614 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0x7f9045e63950 (LWP 30291)]
0x00007f90668f828f in __libc_waitpid (pid=30293, stat_loc=0x7fff9936ce30, 
    options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41
	in ../sysdeps/unix/sysv/linux/waitpid.c

+ Trace 218232

Thread 1 (Thread 0x7f9068096800 (LWP 3079))

  • #0 __libc_waitpid
    at ../sysdeps/unix/sysv/linux/waitpid.c line 41
  • #1 g_spawn_sync
    from /lib/libglib-2.0.so.0
  • #2 g_spawn_command_line_sync
    from /lib/libglib-2.0.so.0
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 <signal handler called>
  • #5 g_type_check_instance
    from /usr/lib/libgobject-2.0.so.0
  • #6 g_signal_handlers_disconnect_matched
    from /usr/lib/libgobject-2.0.so.0
  • #7 remove_pending
    at fm-properties-window.c line 5322
  • #8 is_directory_ready_callback
    at fm-properties-window.c line 5349
  • #9 call_ready_callbacks_at_idle
    at nautilus-directory-async.c line 1835
  • #10 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #11 ??
    from /lib/libglib-2.0.so.0
  • #12 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #13 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 main
    at nautilus-main.c line 544 


---- Critical and fatal warnings logged during execution ----

** Eel **: eel_timed_wait_stop: assertion `wait != NULL' failed 


----------- .xsession-errors (51319 sec old) ---------------------
(firefox-bin:19118): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:19118): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:19118): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:19118): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:19118): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:19118): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:19118): Gdk-WARNING **: XID collision, trouble ahead
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Akhil Laddha 2009-10-12 05:48:38 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 554550 ***