GNOME Bugzilla – Bug 554939
crash in Open Folder:
Last modified: 2008-10-04 08:48:01 UTC
Version: 2.20.0 What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.22.2 2008-05-29 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-686 #1 SMP Thu May 8 02:16:39 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 66207744 vsize: 66207744 resident: 22061056 share: 14356480 rss: 22061056 rss_rlim: 4294967295 CPU usage: start_time: 1223073938 rtime: 1088 utime: 987 stime: 101 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/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6b03720 (LWP 2696)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 207729
Thread 1 (Thread 0xb6b03720 (LWP 2696))
----------- .xsession-errors (14 sec old) --------------------- ** Message: mBytesStreamed 3399684 ** Message: DestroyStream reason 0 TotemEmbedded-Message: Viewer state: STOPPED ** Message: URLNotify URL 'http://galleries.amateurallure.com/aam-eve01/03.mpg' reason 0 TotemEmbedded-Message: totem_embedded_open_internal 'file:///home/paul/.mozilla/firefox/303s26kj.default/Cache/C0A874B0d01' is-browser-stream 0 start-play 0 TotemEmbedded-Message: BEFORE _open TotemEmbedded-Message: AFTER _open (ret: 1) TotemEmbedded-Message: Viewer state: PLAYING TotemEmbedded-Message: Viewer state: STOPPED ** Message: totemPlugin dtor [0xa8acf18] ** Message: NP_Shutdown connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! --------------------------------------------------
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 522534 ***