I don't know if this is a different bug, but I have searched high and low and cannot find a similar bug. This one is the closest to the problems I am having. I have Hardy 64bit (haven't tested 32bit) with a Gateway MX6433 (There are many other similar laptops from Gateway 6000 series) which has a Turion64 single core cpu and and I upgraded to Hardy from Gutsy. I use the -rt kernel for multimedia editing. I tried to fix the problem using the notes above, but I run in KDE and kdm, not Gnome and my rc2.d links are all correct as noted above. Nothing changes it. Here is the problem and here is the dmesg log section that identifies what happened: [ 4233.202422] dbus-daemon[5257]: segfault at 7fe705dd18e0 rip 7fe704eedae2 rsp 7fff0daa4778 error 4 I will attach a full log.
I have no idea what error 4 is, but this seems to happen randomly whether I am at my machine or not. When dbus fails networkmanger and the battery monitor fail to report properly in KDE and it says that network manager is not running and the battery is not present. It is this second notification that alerts me when dbus crashes since network manager doesn't tell me it isn't running unless I go to use it. This doesn't seem to interrupt my use of the internet or local LAN however so it isn't a total show stopper, but it does prevent me from using my DVD writer (which also doesn't burn properly since Hardy either). DBus worked fine in Gutsy so this is definitely a regression of some kind or maybe a conflict with the new ATI drivers. I haven't had a chance to check this. ** Attachment added: "dmesg.log" http://launchpadlibrarian.net/14661507/dmesg.log -- Failed to initalize HAL. https://bugs.launchpad.net/bugs/25931 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a direct subscriber. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
