You are not logged in.

#1 2020-01-13 05:52:15

sadboi389
Member
Registered: 2018-03-31
Posts: 33

"Oh no! Somethign has gone wrong." screen on gnome after -Syu

Just did a -Syu, I ran into this issue: https://www.archlinux.org/news/xorg-cle … ervention/
Did what it says, libdmx wasn't installed on my system though. -Syu ran fine. I'm using the "nvidia" package as my graphics driver and it got updated aswell (I suspect a relation).

When starting gnome (I do so manually using startx), I get greeted with the lovely "A problem has occurred and the system can't receover. Please log out and try again" screen, and a log out button.

Funny thing is, I can completely ignore this. It's only on my main monitor, I can hit the SUPER button and use the activity launcher. In fact, I'm writing this post using firefox on a second monitor. My main monitor is useless though, as no windows can be placed above said lovely fullscreen message.

Warnings from the /var/log/Xorg.0.log:

[   124.801] (WW) Failed to open protocol names file lib/xorg/protocol.txt
[   125.083] (WW) The directory "/usr/share/fonts/Type1" does not exist.
[   125.083] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi".
[   125.083] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi".
[   125.097] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[   125.101] (WW) Warning, couldn't open module nouveau
[   125.101] (WW) Warning, couldn't open module nv
[   125.102] (WW) Warning, couldn't open module fbdev
[   125.103] (WW) Warning, couldn't open module vesa
[   125.105] (WW) Falling back to old probe method for modesetting

Errors from the /var/log/Xorg.0.log:

[   125.101] (EE) Failed to load module "nouveau" (module does not exist, 0)
[   125.101] (EE) Failed to load module "nv" (module does not exist, 0)
[   125.102] (EE) Failed to load module "fbdev" (module does not exist, 0)
[   125.103] (EE) Failed to load module "vesa" (module does not exist, 0)
[   136.445] (EE) client bug: timer event7 debounce: offset negative (-54ms)
[   136.445] (EE) client bug: timer event7 debounce short: offset negative (-67ms)
[   152.638] (EE) client bug: timer event7 debounce short: offset negative (-0ms)
[   205.203] (EE) client bug: timer event7 debounce short: offset negative (-12ms)
[   207.111] (EE) client bug: timer event7 debounce: offset negative (-233ms)
[   207.111] (EE) client bug: timer event7 debounce short: offset negative (-246ms)
[   219.297] (EE) client bug: timer event7 debounce: offset negative (-659ms)
[   219.297] (EE) client bug: timer event7 debounce short: offset negative (-672ms)
[   420.500] (EE) client bug: timer event7 debounce: offset negative (-83ms)
[   420.500] (EE) client bug: timer event7 debounce short: offset negative (-96ms)
[   454.028] (EE) client bug: timer event7 debounce: offset negative (-107ms)
[   454.028] (EE) client bug: timer event7 debounce short: offset negative (-120ms)

I might be really off here and I don't know what nv and fbdev (guessing it means framebufferdevice?) is, but nouveau and vesa are drivers and unless I'm missing something here I'm sure they shouldn't be attempted to be loaded in the first place, as I am using the nvidia driver.

The NVIDIA X Server Settings tool runs fine, everything in there seems normal, all X server information looks correct, this makes it certain to me that the nvidia driver is being used.

The journalctl -b command gives a bunch of stuff, here is everything that I think might have relevance:

