Weird GNOME issue after 7.5 upgrade

General support questions
Post Reply
vtwin@cox.net
Posts: 23
Joined: 2017/02/16 16:41:29

Weird GNOME issue after 7.5 upgrade

Post by vtwin@cox.net » 2018/05/17 13:30:39

I have several systems which have been running 7.4 w/o an issue. After upgrading/rebooting into 7.5, logging in (gnome desktop), the screens look like the following:

Image

No status bar, no menus, nothing but the desktop icons I have in the Desktop folder in my home directory.

Some messages from /var/log/rsyslog pertaining to X:

Code: Select all

May 16 16:27:22 mybox systemd[1]: Started GNOME Display Manager.
May 16 16:27:25 mybox systemd[1]: Reached target Graphical Interface.
May 16 16:27:25 mybox systemd[1]: Starting Graphical Interface.
May 16 16:27:26 mybox systemd[1]: Created slice User Slice of gdm.
May 16 16:27:26 mybox systemd[1]: Starting User Slice of gdm.
May 16 16:27:26 mybox systemd-logind[2178]: New session c1 of user gdm.
May 16 16:27:26 mybox systemd[1]: Started Session c1 of user gdm.
May 16 16:27:26 mybox systemd[1]: Starting Session c1 of user gdm.
May 16 16:27:26 mybox gdm-launch-environment]: pam_unix(gdm-launch-environment:session): session opened for user gdm by (uid=0)
May 16 16:27:28 mybox gnome-session[2922]: generating cookie with syscall
May 16 16:27:28 mybox gnome-session[2922]: generating cookie with syscall
May 16 16:27:28 mybox gnome-session[2922]: generating cookie with syscall
May 16 16:27:28 mybox gnome-session[2922]: generating cookie with syscall
May 16 16:27:35 mybox gnome-shell[2964]: JS WARNING: [resource:///org/gnome/shell/ui/main.js 315]: reference to undefined property "MetaStage"
May 16 16:27:35 mybox gnome-shell[2964]: JS WARNING: [resource:///org/gnome/shell/ui/layout.js 221]: reference to undefined property "MetaWindowGroup"
May 16 16:27:35 mybox gnome-shell[2964]: JS WARNING: [resource:///org/gnome/shell/ui/osdMonitorLabeler.js 59]: reference to undefined property "MetaDBusDisplayConfigSkeleton"
May 16 16:27:37 mybox polkitd[2044]: Registered Authentication Agent for unix-session:c1 (system bus name :1.31 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
May 16 16:27:37 mybox gnome-shell[2964]: Failed to load background 'file:///usr/share/backgrounds/gnome/adwaita-lock.jpg': Error opening file /usr/share/backgrounds/gnome/adwaita-lock.jpg: No such file or directory
May 16 16:27:37 mybox gnome-session-binary[2922]: Entering running state
May 16 16:27:39 mybox gnome-shell[2964]: Some code accessed the property 'AuthList' on the module 'authList'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
May 16 16:27:39 mybox org.gnome.Shell.desktop[2964]: Window manager warning: "XF86RFKill" is not a valid accelerator
May 16 16:27:39 mybox gnome-shell[2964]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
May 16 16:27:39 mybox gnome-shell[2964]: JS WARNING: [resource:///org/gnome/shell/gdm/realmd.js 130]: reference to undefined property "_loginFormat"
May 16 16:27:39 mybox gnome-shell[2964]: JS WARNING: [resource:///org/gnome/shell/ui/layout.js 29]: reference to undefined property "MetaWindowX11"
May 16 16:28:52 mybox gdm-password]: pam_sss(gdm-password:auth): authentication success; logname= uid=0 euid=0 tty=/dev/tty1 ruser= rhost= user=vtwin
May 16 16:28:53 mybox systemd[1]: Created slice User Slice of vtwin.
May 16 16:28:53 mybox systemd[1]: Starting User Slice of vtwin.
May 16 16:28:53 mybox systemd-logind[2178]: New session 2 of user vtwin.
May 16 16:28:53 mybox systemd[1]: Started Session 2 of user vtwin.
May 16 16:28:53 mybox systemd[1]: Starting Session 2 of user vtwin.
May 16 16:28:53 mybox gdm-password]: pam_unix(gdm-password:session): session opened for user vtwin by (uid=0)
May 16 16:28:56 mybox gnome-session-binary[2922]: WARNING: Application 'org.gnome.SettingsDaemon.Sharing.desktop' killed by signal 15
May 16 16:28:56 mybox gnome-session[2922]: gnome-session-binary[2922]: WARNING: Application 'org.gnome.SettingsDaemon.Sharing.desktop' killed by signal 15
May 16 16:28:56 mybox gnome-session[2922]: gnome-session-binary[2922]: WARNING: Lost name on bus: org.gnome.SessionManager
May 16 16:28:56 mybox gnome-session-binary[2922]: WARNING: Lost name on bus: org.gnome.SessionManager
May 16 16:28:56 mybox gnome-session-f[3465]: Cannot open display:
May 16 16:28:57 mybox com.redhat.imsettings[3477]: [ 1526502537.412667]: IMSettings-Daemon[3547]: INFO: Starting imsettings-daemon...
May 16 16:28:57 mybox com.redhat.imsettings[3477]: [ 1526502537.414277]: IMSettings-Daemon[3547]: INFO:   [HOME=/home/user/vtwin/.config/imsettings]
May 16 16:28:57 mybox com.redhat.imsettings[3477]: [ 1526502537.415287]: IMSettings-Daemon[3547]: INFO:   [XINPUTRCDIR=/etc/X11/xinit/]
May 16 16:28:57 mybox com.redhat.imsettings[3477]: [ 1526502537.416265]: IMSettings-Daemon[3547]: INFO:   [XINPUTDIR=/etc/X11/xinit/xinput.d/]
May 16 16:28:57 mybox com.redhat.imsettings[3477]: [ 1526502537.417141]: IMSettings-Daemon[3547]: INFO:   [MODULEDIR=/usr/lib64/imsettings]
May 16 16:28:57 mybox com.redhat.imsettings[3477]: [ 1526502537.418087]: IMSettings-Daemon[3547]: INFO:   [MODULES=gsettings, qt]
May 16 16:29:13 mybox gnome-session[3724]: generating cookie with syscall
May 16 16:29:13 mybox gnome-session[3724]: generating cookie with syscall
May 16 16:29:13 mybox gnome-session[3724]: generating cookie with syscall
May 16 16:29:13 mybox gnome-session[3724]: generating cookie with syscall
May 16 16:29:13 mybox gnome-session[3724]: generating cookie with syscall
May 16 16:29:14 mybox gnome-keyring-ssh.desktop[3761]: SSH_AUTH_SOCK=/run/user/1734686988/keyring/ssh
May 16 16:29:14 mybox gnome-keyring-pkcs11.desktop[3759]: SSH_AUTH_SOCK=/run/user/1734686988/keyring/ssh
May 16 16:29:14 mybox gnome-keyring-secrets.desktop[3760]: SSH_AUTH_SOCK=/run/user/1734686988/keyring/ssh
May 16 16:30:44 mybox gnome-session[3724]: gnome-session-binary[3724]: WARNING: Application 'org.gnome.Shell.desktop' failed to register before timeout
May 16 16:30:44 mybox gnome-session-binary[3724]: Unrecoverable failure in required component org.gnome.Shell.desktop
May 16 16:30:44 mybox gnome-session-f[3880]: Cannot open display:
May 16 16:30:44 mybox spice-vdagent[3897]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
May 16 16:30:44 mybox gnome-session[3724]: gnome-session-binary[3724]: WARNING: App 'spice-vdagent.desktop' exited with code 1
May 16 16:30:44 mybox gsd-rfkill[3889]: Error setting up rfkill: Could not open RFKILL control device, please verify your installation
May 16 16:30:44 mybox dbus[1996]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
May 16 16:30:44 mybox systemd[1]: Starting Hostname Service...
May 16 16:30:44 mybox dbus[1996]: [system] Successfully activated service 'org.freedesktop.hostname1'
May 16 16:30:44 mybox gsd-housekeepin[3912]: Loading NVML: libnvidia-ml.so: cannot open shared object file: No such file or directory
May 16 16:30:44 mybox dbus[1996]: [system] Activating via systemd: service name='org.freedesktop.GeoClue2' unit='geoclue.service'
May 16 16:30:44 mybox gsd-xsettings[3893]: Failed to get current display configuration state: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.gnome.Mutter.DisplayConfig" does not exist
May 16 16:30:46 mybox kernel: [  244.623995] lockd: server myserver.mydomain not responding, still trying
May 16 16:32:14 mybox gnome-session-binary[3724]: WARNING: Application 'pulseaudio.desktop' failed to register before timeout
May 16 16:32:14 mybox gnome-session[3724]: gnome-session-binary[3724]: WARNING: Application 'pulseaudio.desktop' failed to register before timeout
May 16 16:32:16 mybox gnome-session-binary[3724]: Entering running state
May 16 16:32:16 mybox com.redhat.imsettings[3477]: [ 1526502736.145498]: IMSettings-Daemon[3547]: INFO: Attempting to switch IM to none [lang=en_US.UTF-8, update=false]
May 16 16:32:16 mybox com.redhat.imsettings[3477]: /usr/libexec/imsettings-target-checker.sh: line 71: [: ==: unary operator expected
May 16 16:32:16 mybox com.redhat.imsettings[3477]: [ 1526502736.273371]: IMSettings-Daemon[3547]: INFO:   no need to invoke any auxiliary process for none
May 16 16:32:16 mybox com.redhat.imsettings[3477]: [ 1526502736.274372]: IMSettings-Daemon[3547]: INFO:   no need to invoke any main process for none
May 16 16:32:16 mybox com.redhat.imsettings[3477]: [ 1526502736.279725]: IMSettings-Qt backend[3547]: INFO: Setting up xim as Qt immodule
May 16 16:32:16 mybox com.redhat.imsettings[3477]: [ 1526502736.280917]: IMSettings-GSettings backend[3547]: INFO: Setting up gtk-im-context-simple:xim as gtk+ immodule
May 16 16:32:45 mybox evolution-calen[4456]: book_client_connected_cb: Unable to connect to 'Personal': Timeout was reached
May 16 20:38:53 mybox org.gnome.SettingsDaemon.MediaKeys.desktop[3914]: lock: No locks available
May 16 20:45:54 mybox org.gnome.Shell.desktop[3769]: lock: No locks available
May 16 20:45:55 mybox gnome-shell[3769]: JS WARNING: [resource:///org/gnome/shell/ui/main.js 315]: reference to undefined property "MetaStage"
May 16 20:45:55 mybox gnome-shell[3769]: JS WARNING: [resource:///org/gnome/shell/ui/layout.js 221]: reference to undefined property "MetaWindowGroup"
May 16 20:45:55 mybox gnome-shell[3769]: JS WARNING: [resource:///org/gnome/shell/ui/osdMonitorLabeler.js 59]: reference to undefined property "MetaDBusDisplayConfigSkeleton"
May 16 20:45:56 mybox gnome-shell[3769]: JS WARNING: [resource:///org/gnome/shell/ui/slider.js 38]: reference to undefined property "CallyActor"
May 16 20:45:58 mybox gnome-shell[3769]: Failed to load background 'file:///usr/share/backgrounds/gnome/adwaita-lock.jpg': Error opening file /usr/share/backgrounds/gnome/adwaita-lock.jpg: No such file or directory
May 16 20:46:23 mybox gsd-xsettings[3893]: Failed to get current display configuration state: Timeout was reached
May 16 20:46:48 mybox gsd-color[3910]: failed to get screens: Timeout was reached
May 16 20:46:48 mybox gsd-wacom[3892]: Failed to construct RR screen: Timeout was reached
May 16 22:23:10 mybox org.gnome.Shell.desktop[3769]: lock: No locks available
I tried "resetting" my gnome environment by booting into runlevel 3, deleting .gnome, .gconf, and a series of other directories, and then back into runlevel 5, but logging in yielded the same result. Thinking perhaps something became corrupt during the upgrade, I reinstalled 7.5 from scratch, but have the same result.

I can log in as root and get a "normal" gnome desktop. I can also log in using a KDE desktop and things seem to work.

Not sure where to go with this one. It is happening on several systems I administer. Any pointers to a resolution would be appreciated.

desertcat
Posts: 440
Joined: 2014/08/07 02:17:29
Location: Tucson, AZ

Re: Weird GNOME issue after 7.5 upgrade

Post by desertcat » 2018/05/17 13:44:44

OK I am glad I'm not the only one: I was coming from KDE and using sddm for my display manager. sddm would not come up so I switched from sddm to gdm, when I typed startx that is exactly what I got too. I was thinking it was some other problem not GNOME but rather some broken implementation of GNOME which is why I simply punted and restored my entire disk from my backup back to 7.4 I thought this was due to my sddm problems. So now there are at least two things that seem to be broken: sddm -- a display manager that works well in 7.4 but broken in 7.5, and now GNOME which works well in 7.4 (though I prefer to use KDE I have "experimented with GNOME and other desktop environments), but now seems to be broken in 7.5

Thanks for sharing.

bonedome
Posts: 45
Joined: 2017/04/22 08:11:04

Re: Weird GNOME issue after 7.5 upgrade

Post by bonedome » 2018/05/17 17:28:50

Hello
looks like overscan, I used get that when plugging my laptop into my tv, until I found the tv has a setting to auto resize the desktop to the screen size.
Does the mouse cursor disappear off the edge of the screen ?
Not sure what most of that x log means other than gnome doesn't seem to get the message about what size monitor is attached, you could try the gnome-control-center or xrandr to adjust it to the correct screen size.
For a (possible) quick fix you could try

Code: Select all

xrandr
to find the name of your monitor, then

Code: Select all

xrandr --output LVDS-1 --auto
replace LVDS-1 with whatever your connected primary is.

vtwin@cox.net
Posts: 23
Joined: 2017/02/16 16:41:29

Re: Weird GNOME issue after 7.5 upgrade

Post by vtwin@cox.net » 2018/05/18 10:01:59

No, definitely not overscan. Simply no underlying display manager.

I have resolved the problem.

May 16 22:23:10 mybox org.gnome.Shell.desktop[3769]: lock: No locks available

Was the culprit.

My home directories are on a central server, mounted via automount. the autofs parameters included an nfsvers=3.

This apparently caused some type of problem with lockd -- not sure what may have changed from 7.4 to 7.5 in this regard, since it was working.

Eliminating the parameter, rebooting, and re-automounting the home directories "fixed" the issue and now the gnome sessions appear as expected.

Unfortunately, this has ended up creating a new problem, but, that's a post for the networking forum :)

desertcat
Posts: 440
Joined: 2014/08/07 02:17:29
Location: Tucson, AZ

Re: Weird GNOME issue after 7.5 upgrade

Post by desertcat » 2018/05/18 12:48:00

vtwin@cox.net wrote:No, definitely not overscan. Simply no underlying display manager.

I have resolved the problem.

May 16 22:23:10 mybox org.gnome.Shell.desktop[3769]: lock: No locks available

Was the culprit.

My home directories are on a central server, mounted via automount. the autofs parameters included an nfsvers=3.

This apparently caused some type of problem with lockd -- not sure what may have changed from 7.4 to 7.5 in this regard, since it was working.

Eliminating the parameter, rebooting, and re-automounting the home directories "fixed" the issue and now the gnome sessions appear as expected.

Unfortunately, this has ended up creating a new problem, but, that's a post for the networking forum :)
Hummmm. Makes me wonder. I *was* running sddm until 7.5 came out, I then got nothing. even after switching back to gdm got me nothing and startx gave me exactly what you got. Where are these files you modified located and what is this "lockd"?Where is it located so I can look on both my 7.4 machine and my 7.5 machine.

Thanks for your help

vtwin@cox.net
Posts: 23
Joined: 2017/02/16 16:41:29

Re: Weird GNOME issue after 7.5 upgrade

Post by vtwin@cox.net » 2018/05/18 13:54:47

in my case, I did not make any changes to the nfs configuration on the server - merely, changed the automount options in /etc/autofs.net to remove the nfsvers=3 parameter, rebooted, and the problem was solved.

The quoted error above was the clue.... the client was unable to obtain a lock on the nfs-mounted file system where the users' home directories were located (why, do not know, given nothing changed in my environment except moving from 7.4 to 7.5).

My guess is this is not your problem, because I suspect your environment is not the same as mine. However, modifying your /etc/rsyslog.conf to log all messages to /var/log/messages or /var/log/rsyslog, and then rebooting and re-launching X, might give you an indication when you examine the log file, of what the real error is that causes the problem on your end.

Post Reply