Startup/boot; delay, pause, slow, long

MrNice · June 7, 2023, 12:08pm

Hi there,
I am not the only one with the issue that the boot take long to proceed.
At least 2 threads
here and here
To sum up, the boot is fast until the arrow appears on the screen then the icons take around 20s to appear.
I have 2 desktop and 1 old laptop with Leap 15.4 Mate with the issue.
I just installed Leap 15.4 Mate on the laptop in a empty HDD.
I want to add one by on all the add-on and programs to find what is the culprit.

Could someone help me to write a script that can start at boot to time the boot process automatically and save the results in a file and compare with previous boots.
More this script is automate more I could find the culprit fast.
I don’t know what to measure, I let expert to imagine the best way, I can offer the time to run it in the situation.
If you need more info, let me know.
Thanks

aggie · June 7, 2023, 1:25pm

Your first hyperlink (“here”) is to my thread about icon delay.

My issue has been resolved, although the cause is unknown.

Keep in mind two things of difference:
a) I use TW (not Leap) on all our machines.
2) I use KDE / Plasma (not Mate) for desktop on all our machines.

My fix turned out to be easy … I simply removed the Widgets, one by one from the top KDE Panel, restarted GUI, then added those same Widgets back.

No more “20 seconds until icons appear on desktop” issue. Five minute fix.

Good luck!

MrNice · June 7, 2023, 2:32pm

Thanks aggie,
I did the same, removing 3 widgets that I can see. No luck for me.
Could you tell me how to list the widgets that could still be on the panels ?
Are the shortcuts like terminal, system monitor, caja (nautilus), Brave should be removed ?

aggie · June 7, 2023, 3:04pm

I did it the easy way … point and click with the mouse
Look at my two screenshots - this is the KDE Panel at the top.

The first screenshot shows the Panel in normal use … I’ve put arrows pointing to each Widget.

The second screenshot shows the Panel in “Edit” mode (right-click and select “Edit Panel”).

I’ve also shown where all the Widgets are in Edit mode … notice that I slid the mouse over to the “Clock” Widget and it’s Edit pop-up is displayed, and my mouse is resting on the “Remove” option for that Widget … I simply did this for each Widget (but I left one Application menu Widget).

Dropped to Run-level 3, then switched to Run-level 5, then added back the Widgets I removed … now the Desktop icons show up almost instantly.

So, for whatever reason (unknown), the KDE desktop was “busy” doing something in the background with the top Panel", then when finished (after 20 seconds), the Desktop icons were displayed.

.
.

aggie · June 7, 2023, 3:16pm

On the KDE Panel, yes … if I had Brave, terminal, system monitor, file manager there … those would be shown as a Widget (each), and I could remove each one … each Widget has a menu pop-up with Remove option.

But all my application icons are on a Latte Panel at bottom of screen
.

MrNice · June 7, 2023, 5:21pm

The widgets management is not the same with Mate. As I don’t want to remove what I added, I’d prefer to investigate on my test box, I mean my laptop, unless I can backup the config and restore with few clicks.

How did you know it was KDE desktop and moreover the top panel the responsible for the issue?

MrNice · June 8, 2023, 5:50pm

First I backed up the Mate config
from here

~> dconf dump / > ~/Desktop/dconf-full-backup

Then I removed every widget one by one with a restart between.
Then I removed the top panel and left only the bottom panel as it’s not possible to remove the both.
Still the issue
Then I restored the backup

~> dconf load / < dconf-full-backup

Still the issue
So, I’ll have to carry on with the new install.

