Bug 106107

Summary: suseplugger should handle bluetooth-requests
Product: [openSUSE] SUSE LINUX 10.0 Reporter: Stefan Behlert <behlert>
Component: HotplugAssignee: Stephan Kulow <coolo>
Status: VERIFIED FIXED QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None    
Version: Beta 2   
Target Milestone: ---   
Hardware: Other   
OS: All   
Whiteboard:
Found By: Development Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Stefan Behlert 2005-08-22 10:31:48 UTC
in 9.3 we had the following functionality: 
inserting a Bluetooth-USB-dongle, a window popped up telling the user that new 
hardware was found, and if it should be configured. Accepting this, the 
yast-module for Bluetooth was started. 
With 10.0 beta2 this is not working. 
I was told that hal has to report this to the suseplugger, which should ask 
the question then.please make this happen :) 
Bluetooth-USB-dongles are available from the Mobile-Devices-Team
Comment 1 Marcel Hilzinger 2005-08-23 10:01:40 UTC
Also the KDE Bluetooth Tools should be started then (as it was default for 
9.3) Because otherwise you won't be able to send files via Bluetooth from any 
device to the PC. 
 
Btw. Bluetooth is working very fine in 10.0 even the remote control of my SE 
k700i works out of the box! 
Comment 2 Stephan Kulow 2005-08-23 11:17:53 UTC
the problem here is the timing. Starting kbluetoothd doesn't make sense before  
the yast module is done, so I need to find a way to figure this. But for now 
the yast2 module is at least started 
Comment 3 Stephan Kulow 2005-08-24 11:14:39 UTC
it works for me and I'll prepare a mbuild to be sure you have the right 
version to test on your computer too 
Comment 4 Marcel Hilzinger 2005-08-25 12:00:58 UTC
Seems not to be fixed in beta3 (at least it doesn't work for me :-( 
Comment 5 Stephan Kulow 2005-08-25 12:19:18 UTC
Stefan: portia-coolo-5 is a mbuild for you to test. 
Comment 6 Stefan Behlert 2005-08-25 15:59:14 UTC
ok, with that version the 'new hardware'-window pops up. And kbluetoothd is 
started.