GNOME Bugzilla – Bug 494990
crash in Computer: I just opened the proper...
Last modified: 2007-11-13 21:53:55 UTC
Version: 2.18.3 What were you doing when the application crashed? I just opened the properties dialog box on nautilus on a sub-directory of my usb-key (automounted by gnome). The bug is repeatable. Other open apps : - firefox (with fire-ftp running) - gnome-terminal - several nautilus windows Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.21-2-686 #1 SMP Wed Jul 11 03:53:02 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 114360320 vsize: 114360320 resident: 28377088 share: 17543168 rss: 28377088 rss_rlim: 4294967295 CPU usage: start_time: 1194528998 rtime: 459 utime: 428 stime: 31 cutime:14 cstime: 5 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6dfe6b0 (LWP 9928)] (no debugging symbols found) 0xb7fae7f2 in ?? () from /lib/ld-linux.so.2
+ Trace 176336
Thread 1 (Thread 0xb6dfe6b0 (LWP 9928))
----------- .xsession-errors --------------------- ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** (nautilus:9928): CRITICAL **: dbus_g_proxy_cancel_call: assertion `pending != NULL' failed ** (nautilus:9928): CRITICAL **: dbus_g_proxy_cancel_call: assertion `pending != NULL' failed ** (nautilus:9928): CRITICAL **: dbus_g_proxy_cancel_call: assertion `pending != NULL' failed ** (nautilus:9928): CRITICAL **: dbus_g_proxy_cancel_call: assertion `pending != NULL' failed ** (nautilus:9928): CRITICAL **: dbus_g_proxy_cancel_call: assertion `pending != NULL' failed GetBoundingMetrics (char *) GetBoundingMetrics (char *) --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, the stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Could you please help fixing this by installing some debugging packages [1], start the application as normal, and try to reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the 'Details', now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance! [1] Please install debug packages for nautilus, glib2, gtk2, pango, gnome-vfs2, libgnome, and libgnomeui. More details can be found here: http://live.gnome.org/GettingTraces
Hi, I added the debug packages and paste the dbg stack here. Note that some info changes (as the uname) since I didn't have the hand on the first computer to install the packages, but the bug was reproducible on another one. ------------------------------------- Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.21.070802 #1 Thu Aug 2 00:10:52 CEST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 77987840 vsize: 77987840 resident: 26595328 share: 15183872 rss: 26595328 rss_rlim: 4294967295 CPU usage: start_time: 1194977217 rtime: 264 utime: 229 stime: 35 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb6d596b0 (LWP 4921)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 177486
Thread 1 (Thread 0xb6d596b0 (LWP 4921))
----------- .xsession-errors (24 sec old) --------------------- ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 355018 ***