On 2024-02-28 13:51, Stakanov via openSUSE Users wrote:
In data mercoledì 28 febbraio 2024 16:03:04 CET, Darryl Gregorash ha scritto:
systemctl --user status dbus-org.bluez.obex.service
Yes thank you. There is still an issue that it complains the UUID is already registered, but I do not know how much of importance this might have. If you generated a billion UUIDs per second, you could expect to see 1 UUID collision (duplication) every 86 years.
Try stopping and then restarting the service. It the problem still exists, try rebooting, or at the very least, logging out then back in. You may need to examine the system log to find out if there is still UUID duplication. If there is, it should probably be reported as a bug -- at the very least, raise the issue in the openSUSE forums.
But it is running now. What puzzles me that they make this such a hurdle for a GDI. One would expect bluetooth to be useable or at least some advice in the install notice (which I do not recall). Will have to do this also on my laptop, thank you for the help given. Much appreciated.
Absolutely. Average computer users today do not want to have to spend a lot of time figuring out why something doesn't work, and searching for solutions can take a great deal of time. If there is a simple solution to such a problem (as there is here), it should be taken care of at installation time. In this case, simply adding the command systemctl --global enable obex to a post-install script for the bluez-obexd package will do just that. This is definitely a bug which should be reported -- though I do not know what good that might have. Earlier I mentioned I got this information from a bug report on the archlinux website. That bug actually dates from summer of 2015, and user intervention is still needed to get the thing to work.