Hi Michelle, >> you can try the helper manually with sudo >> /usr/lib/dbus-1.0/dbus-daemon-launch-helper org.blueman.mechanism and >> see what happens. Also check /var/log/daemon.log. > > Nothing special, it loads proprtly. > Should this service not started automatically?
the service is not meant to run permanently. It gets activated via D-Bus (the service is defined in /usr/share/dbus-1/system-services/org.blueman.Mechanism.service) and has a timeout after which it terminates. > ----[ c '/usr/lib/blueman/blueman-mechanism' ]---------------------------- > No protocol specified > Unable to init server: Could not connect: Connection refused > No protocol specified > Unable to init server: Could not connect: Connection refused > Starting blueman-mechanism > > (blueman-mechanism:2331): Gtk-CRITICAL **: gtk_icon_theme_get_for_screen: > assertion 'GDK_IS_SCREEN (screen)' failed > loading Ppp > loading Rfcomm > loading Network > loading RfKill > Exiting > -------------------------------------------------------------------------- > > Can it be, that because I am loged in as user "michelle.konzack" it is > not allowed to start a GUI? (I am in a "root" XTerm) Yes, it will not start outside the desktop. blueman-applet cannot work outside as well. You're not trying to run it there, are you? > OK, it seems, that the error is, that blueman place its modules in > > /usr/lib/python3.5/site-packages > > and NOT in > > /usr/lib/python3.5/dist-packages > > Is this an upstream bug since "site-packages" appear only in the > orig.tar.gz site-packages is the standard Python way, dist-packages is the way used in deb packages (dh_python takes care of that) to avoid conflicts. If your package contains site-packages path, something went wrong when it was built. Regards