Could someone help me to write a script that parse the log, write the time for 3 or 4 majeure events and save the result in a file (named with the date and time. The first file will be the ref.
Another script to calculate the times difference with the ref and save in an unique file ( file name, time diff 1, time diff 2, …) in each line.
You can add your one idea.

Many thanks

MrNice · June 13, 2023, 4:10pm

After Leap 15.4 install I recorded a boot log with

do journalctl -b -o short-monotonic > "/home/test/Desktop/Boots/boot_$(date +"%F-%T")"

Then I did
First update after install
Boot record

[   77.902890] localhost.localdomain pulseaudio[1932]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[   81.289025] localhost.localdomain systemd[1]: systemd-hostnamed.service: Deactivated successfully.
[  111.769398] localhost.localdomain chronyd[1101]: Selected source 212.85.158.10 (1.opensuse.pool.ntp.org)
[  118.933595] localhost.localdomain wnck-applet[2006]: Negative content width -1 (allocation 1, extents 1x1) while allocating gadget (node button, owner WnckButton)
[  118.954141] localhost.localdomain wnck-applet[2006]: Negative content width -1 (allocation 1, extents 1x1) while allocating gadget (node button, owner WnckButton)
[  119.072086] localhost.localdomain org.mate.panel.applet.MateMenuAppletFactory[2270]: No protocol specified
[  119.133800] localhost.localdomain mate-terminal[2270]: Theme parsing error: gtk.css:7602:21: Not using units is deprecated. Assuming 'px'.
[  119.209690] localhost.localdomain org.mate.panel.applet.MateMenuAppletFactory[2270]: No protocol specified
[  119.221989] localhost.localdomain at-spi-bus-launcher[1890]: dbus-daemon[1890]: Activating service name='org.a11y.atspi.Registry' requested by ':1.66' (uid=1000 pid=2270 comm="mate-terminal ")
[  119.234208] localhost.localdomain at-spi-bus-launcher[2277]: No protocol specified
[  119.235171] localhost.localdomain at-spi-bus-launcher[2277]: No protocol specified
[  119.235318] localhost.localdomain at-spi2-registr[2277]: Could not open X display
[  119.240501] localhost.localdomain at-spi-bus-launcher[1890]: dbus-daemon[1890]: Successfully activated service 'org.a11y.atspi.Registry'
[  119.244740] localhost.localdomain at-spi-bus-launcher[2277]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
[  119.246345] localhost.localdomain at-spi-bus-launcher[2277]: No protocol specified
[  119.248305] localhost.localdomain at-spi-bus-launcher[2277]: No protocol specified
[  119.248737] localhost.localdomain at-spi2-registr[2277]: AT-SPI: Cannot open default display
[  119.252570] localhost.localdomain mate-volume-con[2007]: AT-SPI: Could not obtain desktop path or name
[  119.253322] localhost.localdomain mate-session[1830]: WARNING: AT-SPI: Could not obtain desktop path or name
[  119.253975] localhost.localdomain clock-applet[2005]: AT-SPI: Could not obtain desktop path or name
[  119.254666] localhost.localdomain wnck-applet[2006]: AT-SPI: Could not obtain desktop path or name
[  119.256262] localhost.localdomain stickynotes-app[1999]: AT-SPI: Could not obtain desktop path or name
[  119.256865] localhost.localdomain mate-menu[2000]: AT-SPI: Could not obtain desktop path or name
[  119.257453] localhost.localdomain notification-ar[2008]: AT-SPI: Could not obtain desktop path or name
[  119.889776] localhost.localdomain mate-terminal[2270]: AT-SPI: Could not obtain desktop path or name
[  119.890204] localhost.localdomain at-spi-bus-launcher[1890]: dbus-daemon[1890]: Activating service name='org.a11y.atspi.Registry' requested by ':1.66' (uid=1000 pid=2270 comm="mate-terminal ")
[  119.945960] localhost.localdomain systemd[1822]: Started VTE child process 2307 launched by mate-terminal process 2270.
[  119.951441] localhost.localdomain at-spi-bus-launcher[2306]: No protocol specified
[  119.956220] localhost.localdomain at-spi-bus-launcher[2306]: No protocol specified
[  119.956533] localhost.localdomain at-spi2-registr[2306]: Could not open X display
[  119.964357] localhost.localdomain at-spi-bus-launcher[1890]: dbus-daemon[1890]: Successfully activated service 'org.a11y.atspi.Registry'
[  119.964622] localhost.localdomain at-spi-bus-launcher[2306]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
[  119.974855] localhost.localdomain at-spi-bus-launcher[2306]: No protocol specified
[  119.978168] localhost.localdomain at-spi-bus-launcher[2306]: No protocol specified
[  119.978519] localhost.localdomain at-spi2-registr[2306]: AT-SPI: Cannot open default display
[  119.982725] localhost.localdomain stickynotes-app[1999]: AT-SPI: Could not obtain desktop path or name
[  119.983173] localhost.localdomain mate-session[1830]: WARNING: AT-SPI: Could not obtain desktop path or name
[  119.983373] localhost.localdomain mate-menu[2000]: AT-SPI: Could not obtain desktop path or name
[  119.983663] localhost.localdomain clock-applet[2005]: AT-SPI: Could not obtain desktop path or name
[  119.983923] localhost.localdomain notification-ar[2008]: AT-SPI: Could not obtain desktop path or name
[  119.984176] localhost.localdomain mate-volume-con[2007]: AT-SPI: Could not obtain desktop path or name
[  119.986685] localhost.localdomain wnck-applet[2006]: AT-SPI: Could not obtain desktop path or name
[  119.990696] localhost.localdomain at-spi-bus-launcher[1890]: dbus-daemon[1890]: Activating service name='org.a11y.atspi.Registry' requested by ':1.66' (uid=1000 pid=2270 comm="mate-terminal ")
[  120.013016] localhost.localdomain at-spi-bus-launcher[2311]: No protocol specified
[  120.013016] localhost.localdomain at-spi-bus-launcher[2311]: No protocol specified
[  120.014115] localhost.localdomain at-spi2-registr[2311]: Could not open X display
[  120.019357] localhost.localdomain mate-terminal[2270]: atk-bridge: get_device_events_reply: unknown signature
[  120.024773] localhost.localdomain at-spi-bus-launcher[1890]: dbus-daemon[1890]: Successfully activated service 'org.a11y.atspi.Registry'
[  120.027186] localhost.localdomain at-spi-bus-launcher[2311]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
[  120.037099] localhost.localdomain at-spi-bus-launcher[2311]: No protocol specified
[  120.042878] localhost.localdomain mate-terminal[2270]: atk-bridge: get_device_events_reply: unknown signature
[  120.043347] localhost.localdomain mate-terminal[2270]: atk-bridge: GetRegisteredEvents returned message with unknown signature
[  120.096070] localhost.localdomain at-spi-bus-launcher[2311]: No protocol specified
[  120.096396] localhost.localdomain at-spi2-registr[2311]: AT-SPI: Cannot open default display
[  120.101646] localhost.localdomain clock-applet[2005]: AT-SPI: Could not obtain desktop path or name
[  120.102034] localhost.localdomain mate-session[1830]: WARNING: AT-SPI: Could not obtain desktop path or name
[  120.102176] localhost.localdomain stickynotes-app[1999]: AT-SPI: Could not obtain desktop path or name
[  120.102349] localhost.localdomain mate-menu[2000]: AT-SPI: Could not obtain desktop path or name
[  120.102514] localhost.localdomain notification-ar[2008]: AT-SPI: Could not obtain desktop path or name
[  120.102677] localhost.localdomain mate-volume-con[2007]: AT-SPI: Could not obtain desktop path or name
[  120.102889] localhost.localdomain mate-terminal[2270]: AT-SPI: Could not obtain desktop path or name
[  120.103630] localhost.localdomain mate-terminal[2270]: AT-SPI: Could not obtain desktop path or name
[  120.106900] localhost.localdomain wnck-applet[2006]: AT-SPI: Could not obtain desktop path or name
[  131.974857] localhost.localdomain sudo[2334]: gkr-pam: unable to locate daemon control file
[  131.976408] localhost.localdomain sudo[2334]: gkr-pam: stashed password to try later in open session

MrNice · June 13, 2023, 4:12pm

Then added some widgets, repo and media codecs as follow

sudo zypper ar -cfp 90 http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Leap_15.4/ packman
sudo zypper install flatpak
flatpak remote-add --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo
sudo zypper refresh
sudo zypper dist-upgrade --from packman --allow-vendor-change
sudo zypper install --from packman ffmpeg gstreamer-plugins-{good,bad,ugly,libav} libavcodec-full vlc-codecs

Boot record

[   88.025748] localhost.localdomain systemd[1751]: Starting Virtual filesystem metadata service...
[   88.052512] localhost.localdomain dbus-daemon[1802]: [session uid=1000 pid=1802] Successfully activated service 'org.gtk.vfs.Metadata'
[   88.054822] localhost.localdomain systemd[1751]: Started Virtual filesystem metadata service.
[   88.089248] localhost.localdomain at-spi-bus-launcher[1875]: dbus-daemon[1875]: Activating service name='org.a11y.atspi.Registry' requested by ':1.24' (uid=1000 pid=1947 comm="/usr/bin/caja ")
[   88.102125] localhost.localdomain at-spi-bus-launcher[2317]: No protocol specified
[   88.102125] localhost.localdomain at-spi-bus-launcher[2317]: No protocol specified
[   88.103172] localhost.localdomain at-spi2-registr[2317]: Could not open X display
[   88.107033] localhost.localdomain at-spi-bus-launcher[1875]: dbus-daemon[1875]: Successfully activated service 'org.a11y.atspi.Registry'
[   88.110502] localhost.localdomain at-spi-bus-launcher[2317]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
[   88.110502] localhost.localdomain at-spi-bus-launcher[2317]: No protocol specified
[   88.111000] localhost.localdomain at-spi-bus-launcher[2317]: No protocol specified
[   88.111243] localhost.localdomain at-spi2-registr[2317]: AT-SPI: Cannot open default display
[   88.115228] localhost.localdomain wnck-applet[1960]: AT-SPI: Could not obtain desktop path or name
[   88.116415] localhost.localdomain mate-session[1777]: WARNING: AT-SPI: Could not obtain desktop path or name
[   88.116679] localhost.localdomain trashapplet[1964]: AT-SPI: Could not obtain desktop path or name
[   88.116963] localhost.localdomain mate-volume-con[1963]: AT-SPI: Could not obtain desktop path or name
[   88.117234] localhost.localdomain clock-applet[2183]: AT-SPI: Could not obtain desktop path or name
[   88.117714] localhost.localdomain notification-ar[2173]: AT-SPI: Could not obtain desktop path or name
[   88.153199] localhost.localdomain at-spi-bus-launcher[1875]: dbus-daemon[1875]: Activating service name='org.a11y.atspi.Registry' requested by ':1.24' (uid=1000 pid=1947 comm="/usr/bin/caja ")
[   88.159585] localhost.localdomain at-spi-bus-launcher[2319]: No protocol specified
[   88.160652] localhost.localdomain at-spi-bus-launcher[2319]: No protocol specified
[   88.160946] localhost.localdomain at-spi2-registr[2319]: Could not open X display
[   88.165113] localhost.localdomain at-spi-bus-launcher[1875]: dbus-daemon[1875]: Successfully activated service 'org.a11y.atspi.Registry'
[   88.169347] localhost.localdomain at-spi-bus-launcher[2319]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
[   88.169347] localhost.localdomain at-spi-bus-launcher[2319]: No protocol specified
[   88.169347] localhost.localdomain at-spi-bus-launcher[2319]: No protocol specified
[   88.170205] localhost.localdomain at-spi2-registr[2319]: AT-SPI: Cannot open default display
[   88.176848] localhost.localdomain trashapplet[1964]: AT-SPI: Could not obtain desktop path or name
[   88.177628] localhost.localdomain mate-session[1777]: WARNING: AT-SPI: Could not obtain desktop path or name
[   88.177922] localhost.localdomain wnck-applet[1960]: AT-SPI: Could not obtain desktop path or name
[   88.178273] localhost.localdomain clock-applet[2183]: AT-SPI: Could not obtain desktop path or name
[   88.178562] localhost.localdomain mate-volume-con[1963]: AT-SPI: Could not obtain desktop path or name
[   88.178839] localhost.localdomain notification-ar[2173]: AT-SPI: Could not obtain desktop path or name
[  102.008951] localhost.localdomain wnck-applet[1960]: Negative content width -1 (allocation 1, extents 1x1) while allocating gadget (node button, owner WnckButton)
[  102.017903] localhost.localdomain wnck-applet[1960]: Negative content width -1 (allocation 1, extents 1x1) while allocating gadget (node button, owner WnckButton)
[  102.313330] localhost.localdomain at-spi-bus-launcher[1875]: dbus-daemon[1875]: Activating service name='org.a11y.atspi.Registry' requested by ':1.87' (uid=1000 pid=2320 comm="mate-terminal ")
[  102.325926] localhost.localdomain at-spi-bus-launcher[2327]: No protocol specified
[  102.326972] localhost.localdomain at-spi-bus-launcher[2327]: No protocol specified
[  102.327189] localhost.localdomain at-spi2-registr[2327]: Could not open X display
[  102.333210] localhost.localdomain at-spi-bus-launcher[1875]: dbus-daemon[1875]: Successfully activated service 'org.a11y.atspi.Registry'
[  102.337086] localhost.localdomain at-spi-bus-launcher[2327]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
[  102.338414] localhost.localdomain at-spi-bus-launcher[2327]: No protocol specified
[  102.339177] localhost.localdomain at-spi-bus-launcher[2327]: No protocol specified
[  102.339444] localhost.localdomain at-spi2-registr[2327]: AT-SPI: Cannot open default display
[  102.342642] localhost.localdomain clock-applet[2183]: AT-SPI: Could not obtain desktop path or name
[  102.343439] localhost.localdomain mate-session[1777]: WARNING: AT-SPI: Could not obtain desktop path or name
[  102.344101] localhost.localdomain mate-volume-con[1963]: AT-SPI: Could not obtain desktop path or name
[  102.344816] localhost.localdomain trashapplet[1964]: AT-SPI: Could not obtain desktop path or name
[  102.345515] localhost.localdomain wnck-applet[1960]: AT-SPI: Could not obtain desktop path or name
[  102.346967] localhost.localdomain notification-ar[2173]: AT-SPI: Could not obtain desktop path or name
[  103.017731] localhost.localdomain at-spi-bus-launcher[1875]: dbus-daemon[1875]: Activating service name='org.a11y.atspi.Registry' requested by ':1.87' (uid=1000 pid=2320 comm="mate-terminal ")
[  103.033116] localhost.localdomain at-spi-bus-launcher[2357]: No protocol specified
[  103.035369] localhost.localdomain at-spi-bus-launcher[2357]: No protocol specified
[  103.035640] localhost.localdomain at-spi2-registr[2357]: Could not open X display
[  103.043276] localhost.localdomain at-spi-bus-launcher[1875]: dbus-daemon[1875]: Successfully activated service 'org.a11y.atspi.Registry'
[  103.044700] localhost.localdomain at-spi-bus-launcher[2357]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
[  103.048565] localhost.localdomain at-spi-bus-launcher[2357]: No protocol specified
[  103.084609] localhost.localdomain at-spi-bus-launcher[2357]: No protocol specified
[  103.084887] localhost.localdomain at-spi2-registr[2357]: AT-SPI: Cannot open default display
[  103.088666] localhost.localdomain clock-applet[2183]: AT-SPI: Could not obtain desktop path or name
[  103.089015] localhost.localdomain notification-ar[2173]: AT-SPI: Could not obtain desktop path or name
[  103.089249] localhost.localdomain mate-volume-con[1963]: AT-SPI: Could not obtain desktop path or name
[  103.089481] localhost.localdomain trashapplet[1964]: AT-SPI: Could not obtain desktop path or name
[  103.090908] localhost.localdomain mate-session[1777]: WARNING: AT-SPI: Could not obtain desktop path or name
[  103.100668] localhost.localdomain at-spi-bus-launcher[1875]: dbus-daemon[1875]: Activating service name='org.a11y.atspi.Registry' requested by ':1.18' (uid=1000 pid=1960 comm="/usr/lib/mate-panel/wnck-applet ")
[  103.123428] localhost.localdomain at-spi-bus-launcher[2361]: No protocol specified
[  103.127330] localhost.localdomain at-spi-bus-launcher[2361]: No protocol specified
[  103.127616] localhost.localdomain at-spi2-registr[2361]: Could not open X display
[  103.134416] localhost.localdomain at-spi-bus-launcher[1875]: dbus-daemon[1875]: Successfully activated service 'org.a11y.atspi.Registry'
[  103.137982] localhost.localdomain at-spi-bus-launcher[2361]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
[  103.149248] localhost.localdomain at-spi-bus-launcher[2361]: No protocol specified
[  103.152285] localhost.localdomain at-spi-bus-launcher[2361]: No protocol specified
[  103.152580] localhost.localdomain at-spi2-registr[2361]: AT-SPI: Cannot open default display
[  103.156612] localhost.localdomain clock-applet[2183]: AT-SPI: Could not obtain desktop path or name
[  103.156969] localhost.localdomain notification-ar[2173]: AT-SPI: Could not obtain desktop path or name
[  103.157208] localhost.localdomain mate-volume-con[1963]: AT-SPI: Could not obtain desktop path or name
[  103.157452] localhost.localdomain trashapplet[1964]: AT-SPI: Could not obtain desktop path or name
[  103.157682] localhost.localdomain mate-session[1777]: WARNING: AT-SPI: Could not obtain desktop path or name
[  103.164589] localhost.localdomain wnck-applet[1960]: AT-SPI: Could not obtain desktop path or name
[  103.165414] localhost.localdomain wnck-applet[1960]: AT-SPI: Could not obtain desktop path or name
[  113.716879] localhost.localdomain chronyd[1144]: Selected source 94.23.215.121 (1.opensuse.pool.ntp.org)
[  154.060661] localhost.localdomain sudo[2386]: gkr-pam: unable to locate daemon control file
[  154.062229] localhost.localdomain sudo[2386]: gkr-pam: stashed password to try later in open session

MrNice · June 13, 2023, 4:13pm

Shut down, Start only
Boot record

[   77.849347] localhost.localdomain dbus-daemon[650]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)
[   77.850592] localhost.localdomain pulseaudio[1894]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[   80.866660] localhost.localdomain systemd[1]: systemd-hostnamed.service: Deactivated successfully.
[   81.157683] localhost.localdomain at-spi-bus-launcher[1856]: dbus-daemon[1856]: Activating service name='org.a11y.atspi.Registry' requested by ':1.30' (uid=1000 pid=1925 comm="/usr/bin/caja ")
[   81.167445] localhost.localdomain dbus-daemon[1800]: [session uid=1000 pid=1800] Successfully activated service 'org.freedesktop.FileManager1'
[   81.168246] localhost.localdomain at-spi-bus-launcher[2240]: No protocol specified
[   81.169199] localhost.localdomain at-spi-bus-launcher[2240]: No protocol specified
[   81.169379] localhost.localdomain at-spi2-registr[2240]: Could not open X display
[   81.189466] localhost.localdomain dbus-daemon[1800]: [session uid=1000 pid=1800] Activating via systemd: service name='org.freedesktop.impl.portal.desktop.gtk' unit='xdg-desktop-portal-gtk.service' requested by ':1.61' (uid=1000 pid=2003 comm="/usr/lib/xdg-desktop-portal ")
[   81.189835] localhost.localdomain systemd[1749]: Starting Portal service (GTK+/GNOME implementation)...
[   81.201497] localhost.localdomain at-spi-bus-launcher[1856]: dbus-daemon[1856]: Successfully activated service 'org.a11y.atspi.Registry'
[   81.204016] localhost.localdomain at-spi-bus-launcher[2240]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
[   81.210787] localhost.localdomain at-spi-bus-launcher[2240]: No protocol specified
[   81.218766] localhost.localdomain at-spi-bus-launcher[2240]: No protocol specified
[   81.219081] localhost.localdomain mate-session[1793]: WARNING: AT-SPI: Could not obtain desktop path or name
[   81.219782] localhost.localdomain at-spi2-registr[2240]: AT-SPI: Cannot open default display
[   81.220041] localhost.localdomain trashapplet[1936]: AT-SPI: Could not obtain desktop path or name
[   81.220731] localhost.localdomain clock-applet[2161]: AT-SPI: Could not obtain desktop path or name
[   81.221401] localhost.localdomain notification-ar[2151]: AT-SPI: Could not obtain desktop path or name
[   81.222065] localhost.localdomain wnck-applet[1932]: AT-SPI: Could not obtain desktop path or name
[   81.222769] localhost.localdomain mate-volume-con[1935]: AT-SPI: Could not obtain desktop path or name
[   81.236598] localhost.localdomain at-spi-bus-launcher[1856]: dbus-daemon[1856]: Activating service name='org.a11y.atspi.Registry' requested by ':1.30' (uid=1000 pid=1925 comm="/usr/bin/caja ")
[   81.251129] localhost.localdomain at-spi-bus-launcher[2251]: No protocol specified
[   81.251942] localhost.localdomain xdg-desktop-portal-gtk[2246]: No protocol specified
[   81.255227] localhost.localdomain at-spi-bus-launcher[2251]: No protocol specified
[   81.256072] localhost.localdomain at-spi2-registr[2251]: Could not open X display
[   81.265460] localhost.localdomain at-spi-bus-launcher[1856]: dbus-daemon[1856]: Successfully activated service 'org.a11y.atspi.Registry'
[   81.268720] localhost.localdomain at-spi-bus-launcher[2251]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
[   81.269979] localhost.localdomain at-spi-bus-launcher[2251]: No protocol specified
[   81.270784] localhost.localdomain at-spi-bus-launcher[2251]: No protocol specified
[   81.271317] localhost.localdomain at-spi2-registr[2251]: AT-SPI: Cannot open default display
[   81.278648] localhost.localdomain clock-applet[2161]: AT-SPI: Could not obtain desktop path or name
[   81.279037] localhost.localdomain mate-session[1793]: WARNING: AT-SPI: Could not obtain desktop path or name
[   81.279224] localhost.localdomain notification-ar[2151]: AT-SPI: Could not obtain desktop path or name
[   81.279467] localhost.localdomain trashapplet[1936]: AT-SPI: Could not obtain desktop path or name
[   81.279701] localhost.localdomain wnck-applet[1932]: AT-SPI: Could not obtain desktop path or name
[   81.279933] localhost.localdomain mate-volume-con[1935]: AT-SPI: Could not obtain desktop path or name
[   81.292816] localhost.localdomain at-spi-bus-launcher[1856]: dbus-daemon[1856]: Activating service name='org.a11y.atspi.Registry' requested by ':1.30' (uid=1000 pid=1925 comm="/usr/bin/caja ")
[   81.307127] localhost.localdomain at-spi-bus-launcher[2255]: No protocol specified
[   81.308885] localhost.localdomain at-spi-bus-launcher[2255]: No protocol specified
[   81.310336] localhost.localdomain at-spi2-registr[2255]: Could not open X display
[   81.320845] localhost.localdomain at-spi-bus-launcher[1856]: dbus-daemon[1856]: Successfully activated service 'org.a11y.atspi.Registry'
[   81.325332] localhost.localdomain at-spi-bus-launcher[2255]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
[   81.326726] localhost.localdomain at-spi-bus-launcher[2255]: No protocol specified
[   81.326726] localhost.localdomain at-spi-bus-launcher[2255]: No protocol specified
[   81.327168] localhost.localdomain at-spi2-registr[2255]: AT-SPI: Cannot open default display
[   81.329208] localhost.localdomain trashapplet[1936]: AT-SPI: Could not obtain desktop path or name
[   81.329551] localhost.localdomain clock-applet[2161]: AT-SPI: Could not obtain desktop path or name
[   81.329786] localhost.localdomain notification-ar[2151]: AT-SPI: Could not obtain desktop path or name
[   81.330404] localhost.localdomain wnck-applet[1932]: AT-SPI: Could not obtain desktop path or name
[   81.330720] localhost.localdomain mate-volume-con[1935]: AT-SPI: Could not obtain desktop path or name
[   81.332517] localhost.localdomain mate-session[1793]: WARNING: AT-SPI: Could not obtain desktop path or name
[   81.363447] localhost.localdomain xdg-desktop-por[2246]: Theme parsing error: gtk.css:7602:21: Not using units is deprecated. Assuming 'px'.
[   81.474318] localhost.localdomain xdg-desktop-portal-gtk[2246]: No protocol specified
[   81.486169] localhost.localdomain at-spi-bus-launcher[1856]: dbus-daemon[1856]: Activating service name='org.a11y.atspi.Registry' requested by ':1.76' (uid=1000 pid=2246 comm="/usr/lib/xdg-desktop-portal-gtk ")
[   81.502231] localhost.localdomain at-spi-bus-launcher[2258]: No protocol specified
[   81.503992] localhost.localdomain at-spi-bus-launcher[2258]: No protocol specified
[   81.504549] localhost.localdomain at-spi2-registr[2258]: Could not open X display
[   81.512356] localhost.localdomain at-spi-bus-launcher[1856]: dbus-daemon[1856]: Successfully activated service 'org.a11y.atspi.Registry'
[   81.517284] localhost.localdomain at-spi-bus-launcher[2258]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
[   81.518312] localhost.localdomain at-spi-bus-launcher[2258]: No protocol specified
[   81.520548] localhost.localdomain at-spi-bus-launcher[2258]: No protocol specified
[   81.520807] localhost.localdomain at-spi2-registr[2258]: AT-SPI: Cannot open default display
[   81.525085] localhost.localdomain mate-session[1793]: WARNING: AT-SPI: Could not obtain desktop path or name
[   81.525325] localhost.localdomain notification-ar[2151]: AT-SPI: Could not obtain desktop path or name
[   81.525542] localhost.localdomain trashapplet[1936]: AT-SPI: Could not obtain desktop path or name
[   81.525725] localhost.localdomain clock-applet[2161]: AT-SPI: Could not obtain desktop path or name
[   81.525900] localhost.localdomain wnck-applet[1932]: AT-SPI: Could not obtain desktop path or name
[   81.526061] localhost.localdomain mate-volume-con[1935]: AT-SPI: Could not obtain desktop path or name
[   81.561423] localhost.localdomain dbus-daemon[1800]: [session uid=1000 pid=1800] Successfully activated service 'org.freedesktop.impl.portal.desktop.gtk'
[   81.561703] localhost.localdomain systemd[1749]: Started Portal service (GTK+/GNOME implementation).
[   81.565909] localhost.localdomain xdg-desktop-por[2246]: AT-SPI: Could not obtain desktop path or name
[   81.567737] localhost.localdomain at-spi-bus-launcher[1856]: dbus-daemon[1856]: Activating service name='org.a11y.atspi.Registry' requested by ':1.76' (uid=1000 pid=2246 comm="/usr/lib/xdg-desktop-portal-gtk ")
[   81.585125] localhost.localdomain at-spi-bus-launcher[2261]: No protocol specified
[   81.586634] localhost.localdomain at-spi-bus-launcher[2261]: No protocol specified
[   81.587134] localhost.localdomain at-spi2-registr[2261]: Could not open X display
[   81.593030] localhost.localdomain at-spi-bus-launcher[1856]: dbus-daemon[1856]: Successfully activated service 'org.a11y.atspi.Registry'
[   81.597075] localhost.localdomain at-spi-bus-launcher[2261]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
[   81.598613] localhost.localdomain at-spi-bus-launcher[2261]: No protocol specified
[   81.599654] localhost.localdomain at-spi-bus-launcher[2261]: No protocol specified
[   81.600058] localhost.localdomain at-spi2-registr[2261]: AT-SPI: Cannot open default display
[   81.605113] localhost.localdomain xdg-desktop-por[2246]: AT-SPI: Could not obtain desktop path or name
[   81.605564] localhost.localdomain mate-session[1793]: WARNING: AT-SPI: Could not obtain desktop path or name
[   81.605832] localhost.localdomain xdg-desktop-por[2246]: atk-bridge: get_device_events_reply: unknown signature
[   81.606319] localhost.localdomain xdg-desktop-por[2246]: atk-bridge: get_device_events_reply: unknown signature
[   81.606746] localhost.localdomain xdg-desktop-por[2246]: atk-bridge: GetRegisteredEvents returned message with unknown signature
[   81.607162] localhost.localdomain clock-applet[2161]: AT-SPI: Could not obtain desktop path or name
[   81.607520] localhost.localdomain notification-ar[2151]: AT-SPI: Could not obtain desktop path or name
[   81.607902] localhost.localdomain trashapplet[1936]: AT-SPI: Could not obtain desktop path or name
[   81.608268] localhost.localdomain wnck-applet[1932]: AT-SPI: Could not obtain desktop path or name
[   81.608606] localhost.localdomain mate-volume-con[1935]: AT-SPI: Could not obtain desktop path or name
[   81.610619] localhost.localdomain at-spi-bus-launcher[1856]: dbus-daemon[1856]: Activating service name='org.a11y.atspi.Registry' requested by ':1.76' (uid=1000 pid=2246 comm="/usr/lib/xdg-desktop-portal-gtk ")
[   81.633056] localhost.localdomain at-spi-bus-launcher[2263]: No protocol specified
[   81.635847] localhost.localdomain at-spi-bus-launcher[2263]: No protocol specified
[   81.636811] localhost.localdomain at-spi2-registr[2263]: Could not open X display
[   81.642793] localhost.localdomain at-spi-bus-launcher[1856]: dbus-daemon[1856]: Successfully activated service 'org.a11y.atspi.Registry'
[   81.646536] localhost.localdomain at-spi-bus-launcher[2263]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
[   81.646536] localhost.localdomain at-spi-bus-launcher[2263]: No protocol specified
[   81.646536] localhost.localdomain at-spi-bus-launcher[2263]: No protocol specified
[   81.647111] localhost.localdomain at-spi2-registr[2263]: AT-SPI: Cannot open default display
[   81.649818] localhost.localdomain at-spi-bus-launcher[1856]: dbus-daemon[1856]: Activating service name='org.a11y.atspi.Registry' requested by ':1.76' (uid=1000 pid=2246 comm="/usr/lib/xdg-desktop-portal-gtk ")
[   81.652605] localhost.localdomain xdg-desktop-por[2246]: atk-bridge: get_device_events_reply: unknown signature
[   81.652954] localhost.localdomain xdg-desktop-por[2246]: atk-bridge: get_device_events_reply: unknown signature
[   81.653177] localhost.localdomain xdg-desktop-por[2246]: atk-bridge: GetRegisteredEvents returned message with unknown signature
[   81.659137] localhost.localdomain at-spi-bus-launcher[2265]: No protocol specified
[   81.660330] localhost.localdomain at-spi-bus-launcher[2265]: No protocol specified
[   81.660811] localhost.localdomain at-spi2-registr[2265]: Could not open X display
[   81.665026] localhost.localdomain at-spi-bus-launcher[1856]: dbus-daemon[1856]: Successfully activated service 'org.a11y.atspi.Registry'
[   81.668179] localhost.localdomain at-spi-bus-launcher[2265]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
[   81.669196] localhost.localdomain at-spi-bus-launcher[2265]: No protocol specified
[   81.669994] localhost.localdomain at-spi-bus-launcher[2265]: No protocol specified
[   81.670588] localhost.localdomain at-spi2-registr[2265]: AT-SPI: Cannot open default display
[   81.674808] localhost.localdomain mate-session[1793]: WARNING: AT-SPI: Could not obtain desktop path or name
[   81.675818] localhost.localdomain trashapplet[1936]: AT-SPI: Could not obtain desktop path or name
[   81.677051] localhost.localdomain wnck-applet[1932]: AT-SPI: Could not obtain desktop path or name
[   81.677383] localhost.localdomain mate-volume-con[1935]: AT-SPI: Could not obtain desktop path or name
[   81.677608] localhost.localdomain notification-ar[2151]: AT-SPI: Could not obtain desktop path or name
[   81.677819] localhost.localdomain xdg-desktop-por[2246]: AT-SPI: Could not obtain desktop path or name
[   81.678732] localhost.localdomain clock-applet[2161]: AT-SPI: Could not obtain desktop path or name
[   81.679492] localhost.localdomain mate-volume-con[1935]: AT-SPI: Could not obtain desktop path or name
[   81.679805] localhost.localdomain wnck-applet[1932]: AT-SPI: Could not obtain desktop path or name
[   81.681410] localhost.localdomain notification-ar[2151]: AT-SPI: Could not obtain desktop path or name
[   81.681713] localhost.localdomain mate-session[1793]: WARNING: AT-SPI: Could not obtain desktop path or name
[   81.681858] localhost.localdomain xdg-desktop-por[2246]: AT-SPI: Could not obtain desktop path or name
[   81.682037] localhost.localdomain trashapplet[1936]: AT-SPI: Could not obtain desktop path or name
[   81.682199] localhost.localdomain clock-applet[2161]: AT-SPI: Could not obtain desktop path or name
[   81.766238] localhost.localdomain at-spi-bus-launcher[1856]: dbus-daemon[1856]: Activating service name='org.a11y.atspi.Registry' requested by ':1.30' (uid=1000 pid=1925 comm="/usr/bin/caja ")
[   81.778567] localhost.localdomain systemd[1749]: Started PipeWire Multimedia Service.
[   81.781470] localhost.localdomain systemd[1749]: Started Multimedia Service Session Manager.
[   81.784398] localhost.localdomain at-spi-bus-launcher[2267]: No protocol specified
[   81.784398] localhost.localdomain at-spi-bus-launcher[2267]: No protocol specified
[   81.785318] localhost.localdomain at-spi2-registr[2267]: Could not open X display
[   81.790649] localhost.localdomain at-spi-bus-launcher[1856]: dbus-daemon[1856]: Successfully activated service 'org.a11y.atspi.Registry'
[   81.794536] localhost.localdomain at-spi-bus-launcher[2267]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
[   81.799204] localhost.localdomain at-spi-bus-launcher[2267]: No protocol specified
[   81.799889] localhost.localdomain at-spi-bus-launcher[2267]: No protocol specified
[   81.800148] localhost.localdomain at-spi2-registr[2267]: AT-SPI: Cannot open default display
[   81.804372] localhost.localdomain wnck-applet[1932]: AT-SPI: Could not obtain desktop path or name
[   81.804740] localhost.localdomain mate-session[1793]: WARNING: AT-SPI: Could not obtain desktop path or name
[   81.804964] localhost.localdomain mate-volume-con[1935]: AT-SPI: Could not obtain desktop path or name
[   81.805236] localhost.localdomain xdg-desktop-por[2246]: AT-SPI: Could not obtain desktop path or name
[   81.805455] localhost.localdomain trashapplet[1936]: AT-SPI: Could not obtain desktop path or name
[   81.805666] localhost.localdomain notification-ar[2151]: AT-SPI: Could not obtain desktop path or name
[   81.805868] localhost.localdomain clock-applet[2161]: AT-SPI: Could not obtain desktop path or name
[   81.919475] localhost.localdomain rtkit-daemon[1909]: Successfully made thread 2269 of process 2269 (/usr/bin/pipewire) owned by 'test' high priority at nice level -11.
[   81.920094] localhost.localdomain rtkit-daemon[1909]: Supervising 3 threads of 2 processes of 1 users.
[   81.920982] localhost.localdomain rtkit-daemon[1909]: Supervising 3 threads of 2 processes of 1 users.
[   81.966514] localhost.localdomain rtkit-daemon[1909]: Supervising 3 threads of 2 processes of 1 users.
[   81.972424] localhost.localdomain rtkit-daemon[1909]: Successfully made thread 2271 of process 2269 (/usr/bin/pipewire) owned by 'test' RT at priority 20.
[   81.972648] localhost.localdomain rtkit-daemon[1909]: Supervising 4 threads of 2 processes of 1 users.
[   81.982214] localhost.localdomain dbus-daemon[1800]: [session uid=1000 pid=1800] Successfully activated service 'org.freedesktop.portal.Desktop'
[   81.984597] localhost.localdomain systemd[1749]: Started Portal service.
[   82.104361] localhost.localdomain rtkit-daemon[1909]: Successfully made thread 2270 of process 2270 (/usr/bin/wireplumber) owned by 'test' high priority at nice level -11.
[   82.104596] localhost.localdomain rtkit-daemon[1909]: Supervising 5 threads of 3 processes of 1 users.
[   82.105562] localhost.localdomain rtkit-daemon[1909]: Supervising 5 threads of 3 processes of 1 users.
[   82.108587] localhost.localdomain rtkit-daemon[1909]: Supervising 5 threads of 3 processes of 1 users.
[   82.115143] localhost.localdomain rtkit-daemon[1909]: Successfully made thread 2280 of process 2270 (/usr/bin/wireplumber) owned by 'test' RT at priority 20.
[   82.115364] localhost.localdomain rtkit-daemon[1909]: Supervising 6 threads of 3 processes of 1 users.
[   82.233425] localhost.localdomain wireplumber[2270]: Failed to set scheduler settings: Operation not permitted
[   82.513601] localhost.localdomain dbus-daemon[1800]: [session uid=1000 pid=1800] Activating via systemd: service name='org.gtk.vfs.Metadata' unit='gvfs-metadata.service' requested by ':1.42' (uid=1000 pid=1925 comm="/usr/bin/caja ")
[   82.713741] localhost.localdomain systemd[1749]: Starting Virtual filesystem metadata service...
[   82.739502] localhost.localdomain dbus-daemon[1800]: [session uid=1000 pid=1800] Successfully activated service 'org.gtk.vfs.Metadata'
[   82.741649] localhost.localdomain systemd[1749]: Started Virtual filesystem metadata service.
[  171.064348] localhost.localdomain wnck-applet[1932]: Negative content width -1 (allocation 1, extents 1x1) while allocating gadget (node button, owner WnckButton)
[  171.078207] localhost.localdomain wnck-applet[1932]: Negative content width -1 (allocation 1, extents 1x1) while allocating gadget (node button, owner WnckButton)
[  171.365900] localhost.localdomain at-spi-bus-launcher[1856]: dbus-daemon[1856]: Activating service name='org.a11y.atspi.Registry' requested by ':1.82' (uid=1000 pid=2299 comm="mate-terminal ")
[  171.378774] localhost.localdomain at-spi-bus-launcher[2306]: No protocol specified
[  171.379837] localhost.localdomain at-spi-bus-launcher[2306]: No protocol specified
[  171.379995] localhost.localdomain at-spi2-registr[2306]: Could not open X display
[  171.385114] localhost.localdomain at-spi-bus-launcher[1856]: dbus-daemon[1856]: Successfully activated service 'org.a11y.atspi.Registry'
[  171.389476] localhost.localdomain at-spi-bus-launcher[2306]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
[  171.390611] localhost.localdomain at-spi-bus-launcher[2306]: No protocol specified
[  171.391277] localhost.localdomain at-spi-bus-launcher[2306]: No protocol specified
[  171.391539] localhost.localdomain at-spi2-registr[2306]: AT-SPI: Cannot open default display
[  171.394643] localhost.localdomain mate-volume-con[1935]: AT-SPI: Could not obtain desktop path or name
[  171.395451] localhost.localdomain trashapplet[1936]: AT-SPI: Could not obtain desktop path or name
[  171.396104] localhost.localdomain notification-ar[2151]: AT-SPI: Could not obtain desktop path or name
[  171.396715] localhost.localdomain mate-session[1793]: WARNING: AT-SPI: Could not obtain desktop path or name
[  171.399692] localhost.localdomain wnck-applet[1932]: AT-SPI: Could not obtain desktop path or name
[  171.399946] localhost.localdomain clock-applet[2161]: AT-SPI: Could not obtain desktop path or name
[  172.057075] localhost.localdomain at-spi-bus-launcher[1856]: dbus-daemon[1856]: Activating service name='org.a11y.atspi.Registry' requested by ':1.82' (uid=1000 pid=2299 comm="mate-terminal ")
[  172.112047] localhost.localdomain at-spi-bus-launcher[2338]: No protocol specified
[  172.114436] localhost.localdomain at-spi-bus-launcher[2338]: No protocol specified
[  172.114698] localhost.localdomain at-spi2-registr[2338]: Could not open X display
[  172.121183] localhost.localdomain at-spi-bus-launcher[1856]: dbus-daemon[1856]: Successfully activated service 'org.a11y.atspi.Registry'
[  172.123604] localhost.localdomain at-spi-bus-launcher[2338]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
[  172.127135] localhost.localdomain at-spi-bus-launcher[2338]: No protocol specified
[  172.128303] localhost.localdomain at-spi-bus-launcher[2338]: No protocol specified
[  172.128583] localhost.localdomain at-spi2-registr[2338]: AT-SPI: Cannot open default display
[  172.131879] localhost.localdomain notification-ar[2151]: AT-SPI: Could not obtain desktop path or name
[  172.132265] localhost.localdomain clock-applet[2161]: AT-SPI: Could not obtain desktop path or name
[  172.132519] localhost.localdomain mate-volume-con[1935]: AT-SPI: Could not obtain desktop path or name
[  172.132740] localhost.localdomain trashapplet[1936]: AT-SPI: Could not obtain desktop path or name
[  172.135003] localhost.localdomain mate-session[1793]: WARNING: AT-SPI: Could not obtain desktop path or name
[  172.146654] localhost.localdomain at-spi-bus-launcher[1856]: dbus-daemon[1856]: Activating service name='org.a11y.atspi.Registry' requested by ':1.82' (uid=1000 pid=2299 comm="mate-terminal ")
[  172.163881] localhost.localdomain at-spi-bus-launcher[2346]: No protocol specified
[  172.177701] localhost.localdomain at-spi-bus-launcher[2346]: No protocol specified
[  172.177964] localhost.localdomain at-spi2-registr[2346]: Could not open X display
[  172.187914] localhost.localdomain at-spi-bus-launcher[1856]: dbus-daemon[1856]: Successfully activated service 'org.a11y.atspi.Registry'
[  172.190525] localhost.localdomain at-spi-bus-launcher[2346]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
[  172.192516] localhost.localdomain at-spi-bus-launcher[2346]: No protocol specified
[  172.195140] localhost.localdomain at-spi-bus-launcher[2346]: No protocol specified
[  172.195444] localhost.localdomain at-spi2-registr[2346]: AT-SPI: Cannot open default display
[  172.198019] localhost.localdomain mate-session[1793]: WARNING: AT-SPI: Could not obtain desktop path or name
[  172.198285] localhost.localdomain clock-applet[2161]: AT-SPI: Could not obtain desktop path or name
[  172.198565] localhost.localdomain notification-ar[2151]: AT-SPI: Could not obtain desktop path or name
[  172.198797] localhost.localdomain mate-volume-con[1935]: AT-SPI: Could not obtain desktop path or name
[  172.199065] localhost.localdomain trashapplet[1936]: AT-SPI: Could not obtain desktop path or name
[  172.201052] localhost.localdomain wnck-applet[1932]: AT-SPI: Could not obtain desktop path or name
[  172.203233] localhost.localdomain at-spi-bus-launcher[1856]: dbus-daemon[1856]: Activating service name='org.a11y.atspi.Registry' requested by ':1.26' (uid=1000 pid=1932 comm="/usr/lib/mate-panel/wnck-applet ")
[  172.228289] localhost.localdomain at-spi-bus-launcher[2350]: No protocol specified
[  172.228289] localhost.localdomain at-spi-bus-launcher[2350]: No protocol specified
[  172.229330] localhost.localdomain at-spi2-registr[2350]: Could not open X display
[  172.241956] localhost.localdomain at-spi-bus-launcher[1856]: dbus-daemon[1856]: Successfully activated service 'org.a11y.atspi.Registry'
[  172.247539] localhost.localdomain at-spi-bus-launcher[2350]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
[  172.262676] localhost.localdomain at-spi-bus-launcher[2350]: No protocol specified
[  172.263875] localhost.localdomain at-spi-bus-launcher[2350]: No protocol specified
[  172.264156] localhost.localdomain at-spi2-registr[2350]: AT-SPI: Cannot open default display
[  172.267755] localhost.localdomain clock-applet[2161]: AT-SPI: Could not obtain desktop path or name
[  172.268107] localhost.localdomain notification-ar[2151]: AT-SPI: Could not obtain desktop path or name
[  172.268348] localhost.localdomain mate-volume-con[1935]: AT-SPI: Could not obtain desktop path or name
[  172.268571] localhost.localdomain trashapplet[1936]: AT-SPI: Could not obtain desktop path or name
[  172.270856] localhost.localdomain wnck-applet[1932]: AT-SPI: Could not obtain desktop path or name
[  172.271256] localhost.localdomain mate-session[1793]: WARNING: AT-SPI: Could not obtain desktop path or name
[  172.271456] localhost.localdomain wnck-applet[1932]: AT-SPI: Could not obtain desktop path or name
[  172.382562] localhost.localdomain at-spi-bus-launcher[1856]: dbus-daemon[1856]: Activating service name='org.a11y.atspi.Registry' requested by ':1.30' (uid=1000 pid=1925 comm="/usr/bin/caja ")
[  172.399141] localhost.localdomain at-spi-bus-launcher[2363]: No protocol specified
[  172.407716] localhost.localdomain at-spi-bus-launcher[2363]: No protocol specified
[  172.408310] localhost.localdomain at-spi2-registr[2363]: Could not open X display
[  172.414656] localhost.localdomain at-spi-bus-launcher[1856]: dbus-daemon[1856]: Successfully activated service 'org.a11y.atspi.Registry'
[  172.418014] localhost.localdomain at-spi-bus-launcher[2363]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
[  172.418998] localhost.localdomain at-spi-bus-launcher[2363]: No protocol specified
[  172.420587] localhost.localdomain at-spi-bus-launcher[2363]: No protocol specified
[  172.421373] localhost.localdomain at-spi2-registr[2363]: AT-SPI: Cannot open default display
[  172.425603] localhost.localdomain trashapplet[1936]: AT-SPI: Could not obtain desktop path or name
[  172.426734] localhost.localdomain mate-session[1793]: WARNING: AT-SPI: Could not obtain desktop path or name
[  172.427454] localhost.localdomain mate-volume-con[1935]: AT-SPI: Could not obtain desktop path or name
[  172.428141] localhost.localdomain clock-applet[2161]: AT-SPI: Could not obtain desktop path or name
[  172.429364] localhost.localdomain wnck-applet[1932]: AT-SPI: Could not obtain desktop path or name
[  172.429582] localhost.localdomain notification-ar[2151]: AT-SPI: Could not obtain desktop path or name
[  181.917511] localhost.localdomain sudo[2371]: gkr-pam: unable to locate daemon control file
[  181.918727] localhost.localdomain sudo[2371]: gkr-pam: stashed password to try later in open session

