Bug 72859 - DCOP error if click on bluetooth services in KDE Control Center
Summary: DCOP error if click on bluetooth services in KDE Control Center
Status: RESOLVED FIXED
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: KDE (show other bugs)
Version: Beta 3
Hardware: Other SUSE Other
: P5 - None : Critical (vote)
Target Milestone: ---
Assignee: Stephan Binner
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-03-15 16:26 UTC by Danny Al-Gaaf
Modified: 2006-02-09 15:59 UTC (History)
1 user (show)

See Also:
Found By: Development
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Danny Al-Gaaf 2005-03-15 16:26:30 UTC 
This is a bug on a SUSE 9.3Beta4. 

If i click in KDE Control Center on: 'Internet & Network' --> 'Bluetooth 
Service' I get a errormessage "DCOP error while calling services()"
Comment 1 Danny Al-Gaaf 2005-03-22 22:16:49 UTC 
This is also a bug in RC1 but with one more dialog. Don't know if there is no 
errormessage if I had a bluetooth device didn't test it.
Comment 2 Danny Al-Gaaf 2005-04-01 18:25:41 UTC 
Same problem with 9.3final. First a dialog with message "The KDE Bluetooth 
Daemon (kbluetoothd) is needed and was started" and then "DCOP error ... "
Comment 3 Stephan Kulow 2005-08-16 12:01:06 UTC 
can you please retry with beta2? I updated the package to the current SVN, but 
have neither the experience nor the hardware to test. This package really 
should be handled by mobility team I think
Comment 4 Danny Al-Gaaf 2005-08-20 13:29:39 UTC 
same problem with beta2 (the behavior is: first dialog from #3 and if you click 
on OK you get errordialog/message from #1)
Comment 5 Danny Al-Gaaf 2005-11-16 20:11:07 UTC 
This is already present in 10.1 Alpha 3
Comment 6 Stephan Binner 2006-02-03 12:35:49 UTC 
Cannot reproduce with 10.1 Beta 3. I get a message box "The KDE bluetooth Daemon (kbluetoothd) is needed and was started." then the configuration module appears.
Comment 7 Danny Al-Gaaf 2006-02-03 15:11:44 UTC 
If you click in this (new) dialog on OK you get the same error dialog (DCOP error when calling services()) --> reopen the bug
Comment 8 Stephan Binner 2006-02-03 15:30:35 UTC 
Sigh, does kblueboothd start for you then (icon in system tray)? If not please try to start it from console.
Comment 9 Danny Al-Gaaf 2006-02-03 19:02:16 UTC 
Yes kblueboothd started and is available in system tray. If you click on the icon you get a open konqueror window with bluetooth:/ and a localhost service. And a message displayed: "No working Bluetooth adapter found. Only local services will be displayed"
Comment 10 Danny Al-Gaaf 2006-02-03 19:07:45 UTC 
And what I forgot: If kblueboothd is started and I click again on "Bluetooth Services" in kcontrol I get again the DCOP error message.
Comment 11 Stephan Kulow 2006-02-05 11:46:02 UTC 
I can reproduce it too, btw
Comment 12 Stephan Binner 2006-02-06 15:08:05 UTC 
Can you try the package in klempnerei-stbinner-100? It always shows the "kdebluetoothd started" messagebox to avoid the race that the configuration module queries before kdebluetoothd detected the devices and has a rephrased error message for the case that there is no Bluetooth device available.
Comment 13 Stephan Kulow 2006-02-09 15:46:32 UTC 
fixes the bug for me.
Comment 14 Stephan Binner 2006-02-09 15:59:14 UTC 
Submitted new packaged.