gnome-shell[905]: GNOME Shell started at Mon Jan 13 2020 06:07:55 GMT+0100 (CET)
gnome-shell[905]: Registering session with GDM
gnome-shell[905]: Error registering session with GDM: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.DisplayManager was not provided by any .service files
org.gnome.Shell.desktop[905]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x22000f8
gsd-print-notif[1198]: Source ID 3 was not found when attempting to remove it
gnome-shell[905]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed
gnome-shell[905]: cr_declaration_parse_list_from_buf: assertion 'parser' failed
systemd[765]: gsd-xsettings.service: Succeeded.
polkitd[959]: Unregistered Authentication Agent for unix-session:1 (system bus name :1.44, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000c0000-0x000dffff window]
kernel: caller _nv000908rm+0x1bf/0x1f0 [nvidia] mapping multiple BARs
gnome-session[1662]: gnome-session-binary[1662]: WARNING: Falling back to non-systemd startup procedure due to error: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit gnome-session-tty@gnome.target not found.
gnome-session-binary[1662]: WARNING: Falling back to non-systemd startup procedure due to error: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit gnome-session-tty@gnome.target not found.
gnome-session[1662]: gnome-session-binary[1662]: WARNING: Could not get session id for session. Check that logind is properly installed and pam_systemd is getting used at login.
gnome-session-binary[1662]: WARNING: Could not get session id for session. Check that logind is properly installed and pam_systemd is getting used at login.
gnome-keyring-daemon[1698]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
gnome-keyring-d[1698]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
gnome-keyring-daemon[1700]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
gnome-keyring-d[1700]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
org.gnome.Shell.desktop[1706]: Window manager warning: Overwriting existing binding of keysym 70 with keysym 70 (keycode 21).
gnome-shell[1706]: Failed to create file /run/user/1000/gnome-shell-disable-extensions: Error opening file “/run/user/1000/gnome-shell-disable-extensions”: File exists
gnome-shell[1706]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed
gnome-shell[1706]: cr_declaration_parse_list_from_buf: assertion 'parser' failed
systemd[765]: GNOME Session is initialized is not active.
systemd[765]: Dependency failed for GNOME session X11 services.
systemd[765]: Dependency failed for GNOME XSettings.
systemd[765]: gsd-xsettings.target: Job gsd-xsettings.target/start failed with result 'dependency'.
systemd[765]: gnome-session-x11-services.target: Job gnome-session-x11-services.target/start failed with result 'dependency'.
systemd[765]: Starting GNOME XSettings...
org.gnome.Shell.desktop[1706]: Window manager warning: Overwriting existing binding of keysym 70 with keysym 70 (keycode 21).
gnome-shell[1706]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed
gnome-shell[1706]: cr_declaration_parse_list_from_buf: assertion 'parser' failed
gnome-shell[1706]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed
gnome-shell[1706]: cr_declaration_parse_list_from_buf: assertion 'parser' failed
gsd-xsettings[1811]: You can only run one xsettings manager at a time; exiting
org.gnome.SettingsDaemon.XSettings.desktop[1811]: Failed to start: Could not initialize xsettings manager.
gnome-session[1662]: gnome-session-binary[1662]: WARNING: App 'org.gnome.SettingsDaemon.XSettings.desktop' exited with code 1
gnome-session-binary[1662]: WARNING: App 'org.gnome.SettingsDaemon.XSettings.desktop' exited with code 1
gnome-session[1662]: gnome-session-binary[1662]: WARNING: App 'org.gnome.SettingsDaemon.XSettings.desktop' respawning too quickly
gnome-session-binary[1662]: Unrecoverable failure in required component org.gnome.SettingsDaemon.XSettings.desktop
gnome-session-binary[1662]: WARNING: App 'org.gnome.SettingsDaemon.XSettings.desktop' respawning too quickly

In the GUI app. for the logs there's also this:

Unrecoverable failure in required component org.gnome.SettingsDaemon.XSettings.desktop

Nothing else is there in the "Important" tab (besides some ACPI errors that I'm sure aren't related at all).

Any help is greatly appreciated.

Update: Disabled all gnome extensions, restarted X, issue is gone. Enabled all extensions again, works. No crash, no error messages. Extensions work. Restarted X (with extensions kept on), error message appears again. I'm going to go through the extensions one by one to narrow it down, however there are a bunch of other errors/warnings in the logs I shared that I'm sure aren't related to extensions and worry me, so I would appreciate input on those a lot aswell.

Update 2 : Things are weird. It doesn't seem to be an extension. I went through all of them, no matter which extension (even if its just the places menu or just alternate tab switcher..) is on, as long as there is any one (or more) extension on: I get the "crash" screen. If all extensions are off (doesn't matter if I use the main switch on the top or if that one's on but all extensions below are off), the message doesn't appear at all.

Last edited by sadboi389 (2020-01-13 06:11:10)

Offline

#2 2020-01-13 12:53:17

Trilby
Banned
Registered: 2011-11-29
Posts: 22,631
Website

Re: "Oh no! Somethign has gone wrong." screen on gnome after -Syu

sadboi389 wrote:

I might be really off here and I don't know what nv and fbdev (guessing it means framebufferdevice?) is, but nouveau and vesa are drivers and unless I'm missing something here I'm sure they shouldn't be attempted to be loaded in the first place, as I am using the nvidia driver.

Xorg tries to load all suitable drivers whether they are present or not - so those errors are normal.

However, posting grepped logs is useless.  Post your complex Xorg log.


"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" -  Richard Stallman

Offline

#3 2020-01-13 16:02:34

sadboi389
Member
Registered: 2018-03-31
Posts: 33

Re: "Oh no! Somethign has gone wrong." screen on gnome after -Syu

Trilby wrote:
sadboi389 wrote:

I might be really off here and I don't know what nv and fbdev (guessing it means framebufferdevice?) is, but nouveau and vesa are drivers and unless I'm missing something here I'm sure they shouldn't be attempted to be loaded in the first place, as I am using the nvidia driver.

Xorg tries to load all suitable drivers whether they are present or not - so those errors are normal.

However, posting grepped logs is useless.  Post your complex Xorg log.

Sorry, I thought it'd make it easier to read. So I just enabled all extensions again and restarted X, expecting the crash screen again so I can get the full logs. Weirdly enough, I don't get it. I haven't done a thing, didn't even use the PC between this and my last post. Same extensions are on as before.

All errors from the journalctl command don't appear anymore, a few warnings are still there but most of them are related to deprecated functions within extensions and nothing seems critical.

How did this suddenly fix itself over night?

Offline

#4 2020-01-13 16:54:32

