Bug 230728

Summary:	bluetooth service not enabled by yast2 bluetooth module
Product:	[openSUSE] openSUSE 10.2	Reporter:	Carsten Hoeger <choeger>
Component:	YaST2	Assignee:	Ladislav Slezák <lslezak>
Status:	RESOLVED DUPLICATE	QA Contact:	Jiri Srain <jsrain>
Severity:	Major
Priority:	P5 - None
Version:	Final
Target Milestone:	---
Hardware:	i686
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	YaST2.tar.bz2

Description Carsten Hoeger 2006-12-25 10:34:17 UTC

when configuring bluetooth with yast, the bluetooth service is started, but not enabled using insserv.

Comment 1 Cyril Hrubis 2006-12-27 12:34:13 UTC

Can you please attach y2logs. If you are in doubt please follow: http://en.opensuse.org/YaST.



Thanks!

Comment 2 Carsten Hoeger 2006-12-28 10:33:32 UTC

Created attachment 111118 [details]
YaST2.tar.bz2

Comment 3 Daniel Gollub 2007-01-08 15:58:29 UTC

The bluetooth service get started if there is a bluetooth device present/plugged in. So there is no need for insserv. If you have the problem that the hcid get not started while booting (but all other bluetooth services, like hidd, sdpd, ...), then it's likely another known issue: #228234

Or do you insist on a running hcid without any bluetooth device connected?

Comment 4 Carsten Hoeger 2007-01-08 16:49:32 UTC

Sorry, I don't know how that stuff works together.

Fact is, that Bluetooth is permanently switched on on my notebook (HP Compaq nx8220), but it did not work as long as I started yast and configured bluetooth. After I did that, the bluetooth service had been started. After a restart of the machine, the server did not run and Bluetooth did not work unless I start Yast and configure it again and so on and so on.

After insserving this service, it permanently works.
Might be, that this is the same bug as in 228234 because the effect is similar.

Comment 5 Daniel Gollub 2007-01-08 17:02:57 UTC

Do you have an on/off switch on your laptop for bluetooth?
Can you try if you turn off and on your bluetooth device if the bluetooth service get started. You can check the status of the bluetooth service with:

`rcbluetooth status` (as root)

After boot "hcid" status should be unkown (not displayed/empty).
After turning off/on the bluetooth device, the "hcid" status should be "running".

Please, let me know if this switching on/off helped. (Then it is a duplicate bug)

Comment 6 Carsten Hoeger 2007-01-10 07:59:45 UTC

Yes, it's exactly like that, so it's duplicate.

*** This bug has been marked as a duplicate of bug 228234 ***