Description of problem: after installation of mageia i first open a kde session then bluedevil indicates that bluetooth is activated but when i watch my bluetooth dongle then it does not blink. blinking dongle indicates "it is running" if i search with bluedevil a discoverable smartphone then bluedevil does not discover the smartphone if i try to unactivate bluetooth with the option "unactivated bluetooth" then bledevil does not switch to "unactivate" state if i try to restart bluetooth then no success : dongle does not blink
i updated mageia 3 then no more success
mageia 3 a3 with all updates pb still there but for every steps the contrary of mageia 3 a2 - when opening a kde session the dongle bluettooth is activated (dongle is blinking) - bluedevil systray icon indicates"bluetooth unactivated" - if i click on "activate bluetooth" then bluedevil stays "unactivated"
The dongle is recognized if I plug it at the start of Mageia, then there's an issue with the pin number. 1) add a new device (phone) 2) The "Connection Wizard Bluetooth Device" window opens, you can read "current analysis", my phone appear in the list, I select it, then I click Next. 3) Another window opens (without displaying Pin number), a request for pairing appears on my phone, then it request a pin number? With the same manipulation on Mageia 1, a pin number is given for the phone, then pairing is successful, and it's possible to send and receive files.
CC: (none) => jaidesantennes
(In reply to R Blade from comment #3) > The dongle is recognized if I plug it at the start of Mageia, then there's > an issue with the pin number. Your issue seems different that that of the original report, please open a separate bug if the issue still persits. @episteme: Does this bug persist with Mageia 4? What is the output of rfkill list all lspcidrake -v | grep -i -e blue -e bt
CC: (none) => doktor5000
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution. Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Closing as OLD.
Status: NEW => RESOLVEDCC: (none) => nicResolution: (none) => OLD