GNOME Bugzilla – Bug 512699
crash in Open Folder: same as previous report ...
Last modified: 2008-01-29 08:54:25 UTC
Version: 2.21.6 What were you doing when the application crashed? same as previous report (5 seconds ago)- I have to enter in no X mode to uninstall nautilus-open-terminal Distribution: Ubuntu 8.04 (hardy) Gnome Release: 2.21.5 2008-01-15 (Ubuntu) BugBuddy Version: 2.20.1 System: Linux 2.6.24-5-generic #1 SMP Thu Jan 24 19:45:21 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Aurora-looks Icon Theme: nuoveXT.2.2 Memory status: size: 118591488 vsize: 118591488 resident: 47058944 share: 23015424 rss: 47058944 rss_rlim: 4294967295 CPU usage: start_time: 1201569375 rtime: 424 utime: 312 stime: 112 cutime:0 cstime: 0 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/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6b326c0 (LWP 7110)] [New Thread 0xb2e3cb90 (LWP 7119)] [New Thread 0xb363db90 (LWP 7116)] (no debugging symbols found) 0xb7fcf410 in __kernel_vsyscall ()
+ Trace 187140
Thread 1 (Thread 0xb6b326c0 (LWP 7110))
----------- .xsession-errors (9 sec old) --------------------- xrdb: "*Label.foreground" on line 232 overrides entry on line 151 xrdb: "*Text.foreground" on line 238 overrides entry on line 192 Initializing nautilus-open-terminal extension ** (nautilus:5858): WARNING **: Unable to add monitor: Not supported (gnome-panel:5857): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed PID TTY TIME CMD 5806 ? 00:00:00 pulseaudio (update-notifier:5869): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed checking for valid crashreport now Initializing nautilus-open-terminal extension ** (nautilus:7110): WARNING **: Unable to add monitor: Not supported --------------------------------------------------
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 511406 ***