>On Tuesday, May 14, 2019, Cliff McDiarmid via blfs-support ><[email protected][mailto:[email protected]]> > wrote:>Sent: Tuesday, May 14, 2019 at 6:30 PM >From: "Grover 92000 via blfs-support" ><[email protected][mailto:[email protected]]> >To: "BLFS Support List" ><[email protected][mailto:[email protected]]> >Cc: "Grover 92000" <[email protected][mailto:[email protected]]> >Subject: Re: [blfs-support] Bluez and Obex daemon
>On 12.5.2019. 19:17, Cliff McDiarmid via >It sounds like /etc/X11/xinit/xinitrc.d/50-systemd-user.sh isn't getting >sourced when you login. >I had a similar problem when I switched to lightdm. >When I was using lxdm I didn't have the problem. What desktop manager are you >using? >Thanks for that. I'm using GDM. And it's same on the previous system where >Bluetooth is working, so how is 50-systemd-user.sh being sourced >assuming this is the problem? >50-systemd-user.sh is typically sourced early in the xorg startup by either a >wrapper script or the desktop manager. I don't think that the script being >sourced is the problem - the opposite. >'systemctl enable --user obex' does work from a user environment, but makes no >difference to my problem. >I would try this. Back out all the systemd changes made and make obex globally >available to all users like you did originally. Then disable gdm. Login >manually and create a ~/.xinitrc file with this: >export GDK_BACKEND=x11 >if [ -d /etc/X11/xinit/xinitrc.d ]; then >for f in /etc/X11/xinit/xinitrc.d/?.sh > [ -x "$f" ] && . "$f" > done >fi >exec gnome-session Thanks for that Grover, but I've found the problem. In fact I'm moving files now so it's solved I feel. The culprit was the 'org.bluez.obex.service' file. It read: [D-BUS Service] Name=org.bluez.obex Exec=/usr/false SystemdService=dbus-org.bluez.obex.service !!!!!!!!(don't ask me how this happened) now [D-BUS Service] Name=org.bluez.obex Exec=/usr/libexec/bluetooth/obexd SystemdService=dbus-org.bluez.obex.service I'm still getting errors from 'systemctl status bluetooth' and from the journal such as: Unable to get io data for Object Push: getpeername: Transport endpoint is not connected but as mentioned I'm able to move files. thanks again Cliff -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
