GNOME Bugzilla – Bug 511454
crash in Open Folder: pulling the 'volume' tab
Last modified: 2008-01-23 10:34:03 UTC
Version: 2.18.3 What were you doing when the application crashed? pulling the 'volume' tab Distribution: Debian lenny/sid Gnome Release: 2.20.2 2007-11-29 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-3-486 #1 Mon Nov 12 07:53:08 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: 76615680 vsize: 76615680 resident: 26955776 share: 14856192 rss: 26955776 rss_rlim: 4294967295 CPU usage: start_time: 1201067751 rtime: 925 utime: 849 stime: 76 cutime:24 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/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6e296b0 (LWP 5743)] (no debugging symbols found) 0xb767c321 in waitpid () from /lib/libpthread.so.0
+ Trace 186442
Thread 1 (Thread 0xb6e296b0 (LWP 5743))
----------- .xsession-errors (397225 sec old) --------------------- ** Message: IsSchemeSupported scheme 'http': yes ** Message: totem_embedded_open_internal 'fd://0' is-browser-stream 1 start-play 1 ** Message: BEFORE _open ** Message: AFTER _open (ret: 1) ** Message: Viewer state: PLAYING ** Message: OpenStream reply ** Message: NewStream mimetype 'video/mpeg' URL 'http://freshteenssex.com/hun3/5.mpg' ** Message: Is unsupported mime-type 'video/mpeg' AFD changed from -2 to -1 ** Message: totemPlugin ctor [0x9c5cb68] ** Message: Init mimetype 'video/mpeg' mode 2 ** Message: Base URI is 'http://xxxtremebabes.com/gal/fisting/071107/content/clip04.mpg' ** Message: Real mimetype for 'video/mpeg' is 'video/mpeg' argv[0] type video/mp ...Too much output, ignoring rest... --------------------------------------------------
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 ***