https://bugzilla.novell.com/show_bug.cgi?id=735997 https://bugzilla.novell.com/show_bug.cgi?id=735997#c1 Max Lin changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |mlin@suse.com InfoProvider| |golstar@gmail.com --- Comment #1 from Max Lin 2011-12-12 06:06:23 UTC --- I saw your bluetooth is blocked in your rfkill list in forum thread, iirc bluedevil shound not handle rfkill itself, can you run following command and attached result here? 1) rfkill unblock all 2) rfkill list -> guarantee all rfkill not block 3) try to turn bluetooth on/off via bluetooth icon in the tray if you can not turn it on, please do 1) rfkill list -> attached result here 2) hciconfig -a dev -> attached result here 3) hciconfig hciX up -> X as what yours created bluetooth killswitch, normal should be hci0, you can check it from above command, and looks what message output when you run this command and whether turn your bluetooth on -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=735997 https://bugzilla.novell.com/show_bug.cgi?id=735997#c3 Max Lin changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |golstar@gmail.com --- Comment #3 from Max Lin 2011-12-14 16:14:54 UTC --- (In reply to comment #2)

ok, i do "rfkill unblock all" and "rfkill list -> guarantee all rfkill not block" and then "try to turn bluetooth on/off via bluetooth icon in the tray" and my bluetooth successfully turned on. but i restarted my laptop to see if it work correctly always and unfortunately i saw that bluetooth does not work. (in

Well, the issue appeared after you reboot laptop. Can you run "rfkill unblock all" and guarantee no one blocked, then reboot your laptop, after reboot done, please run "rfkill list" and have a look does all killswitches(I guess you have 2 killswitches there, hp-bluetooth and hci0) of bluetooth are unblock?

fact now the bluetooth light of laptop is on but there is not any bluetooth icon in tray. before doing your advice even bluetooth light of laptop didnot turned on) and what do you mean with following expresion: "rfkill list -> attached result here" is it a command? if it is a command, it doesnot work.

I meant can you paste the result of "rfkill list" at here or let it be a text file as attachment and attached it here :) -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=735997 https://bugzilla.novell.com/show_bug.cgi?id=735997#c5 --- Comment #5 from Max Lin 2011-12-19 07:30:36 UTC --- Well, as you saw, your bluetooth killswitch(hci0) set blocked after reboot, is it always blocked after rebooted? if so, I think it's driver issue or ACPI problem probably, not related to KDE, due to bluedevil didn't change the state of killswitch even it have no functional do that, thus it don't know what states of rfkill no more when you turn on/off bluetooth via tray icon. BTW, but there has one thing is weird from your explained, if bluedevil shows "No adapters found" that means you have no org.bluez dbus service running(also meant as no device node found), however set hci0 killswitch blocked should not caused org.bluez disappear AFAIK, that's what the behavior in my machine at least. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=735997 https://bugzilla.novell.com/show_bug.cgi?id=735997#c7 --- Comment #7 from Ali H Zadeh 2011-12-21 20:42:30 UTC --- ok, how can i solve that? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=735997 https://bugzilla.novell.com/show_bug.cgi?id=735997#c9 Ali H Zadeh changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kde-maintainers@suse.de |golstar@gmail.com --- Comment #9 from Ali H Zadeh 2011-12-24 20:11:59 UTC --- Created an attachment (id=468906) --> (http://bugzilla.novell.com/attachment.cgi?id=468906) dmesg output dmesg output -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=735997 https://bugzilla.novell.com/show_bug.cgi?id=735997#c11 --- Comment #11 from Max Lin 2011-12-26 03:08:22 UTC --- Hi Ali, Can you get output of lsusb after unblock your BT killswitch? because I can not saw your bluetooth device information in lsusb, I guess it disappear due to it's blocked :) BTW, did you try added hp-wmi to blacklist like as I said in comment 8? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=735997 https://bugzilla.novell.com/show_bug.cgi?id=735997#c13 --- Comment #13 from Max Lin 2011-12-26 09:18:35 UTC --- (In reply to comment #12)

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.

https://bugzilla.novell.com/show_bug.cgi?id=735997 https://bugzilla.novell.com/show_bug.cgi?id=735997#c15 Ali H Zadeh changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #468907|0 |1 is obsolete| | --- Comment #15 from Ali H Zadeh 2011-12-26 16:17:30 UTC --- Created an attachment (id=468957) --> (http://bugzilla.novell.com/attachment.cgi?id=468957) lsusb -vv resault after rfkill unblock all -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=735997 https://bugzilla.novell.com/show_bug.cgi?id=735997#c17 Christian Trippe changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ctrippe@opensuse.org AssignedTo|golstar@gmail.com |kde-maintainers@suse.de --- Comment #17 from Christian Trippe 2012-01-02 19:55:56 UTC --- You have assigned the bug to yourself. This normally means you are working on a solution (and nobody else needs to do so). I guess this was an accident? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=735997 https://bugzilla.novell.com/show_bug.cgi?id=735997#c19 --- Comment #19 from Max Lin 2012-01-04 06:49:30 UTC --- What is the status if you add hp_wmi to blacklist? it can be clarify does it related to hp_wmi. If that not helpful to solve your problem, then I guess it's related to driver(03f0:171d seems is BCM2045) or ACPI, because your bluetooth seems always blocked after you booted. If so, something is beyond my knowledge and I have no that chip around. I only can suggests run "rfkill unblock all" yourself after log in. Might other guys have good ideas for you, unsure... BTW, @Christian meant you assigned this bug to yourself(you can saw that in modified history), that might be an accident, because that means you want to fix this bug *yourself*, and except who are in the CC list that no one can got mail what new comment added in this thread :) -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=735997 https://bugzilla.novell.com/show_bug.cgi?id=735997#c21 Ali H Zadeh changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #21 from Ali H Zadeh 2012-01-11 18:12:26 UTC --- the problem has been solved with using "blacklist hp_wmi". thanks all. -- 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.