Bug 3867

Summary:	Bluetoothd lacks a sysv init/systemd startscript
Product:	Mageia	Reporter:	diego w <smiling.diego>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED FIXED	QA Contact:
Severity:	minor
Priority:	Normal	CC:	dmorganec, mageia
Version:	Cauldron
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:	bluez-4.96-3.mga2.src.rpm	CVE:
Status comment:
Attachments:	lsusb -v shortened to only show the bus with the bt module, just in case it might prove useful

Description diego w 2011-12-24 00:07:26 CET

Description of problem:
bluetooth applet can't find adapter

Version-Release number of selected component (if applicable):
cauldron current as of today 

How reproducible:
after boot-up, no special prerequisites

Steps to Reproduce:
hover mouse over bluetooth applet, it states bluetooth is off
click applet, it states no adapters found

works if running "bluetoothd" from a console

nothing like "/etc/init.d/bluetoothd start" or "systemctl status bluetoothd.service" works

the

Comment 1 diego w 2011-12-24 00:09:56 CET

Created attachment 1288 [details]
lsusb -v  shortened to only show the bus with the bt module, just in case it might prove useful

Comment 2 Manuel Hiebel 2011-12-24 12:07:40 CET

what do you get for error is you do systemctl status
bluetoothd.service ?

also according to bug 3655, comment 3 i works.

Comment 3 D Morgan 2011-12-24 12:16:49 CET

btw this is systemctl start bluetooth.service           ( not bluetoothd.service )

CC: (none) => dmorganec

Comment 4 D Morgan 2011-12-24 12:20:16 CET

btw now it should be enabled at install time

Comment 5 diego w 2011-12-24 12:53:40 CET

now im feeling more than stupid...

"systemctl start bluetooth.service" works

have there been any changes in the last few days?

if a few days ago I did the following:

"systemctl status blu<tab>" I got nothing

if however for example i entered:

"systemctl status cu<tab>" I got: "cups.path     cups.service  cups.socket"

today "systemctl status blu<tab>" suggests: "bluetooth.service  bluetooth.target"
there is still no traditional initscript for bluetooth, are there plans to add this for compatibility? or will /etc/init.d eventually go away?

now the second point: bluetoothd and cups both are no more starting on their own, is there an easy tweak? should i file a new bug?

in any case i think this bug can be closed now, as there is a script now.

Thanks to all! Wishing a merry Christmas!

Comment 6 Sander Lepik 2011-12-24 13:05:34 CET

See comment #4. It's now enabled when installing. You should be able to enable manually with this command: systemctl enable bluetooth.service

And you might want to read this little tutorial as well: https://www.linux.com/learn/tutorials/527639:managing-services-on-linux-with-systemd

CC: (none) => sander.lepik

Comment 7 Manuel Hiebel 2011-12-24 13:12:52 CET

(In reply to comment #5)
> in any case i think this bug can be closed now, as there is a script now.
> 
> Thanks to all! Wishing a merry Christmas!

Thanks for the bug, and merry Christmas you too :)

Comment 8 Manuel Hiebel 2011-12-24 14:25:06 CET

forget, and closing

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

Comment 9 diego w 2011-12-24 14:32:33 CET

(In reply to comment #6)
> See comment #4. It's now enabled when installing. You should be able to enable
> manually with this command: systemctl enable bluetooth.service
> 
> And you might want to read this little tutorial as well:
> https://www.linux.com/learn/tutorials/527639:managing-services-on-linux-with-systemd

thanks for the link, bookmarked for reading after the holidays :)