GNOME Bugzilla – Bug 170894
crash after dbus/hal restarts
Last modified: 2005-08-03 19:09:20 UTC
Distribution: Debian 3.1 Package: gnome-volume-manager Severity: normal Version: GNOME2.10.0 1.2.x Gnome-Distributor: Ubuntu Synopsis: crash under unknown circumstances (unattended operation) Bugzilla-Product: gnome-volume-manager Bugzilla-Component: general Bugzilla-Version: 1.2.x BugBuddy-GnomeVersion: 2.0 (2.10.0) Description: Description of the crash: gnome-volume-manager just crashed, can't say anything about it as there is an "Error" window but i can't read it's contents - it's just labeled "Error" and empty when i activate it Steps to reproduce the crash: 1. unknown Expected Results: well... it shouldn't "just" crash, should it? How often does this happen? this has happened before, but doesn't occur regularly. situation was like- wise like now. totally unexpected. Additional Information: maybe its triggered by one of my hdds being written on while its almost full? it's not the system partition, though. sorry that i can't come up with any piece of useful information, but there was really nothing special i've been doing, in fact i get off to the coffee machine and when i came back that 'crash' was all up there. i didn't even do anything special. a couple of minutes ago i ran synaptic and upgraded some parts of my current hoary desktop (i hope i don't contribute to giving ubuntu users a bad reputation). Torsmo (lightweight system monitor), mozilla-firefox, Grip, aMule, bittornado (gui), X-Chat amd the Gnome System Monitor Panel are open, but the only application doing some cpu usage and network traffic is a "niced" aMule in the background - X-Chat and bittorrent are connected though, but there hasn't been anything going. Debugging Information: Backtrace was generated from '/usr/bin/gnome-volume-manager' (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) [Thread debugging using libthread_db enabled] [New Thread -1221834016 (LWP 11580)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (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 57048
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-03-19 08:54 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gnome-volume-manager". 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 f1losof@despammed.com. 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.
*** Bug 170904 has been marked as a duplicate of this bug. ***
The duplicate said this happened while applying updates...
*** Bug 170934 has been marked as a duplicate of this bug. ***
*** Bug 170935 has been marked as a duplicate of this bug. ***
*** Bug 170976 has been marked as a duplicate of this bug. ***
it might have happened due to the updates, with a little bit of delay. it's very much possible. again, sorry for my unprecise report and the inconvenience it caused. if you have any problems, or questions just leave them here and i will try to answer them as good as possible. after all i learned where my system logs are.
*** Bug 171046 has been marked as a duplicate of this bug. ***
*** Bug 171199 has been marked as a duplicate of this bug. ***
*** Bug 171286 has been marked as a duplicate of this bug. ***
*** Bug 171353 has been marked as a duplicate of this bug. ***
*** Bug 171522 has been marked as a duplicate of this bug. ***
*** Bug 171576 has been marked as a duplicate of this bug. ***
this just happened again, definately during upgrade this time, just the moment it was applied
This has happened to me several times during dist-upgrades when hal has been upgraded. I got this backtrace, which is different to the others I've seen in dupes, but the circumstances seem the same. 0xb7db0f9e in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 57698
*** Bug 172644 has been marked as a duplicate of this bug. ***
*** Bug 172647 has been marked as a duplicate of this bug. ***
Ubuntu people, _please_ look into fixing this. Look at all these dupes!
*** Bug 172649 has been marked as a duplicate of this bug. ***
*** Bug 172692 has been marked as a duplicate of this bug. ***
Also happened to me while installing recent updates (not to the gnome-volume-manager) in update-manager; I'm not sure at what point as I was afk. Stacktrace was like last dupe.
*** Bug 172801 has been marked as a duplicate of this bug. ***
*** Bug 172831 has been marked as a duplicate of this bug. ***
*** Bug 172850 has been marked as a duplicate of this bug. ***
Sebastien: As pointed out by Robert, all these dupes were using Ubuntu so it looks Ubuntu-specific. Is there an Ubuntu bug for this we should point people at for more info or anything like that? Thanks.
Ccing the g-v-m package maintainer
bugzilla.ubuntu.com does not have such a bug (maybe somebody who can reproduce this should file one). The only situation where I saw g-v-m crashing was during or shortly after an upgrade of dbus-1. On a package upgrade, dbus-1 is restarted and g-v-m loses its connection. The ubuntu and debian version of g-v-m has a patch which attempts to reconnect to dbus-1 (see #153673), but it still seems to be imperfect.
Martin: Does it matter if the bug is in your Bugzilla? All of these reports are from Ubuntu users! Look at all those dupes! Maybe the bug is in your restart patch? I don't see this on other platforms.
Martin is replying to "Is there an Ubuntu bug for this we should point people" ... no need to get nervous imho
> Martin: Does it matter if the bug is in your Bugzilla? All of these reports are > from Ubuntu users! Look at all those dupes! The bug not being in our bz means that I wasn't aware of it. I don't question that it is an ubuntu-specific one, so if you don't want to see it here, just close it (and ask the reporters to use bugzilla.ubuntu.com instead). > Maybe the bug is in your restart patch? Yes, that's what I wanted to say. have a nice day, Martin
*** Bug 172983 has been marked as a duplicate of this bug. ***
*** Bug 173033 has been marked as a duplicate of this bug. ***
*** Bug 300079 has been marked as a duplicate of this bug. ***
*** Bug 173133 has been marked as a duplicate of this bug. ***
*** Bug 173188 has been marked as a duplicate of this bug. ***
*** Bug 300116 has been marked as a duplicate of this bug. ***
*** Bug 300123 has been marked as a duplicate of this bug. ***
*** Bug 300189 has been marked as a duplicate of this bug. ***
*** Bug 300207 has been marked as a duplicate of this bug. ***
*** Bug 300393 has been marked as a duplicate of this bug. ***
*** Bug 300603 has been marked as a duplicate of this bug. ***
*** Bug 302573 has been marked as a duplicate of this bug. ***
Created attachment 46393 [details] [review] attempt to reconnect to dbus/hal after dbus exit After the dbus connection exits, don't just crash, but attempt to reconnect to dbus/hal 100 times (timeout 0.5 seconds each). This usually happens after a system upgrade when new hal and/or dbus versions are installed and restarted.
Robert, do you consider adopting this upstream? Robert, please change the summary to "crashes shortly after dbus restart" (I can't, crappy bugzilla...)
Martin: you should be able to update bugs now. Let me know if you have troubles.
so here's what I have found in my rigorous testing of CVS... (prior to committing any patches attached to this bug report) - if you stop/restart dbus while g-v-m is running, g-v-m simply exits cleanly. there's no crash - if you stop hald while g-v-m is running, nothing happens. plugging in new devices does nothing because g-v-m isn't getting events, etc - if you restart hald while g-v-m is running, things continue to work. plugging in new devices will magically do the right thing. closing since this backtrace doesn't happen with unpatched CVS
*** Bug 153673 has been marked as a duplicate of this bug. ***