GNOME Bugzilla – Bug 305967
totem crash
Last modified: 2005-06-06 13:03:37 UTC
Distribution: Debian 3.1 Package: totem Severity: normal Version: GNOME2.8.3 0.100 Gnome-Distributor: Debian Synopsis: totem crash Bugzilla-Product: totem Bugzilla-Component: general Bugzilla-Version: 0.100 BugBuddy-GnomeVersion: 2.0 (2.8.1) Description: Description of the crash: Clicked a link http://hex.xs4all.nl/EdsgerWybeDijkstra.wav in Firefox. Firefox launched Totem. Totem crashed. Debian unstable, updated couple weeks ago. Debugging Information: Backtrace was generated from '/usr/bin/totem' (no debugging symbols found) Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1224514848 (LWP 9506)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xb74ae53e in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 60357
Thread 1 (Thread -1224514848 (LWP 9506))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-05-30 21:40 UTC ------- The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was ilatypov@diskstream.com.
This matches the stack trace in bug 303431, comment from there: This looks like the stack trace in bug 166654, which is a duplicate of bug 157723; does removing your ~/.recently-used file fix the problem?
Yes, removing ~/.recently-used did fix the problem. Thanks.
*** This bug has been marked as a duplicate of 157723 ***