GNOME Bugzilla – Bug 512696
crash in Open Folder: Pretty nice - this time ...
Last modified: 2008-01-29 08:54:47 UTC
Version: 2.21.6 What were you doing when the application crashed? Pretty nice - this time I must reboot because - Nautilus trow me this error window from 5 to 5 seconds. Lol. 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: 112214016 vsize: 112214016 resident: 48377856 share: 23048192 rss: 48377856 rss_rlim: 4294967295 CPU usage: start_time: 1201568697 rtime: 391 utime: 360 stime: 31 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 0xb6a916c0 (LWP 15557)] [New Thread 0xb2902b90 (LWP 15561)] (no debugging symbols found) 0xb7f2e410 in __kernel_vsyscall ()
+ Trace 187137
Thread 1 (Thread 0xb6a916c0 (LWP 15557))
----------- .xsession-errors --------------------- Initializing nautilus-open-terminal extension ** (nautilus:13277): WARNING **: Unable to add monitor: Not supported Initializing nautilus-open-terminal extension ** (nautilus:13294): WARNING **: Unable to add monitor: Not supported Initializing nautilus-open-terminal extension ** (nautilus:13308): WARNING **: Unable to add monitor: Not supported Initializing nautilus-open-terminal extension ** (nautilus:13324): WARNING **: Unable to add monitor: Not supported Initializing nautilus-open-terminal extension ** (nautilus:15557): 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 ***