On 2024-02-28 05:51, Stakanov via openSUSE Users wrote:
In data mercoledì 28 febbraio 2024 11:54:32 CET, Darryl Gregorash ha scritto:
As root, run this:
systemctl enable dbus-org.bluez.obex.service
Then the service will be started every time the system boots.
Note that you may have to modify some user's details for it to work for everyone. For example, you may need to add everyone to some group to give access to system files. I don't use this, so I can't do more than mention it so you are aware of the possibility.
entropy@silversurfer:~> sudo systemctl enable dbus-org.bluez.obex.service Failed to enable unit: Unit file dbus-org.bluez.obex.service does not exist. OK, time to gather all of this into one post. First let me apologize for not doing that right at the beginning. I also made a couple of errors that are corrected in this post.
The service dbus-org.bluez.obex.service does not even exist until you first enable obex.service, which is in the package bluez-obexd. So make sure that package is installed, then run (as root): # systemctl --global enable obex Created symlink /etc/systemd/user/dbus-org.bluez.obex.service → /usr/lib/systemd/user/obex.service Now the service file we need does exist. It is a _user_ service, so I was wrong when I said to enable it from the root account. It's already located in /etc/systemd/user, which means it is already enabled -- to there is no need to enable it. Let's get its status to check this. Run (as you, or any ordinary user): hadron:~> systemctl --user status dbus-org.bluez.obex.service ○ obex.service - Bluetooth OBEX service Loaded: loaded (/usr/lib/systemd/user/obex.service; enabled; vendor preset: disabled) Active: inactive (dead) Yes, it is enabled, so (I think/hope) it should be started every time you log into your user account. If it is not, simply create a script to start the service and place it in some convenient place, eg somewhere in your home directory (personally I'd use ~/bin), then add it to System Settings/Startup and Shutdown/Autostart. Again, my apologies for all the confusion. I've verified all the above except for my speculation about the service starting automatically when you log in -- which I can't do since I don't use bluetooth at all.