https://bugzilla.novell.com/show_bug.cgi?id=735997
https://bugzilla.novell.com/show_bug.cgi?id=735997#c13
--- Comment #13 from Max Lin
OK, i will send output of lsusb after unblock my BT killswitch soon. but what do you mean with BT killswitch? do you mean the physical key that i push it to turn Bluetooth on or off? if yes, now in kde when i push it, it does not work at all (it's light remain red) so i should go to genome and then push it and then in gnome turn on Bluetooth so after logging gnome off go back to kde and now the Bluetooth is on (physical key light is blue now). do you want me to do these?
ah..no, I just hope you unblock your bluetooth via rfkill before get output of lsusb :) sorry for confusing!
and how can i add hp-wmi to blacklist?
added "blacklist hp-wmi" to /etc/modprobe.d/50-blacklist.conf, and reboot then check whether the issue gone, if no, revert it back, it's just to check hp-wmi have no caused side effect. If this issue is urgent for you, I only can suggests you run "rfkill unblock all" after log in, due to we are not sure what is the exact problem cause that always auto-blocked bluetooth. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.