Error when starting MATE

Argentum

Argentum

Seems that I am running out of gunpowder investigating this issue. Need some advice.

When starting MATE, there is an error
Code: 
mate-session[90618]: WARNING: Unable to find provider '' of required component 'dock'
Seems that this causes a significant delay before the MATE starts. After that, everything seems normal. Have googled this and tried dconf-editor but without a progress.
 
judd said:
Remove.
Click to expand...
I do not see any way to remove it.

1735636645983.png

1735636681265.png
 
Argentum said:
Seems that I am running out of gunpowder investigating this issue. Need some advice.

When starting MATE, there is an error
Code: 
mate-session[90618]: WARNING: Unable to find provider '' of required component 'dock'
Seems that this causes a significant delay before the MATE starts. After that, everything seems normal. Have googled this and tried dconf-editor but without a progress.
Click to expand...
I found the same warning in /var/log/messages, but it doesn't hurt me.
Possibly depend on the performance of the computer, though.

Code: 
Dec 31 12:46:06 ********** mate-session[5814]: WARNING: Unable to find provider '' of required component 'dock'

(Host name is punched out with unmatched digits of "*".)

And it's a warning, not an error.

Just a possibility (I've not tested), but installing x11/mate-dock-applet could change the situation. But possibly making it worse.
At least, x11/mate-applets doesn't seem to contain anything having name "dock".
 
T-Aoki said:
Just a possibility (I've not tested), but installing x11/mate-dock-applet could change the situation. But possibly making it worse.
At least, x11/mate-applets doesn't seem to contain anything having name "dock".
Click to expand...
I did reinstall the x11/mate-dock-applet and the message disappeared. This is good, of-course.

Seems that I was wrong in my conclusions, what is causing the delay. Computer is better than average - with 6 cores, hyperthreading and 3.7GHz clock. The delay is still there and affects only one user. The other test user does not have this delay and also my other installation on a slower computer does not have it.

Now the delay moved to another location.

Code: 
Dec 31 14:16:10 xxxxxxxxxx gnome-keyring-daemon[4318]: couldn't access control socket: /var/run/xdg/xxx/keyring/control: No such file or directory
Dec 31 14:16:10 xxxxxxxxxx gnome-keyring-daemon[4318]: discover_other_daemon: 0
Dec 31 14:16:36 xxxxxxxxxx gnome-keyring-daemon[4318]: The Secret Service was already initialized
Dec 31 14:16:36 xxxxxxxxxx gnome-keyring-daemon[4358]: discover_other_daemon: 1
Dec 31 14:16:36 xxxxxxxxxx gnome-keyring-daemon[4318]: The PKCS#11 component was already initialized
Dec 31 14:16:36 xxxxxxxxxx gnome-keyring-daemon[4360]: discover_other_daemon: 1

There is 26 seconds delay between the second and third log entry. I will rephrase my question - what is wrong and how to get rid of this delay?

Did also try to de-install the security/gnome-keyring, but the delay remained.

With a test user -
Code: 
Dec 31 14:33:55 xxxxxxxxxx gnome-keyring-daemon[4555]: couldn't access control socket: /var/run/xdg/test/keyring/control: No such file or directory
Dec 31 14:33:55 xxxxxxxxxx gnome-keyring-daemon[4555]: discover_other_daemon: 0
Dec 31 14:33:55 xxxxxxxxxx gnome-keyring-daemon[4555]: The Secret Service was already initialized
Dec 31 14:33:55 xxxxxxxxxx gnome-keyring-daemon[4585]: discover_other_daemon: 1
Dec 31 14:33:55 xxxxxxxxxx gnome-keyring-daemon[4555]: The PKCS#11 component was already initialized
Dec 31 14:33:55 xxxxxxxxxx gnome-keyring-daemon[4589]: discover_other_daemon: 1
Dec 31 14:33:55 xxxxxxxxxx gnome-keyring-daemon[4555]: The SSH agent was already initialized
Dec 31 14:33:55 xxxxxxxxxx gnome-keyring-daemon[4606]: discover_other_daemon: 1

Threre are similar gnome-keyring-daemon messages, but the the login moves on within the same second.
 
If the delay depends on the user started Mate DE, possibly there could be some remnants of old and no longer existing entries in auto-start apps and/or desktop entries, both on per-user config (typically under ~/.config/).

Possibly look into there for *.desktop files, confirm each one is for what you actually need or not, and even if still needed, check whether it also exists under /usr/local/share, and finally delete (or to be more safe, move to somewhere outside ~/.config/) duplicated and unneeded ones could help.

But what I most suspect in these cases are that some obsolete entries point to somewhere non-existent or slow (i.e., on remote servers) filesystems.
 
T-Aoki said:
Possibly look into there for *.desktop files, confirm each one is for what you actually need or not, and even if still needed, check whether it also exists under /usr/local/share, and finally delete (or to be more safe, move to somewhere outside ~/.config/) duplicated and unneeded ones could help.

But what I most suspect in these cases are that some obsolete entries point to somewhere non-existent or slow (i.e., on remote servers) filesystems.
Click to expand...
Did not find anything suspicious.
Also, it is interesting that both Gnome and KDE Plasma start without such delay.
 
You must log in or register to reply here.
Back
Top