>Sent: Monday, May 13, 2019 at 5:06 AM >From: "Armin K. via blfs-support" <[email protected]> >To: [email protected] >Cc: "Armin K." <[email protected]> >Subject: Re: [blfs-support] Bluez and Obex daemon >On 12.5.2019. 19:17, Cliff McDiarmid via blfs-support wrote: > Hi > > Can anyone help here? I have previously installed Bluez for my Bluetooth > device and everything has worked in my LFS box. > > This time, in a new LFS, the obex daemon is not being loaded when I try to to > transfer data/pictures from phone to laptop. > > I have a pairing, trusted and connection, but cannot transfer. I have > followed the BLFS book. > > 'systemctl --global is-enabled obex' - gives 'enabled' > > journalctl -u obexd - nothing > > journalctl | grep obexd - nothing > > > My other LFS box gives: > > May 11 22:09:44 cliffhangers obexd[5690]: CONNECT(0x0), (null)(0xffffffff) > May 11 22:09:44 cliffhangers obexd[5690]: CONNECT(0x0), (null)(0x0) > May 11 22:09:45 cliffhangers obexd[5690]: PUT(0x2), (null)(0xffffffff) > May 11 22:09:45 cliffhangers obexd[5690]: PUT(0x2), CONTINUE(0x10) > > when 'journalctl -u obexd' is run
>In one system you use -u, in other you use. Switch obex from >global to user service and you'll be good to go Thanks Armin, but sorry, I don't understand. --global was used to start the daemon. -u was used to look at the journal for errors. >systemctl disable obexd >systemctl enable -u --now obexd Anyway. I disabled the daemon globally and have tried to enable it for a user but 'systemctl enable -u --now obexd' gives: systemctl: invalid option -- 'u' 'systemctl enable --now obexd' gives: Failed to enable unit: Unit file obexd.service does not exist. 'systemctl enable --user obex' gives: Failed to connect to bus: Operation not permitted. This could be my problem. A dbus problem, not present on other system. Cliff -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