sadboi389
Member
Registered: 2018-03-31
Posts: 33

Re: "Oh no! Somethign has gone wrong." screen on gnome after -Syu

Okay, things are getting weirder. With all extensions still on, I did a system reboot. I started X, and the error message came back. I saved the logs.
After that, I did another -Syu, the following packages were updated:

cantarell-fonts-1:0.201-1  ffmpeg-1:4.2.2-1  graphicsmagick-1.3.34-1  gst-plugins-ugly-1.16.2-2  imagemagick-7.0.9.16-1  intel-gmmlib-19.4.1-1  intel-media-driver-19.4.0.r-1  intel-media-sdk-19.4.0-1  libquicktime-1.2.4-21 linux-5.4.11.arch1-1  mplayer-38157-1  nvidia-440.44-11  virtualbox-host-modules-arch-6.1.0-11  vlc-3.0.8-8  x264-3:0.159.r2991.1771b55-1

Another full reboot after, same error message still appears. Everything (all extensions aswell) still work though, just like before.

After that, I disabled all extensions again (main switch on the top) but: Instead of just restarting X after that like I did before, I restarted the whole system. And I was greeted once again with the crash message, even with all extensions disabled. So I'm 100% certain the extensions are innocent.

Trying to get the crash screen to disappear now again (while all extensions remain off) so I can compare the logs. The Xorg log doesn't contain anything unusual by the way, no warning, no error, not even a debug message that seems weird or unclear. Journal has a lot more, but everything's already in my first post. Is there any other place to look for logs?

Offline

#5 2020-01-13 17:18:14

sadboi389
Member
Registered: 2018-03-31
Posts: 33

Re: "Oh no! Somethign has gone wrong." screen on gnome after -Syu

Alright, so I did a full reboot again (extensions still off) and first try the crash screen did not appear. I used diff on the Xorg log with the crash and the one without the crash (both times extensions off) - No differences in the file.

I did the same with the journalctl -b log and this is the result (I did account for changes in time and process IDs):

Unrecoverable failure in required component org.gnome.SettingsDaemon.XSettings.desktop
WARNING: App 'org.gnome.SettingsDaemon.XSettings.desktop' respawning too quickly

So I'm guessing that's where the issue lays. I did a "grep --recursive -ia 'xsettings' /var/log" and all it found was journal entries, which are these:

 5:59:44 PM systemd: Started GNOME XSettings.
 5:59:44 PM gnome-session-b: WARNING: App 'org.gnome.SettingsDaemon.XSettings.desktop' exited with code 1
 5:59:44 PM gnome-session-b: WARNING: App 'org.gnome.SettingsDaemon.XSettings.desktop' exited with code 1
 5:59:44 PM gnome-session-b: gnome-session-binary[843]: WARNING: App 'org.gnome.SettingsDaemon.XSettings.desktop' exited with code 1
 5:59:44 PM gsd-xsettings: Failed to start: Could not initialize xsettings manager.
 5:59:44 PM gsd-xsettings: Failed to start: Could not initialize xsettings manager.
 5:59:44 PM gsd-xsettings: You can only run one xsettings manager at a time; exiting
 5:59:44 PM gnome-session-b: WARNING: App 'org.gnome.SettingsDaemon.XSettings.desktop' exited with code 1
 5:59:44 PM gnome-session-b: WARNING: App 'org.gnome.SettingsDaemon.XSettings.desktop' exited with code 1
 5:59:44 PM gnome-session-b: gnome-session-binary[843]: WARNING: App 'org.gnome.SettingsDaemon.XSettings.desktop' exited with code 1
 5:59:44 PM gsd-xsettings: Failed to start: Could not initialize xsettings manager.
 5:59:44 PM gsd-xsettings: Failed to start: Could not initialize xsettings manager.
 5:59:44 PM gsd-xsettings: You can only run one xsettings manager at a time; exiting
 5:59:43 PM systemd: Starting GNOME XSettings...
 5:59:43 PM systemd: Starting GNOME XSettings...
 5:59:43 PM systemd: gsd-xsettings.target: Job gsd-xsettings.target/start failed with result 'dependency'.
 5:59:43 PM systemd: Dependency failed for GNOME XSettings.

Where else could I look?

(By the way, using the journal GUI app, comparing the current boot log (no crash) with the previous one (crash), the only difference here in the "Important" tab is also just the line I found using diff, so I'm certain this has to do with "XSettings".)

The "gnome-settings-daemon" package (responsible for XSettings as it seems) has been updated in my -Syu, so yeah I'm certain this is causing the issue. Downgrading seems like a stupid idea. What can I do?

Last edited by sadboi389 (2020-01-13 17:22:53)

Offline

#6 2020-01-13 17:52:50

seth
Member
Registered: 2012-09-03
Posts: 13,514

Re: "Oh no! Somethign has gone wrong." screen on gnome after -Syu

If you see things, X11 is working (there's even a wallpaper for this ;-)

Please post a complete and unfiltered system journal for a boot where this happened.

Offline

Board footer

Powered by FluxBB