I have the issue now.
Could someone look at the boot logs and try to find the issue?

MrNice · June 16, 2023, 12:02pm

Nobody to help me
I carry on with my desktop and my test laptop.
On the laptop, new install again, added Mate panels, etc… still good, I can’t get the issue and don’t know what to do more.
On my Desktop, I removed all the widgets kept only the bottom empty panel, still the issue. I don’t know what to do more.

MrNice · June 16, 2023, 1:59pm

Played around wit dconf dump and dconf load.
Removed all widgets, top panel bottom panel…
Issue is still here.
BTW, dcong load is not working fine all the time, need to load again few times to get it right.

I need help, please !!!

marel · June 18, 2023, 5:48am

Just post the output of “sudo systemd-analyze”, “systemd-analyze critical-chain” and “sudo systemd-analyze blame”.

Does that give a better clue on what is holding up?

MrNice · June 20, 2023, 1:02pm

From restart (not shutdown).
I counted ~9s after the pointer (arrow) appears to get the background image then ~16s more to get the icons in the desktop.
I can’t really see any clue in the output

~> sudo systemd-analyze
[sudo] password for root: 
Startup finished in 17.443s (firmware) + 1.404s (loader) + 784ms (kernel) + 4.022s (initrd) + 1.772s (userspace) = 25.428s 
graphical.target reached after 1.763s in userspace

~> systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @1.763s
└─display-manager.service @896ms +866ms
  └─time-sync.target @894ms
    └─chronyd.service @832ms +61ms
      └─network.target @831ms
        └─NetworkManager.service @812ms +18ms
          └─network-pre.target @811ms
            └─firewalld.service @542ms +268ms
              └─polkit.service @498ms +42ms
                └─basic.target @490ms
                  └─sockets.target @490ms
                    └─pcscd.socket @490ms
                      └─sysinit.target @489ms
                        └─systemd-update-utmp.service @484ms +4ms
                          └─auditd.service @453ms +30ms
                            └─systemd-tmpfiles-setup.service @437ms +14ms
                              └─local-fs.target @434ms
                                └─boot-efi.mount @335ms +97ms
                                  └─systemd-fsck@dev-disk-by\x2duuid-12B5\x2dE240.service @315ms +19ms
                                    └─dev-disk-by\x2duuid-12B5\x2dE240.device @584542y 2w 2d 20h 1min 45.878s +3.988s

~> sudo systemd-analyze blame
[sudo] password for root: 
4.098s dev-ttyS1.device
4.098s sys-devices-platform-serial8250-tty-ttyS1.device
4.097s sys-devices-platform-serial8250-tty-ttyS0.device
4.097s dev-ttyS0.device
4.097s dev-ttyS10.device
4.097s sys-devices-platform-serial8250-tty-ttyS10.device
4.097s sys-devices-platform-serial8250-tty-ttyS12.device
4.097s dev-ttyS12.device
4.096s sys-devices-platform-serial8250-tty-ttyS11.device
4.096s dev-ttyS11.device
4.096s dev-ttyS22.device
4.096s sys-devices-platform-serial8250-tty-ttyS22.device
4.096s dev-ttyS25.device
4.096s sys-devices-platform-serial8250-tty-ttyS25.device
4.096s dev-ttyS18.device
4.096s sys-devices-platform-serial8250-tty-ttyS18.device
4.096s sys-devices-platform-serial8250-tty-ttyS15.device
4.096s dev-ttyS15.device
4.095s dev-ttyS14.device
4.095s sys-devices-platform-serial8250-tty-ttyS14.device
4.095s sys-devices-platform-serial8250-tty-ttyS16.device
4.095s dev-ttyS16.device
4.095s dev-ttyS23.device
4.095s sys-devices-platform-serial8250-tty-ttyS23.device
4.095s dev-ttyS20.device
4.095s sys-devices-platform-serial8250-tty-ttyS20.device
4.095s sys-devices-platform-serial8250-tty-ttyS17.device
4.095s dev-ttyS17.device
4.095s sys-devices-platform-serial8250-tty-ttyS27.device
4.095s dev-ttyS27.device
4.095s sys-devices-platform-serial8250-tty-ttyS21.device
4.095s dev-ttyS21.device
4.094s dev-ttyS29.device
4.094s sys-devices-platform-serial8250-tty-ttyS29.device
4.093s sys-devices-platform-serial8250-tty-ttyS26.device
4.093s dev-ttyS26.device
4.093s sys-devices-platform-serial8250-tty-ttyS19.device
4.093s dev-ttyS19.device
4.093s dev-ttyS28.device
4.093s sys-devices-platform-serial8250-tty-ttyS28.device
4.092s sys-devices-platform-serial8250-tty-ttyS3.device
4.092s dev-ttyS3.device
4.092s sys-devices-platform-serial8250-tty-ttyS4.device
4.092s dev-ttyS4.device
4.092s dev-ttyS30.device
4.092s sys-devices-platform-serial8250-tty-ttyS30.device
4.092s sys-devices-platform-serial8250-tty-ttyS31.device
4.092s dev-ttyS31.device
4.091s dev-ttyS2.device
4.091s sys-devices-platform-serial8250-tty-ttyS2.device
4.091s dev-ttyS6.device
4.091s sys-devices-platform-serial8250-tty-ttyS6.device
4.091s sys-devices-platform-serial8250-tty-ttyS7.device
4.091s dev-ttyS7.device
4.091s dev-ttyS5.device
4.091s sys-devices-platform-serial8250-tty-ttyS5.device
4.091s dev-ttyS8.device
4.091s sys-devices-platform-serial8250-tty-ttyS8.device
4.090s sys-devices-platform-serial8250-tty-ttyS9.device
4.090s dev-ttyS9.device
4.089s dev-ttyS24.device
4.089s sys-devices-platform-serial8250-tty-ttyS24.device
4.088s dev-ttyS13.device
4.088s sys-devices-platform-serial8250-tty-ttyS13.device
3.988s dev-disk-by\x2dpartuuid-84ae0047\x2d1eb2\x2d4a96\x2dbe20\x2d75c1bd6c7ae2.device
3.988s sys-devices-pci0000:00-0000:00:02.2-0000:05:00.0-nvme-nvme0-nvme0n1-nvme0n1p1.device
3.988s dev-nvme0n1p1.device
3.988s dev-disk-by\x2did-nvme\x2dSamsung_SSD_980_1TB_S649NX0RC29102M\x2dpart1.device
3.988s dev-disk-by\x2did-nvme\x2deui.002538dc11b36118\x2dpart1.device
3.988s dev-disk-by\x2duuid-12B5\x2dE240.device
3.988s dev-disk-by\x2dpath-pci\x2d0000:05:00.0\x2dnvme\x2d1\x2dpart1.device
3.987s dev-disk-by\x2dpath-pci\x2d0000:05:00.0\x2dnvme\x2d1\x2dpart2.device
3.987s dev-disk-by\x2dpartuuid-92ea66bb\x2d027a\x2d4813\x2d861c\x2d8666298722db.device
3.987s sys-devices-pci0000:00-0000:00:02.2-0000:05:00.0-nvme-nvme0-nvme0n1-nvme0n1p2.device
3.987s dev-nvme0n1p2.device
3.987s dev-disk-by\x2did-nvme\x2deui.002538dc11b36118\x2dpart2.device
3.987s dev-disk-by\x2duuid-84f2d093\x2d61f4\x2d4802\x2dbbcd\x2d4118245a1093.device
3.987s dev-disk-by\x2did-nvme\x2dSamsung_SSD_980_1TB_S649NX0RC29102M\x2dpart2.device
3.986s dev-nvme0n1p4.device
3.986s sys-devices-pci0000:00-0000:00:02.2-0000:05:00.0-nvme-nvme0-nvme0n1-nvme0n1p4.device
3.986s dev-disk-by\x2duuid-2fe35d31\x2db3ea\x2d42aa\x2d9c8e\x2d56171e3eae0b.device
3.986s dev-disk-by\x2dpath-pci\x2d0000:05:00.0\x2dnvme\x2d1\x2dpart4.device
3.986s dev-disk-by\x2did-nvme\x2dSamsung_SSD_980_1TB_S649NX0RC29102M\x2dpart4.device
3.986s dev-disk-by\x2did-nvme\x2deui.002538dc11b36118\x2dpart4.device
3.986s dev-disk-by\x2dpartuuid-e8ff52b4\x2dc5da\x2d464a\x2d8f96\x2d54f47f15e3b7.device
3.985s dev-disk-by\x2dpath-pci\x2d0000:05:00.0\x2dnvme\x2d1.device
3.985s sys-devices-pci0000:00-0000:00:02.2-0000:05:00.0-nvme-nvme0-nvme0n1.device
3.985s dev-disk-by\x2did-nvme\x2dSamsung_SSD_980_1TB_S649NX0RC29102M.device
3.985s dev-nvme0n1.device
3.985s dev-disk-by\x2did-nvme\x2deui.002538dc11b36118.device
3.984s dev-disk-by\x2duuid-e80565f5\x2d87a0\x2d4dd7\x2d92aa\x2dd22791bb30db.device
3.984s dev-disk-by\x2did-nvme\x2dSamsung_SSD_980_1TB_S649NX0RC29102M\x2dpart3.device
3.984s dev-nvme0n1p3.device
3.984s sys-devices-pci0000:00-0000:00:02.2-0000:05:00.0-nvme-nvme0-nvme0n1-nvme0n1p3.device
3.984s dev-disk-by\x2did-nvme\x2deui.002538dc11b36118\x2dpart3.device
3.984s dev-disk-by\x2dpath-pci\x2d0000:05:00.0\x2dnvme\x2d1\x2dpart3.device
3.984s dev-disk-by\x2dpartuuid-2a0a4a50\x2df6ce\x2d4458\x2d96a6\x2da203ffdc2e4c.device
3.525s dracut-initqueue.service
1.640s dev-disk-by\x2dpath-pci\x2d0000:01:00.1\x2data\x2d2.device
1.640s dev-disk-by\x2did-scsi\x2d1ATA_WDC_WD40EFRX\x2d68N32N0_WD\x2dWCC7K3FP1KRD.device
1.640s dev-disk-by\x2did-scsi\x2d0ATA_WDC_WD40EFRX\x2d68N_WD\x2dWCC7K3FP1KRD.device
1.640s dev-disk-by\x2dpath-pci\x2d0000:01:00.1\x2data\x2d2.0.device
1.640s sys-devices-pci0000:00-0000:00:02.1-0000:01:00.1-ata2-host1-target1:0:0-1:0:0:0-block-sda.device
1.640s dev-sda.device
1.640s dev-disk-by\x2did-scsi\x2d350014ee2b936f586.device
1.640s dev-disk-by\x2did-scsi\x2dSATA_WDC_WD40EFRX\x2d68N_WD\x2dWCC7K3FP1KRD.device
1.640s dev-disk-by\x2did-wwn\x2d0x50014ee2b936f586.device
1.640s dev-disk-by\x2did-ata\x2dWDC_WD40EFRX\x2d68N32N0_WD\x2dWCC7K3FP1KRD.device
1.566s dev-disk-by\x2did-wwn\x2d0x50014ee2b936f586\x2dpart1.device
1.566s dev-disk-by\x2did-ata\x2dWDC_WD40EFRX\x2d68N32N0_WD\x2dWCC7K3FP1KRD\x2dpart1.device
1.566s sys-devices-pci0000:00-0000:00:02.1-0000:01:00.1-ata2-host1-target1:0:0-1:0:0:0-block-sda-sda1.device
1.566s dev-sda1.device
1.566s dev-disk-by\x2did-scsi\x2d0ATA_WDC_WD40EFRX\x2d68N_WD\x2dWCC7K3FP1KRD\x2dpart1.device
1.566s dev-disk-by\x2dpath-pci\x2d0000:01:00.1\x2data\x2d2.0\x2dpart1.device
1.566s dev-disk-by\x2dpartuuid-cf885473\x2d26f0\x2d447f\x2db9b7\x2d64c3ece0cac8.device
1.566s dev-disk-by\x2did-scsi\x2d1ATA_WDC_WD40EFRX\x2d68N32N0_WD\x2dWCC7K3FP1KRD\x2dpart1.device
1.566s dev-disk-by\x2duuid-2cb3710b\x2da5e3\x2d4c3b\x2db35e\x2d34629f7f6e55.device
1.566s dev-disk-by\x2dlabel-Store2.device
1.566s dev-disk-by\x2dpath-pci\x2d0000:01:00.1\x2data\x2d2\x2dpart1.device
1.566s dev-disk-by\x2did-scsi\x2dSATA_WDC_WD40EFRX\x2d68N_WD\x2dWCC7K3FP1KRD\x2dpart1.device
1.566s dev-disk-by\x2did-scsi\x2d350014ee2b936f586\x2dpart1.device
 866ms display-manager.service
 387ms plymouth-quit-wait.service
 332ms postfix.service
 275ms initrd-switch-root.service
 268ms firewalld.service
 117ms smartd.service
  97ms boot-efi.mount
  89ms user@1000.service
  84ms lvm2-monitor.service
  81ms initrd-parse-etc.service
  80ms udisks2.service
  61ms chronyd.service
  55ms upower.service
  43ms systemd-udevd.service
  42ms polkit.service
  41ms systemd-udev-trigger.service
  41ms augenrules.service
  37ms systemd-logind.service
  34ms ModemManager.service
  34ms sound-extra.service
  30ms auditd.service
  30ms kbdsettings.service
  29ms systemd-vconsole-setup.service
  29ms avahi-daemon.service
  28ms bluetooth.service
  28ms accounts-daemon.service
  28ms apparmor.service
  20ms dracut-cmdline.service
  20ms mcelog.service
  19ms systemd-fsck@dev-disk-by\x2duuid-12B5\x2dE240.service
  18ms plymouth-start.service
  18ms NetworkManager.service
  18ms plymouth-switch-root.service
  16ms klog.service
  16ms systemd-fsck-root.service
  16ms systemd-fsck@dev-disk-by\x2duuid-2fe35d31\x2db3ea\x2d42aa\x2d9c8e\x2d56171e3eae0b.service
  14ms systemd-tmpfiles-setup.service
  13ms systemd-tmpfiles-setup-dev.service
  11ms home.mount
  11ms dev-disk-by\x2duuid-84f2d093\x2d61f4\x2d4802\x2dbbcd\x2d4118245a1093.swap
  11ms plymouth-read-write.service
  11ms systemd-rfkill.service
  10ms systemd-random-seed.service
  10ms rsyslog.service
   9ms alsa-restore.service
   9ms systemd-journald.service
   8ms dracut-pre-udev.service
   8ms dev-hugepages.mount
   7ms modprobe@fuse.service
   7ms dev-mqueue.mount
   7ms systemd-update-utmp-runlevel.service
   7ms issue-generator.service
   7ms sys-kernel-debug.mount
   7ms sys-kernel-tracing.mount
   6ms initrd-cleanup.service
   6ms kmod-static-nodes.service
   6ms nscd.service
   5ms modprobe@configfs.service
   5ms modprobe@drm.service
   5ms systemd-remount-fs.service
   4ms user-runtime-dir@1000.service
   4ms systemd-update-utmp.service
   4ms systemd-backlight@backlight:acpi_video0.service
   3ms boot-sysctl.service
   3ms systemd-modules-load.service
   3ms systemd-journal-flush.service
   3ms systemd-sysctl.service
   3ms dracut-shutdown.service
   3ms rtkit-daemon.service
   2ms snapperd.service
   2ms initrd-udevadm-cleanup-db.service
   2ms sys-fs-fuse-connections.mount
   2ms systemd-user-sessions.service
   2ms sys-kernel-config.mount

gogalthorp · June 20, 2023, 1:10pm

Those commands only measure up to login but it appears you may be using auto-login Time to get from login to desktop has to be added to the analyze output

MrNice · June 20, 2023, 5:10pm

How to get this time in log?

gogalthorp · June 20, 2023, 10:32pm

Not sure there is a program to measure.

First off deactivate auto logon then see how long it takes to go from login screen full desktop of what ever desktop you use. Time will be different depending on Desktop used.Don’t believe you said which desktop???

MrNice · June 21, 2023, 9:33am

I use Leap 15.4 with MATE DE.
I tried without auto-login.
At password, when I press enter, the image background appears immediately then I have to wait 24-25 s to get the icons.

gogalthorp · June 21, 2023, 12:26pm

So the problem is with the MATE DE.

I’d try a different user and see if they have the same problem. Or try a different DE for debug purpose.

MrNice · June 21, 2023, 12:46pm

I am on the way to upgrade my laptop with same issue to Leap 15.5 MATE.
I’ll see what happen and let you know.