error spamming journal files
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 Oct 14 09:55:52 desktop-tumbleweed bamfdaemon[6594]: Authorization required, but no authorization protocol specified Oct 14 09:55:52 desktop-tumbleweed bamfdaemon[6594]: Authorization required, but no authorization protocol specified Oct 14 09:55:52 desktop-tumbleweed bamfdaemon[6594]: Authorization required, but no authorization protocol specified Oct 14 09:55:52 desktop-tumbleweed bamfdaemon[6594]: Authorization required, but no authorization protocol specified Oct 14 09:55:52 desktop-tumbleweed bamfdaemon[6594]: Authorization required, but no authorization protocol specified Oct 14 09:55:52 desktop-tumbleweed bamfdaemon[6594]: Authorization required, but no authorization protocol specified Oct 14 09:55:52 desktop-tumbleweed bamfdaemon[6594]: Authorization required, but no authorization protocol specified This error goes on for literally hundreds of lines. I checked older boots and found the same thing so I am not sure how long this has been going on. Can someone suggest where I could start looking to resolve this ? Thanks
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.
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 ??
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
On 2023-10-15 02:33, Andrei Borzenkov wrote:
systemctl --user show-environment
frank@desktop-tumbleweed:~> systemctl --user show-environment HOME=/home/frank LANG=en_US.UTF-8 LOGNAME=frank PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin SHELL=/bin/bash USER=frank XDG_RUNTIME_DIR=/run/user/1000 XDG_CONFIG_DIRS=/etc/xdg:/usr/local/etc/xdg:/usr/etc/xdg DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus DISPLAY=:0 XAUTHORITY=/home/frank/.Xauthority Display variable is there. Then I did journalctl -b0 | grep bamf | less and it spewed out hundreds of the offending lines in the journal. Next I will try booting directly into Openbox to see whether it happens then. Thanks
On 15.10.2023 14:36, Frank McCormick wrote:
On 2023-10-15 02:33, Andrei Borzenkov wrote:
systemctl --user show-environment
frank@desktop-tumbleweed:~> systemctl --user show-environment HOME=/home/frank LANG=en_US.UTF-8 LOGNAME=frank PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin SHELL=/bin/bash USER=frank XDG_RUNTIME_DIR=/run/user/1000 XDG_CONFIG_DIRS=/etc/xdg:/usr/local/etc/xdg:/usr/etc/xdg DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus DISPLAY=:0 XAUTHORITY=/home/frank/.Xauthority
Display variable is there.
Then I did journalctl -b0 | grep bamf | less
and it spewed out hundreds of the offending lines in the journal.
This command shows system journal, not user journal. Which suggests, your program is started as the system program which knows nothing about your user session variables. Without knowing how this program is started it is difficult to know why it fails.
Next I will try booting directly into Openbox to see whether it happens then.
Thanks
On 2023-10-15 08:01, Andrei Borzenkov wrote:
On 15.10.2023 14:36, Frank McCormick wrote:
On 2023-10-15 02:33, Andrei Borzenkov wrote:
systemctl --user show-environment
frank@desktop-tumbleweed:~> systemctl --user show-environment HOME=/home/frank LANG=en_US.UTF-8 LOGNAME=frank PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin SHELL=/bin/bash USER=frank XDG_RUNTIME_DIR=/run/user/1000 XDG_CONFIG_DIRS=/etc/xdg:/usr/local/etc/xdg:/usr/etc/xdg DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus DISPLAY=:0 XAUTHORITY=/home/frank/.Xauthority
Display variable is there.
Then I did journalctl -b0 | grep bamf | less
and it spewed out hundreds of the offending lines in the journal.
This command shows system journal, not user journal. Which suggests, your program is started as the system program which knows nothing about your user session variables.
Without knowing how this program is started it is difficult to know why it fails.
As I mentioned in an earlier mail, it only fails when I am running Plank as a desktop launcher, and then logging out and logging back in. Something gets lost in the middle. Strangely, I am now running Plank in Mate and there is no such problem with that desktop only with Icewm and Openbox. Mate must set something up which the other two don't.
On 2023-10-15 13:36, Frank McCormick wrote:
On 2023-10-15 02:33, Andrei Borzenkov wrote:
systemctl --user show-environment
frank@desktop-tumbleweed:~> systemctl --user show-environment HOME=/home/frank LANG=en_US.UTF-8 LOGNAME=frank PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin SHELL=/bin/bash USER=frank XDG_RUNTIME_DIR=/run/user/1000 XDG_CONFIG_DIRS=/etc/xdg:/usr/local/etc/xdg:/usr/etc/xdg DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus DISPLAY=:0 XAUTHORITY=/home/frank/.Xauthority
Display variable is there.
But no "SYSTEMD_EXEC_PID=..." cer@Laicolasse:~> systemctl --user show-environment HOME=/home/cer LANG=en_US.UTF-8 LOGNAME=cer PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin SHELL=/bin/bash SYSTEMD_EXEC_PID=2620 USER=cer XDG_DATA_DIRS=/home/cer/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share/:/usr/share/ XDG_RUNTIME_DIR=/run/user/1000 DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus DISPLAY=:0 XAUTHLOCALHOSTNAME=Laicolasse.valinor XAUTHORITY=/run/user/1000/gdm/Xauthority cer@Laicolasse:~> -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.5 (Laicolasse))
On 2023-10-15 08:15, Carlos E. R. wrote:
On 2023-10-15 13:36, Frank McCormick wrote:
On 2023-10-15 02:33, Andrei Borzenkov wrote:
systemctl --user show-environment
frank@desktop-tumbleweed:~> systemctl --user show-environment HOME=/home/frank LANG=en_US.UTF-8 LOGNAME=frank PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin SHELL=/bin/bash USER=frank XDG_RUNTIME_DIR=/run/user/1000 XDG_CONFIG_DIRS=/etc/xdg:/usr/local/etc/xdg:/usr/etc/xdg DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus DISPLAY=:0 XAUTHORITY=/home/frank/.Xauthority
Display variable is there.
But no "SYSTEMD_EXEC_PID=..."
cer@Laicolasse:~> systemctl --user show-environment HOME=/home/cer LANG=en_US.UTF-8 LOGNAME=cer PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin SHELL=/bin/bash SYSTEMD_EXEC_PID=2620 USER=cer XDG_DATA_DIRS=/home/cer/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share/:/usr/share/ XDG_RUNTIME_DIR=/run/user/1000 DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus DISPLAY=:0 XAUTHLOCALHOSTNAME=Laicolasse.valinor XAUTHORITY=/run/user/1000/gdm/Xauthority cer@Laicolasse:~>
Well on my three desktops Icewm ,Openbox and Mate, none shows SYSTEMD_EXEC_PID= and there are not any problems such as the spamming of the journal. I wonder what SYSTEMD_EXEC_PID= is anyway ? Frank
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 El 2023-10-15 a las 09:14 -0400, Frank McCormick escribió:
On 2023-10-15 08:15, Carlos E. R. wrote:
On 2023-10-15 13:36, Frank McCormick wrote:
On 2023-10-15 02:33, Andrei Borzenkov wrote:
...
Well on my three desktops Icewm ,Openbox and Mate, none shows SYSTEMD_EXEC_PID= and there are not any problems such as the spamming of the journal. I wonder what SYSTEMD_EXEC_PID= is anyway ?
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND cer 2620 0.0 0.0 68596 8308 ? Ss Oct11 0:00 /usr/lib/systemd/systemd --user (ps afxu) And it is used to start a lot of things (I'm on XFCE): cer 2620 0.0 0.0 68596 8308 ? Ss Oct11 0:00 /usr/lib/systemd/systemd --user cer 2629 0.0 0.0 275856 4 ? S Oct11 0:00 \_ (sd-pam) cer 2752 0.0 0.0 33996 5096 ? Ss Oct11 0:41 \_ /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only cer 3037 0.0 0.0 261564 6224 ? Ssl Oct11 0:00 \_ /usr/lib/gvfs/gvfsd cer 3375 0.0 0.0 337588 4140 ? Sl Oct11 0:00 | \_ /usr/lib/gvfs/gvfsd-trash --spawner :1.7 /org/gtk/gvfs/exec_spaw/0 cer 10233 0.0 0.0 309188 10040 ? Sl Oct11 0:00 | \_ /usr/lib/gvfs/gvfsd-http --spawner :1.7 /org/gtk/gvfs/exec_spaw/1 cer 26488 0.0 0.0 412744 4076 ? Sl Oct12 0:00 | \_ /usr/lib/gvfs/gvfsd-network --spawner :1.7 /org/gtk/gvfs/exec_spaw/2 cer 26505 0.0 0.0 346320 4188 ? Sl Oct12 0:00 | \_ /usr/lib/gvfs/gvfsd-dnssd --spawner :1.7 /org/gtk/gvfs/exec_spaw/4 cer 3043 0.0 0.0 401336 2644 ? Sl Oct11 0:00 \_ /usr/lib/gvfs/gvfsd-fuse /run/user/1000/gvfs -f cer 3053 0.0 0.0 335472 4208 ? Ssl Oct11 0:00 \_ /usr/lib/at-spi2/at-spi-bus-launcher cer 3059 0.0 0.0 32772 3360 ? S Oct11 0:01 | \_ /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3 cer 3061 0.0 0.0 242740 3136 ? Sl Oct11 1:07 \_ /usr/lib/xfce4/xfconf/xfconfd cer 3067 0.0 0.0 202524 6392 ? Sl Oct11 0:04 \_ /usr/lib/at-spi2/at-spi2-registryd --use-gnome-session cer 3096 2.1 0.0 2744740 11124 ? Ssl Oct11 122:11 \_ /usr/bin/pulseaudio --daemonize=no --log-target=journal cer 3205 0.0 0.0 287476 3944 ? Sl Oct11 0:00 | \_ /usr/lib/pulse/gsettings-helper cer 3114 0.0 0.0 521804 6700 ? SLsl Oct11 0:00 \_ /usr/lib/gvfs/gvfs-udisks2-volume-monitor cer 3246 0.0 0.0 246644 3364 ? Ssl Oct11 0:00 \_ /usr/lib/gvfs/gvfs-mtp-volume-monitor cer 3252 0.0 0.0 265468 3864 ? Ssl Oct11 0:00 \_ /usr/lib/gvfs/gvfs-gphoto2-volume-monitor cer 3256 0.0 0.0 344840 5120 ? Ssl Oct11 0:04 \_ /usr/lib/gvfs/gvfs-afc-volume-monitor cer 3262 0.0 0.0 243220 4264 ? Ssl Oct11 0:00 \_ /usr/lib/gvfs/gvfs-goa-volume-monitor cer 3266 0.0 0.0 854156 9548 ? Ssl Oct11 0:02 \_ /usr/lib/xdg-desktop-portal cer 3270 0.0 0.0 990496 13052 ? Sl Oct11 0:00 \_ /usr/lib/goa-daemon cer 3281 0.0 0.0 558976 3624 ? Ssl Oct11 0:00 \_ /usr/lib/xdg-document-portal root 3297 0.0 0.0 2752 0 ? Ss Oct11 0:00 | \_ fusermount3 -o rw,nosuid,nodev,fsname=portal,auto_unmount,subtype=portal -- /run/user/1000/doc cer 3287 0.0 0.0 258152 2036 ? Ssl Oct11 0:00 \_ /usr/lib/xdg-permission-store cer 3313 0.0 0.0 1328060 20064 ? Ssl Oct11 0:04 \_ /usr/lib/xdg-desktop-portal-gnome cer 3326 0.0 0.0 489088 8588 ? Sl Oct11 0:07 \_ /usr/lib/goa-identity-service cer 3365 0.0 0.0 175704 2800 ? Ssl Oct11 0:00 \_ /usr/lib/gvfs/gvfsd-metadata cer 3612 0.0 0.0 1539092 16448 ? Ssl Oct11 0:00 \_ /usr/lib/evolution-data-server/evolution-source-registry cer 3621 0.0 0.0 481340 11844 ? Ssl Oct11 0:02 \_ /usr/lib/xdg-desktop-portal-gtk cer 3764 0.0 0.0 444380 7548 ? Ssl Oct11 0:03 \_ /usr/lib/xdg-desktop-portal-kde cer 3939 0.0 0.0 51536 5244 ? Ssl Oct11 0:00 \_ /usr/bin/pipewire cer 3940 0.0 0.0 380308 13800 ? Ssl Oct11 0:00 \_ /usr/bin/wireplumber cer 3957 0.0 0.0 1577864 18300 ? Ssl Oct11 0:00 \_ /usr/lib/evolution-data-server/evolution-calendar-factory cer 4090 0.0 0.0 166280 4420 ? Ssl Oct11 0:00 \_ /usr/lib/dconf-service cer 4095 0.0 0.0 1180444 17728 ? Ssl Oct11 0:00 \_ /usr/lib/evolution-data-server/evolution-addressbook-factory - -- Cheers Carlos E. R. (from openSUSE 15.5 (Laicolasse)) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCZSwktRwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVLkMAnRQ9OfWqHMcA1C+0sEfW LmCDbPkNAKCVnJIsp2Yrlih3oax2h8XAKJYGkA== =eZLH -----END PGP SIGNATURE-----
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
On 2023-10-15 02:33, Andrei Borzenkov wrote:
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
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 much experimentation I found out what causes the problem. I have three desktops on this machine - Icewm, Openbox and Mate. There is no problem with Mate, and the spamming of the journal only happens with Icewm and Openbox when I run Plank as a desktop launcher. Remove Plank and there is no problem. There doesn't seem to have been much development with Plank lately but I'll try filing a bug. Thanks
participants (3)
-
Andrei Borzenkov -
Carlos E. R. -
Frank McCormick