Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
bluetooth on kde
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
The_Document
Apprentice
Apprentice


Joined: 03 Feb 2018
Posts: 272

PostPosted: Thu Dec 27, 2018 5:07 am    Post subject: bluetooth on kde Reply with quote

doesent connect to paired devices unlike on other distros.

is this a kde issue?
Back to top
View user's profile Send private message
fedeliallalinea
Bodhisattva
Bodhisattva


Joined: 08 Mar 2003
Posts: 21584
Location: here

PostPosted: Thu Dec 27, 2018 1:45 pm    Post subject: Reply with quote

But problem is kde or something missing in kernel config?
_________________
Questions are guaranteed in life; Answers aren't.
Back to top
View user's profile Send private message
asturm
Developer
Developer


Joined: 05 Apr 2007
Posts: 6880
Location: Austria

PostPosted: Thu Dec 27, 2018 1:47 pm    Post subject: Reply with quote

works fine
_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic
Back to top
View user's profile Send private message
Hu
Moderator
Moderator


Joined: 06 Mar 2007
Posts: 13628

PostPosted: Fri Dec 28, 2018 1:28 am    Post subject: Reply with quote

Document: if you want help, you will need to be more specific and more detailed. On what distributions did you observe the pairing to work? What, if anything, did you do on those distributions that might have encouraged them to work? Did you do those same things on Gentoo? In what way does the pairing fail on Gentoo? Are you comparing the same version of KDE programs between distributions? If one is much older or much newer, the issue could be an upstream change.
Back to top
View user's profile Send private message
The_Document
Apprentice
Apprentice


Joined: 03 Feb 2018
Posts: 272

PostPosted: Fri Dec 28, 2018 2:29 am    Post subject: Reply with quote

The pin codes are correct but doesn't get connected to device after pairing.

Cannot even pair to bluetooth speaker which doesn't even need pincodes.

Kernel config
https://paste.pound-python.org/show/9zCYBgMBqSCoxblXLl2B/

Bluez
https://paste.pound-python.org/show/ei00QNuw66et8IilLDNk/

the adapter can find devices just fine but cannot pair. After confirming pin code is correct it always says connection to device failed.
Back to top
View user's profile Send private message
firephoto
Veteran
Veteran


Joined: 29 Oct 2003
Posts: 1599
Location: +48° 5' 23.40", -119° 48' 30.00"

PostPosted: Thu Jan 03, 2019 2:43 am    Post subject: Reply with quote

Make sure the systemd bluetooth.service is running.

Your problem sounds very similar to mine I fought off an on for a while on a couple of systems. Bluetooth hardware seemed to be recognized but wouldn't pair. One system was an old ubuntu that dist upgraded then my bluetooth keyboard wouldn't sync. After recently realizing what I needed to do on Gentoo to get the bluetooth working, and confirming that the ubuntu upgrade hadn't somehow nuked my old v1 bluetooth dongle that actually has a sync button on the dongle.. I came to the conclusion that the dist-upgrade was probably the switch to systemd and they missed a few services to enable.

For whatever reason the docs, wiki, installation of the bluetooth stuff even misses the enabling the systemd service for the bluetooth. If you're not using systemd then it's whatever you have to enable the bluetooth daemon.

The fact that the errors sort of give you the impression it's not something major like the daemon not running doesn't help.

Hope this helps.
_________________
#gentoo-kde on freenode
Back to top
View user's profile Send private message
The_Document
Apprentice
Apprentice


Joined: 03 Feb 2018
Posts: 272

PostPosted: Thu Jan 03, 2019 2:52 am    Post subject: Reply with quote

firephoto wrote:
Make sure the systemd bluetooth.service is running.

Your problem sounds very similar to mine I fought off an on for a while on a couple of systems. Bluetooth hardware seemed to be recognized but wouldn't pair. One system was an old ubuntu that dist upgraded then my bluetooth keyboard wouldn't sync. After recently realizing what I needed to do on Gentoo to get the bluetooth working, and confirming that the ubuntu upgrade hadn't somehow nuked my old v1 bluetooth dongle that actually has a sync button on the dongle.. I came to the conclusion that the dist-upgrade was probably the switch to systemd and they missed a few services to enable.

For whatever reason the docs, wiki, installation of the bluetooth stuff even misses the enabling the systemd service for the bluetooth. If you're not using systemd then it's whatever you have to enable the bluetooth daemon.

The fact that the errors sort of give you the impression it's not something major like the daemon not running doesn't help.

Hope this helps.


I dont use systemd and have have had bluetooth deamon running ever since this topic was made.

Didnt solve the issue.
Back to top
View user's profile Send private message
firephoto
Veteran
Veteran


Joined: 29 Oct 2003
Posts: 1599
Location: +48° 5' 23.40", -119° 48' 30.00"

PostPosted: Thu Jan 03, 2019 3:27 am    Post subject: Reply with quote

The only difference I see from your useflags on bluez is the user session related to systemd so there might be some manual intervention needed related to the permissions with dbus.

This might get you the answer you need.

http://thread.gmane.org/gmane.linux.bluez.kernel/38725/focus=38843

from the first reply.
Quote:

that is something your distro specific package should be fixing if that is
needed. The focus is on integration with systemd and nothing else. You can
use --disable-systemd and provide your own set of D-Bus service files.


That goes onto this

https://bugzilla.redhat.com/show_bug.cgi?id=1018496

Quote:

Description of problem:
The org.bluez.obex.service file installed in /usr/share/dbus-1/services is broken if systemd in the session is not used, because it references /bin/false as the spawned binary.
Thus, attempting to talk to obexd over DBus fails.

Upstream refuses to fix the problem, see
http://marc.info/?l=linux-bluetooth&m=138159411710742&w=2

Version-Release number of selected component (if applicable):
bluez-5.9-4.fc20.x86_64

How reproducible:
Always

Steps to Reproduce:
killall obexd
gdbus --introspect --session org.bluex.obex --object-path /

This is pretty old but I suspect the parts are missing for non systemd installations so dbus is preventing it from connecting proper.
_________________
#gentoo-kde on freenode
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum