https://bugs.kde.org/show_bug.cgi?id=481870
--- Comment #1 from tagwer...@innerjoin.org ---
This doesn't seem to affect all Neon Testing systems, I have one older version
where it works.
What seems different is that the failing systems have:
$ systemctl --user status obex
○ obex.service - Bluetooth OBEX service
Loaded: loaded (/usr/lib/systemd/user/obex.service; disabled; vendor
preset: enabled)
Active: inactive (dead)
and the working system has:
$ systemctl --user status obex
● obex.service - Bluetooth OBEX service
Loaded: loaded (/usr/lib/systemd/user/obex.service; disabled; vendor
preset: enabled)
Active: active (running) since Tue 2024-02-27 23:26:19 CET; 21s ago
Main PID: 1154 (obexd)
Tasks: 1 (limit: 9361)
Memory: 2.0M
CPU: 6ms
CGroup:
/user.slice/user-1000.slice/user@1000.service/app.slice/obex.service
└─1154 /usr/lib/bluetooth/obexd
Feb 27 23:26:19 neon-testing systemd[774]: Starting Bluetooth OBEX
service...
Feb 27 23:26:19 neon-testing obexd[1154]: OBEX daemon 5.64
Feb 27 23:26:19 neon-testing systemd[774]: Started Bluetooth OBEX service.
It's not evident what is forcing the service on or off. Just doing a:
$ systemctl --user enable obex
$ systemctl --user start obex
seems *not* to be enough. What seems new is that the desktop hangs until the
service_start_timeout
Found this lead from https://bugs.archlinux.org/task/45816, dated 2015
--
You are receiving this mail because:
You are watching all bug changes.
