Xfce Forum

Sub domains
 

You are not logged in.

#1 2018-11-14 09:30:34

strangeuser
Member
Registered: 2018-11-14
Posts: 4

Keyboard shorcut load

Hello,

My keyboard shortcuts put 25 second to be activate after XFCE loading.
For the use of Linux hosts in my company, we must have them instantly.

What is the good configuration?

The system is UBUNTU 18.04 LTS
The hosts is Lenovo M720s

Thank's wink

(ps= sorry for my english)

Last edited by strangeuser (2018-11-14 09:49:48)

Offline

#2 2018-11-14 10:58:29

MountainDewManiac
Member
From: Where Mr. Bankruptcy is Prez
Registered: 2013-03-24
Posts: 1,087

Re: Keyboard shorcut load

Have you thought about switching to SSD hard drives? While requiring 25 seconds for your keyboard shortcuts to begin working does seem to be somewhat unusual, if it's something that is needed "instantly," that implies solid state instead of magnetic media (or a need for at least minimal prior planning - turn the machines on half a minute earlier and you now have a five-second cushion roll ), and if it's a for-profit business, occasional hardware upgrades should be looked at as just another business expense... and upgrading computers' hard drives to SSD can sometimes mean getting two or three (or more) years' worth of use out of those computers before selling them for a fraction of what they originally cost and replacing them with brand new ones (which can make the drive swap option seem relatively cheap).

A few years ago, I noticed people were complaining because it took a little time for their desktop background image to load/display. Things were changed (as far as I know) to make it display sooner. But it seems to me that, when multiple components have to be loaded, there is always going to be something that gets loaded last - and that will probably always end up being inconvenient to someone because they will have different priorities than most people. I remember thinking at the time that the ultimate solution was simple: Keep the "LOADING" display (the mouse graphic, one of the alternates, or even just a black/blank screen) showing until 100% of everything gets loaded and ready to function and then display the desktop, with everything showing, all components ready to function, et cetera.

But then someone would come along and demand that everything appear two-and-a-half seconds quicker.

Switch to SSDs, lol.

Regards,
MDM

Last edited by MountainDewManiac (2018-11-14 11:09:20)


Mountain Dew Maniac

How to Ask for Help <=== Click on this link

Offline

#3 2018-11-14 11:34:37

ToZ
Moderator
From: Canada
Registered: 2011-06-02
Posts: 6,236

Re: Keyboard shorcut load

A couple of things to try:

1. Clear your saved sessions cache by deleting the contents of ~/.cache/sessions while not logged in.
2. Create a second account on your computer and log in with that account. This will help to identify whether it is a problem with your profile or with  computer configuration.
3. Have a read through this thread especially post #7 and get the xfsettingsd log output.

Can you also post the contents of ~/.xsession-errors?

BTW, welcome to the forums.

Offline

#4 2018-11-14 12:19:34

strangeuser
Member
Registered: 2018-11-14
Posts: 4

Re: Keyboard shorcut load

MountainDewManiac wrote:

Switch to SSDs, lol

MountainDewManiac, thank's but it's in SSD (128 Go M2 nvme wink)

Offline

#5 2018-11-14 12:20:48

strangeuser
Member
Registered: 2018-11-14
Posts: 4

Re: Keyboard shorcut load

ToZ wrote:

Can you also post the contents of ~/.xsession-errors?

root@localhost:/home/local# cat .xsession-errors
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting DISPLAY=:0
dbus-update-activation-environment: setting XAUTHORITY=/home/local/.Xauthority
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: setting LANG=fr_FR.UTF-8
dbus-update-activation-environment: setting GDM_LANG=fr_FR
dbus-update-activation-environment: setting DISPLAY=:0
dbus-update-activation-environment: setting MANDATORY_PATH=/usr/share/gconf/xfce.mandatory.path
dbus-update-activation-environment: setting XDG_GREETER_DATA_DIR=/var/lib/lightdm-data/local
dbus-update-activation-environment: setting USER=local
dbus-update-activation-environment: setting DESKTOP_SESSION=xfce
dbus-update-activation-environment: setting DEFAULTS_PATH=/usr/share/gconf/xfce.default.path
dbus-update-activation-environment: setting PWD=/home/local
dbus-update-activation-environment: setting HOME=/home/local
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: setting XDG_SESSION_TYPE=x11
dbus-update-activation-environment: setting XDG_DATA_DIRS=/usr/share/xfce4:/usr/share/xfce:/usr/local/share:/usr/share:/var/lib/snapd/desktop
dbus-update-activation-environment: setting XDG_SESSION_DESKTOP=xfce
dbus-update-activation-environment: setting SHELL=/bin/bash
dbus-update-activation-environment: setting XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
dbus-update-activation-environment: setting IM_CONFIG_PHASE=1
dbus-update-activation-environment: setting XDG_CURRENT_DESKTOP=XFCE
dbus-update-activation-environment: setting GPG_AGENT_INFO=/run/user/1000/gnupg/S.gpg-agent:0:1
dbus-update-activation-environment: setting SHLVL=1
dbus-update-activation-environment: setting LANGUAGE=fr_FR.utf8
dbus-update-activation-environment: setting GDMSESSION=xfce
dbus-update-activation-environment: setting LOGNAME=local
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting XDG_RUNTIME_DIR=/run/user/1000
dbus-update-activation-environment: setting XAUTHORITY=/home/local/.Xauthority
dbus-update-activation-environment: setting XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session0
dbus-update-activation-environment: setting XDG_CONFIG_DIRS=/etc/xdg/xdg-xfce:/etc/xdg
dbus-update-activation-environment: setting PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
dbus-update-activation-environment: setting _=/usr/bin/dbus-update-activation-environment
xrdb:  "Xft.hinting" on line 19 overrides entry on line 5
xrdb:  "Xft.hintstyle" on line 21 overrides entry on line 6
xfce4-session-Message: 11:26:14.662: SSH authentication agent is already running
gpg-agent[1051]: Attention : « --write-env-file » est une option obsolète — non prise en compte
gpg-agent: une instance de gpg-agent fonctionne déjà —
pas de démarrage d'une nouvelle instance

