Blueman manager 2.3.5-2+b1 not start after upgrade to Debian 12 (bookworm) - blueman-applet.service could not be found

[itmagpro]

blueman: 2.3.5-2+b1 i386
BlueZ: 5.66-1+deb12u2 i386
Distribution: Debian 12, Linux 6.1.0-23-rt-686-pae SMP PREEMPT_RT Debian 6.1.99-1 (2024-07-15) i686 GNU/Linux
Desktop environment: Xfce

bluetooth service running fine, chinese BT device connected, but blueman manager 2.3.5-2+b1 not start after upgrade to Debian 12 (bookworm)

Output commands see here:

# dpkg -l|grep blue
...
$ blueman-adapters
...
$ blueman-manager
...

https://pastebin.com/uUJCJAAj

I try purge and reinstall bluez and blueman, but this not help ;(

dmesg about Bluetooth hci0 device here: https://pastebin.com/JGfLpPxR

# sudo rfkill list
0: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no
6: hci0: Bluetooth
        Soft blocked: no
        Hard blocked: no

and

# bluetoothctl devices
NO OUTPUT - not see device?
# bluetoothctl list
...
# bluetoothctl show
...

https://pastebin.com/DepByKD2

Unit blueman-applet.service could not be found.

$ blueman-manager
Blueman applet needs to be running

# less /var/log/syslog|grep blue|less
...
2024-09-08T11:48:12.886707+03:00 locahost systemd[2064]: blueman-applet.service: Main process exited, code=exited, status=1/FAILURE
2024-09-08T11:48:12.887609+03:00 locahost systemd[2064]: blueman-applet.service: Failed with result 'exit-code'.
2024-09-08T11:48:12.891977+03:00 locahost systemd[2064]: Failed to start blueman-applet.service - Bluetooth management applet.

# systemctl status blueman-applet
Unit blueman-applet.service could not be found.

# systemctl list-units | grep -i blue
  sys-devices-pci0000:00-0000:00:1d.0-usb1-1\x2d2-1\x2d2:1.0-bluetooth-hci0.device          loaded active     plugged      /sys/devices/pci0000:00/0000:00:1d.0/usb1/1-2/1-2:1.0/bluetooth/hci0
  sys-subsystem-bluetooth-devices-hci0.device                                               loaded active     plugged      /sys/subsystem/bluetooth/devices/hci0
  bluealsa-aplay.service                                                                    loaded active     running      BlueALSA player service
  bluealsa.service                                                                          loaded active     running      BlueALSA service
  bluetooth.service                                                                         loaded active     running      Bluetooth service
  bluetooth.target                                                                          loaded active     active       Bluetooth Support

https://pastebin.com/thyy7Bmr

logs from journalctl -b|grep blue: Failed to activate service 'org.blueman.Applet': timed out

blueman-applet.service find in:

$ locate blueman-applet
/usr/bin/blueman-applet
/usr/lib/systemd/user/blueman-applet.service
/usr/share/man/man1/blueman-applet.1.gz

but him not have in /etc/systemd - must be how-to install mannualy? :)

P.S. Before on 5.10.0-0.deb10.27-rt-686-pae by Debian 10 chinese blutooth USB dongle worked fine without this BIG PROBLEMS...

Like this (from aliexpress): USB Bluetooth 5.1 Adapter Transmitter Receiver Bluetooth Audio Receiver USB Dongle Wireless USB Adapter for Computer PC Laptop

[cschramm]

blueman-applet.service is a user service, but just run blueman-applet (probably at /usr/bin/blueman-applet). It usually gets started automatically when requested due to org.blueman.Applet.service (/usr/share/dbus-1/services/org.blueman.Applet.service, I guess). There might be something wrong with your D-Bus setup.

[itmagpro]

What "something wrong with your D-Bus setup", for example?

I have in system initscripts* insserv* sysv-rc* pkg installed, may be in your program some problem with sysv?

For example when reinstall bluez:

# apt-get install --reinstall bluez bluez-tools bluez-firmware bluez-obexd
...
Настраивается пакет bluez (5.66-1+deb12u2) …
insserv: Script `ssh' has overlapping Default-Start and Default-Stop runlevels (2 3 4 5) and (2 3 4 5). This should be fixed.
Обрабатываются триггеры для man-db (2.11.2-2) …

See:

• #971713 - sysstat: init or systemd file has overlapping runlevels - Debian Bug report logs

But apt-get install bluetooth blueman no have this problem, also before reinstall I try:

# sctl stop dbus-org.bluez
# sctl disable dbus-org.bluez
# sudo update-rc.d -f dbus-org.bluez remove
# sudo update-rc.d dbus-org.bluez defaults

# sctl stop bluetooth
# sctl disable bluetooth
Synchronizing state of bluetooth.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install disable bluetooth
insserv: warning: current start runlevel(s) (empty) of script `bluetooth' overrides LSB defaults (2 3 4 5).
insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `bluetooth' overrides LSB defaults (0 1 6).
# sudo update-rc.d -f bluetooth remove
# sudo update-rc.d bluetooth defaults

# agi --reinstall bluetooth blueman bluez bluez-tools bluez-firmware bluez-obexd
...
without "insserv: warning"
#

Seems not in sysv or dbus problem because all other work fine, only blueman not start and bluetooth not work ;(

...May be some where in secret place exist some secret some very old-old blueman config file from old previous debian configuration that must be remove..?

Which some any other suggestions?

P.S. I known, that NTO NEED BE UPGRADE TO DEBIAN 12 and need litle wait...

• network-manager, wicd gui applet drop;
• bluetooth, blueman fail;
• grow consumption RAM;
• ..."GREAT" works...

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[cschramm]

I don't really get the problem statement. You provided some data that blueman-manager fails to start blueman-applet via D-Bus. It seems like you are able to run blueman-applet yourself. Does blueman-manager still complain about the applet service when it's already running?