*** This bug is a duplicate of bug 53984 ***
** This bug has been marked a duplicate of bug 53984
hal cannot obtain list of devices
--
gpm refuses to suspend to ram after some time
https://launchpad.net/bugs/49442
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
Are you still experiencing these issues with any of the latest updates
or any of the latest stable releases?
** Changed in: hal (Ubuntu)
Status: Unconfirmed = Needs Info
--
gpm refuses to suspend to ram after some time
https://launchpad.net/bugs/49442
--
desktop-bugs mailing list
So do you have a fix? Do you still have this problem?
--
gpm refuses to suspend to ram after some time
https://launchpad.net/bugs/49442
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Yes, this problem is still there. It's tricky since it only occurs on
one machine (all other Dapper machines work fine, but they have
different hardware too, so it may be a driver issue somewhere which
triggers a bug in gpm). In any case, I'm attaching a gpm log file in
case that helps the
--
gpm refuses to suspend to ram after some time
https://launchpad.net/bugs/49442
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
It just happened again. I re-opened the lid and typed lshal, which gave
lshal: Couldn't obtain list of devices
(typed from memory, might be slightly different).
Now for the weird part: I then ran 'lshal -m', ctrl-c'ed it, 'lshal' again (no
change), checked that lshald and dbus are running
Pinned down to a problem with hal not being able to obtain the device
list.
** Changed in: gnome-power-manager (Ubuntu)
Sourcepackagename: gnome-power-manager = hal
--
gpm refuses to suspend to ram after some time
https://launchpad.net/bugs/49442
--
desktop-bugs mailing list