(xfce4-session:1026): xfce4-session-WARNING **: 11:26:14.668: gpg-agent returned no PID in the variables
[idesk] Background's source not found.
xfce4-panel-migrate-Message: 11:26:14.829: La configuration du tableau de bord doit être migrée...
xfce4-panel-migrate-Message: 11:26:14.829: La configuration du tableau de bord a été mise à jour.
libxfce4panel-Message: 11:26:14.988: Failed to load image "/usr/share/pixmaps/exaile.png": Impossible d'ouvrir le fichier « /usr/share/pixmaps/exaile.png » : Aucun fichier ou dossier de ce type
libxfce4panel-Message: 11:26:14.989: Failed to load image "/usr/share/pixmaps/exaile.png": Impossible d'ouvrir le fichier « /usr/share/pixmaps/exaile.png » : Aucun fichier ou dossier de ce type
libxfce4panel-Message: 11:26:14.990: Failed to load image "/usr/share/pixmaps/exaile.png": Impossible d'ouvrir le fichier « /usr/share/pixmaps/exaile.png » : Aucun fichier ou dossier de ce type
libxfce4panel-Message: 11:26:14.991: Failed to load image "/usr/share/pixmaps/exaile.png": Impossible d'ouvrir le fichier « /usr/share/pixmaps/exaile.png » : Aucun fichier ou dossier de ce type
xfce4-panel-Message: 11:26:15.013: Plugin "xfce4-mixer-plugin-7" was not found and has been removed from the configuration
Gtk-Message: 11:26:15.077: GtkDialog mapped without a transient parent. This is discouraged.

(xfsettingsd:1091): libupower-glib-WARNING **: 11:26:39.826: Couldn't connect to proxy: Erreur lors de l’appel de StartServiceByName pour org.freedesktop.UPower : GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.freedesktop.UPower': timed out (service_start_timeout=25000ms)

(xfsettingsd:1091): libupower-glib-CRITICAL **: 11:26:39.826: up_client_get_lid_is_closed: assertion 'UP_IS_CLIENT (client)' failed

(xfsettingsd:1091): GLib-GObject-WARNING **: 11:26:39.826: invalid (NULL) pointer instance

(xfsettingsd:1091): GLib-GObject-CRITICAL **: 11:26:39.826: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

Offline

#6 2018-11-14 18:53:10

ToZ
Moderator
From: Canada
Registered: 2011-06-02
Posts: 6,236

Re: Keyboard shorcut load

What's interesting, is the last 4 entries in that log file occur about 25 seconds after the first. A little too close for coincidence.

Have you tried the 3 items I listed in my post above? Did any of them yield a better result?

Offline

#7 2018-11-14 22:47:04

MountainDewManiac
Member
From: Where Mr. Bankruptcy is Prez
Registered: 2013-03-24
Posts: 1,087

Re: Keyboard shorcut load

Probably won't help (all I did was perform a web-search for that error), but this is the first result from the search:
https://unix.stackexchange.com/question … -timed-out
...which had this down towards the bottom:

Restarting only systemd-logind service is not enough, it just postpones the main problem.

Seems like this is caused by too many files pilled up under '/run/systemd/system/', created by the service and not properly cleaned up, especially on hosts with a lot of logins. Eventually after some time you would start seeing some weird behavior like hostnamectl not reporting a thing, or timedatectl reports Failed to query server: Connection timed out and other odd things. As well the symptoms reported originally.

One workaround is to delete all 'session-*.scope' files and to restart systemd. Restarting the host is not necessary in that case. This probably is related to a bug in systemd and dbus, hopefully in next updates they will be fixed.

But I received 19,500 results from the search, so it's maybe not so much a question of finding a needle in a haystack as finding one specific needle... in a pile of 19,499 other needles.

I also saw this one:
https://unix.stackexchange.com/question … lts-on-vir

Which appears to be unsolved at the moment, but it specifically mentions Ubuntu 18.04 - and I saw "service_start_timeout=25000ms" so, while not providing any solution, perhaps what that person came up with in terms of log information might help you with troubleshooting yours?

Regards,
MDM

Last edited by MountainDewManiac (2018-11-14 22:47:42)


Mountain Dew Maniac

How to Ask for Help <=== Click on this link

Offline

Board footer

Powered by FluxBB