"Oh no! Something has gone wrong" after last update

Support GNOME
,
1

After letting my computer update during the night, I went back to use it in the morning. As always, when I do a big update, I always restart the PC. After I restarted it, immeadtly when I logged in, appeared a screen with a sad face written “Oh no! Something had gone wrong. A problem occured and the system can’t recover. Please log out and try again”. If I log out and log in again, it just stays the same.

I already tried the following:

  • Disabling extensions;
  • Checking if gnome accessibility options are disabled;
  • Deleting user data from gnome-shell and gdm;
  • Reinstalling gnome-shell and gdm;

And maybe something more that I can’t recall right now.
I browsed through the foruns and nothing work to fix it.

I noticed that I try to use tty3 and run “startx” it works fine. Maybe it’s a problem with gdm?

Any ideas?

1 Like
2

What does your journal mention about gdm?
Have you checked pacnew files?

I’ve had this issue when using the nonfree mesa repo, switching back to default mesa packages solved this for me with gdm. There was another user with a similair sounding issue:

1 Like
3

Yeah, I’ve seen his topic.

I’ve tried journalctl since last boot with priority 3, it returned this:

Sep 26 13:34:40 ncc-74656 kernel: ldm_parse_tocblock(): Cannot find TOCBLOCK, database may be corrupt.
Sep 26 13:34:40 ncc-74656 kernel: ldm_parse_tocblock(): Cannot find TOCBLOCK, database may be corrupt.
Sep 26 13:34:39 ncc-74656 systemd-modules-load[230]: Failed to find module 'akvcam'
Sep 26 13:34:39 ncc-74656 systemd-modules-load[230]: Failed to find module 'v4l2loopback'
Sep 26 13:34:41 ncc-74656 kernel: sp5100-tco sp5100-tco: Failed to reserve MMIO or alternate MMIO region
Sep 26 13:34:42 ncc-74656 kernel: kvm_amd: SVM disabled (by BIOS) in MSR_VM_CR on CPU 0
Sep 26 13:34:42 ncc-74656 kernel: kvm_amd: SVM disabled (by BIOS) in MSR_VM_CR on CPU 5
Sep 26 13:34:42 ncc-74656 kernel: 
Sep 26 13:34:42 ncc-74656 kernel: nvidia-gpu 0000:01:00.3: i2c timeout error e0000000
Sep 26 13:34:42 ncc-74656 kernel: ucsi_ccg 0-0008: i2c_transfer failed -110
Sep 26 13:34:42 ncc-74656 kernel: ucsi_ccg 0-0008: ucsi_ccg_init failed - -110
Sep 26 13:34:43 ncc-74656 systemd-modules-load[230]: Failed to find module 'v4l2loopback'
Sep 26 13:37:14 ncc-74656 gdm-password][1570]: gkr-pam: unable to locate daemon control file
Sep 26 13:37:16 ncc-74656 systemd[1592]: Failed to start Application launched by gnome-session-binary.
Sep 26 13:37:16 ncc-74656 systemd[1592]: Failed to start Application launched by gnome-session-binary.
Sep 26 13:37:16 ncc-74656 systemd[1592]: Failed to start Application launched by gnome-session-binary.
Sep 26 13:37:19 ncc-74656 pulseaudio[1820]: Failed to open module mbeq_1197.so: mbeq_1197.so: cannot open shared object file: No such file or directory
Sep 26 13:37:19 ncc-74656 pulseaudio[1820]: Failed to load LADSPA plugin: file not found
Sep 26 13:37:19 ncc-74656 pulseaudio[1820]: Failed to load module "module-ladspa-sink" (argument: "sink_name=ladspa_output.mbeq_1197.mbeq sink_master=alsa_output.usb-Logitech_G533_Gaming_Headset-00.analog-stere>
Sep 26 13:37:19 ncc-74656 pulseaudio[1820]: Sink ladspa_output.mbeq_1197.mbeq does not exist.
Sep 26 13:37:19 ncc-74656 gnome-shell[1748]: Received an X Window System error.
                                             This probably reflects a bug in the program.
                                             The error was 'BadMatch (invalid parameter attributes)'.
                                               (Details: serial 1149 error_code 8 request_code 147 (unknown) minor_code 6)
                                               (Note to programmers: normally, X errors are reported asynchronously;
                                                that is, you will receive the error a while after causing it.
                                                To debug your program, run it with the MUTTER_SYNC environment
                                                variable to change this behavior. You can then get a meaningful
                                                backtrace from your debugger if you break on the meta_x_error() function.)
Sep 26 13:37:20 ncc-74656 systemd-coredump[2174]: [🡕] Process 1748 (gnome-shell) of user 1000 dumped core.
                                                  
                                                  Stack trace of thread 1748:
                                                  #0  0x00007f2d0728e83c n/a (libc.so.6 + 0x8e83c)
                                                  #1  0x00007f2d0723e668 raise (libc.so.6 + 0x3e668)
                                                  #2  0x000055bf9162af59 n/a (gnome-shell + 0x3f59)
                                                  #3  0x00007f2d0723e710 n/a (libc.so.6 + 0x3e710)
                                                  #4  0x00007f2d07ccd258 g_log_structured_array (libglib-2.0.so.0 + 0x61258)
                                                  #5  0x00007f2d07ccd553 g_log_default_handler (libglib-2.0.so.0 + 0x61553)
                                                  #6  0x00007f2d07cce405 g_logv (libglib-2.0.so.0 + 0x62405)
                                                  #7  0x00007f2d07cce6d4 g_log (libglib-2.0.so.0 + 0x626d4)
                                                  #8  0x00007f2d07718597 n/a (libmutter-12.so.0 + 0x118597)
                                                  #9  0x00007f2d0704068c _XError (libX11.so.6 + 0x4468c)
                                                  #10 0x00007f2d07040798 n/a (libX11.so.6 + 0x44798)
                                                  #11 0x00007f2d07040855 n/a (libX11.so.6 + 0x44855)
                                                  #12 0x00007f2d0704223d _XReply (libX11.so.6 + 0x4623d)
                                                  #13 0x00007f2d04557aed XIGrabDevice (libXi.so.6 + 0xbaed)
                                                  #14 0x00007f2d076c4a93 meta_display_freeze_keyboard (libmutter-12.so.0 + 0xc4a93)
                                                  #15 0x00007f2d06bcb4f6 n/a (libffi.so.8 + 0x74f6)
                                                  #16 0x00007f2d06bc7f5e n/a (libffi.so.8 + 0x3f5e)
4

This line could be something to search for and check if solutions apply in your situation. I’m not sure this is a message that needs attention, it does concern graphics and you have a graphical issue. There are some errors at bootup that do not seem critical to running gnome, but can be fixed if they bother you. Posting some info about your system will give more insight into what kind of system you run and provide context.

1 Like
5

I had the same issue.
I disabled “Allow Flipping” in Nvidia Settings and the error has gone away!