GNOME Bugzilla – Bug 305154
crash during unbuntu boot run level 5
Last modified: 2005-05-23 09:18:40 UTC
Distribution: Debian 3.1 Package: nautilus Severity: normal Version: GNOME2.10.0 2.10.0 Gnome-Distributor: Ubuntu Synopsis: crash during unbuntu boot run level 5 Bugzilla-Product: nautilus Bugzilla-Component: general Bugzilla-Version: 2.10.0 BugBuddy-GnomeVersion: 2.0 (2.10.0) Description: Description of the crash: Steps to reproduce the crash: 1. 2. 3. Expected Results: How often does this happen? Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/nautilus' (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) [Thread debugging using libthread_db enabled] [New Thread -1224591552 (LWP 7299)] [New Thread -1226273872 (LWP 7335)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 60034
Thread 2 (Thread -1226273872 (LWP 7335))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-05-23 01:12 UTC ------- Unknown version 2.10.0 in product nautilus. Setting version to "2.10.x". 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 wbrown@colorfulsoftware.com.
the crash is due to totem-gstreamer. Does it crash while trying to get the properties of some files? Can you get a debug backtrace (http://live.gnome.org/GettingTraces)? If you use a i386 hoary installation you can find debug packages here: http://people.ubuntu.com/~seb128/hoary_dbgdebs/totem/totem-gstreamer_1.0.1-0ubuntu1_i386.deb http://people.ubuntu.com/~seb128/hoary_dbgdebs/gstreamer/libgstreamer0.8-0_0.8.9-1ubuntu4_i386.deb You can install these files with "sudo dpkg -i *.deb". libglib2.0-0-dbg from the archive is also useful to get informations on this crash. (I'm marking this bug as duplicate of bug #305112) *** This bug has been marked as a duplicate of 305112 ***