GNOME Bugzilla – Bug 153699
totem crashes when starting
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Slackware Slackware 10.0.0 Package: totem Severity: normal Version: GNOME2.6.2 0.99.12 Gnome-Distributor: GNOME.Org Synopsis: totem crashes when starting Bugzilla-Product: totem Bugzilla-Component: general Bugzilla-Version: 0.99.12 BugBuddy-GnomeVersion: 2.0 (2.6.1.1) Description: Description of the crash:When I select totem from the menu, it starts, and then most of the time immediately crashes and tries to restart, in which it crashes again. Usually when I start it by the command line though, this doesn't happen. Steps to reproduce the crash: 1. Select totem from the menu 2. 3. Expected Results: To immediately crash How often does this happen? Every time it is opened by the menu, sometimes fromt the command line, but that is after it has been crashed by selecting it from the menu. Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/totem' (no debugging symbols found)...Using host libthread_db library "/lib/libthread_db.so.1". (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)...(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)...0x40b584da in waitpid () from /lib/libpthread.so.0
+ Trace 50463
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-09-25 02:08 ------- Unknown version 0.99.12 in product totem. Setting version to "unspecified". Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "totem". Setting to default milestone for this product, '---' 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 compynerd386@sbcglobal.net. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
*** This bug has been marked as a duplicate of 138830 ***