On 2023-10-15 02:33, Andrei Borzenkov wrote:
More likely Openbox does not update systemd user instance environment variables, so services started by systemd do not know how to access your $DISPLAY.
Log into Openbox, show
systemctl --user show-environment
After booting directly into Openbox I again did the search of journal for bamf references and this is all that was returned. Oct 15 07:39:48 desktop-tumbleweed dbus-daemon[1425]: [session uid=1000 pid=1425] Activating via systemd: service name='org.ayatana.bamf' unit='bamfdaemon.service' requested by ':1.3' (uid=1000 pid=1520 comm="plank") Oct 15 07:39:48 desktop-tumbleweed at-spi-bus-launcher[1552]: dbus-daemon[1552]: Activating service name='org.a11y.atspi.Registry' requested by ':1.1' (uid=1000 pid=1579 comm="/usr/libexec/bamf/bamfdaemon") Oct 15 07:39:48 desktop-tumbleweed dbus-daemon[1425]: [session uid=1000 pid=1425] Successfully activated service 'org.ayatana.bamf' So if I boot directly into Openbox, there is no problem. The bamfdaemon starts successfully. The failure only occurs when I go from Icewm into Openbox. Frank