GNOME Bugzilla – Bug 316880
crash just after Gnome upgrade
Last modified: 2006-04-19 11:46:15 UTC
Distribution: Debian testing/unstable Package: totem Severity: normal Version: GNOME2.10.2 1.0.4 Gnome-Distributor: Debian Synopsis: totem doesn't initialize Bugzilla-Product: totem Bugzilla-Component: general Bugzilla-Version: 1.0.4 BugBuddy-GnomeVersion: 2.0 (2.10.1) Description: Description of the crash: Just I didn't get to initializa the totem program after a update.... Steps to reproduce the crash: 1. just I tried to open the program 2. 3. Expected Results: How often does this happen? Additional Information: 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) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1223407936 (LWP 9917)] [New Thread -1226302544 (LWP 9918)] (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) 0xb7391201 in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 63125
Thread 1 (Thread -1223407936 (LWP 9917))
------- Bug moved to this database by unknown@gnome.bugs 2005-09-21 21:57 UTC ------- Unknown version 1.0.4 in product totem. Setting version to "1.0.x". The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@gnome.bugs. Previous reporter was altamir@emc.ufsc.br.
This is actually a crash in gnome-vfs. gnome_vfs_get_volume_monitor() shouldn't really crash...
*** Bug 316890 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of 316890 ***
Sorry, duplicate snafu.
This looks like what happens when you upgrade gnome-vfs from one major release to another and don't restart gnome-vfs-daemon during the upgrade.
*** Bug 317818 has been marked as a duplicate of this bug. ***
*** Bug 320816 has been marked as a duplicate of this bug. ***
seems to happen only once after upgrade Comment #4 from Martin Wehner (nautilus developer, points: 18) 2006-04-06 19:16 UTC [reply] This is caused by a known binary incompatibility if you run nautilus against a gnome-vfs-daemon process which is a leftover from an older version.
*** Bug 316140 has been marked as a duplicate of this bug. ***
*** Bug 317101 has been marked as a duplicate of this bug. ***
*** Bug 335356 has been marked as a duplicate of this bug. ***
*** Bug 338957 has been marked as a duplicate of this bug. ***
The packaging system must restart the gnome-vfs-daemon process if I am not mistaken Thanks for the bug report. If the affected third party application has a bug tracking system, and you have access to it, you should investigate whether a bug for the reported issue is already filed in this system. If it is not yet filed, please file it, attaching any relevant files attached to the original GNOME bug report that may help the authors of that application to fix the bug. Also ensure that a both bug reports contain a link to each other.