GNOME Bugzilla – Bug 303431
Totem always Crashes when starting
Last modified: 2005-11-23 19:22:47 UTC
Distribution: Debian 3.1 Package: totem Severity: normal Version: GNOME2.10.0 1.0.1 Gnome-Distributor: Ubuntu Synopsis: Totem always Crashes when starting Bugzilla-Product: totem Bugzilla-Component: general Bugzilla-Version: 1.0.1 BugBuddy-GnomeVersion: 2.0 (2.10.0) Description: Description of the crash: Immediately upon start Totem "Quits Unexpectedly" with now useful error message. Steps to reproduce the crash: 1. Start Totem 2. 3. Expected Results: How often does this happen? 100% Additional Information: I've tried both Totem-Xine and Totem-Gstreamer and they both do the same thing. Rhythmbox and mplayer work fine. Debugging Information: Backtrace was generated from '/usr/bin/totem' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/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) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1222445440 (LWP 9900)] (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) 0xffffe410 in __kernel_vsyscall ()
+ Trace 59334
Thread 1 (Thread -1222445440 (LWP 9900))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-05-08 01:58 UTC ------- Unknown version 1.0.1 in product totem. Setting version to "1.0.x".
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?
This is an automated update. Your bug has been in NEEDINFO state for more than 3 months. Please reopen the bug if the problem is still current with recent versions of Totem and that you can provide the information asked for. If your bug has been closed wrongly, feel free to reopen it.