Bug 189125 - kbluetooth4 (or KDE bluetooth framework) cannot memorize the state of the obex server
Summary: kbluetooth4 (or KDE bluetooth framework) cannot memorize the state of the obe...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kde-bluetooth
Classification: Miscellaneous
Component: kbluetoothd (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Unknown
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-08 14:46 UTC by Tamás Németh
Modified: 2013-02-11 20:30 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Tamás Németh 2009-04-08 14:46:14 UTC 
Version:            (using KDE 4.2.2)
OS:                Linux
Installed from:    SuSE RPMs

I have a bluetooth systray icon in KDE, which appears, when I turn on bluetooth, and disappears when I turn it off. Right clicking this icon makes it possible to disable the obex server on my host (I assume) by settings -> obex server. However, when I turn bluetooth off and on again, the obex server will be enabled, regardless of its previous state (and my intention). Shouldn't it remember its previous state?
Comment 1 Tamás Németh 2009-04-08 14:48:38 UTC 
BTW, does KDE4 have a builtin bluetooth clien/browser, like KDE3 in konqueror, or do I have to push the files from my phone to my computer, instead of pulling them controlled by the machine? If not, will it have one? In which version?
Comment 2 H.H. 2010-02-01 22:54:44 UTC 
kde4 still has no client. see bug 193241
Comment 3 Tom Albers 2013-02-11 20:27:01 UTC 
Bluetooth support has been replaced by "BlueDevil" and the old code is no
longer maintained. If you still have an issue with Bluetooth support in a
recent KDE version, such as KDE 4.9.5 or 4.10, please report a new bug.

Also, if this is a feature request that has not yet been implemented in
BlueDevil, please add a comment.