Difference between revisions of "User:Andy/Kubuntu on ThinkPad R52"
(workaround for kbluetoothd) |
(→Ongoing problems: Hibernate) |
||
| Line 1: | Line 1: | ||
==Ongoing problems== | ==Ongoing problems== | ||
| + | ===s2d, hibernate, whatever=== | ||
| + | Right clicking the power meter and then selecting '''Hibernate''' does seem to hibernate, but then pressing the power button starts a boot, does some swusp thing and then stalls. I can't do anything then except hold the power button until it turns off, then do a normal boot. | ||
==Workarounds== | ==Workarounds== | ||
Revision as of 22:28, 6 March 2006
Contents
Ongoing problems
s2d, hibernate, whatever
Right clicking the power meter and then selecting Hibernate does seem to hibernate, but then pressing the power button starts a boot, does some swusp thing and then stalls. I can't do anything then except hold the power button until it turns off, then do a normal boot.
Workarounds
kbluetoothd
I get the following every few seconds in ~/.xsession-errors while bluetooth is disabled:
kbluetoothd: Bind failed: No such device kbluetoothd: HciSocket::open() kbluetoothd: Bind failed: No such device kbluetoothd: HciSocket::open()
If I enable bluetooth (Fn+F5) then the problem goes away (and bluetooth seems to work, though I can't really tell as I have no other bluetooth devices!), but this will drain my battery.
How do I tell KDE to not bother trying to use bluetooth until it's turned on?
http://ubuntuforums.org/archive/index.php/t-76759.html advises editing ~/.kde/share/config/kbluetoothdrc to read AutoStart=false and then starting kbluetoothd manually when needed.
It would be nice if it could start automatically when bluetooth is enabled and die when it's not, though.
