Weird experience with gnome on 15.2
I was busy whit firefox when the environment got instantly frozen. no problem, I thought, I will wait but this did not help. I decided to reboot my laptop and logged than in to my user and Gnome remained frozen. Quite interestingly, if I login to an another user on my box, I do not have any problem, only “my” occurrence seems to freeze.
Any idea on how I could solve this?
Hi
If you switch to a tty (ctrl+alt+F1) and log in as your user, no freeze? Are you running some gnome shell extensions?
I can login from a tty and work without problem in such an environment.
From tty1, making startx does not succeed (I get messages about the keyboard resolution (and it is true I have six keyboards implemented).
Loging in from gdm leads to the freeze (X11 session, no wayland because I have an optimus laptop with nvidia)
And, no, I have not any extension installed yet.
Hi
Ahhh, have you set the gdm to allow for the Nvidia card?
cat /etc/gdm/custom.conf | grep Way
WaylandEnable=false
Yes I did (and it works good for the other users)
Hi
So what recent changes did the affected user modify on the desktop? Likely a drill down into ~/.config and ~/.cache did you make any recent display type changes, removing the ~/.config/monitors.xml* file may help (maybe make a backup… but it should re-create)
Anything in;
ls .config/gnome-session/saved-session/
The result is nothing (and it is no surprise it is/was a fresh installation when the problem occurred).
Now when I do journalctl -l -b -r, I see a lot of messages about the keyboard configuration. I have 7 keyboard layouts (be, cs, de, ge, ru, ja, pe) and Gnome let me configure them all but if I remember good, in the past it was only possible to configure 4 keyboard layouts.
I will try now to create the same configuration with a third user to see if the problem also occurs.
So I could replicate the problem.
user 3 created, no personal configuration but 7 keyboard configurations, tried to change the keyboard and gnome got frozen.
then user 4 created, same situation but this time 2 keyboard configurations, both with latin alphabet, tried to switch keyboard and same result (freeze)
user 2 (the one I am using now) has just 1 keyboard layout and has no problem
Hereunder a part of the output of journalctl -l -b -r:
Oct 20 19:12:07 gwerlas PackageKit[5081]: get-updates transaction /16_aaaadecb from uid 1002 finished with success after 3447ms
Oct 20 19:12:04 gwerlas PackageKit[5081]: get-update-detail transaction /15_ddbaabcc from uid 1002 finished with success after 35ms
Oct 20 19:12:03 gwerlas PackageKit[5081]: get-updates transaction /14_bcddebad from uid 1002 finished with success after 4527ms
Oct 20 19:11:59 gwerlas gnome-software[5147]: not handling error no-security for action refresh: Failed to obtain authentication.
Oct 20 19:11:59 gwerlas PackageKit[5081]: uid 1002 failed to obtain auth
Oct 20 19:11:59 gwerlas PackageKit[5081]: uid 1002 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
Oct 20 19:11:59 gwerlas systemd[1]: Started Location Lookup Service.
Oct 20 19:11:59 gwerlas dbus-daemon[1271]: [system] Successfully activated service 'org.freedesktop.GeoClue2'
Oct 20 19:11:59 gwerlas systemd[1]: Starting Location Lookup Service...
Oct 20 19:11:59 gwerlas dbus-daemon[1271]: [system] Activating via systemd: service name='org.freedesktop.GeoClue2' unit='geoclue.service' requested by ':1.26' (uid=460 pid=2247 comm="/usr/bin/gnome-shell ")
Oct 20 19:11:58 gwerlas /usr/lib/gdm/gdm-x-session[2087]: Errors from xkbcomp are not fatal to the X server
Oct 20 19:11:58 gwerlas /usr/lib/gdm/gdm-x-session[2087]: > Internal error: Could not resolve keysym XF86RFKill
Oct 20 19:11:58 gwerlas /usr/lib/gdm/gdm-x-session[2087]: > Internal error: Could not resolve keysym XF86WWAN
Oct 20 19:11:58 gwerlas /usr/lib/gdm/gdm-x-session[2087]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Oct 20 19:11:58 gwerlas /usr/lib/gdm/gdm-x-session[2087]: Errors from xkbcomp are not fatal to the X server
Oct 20 19:11:58 gwerlas /usr/lib/gdm/gdm-x-session[2087]: > Internal error: Could not resolve keysym XF86RFKill
Oct 20 19:11:58 gwerlas /usr/lib/gdm/gdm-x-session[2087]: > Internal error: Could not resolve keysym XF86WWAN
Oct 20 19:11:58 gwerlas /usr/lib/gdm/gdm-x-session[2087]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Oct 20 19:11:58 gwerlas /usr/lib/gdm/gdm-x-session[2087]: Errors from xkbcomp are not fatal to the X server
Oct 20 19:11:58 gwerlas /usr/lib/gdm/gdm-x-session[2087]: > Internal error: Could not resolve keysym XF86RFKill
Oct 20 19:11:58 gwerlas /usr/lib/gdm/gdm-x-session[2087]: > Internal error: Could not resolve keysym XF86WWAN
Oct 20 19:11:58 gwerlas /usr/lib/gdm/gdm-x-session[2087]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Oct 20 19:11:58 gwerlas /usr/lib/gdm/gdm-x-session[2087]: Errors from xkbcomp are not fatal to the X server
Oct 20 19:11:58 gwerlas /usr/lib/gdm/gdm-x-session[2087]: > Internal error: Could not resolve keysym XF86RFKill
Oct 20 19:11:58 gwerlas /usr/lib/gdm/gdm-x-session[2087]: > Internal error: Could not resolve keysym XF86WWAN
Oct 20 19:11:58 gwerlas /usr/lib/gdm/gdm-x-session[2087]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Oct 20 19:11:58 gwerlas /usr/lib/gdm/gdm-x-session[2087]: Errors from xkbcomp are not fatal to the X server
Oct 20 19:11:58 gwerlas /usr/lib/gdm/gdm-x-session[2087]: > Internal error: Could not resolve keysym XF86RFKill
Oct 20 19:11:58 gwerlas /usr/lib/gdm/gdm-x-session[2087]: > Internal error: Could not resolve keysym XF86WWAN
Oct 20 19:11:58 gwerlas /usr/lib/gdm/gdm-x-session[2087]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Oct 20 19:11:58 gwerlas /usr/lib/gdm/gdm-x-session[2087]: Errors from xkbcomp are not fatal to the X server
Oct 20 19:11:58 gwerlas /usr/lib/gdm/gdm-x-session[2087]: > Internal error: Could not resolve keysym XF86RFKill
Oct 20 19:11:58 gwerlas /usr/lib/gdm/gdm-x-session[2087]: > Internal error: Could not resolve keysym XF86WWAN
Oct 20 19:11:58 gwerlas /usr/lib/gdm/gdm-x-session[2087]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Oct 20 19:11:58 gwerlas gsd-color[2353]: failed to set screen _ICC_PROFILE: L’ouverture du fichier « /home/leon/.local/share/icc/edid-dfce2d4b9f57ed71110d4a83896d9c7e.icc » a échoué : Permission non accordée
Oct 20 19:11:58 gwerlas /usr/lib/gdm/gdm-x-session[2087]: (II) event4 - Power Button: device is a keyboard
Oct 20 19:11:58 gwerlas /usr/lib/gdm/gdm-x-session[2087]: (II) event4 - Power Button: is tagged by udev as: Keyboard
Oct 20 19:11:58 gwerlas /usr/lib/gdm/gdm-x-session[2087]: (II) systemd-logind: got resume for 13:68
Oct 20 19:11:58 gwerlas /usr/lib/gdm/gdm-x-session[2087]: Errors from xkbcomp are not fatal to the X server
Oct 20 19:11:58 gwerlas /usr/lib/gdm/gdm-x-session[2087]: > Internal error: Could not resolve keysym XF86RFKill
Oct 20 19:11:58 gwerlas /usr/lib/gdm/gdm-x-session[2087]: > Internal error: Could not resolve keysym XF86WWAN
Oct 20 19:11:58 gwerlas /usr/lib/gdm/gdm-x-session[2087]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Oct 20 19:11:58 gwerlas kernel: rfkill: input handler disabled
Oct 20 19:11:58 gwerlas kernel: rfkill: input handler enabled
Oct 20 19:11:58 gwerlas /usr/lib/gdm/gdm-x-session[2087]: (II) event1 - Power Button: device is a keyboard
Oct 20 19:11:58 gwerlas /usr/lib/gdm/gdm-x-session[2087]: (II) event1 - Power Button: is tagged by udev as: Keyboard
Oct 20 19:11:58 gwerlas /usr/lib/gdm/gdm-x-session[2087]: (II) systemd-logind: got resume for 13:65
Oct 20 19:11:58 gwerlas /usr/lib/gdm/gdm-x-session[2087]: Errors from xkbcomp are not fatal to the X server
Oct 20 19:11:58 gwerlas /usr/lib/gdm/gdm-x-session[2087]: > Internal error: Could not resolve keysym XF86RFKill
Oct 20 19:11:58 gwerlas /usr/lib/gdm/gdm-x-session[2087]: > Internal error: Could not resolve keysym XF86WWAN
After a bit of googling it seems it is a known problem (Gnome + x11 + keyboard layout switching), certainly for 3.34 and 3.36.
It could be repaired in 3.38 but not sure. And so, back to KDE!
For those who could be interested, neither Gnome 3.38 solves this problem, also still no keyboard layout switching under Xorg
Care to post any link? The only problem I am aware of is delay in switching keyboard layouts (I experienced it myself), but that is quite different from “freezing”.
Strange enough, I tried it in Virtualbox and the problem does not occur there.
But on a harddisk, it just freezes. (last tested a few hours ago in Tumbleweed and some weeks ago in Leap 15.2)
There is no explanation what was “frozen” and the very fact that user was able to record video of what was happening with desktop implies that at least desktop was not “frozen”. May be we are facing language problem here. But as usual, it is much better to describe what was done and what was observed instead of using generic word that you think is crystal clear but usually means different things for different people.
I will not argue on it but jut describe what is happening: if, under Xorg, I try to switch my keyboard layout, I may have a delay of some seconds but at the end, I cannot do anything in my session except logging out (alt+ctrl+f7) or go to a tty (alt+ctrl+f*). If some time later, after a shutdown, I want to log in again, the freeze is still there, the only way to stop it, is to start the session under Wayland.