On 10-10-07 01:32 AM, Jeff Lane wrote: > Public bug reported: > > Binary package hint: dbus > > After periods of heavy load, dbus goes off into the weeds and just > refuses to come back and work. This requires a reboot to fix and since > so many things rely on dbus, many things just stop working until the > system is rebooted. > > I've noticed this can happen after a few days of uptime with moderate > system use, or after a lot of heavy use. For example, today, I've been > using usb-creator-gtk to make a lot of usb keys from Maverick ISOs for > test purposes. After a while I started getting dbus timeout error > messages whenever I'd try to make a new bootable usb key. After a > while, it happened every single time I tried doing anything via usb- > creator-gtk. If I was in the process of actually putting the ISO onto > the usb key, I'd just get a generic message saying that the action > failed. If I tried erasing the usb key prior to starting the ISO > transfer, I'd get a popup explaining that there was a dbus message > timeout error. > > I also got that by running u1sdtool -s, which also relies on dbus for > communications. So, the point is, once dbus goes off into the weeds, > everything that relies on dbus stops working right. And trying to just > restart dbus is ... well, and adventure in itself. > > So the only remedy I can find so far is a system reboot which is > disappointing to say the least. > > I've noticed this happens a LOT now that I've upgraded to Maverick. I > don't recall them happening that frequently in Lucid, though I DID > experience the dbus issues there as well. It just seems more prevalent > in Maverick, and happens especially after periods of heavy usage or > several days of uptime. Hi,
I haven't seen this myself. Can you prove that it is dbus that is non-responsive, rather than whatever is receiving the messages, as it is my belief that both would give the same symptoms. Something like an strace of the dbus-daemon process during the interaction, (ensuring you get the right one for the action you are doing) would help to diagnose this. Also, how long does it take you to get the timeout messages? If they are particularly quick then it would indicate some other bug. Thanks, James -- dbus periodically becomes unresponsive and a reboot is required to regain system functionality https://bugs.launchpad.net/bugs/656134 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
