On 14.10.2023 22:12, Frank McCormick wrote:
On 2023-10-14 12:05, Andrei Borzenkov wrote:
On 14.10.2023 18:35, Frank McCormick wrote:
Looking through my journal log files today and I noticed this:
Oct 14 09:55:52 desktop-tumbleweed bamfdaemon[6594]: Authorization required, but no authorization protocol specified
This means that application attempts to access X11 display which it is not allowed to access.
I have since discovered what triggers the problem. In the following extract from the user journal ---
I logged out of Icewm to log into Openbox.
Oct 14 12:47:28 desktop-tumbleweed dbus-daemon[1423]: [session uid=1000 pid=1423] Successfully activated service 'org.ayatana.bamf' Oct 14 12:48:09 desktop-tumbleweed bamfdaemon[1912]: Source ID 2863311530 was not found when attempting to remove it Oct 14 12:55:55 desktop-tumbleweed bamfdaemon[1912]: Source ID 2863311530 was not found when attempting to remove it
This is the journal after immediately logging into Openbox :
Oct 14 13:53:11 desktop-tumbleweed bamfdaemon[1912]: Source ID 2863311530 was not found when attempting to remove it Oct 14 15:03:11 desktop-tumbleweed dbus-daemon[1423]: [session uid=1000 pid=1423] Activating via systemd: service name='org.gtk.vfs.Metadata' unit='gvfs-metadata.service' requested by ':1.29' (uid=1000 pid=1912 comm="/usr/libexec/bamf/bamfdaemon") Oct 14 15:03:11 desktop-tumbleweed systemd[1387]: bamfdaemon.service: Main process exited, code=exited, status=1/FAILURE Oct 14 15:03:11 desktop-tumbleweed systemd[1387]: bamfdaemon.service: Failed with result 'exit-code'. Oct 14 15:03:11 desktop-tumbleweed systemd[1387]: bamfdaemon.service: Scheduled restart job, restart counter is at 1.
So bamfdaemon fails and it starts to spam the journal with hundreds of the following :
Oct 14 15:03:12 desktop-tumbleweed bamfdaemon[6441]: Authorization required, but no authorization protocol specified
So to trigger the problem I logged out of Icewm to log into Openbox.
Cold it be some problem with the display manager...in my case Lightdm ??
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