Bug 11437

Summary:	Bluetooth not started automatically in MGA4 alpha 3
Product:	Mageia	Reporter:	Philippe Leblanc <philippel>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	mageia
Version:	Cauldron
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	gnome-bluetooth-3.10.0-2.mga4.src.rpm	CVE:
Status comment:

Description Philippe Leblanc 2013-10-10 22:38:12 CEST

In mageia 3 using the gnome environment, it use to be that bluetooth would be started automatically upon boot. It would then automatically pick up my bt keyboard and I could use it to login normally. Currently in cauldron, bluetooth isn't started automatically and I don't see any settings to change that. Luckily my computer is a laptop and I can use its builtin keyboard to login and enable the bt connection to the wireless keyboard manually.

Not sure where exactly does this bug originate from, but bluetooth behavior from Mageia 3 seems preferable and more convenient. I can't say if this is a gnome bug or something related to bluetooth service. Could this be a problem relating to the systemd migration?


Reproducible: 

Steps to Reproduce:

Comment 1 Manuel Hiebel 2013-10-12 22:41:53 CEST

no ideas, colin ?

CC: (none) => mageia

Comment 2 Philippe Leblanc 2013-10-14 23:04:10 CEST

Definitely having some bigger problems with bluetooth. I'm having trouble pairing my keyboard altogether. When I go through the bluetooth pairing tool in gnome, the keyboard keeps appearing and dissappearing from the list of bluetooth devices in range. And when it finally appears long enough for me to pair it, it keeps resulting in setup failed. I can't figure out why it's not reliably pairing. I don't believe it's the keyboard since it pairs just fine when booted into my windows partition on the same machine.

Comment 3 Samuel Verschelde 2015-05-17 01:24:20 CEST

Closing as OLD. If you still have issues in Mageia 4 and/or Mageia 5 (would be nice to know for both), please reopen.

Status: NEW => RESOLVED
Resolution: (none) => OLD