After upgrading from Ubuntu 22 to 24, I started getting the Oh no! Something went wrong error screen. Searching for a solution, I found https://askubuntu.com/a/1515011/1783386
Did the soft link and also fixed the packages.
When using a browser or code editor still gives me the screen after a while, in the syslog I found:
2025-01-25T11:04:42.658233-03:00 hss gnome-shell[9165]: Received an X Window System error.#012This probably reflects a bug in the program.#012The error was 'BadDrawable (invalid Pixmap or Window parameter)'.#012 (Details: serial 24146 error_code 9 request_code 55 (core protocol) minor_code 0)#012 (Note to programmers: normally, X errors are reported asynchronously;#012 that is, you will receive the error a while after causing it.#012 To debug your program, run it with the MUTTER_SYNC environment#012 variable to change this behavior. You can then get a meaningful#012 backtrace from your debugger if you break on the mtk_x_error() function.)
2025-01-25T11:04:42.658509-03:00 hss gnome-shell[9165]: GNOME Shell crashed with signal 5
I tried setting these variables in the /etc/environment:
QT_X11_NO_MITSHM=1
QT_GRAPHICSSYSTEM=native
Also tried to reinstall the gnome-shell. Nothing worked, I can use the OS for some minutes and it requires the log out due to previous error displayed on log. Any other ideas?
Edit: Disabled wayland and enabled more logs in /etc/gdm3/custom.conf. Additional logs:
2025-02-05T18:56:35.974293-03:00 hss gnome-shell[2888]: NOTE: Not using GLX TFP!
2025-02-05T18:57:18.393252-03:00 hss gnome-shell[2888]: Received an X Window System error.#012This probably reflects a bug in the program.#012The error was 'BadDrawable (invalid Pixmap or Window parameter)'.#012 (Details: serial 38737 error_code 9 request_code 55 (core protocol) minor_code 0)#012 (Note to programmers: normally, X errors are reported asynchronously;#012 that is, you will receive the error a while after causing it.#012 To debug your program, run it with the MUTTER_SYNC environment#012 variable to change this behavior. You can then get a meaningful#012 backtrace from your debugger if you break on the mtk_x_error() function.)
2025-02-05T18:57:18.393603-03:00 hss kernel: traps: gnome-shell[2888] trap int3 ip:7e7bfece60df sp:7ffc28542c30 error:0 in libglib-2.0.so.0.8000.0[7e7bfeca2000+a0000]
2025-02-05T18:57:19.902287-03:00 hss systemd[1847]: org.gnome.Shell@x11.service: Main process exited, code=dumped, status=5/TRAP
2025-02-05T18:57:19.903540-03:00 hss systemd[1847]: launchpadlib-cache-clean.service - Clean up old files in the Launchpadlib cache was skipped because of an unmet condition check (ConditionPathExists=/home/henrique/.launchpadlib/api.launchpad.net/cache).
2025-02-05T18:57:20.961815-03:00 hss systemd[1847]: org.gnome.Shell@x11.service: Failed with result 'core-dump'.
2025-02-05T18:57:20.961932-03:00 hss systemd[1847]: org.gnome.Shell@x11.service: Triggering OnFailure= dependencies.
2025-02-05T18:57:20.962108-03:00 hss systemd[1847]: org.gnome.Shell@x11.service: Consumed 2min 12.113s CPU time.
2025-02-05T18:57:20.962261-03:00 hss systemd[1847]: org.gnome.Shell@x11.service: Scheduled restart job, restart counter is at 1.
2025-02-05T18:57:20.974826-03:00 hss systemd[1847]: Started gnome-session-failed.service - GNOME Session Failed lockdown screen (user).
2025-02-05T18:57:20.974933-03:00 hss systemd[1847]: Reached target gnome-session-failed.target - GNOME Session Failed.
.xsession-errors:
Failed to get properties: Unit name drkonqi-coredump-launcher@.service is neither a valid invocation ID nor unit name.
Failed to get properties: Unit name gnome-session-manager@.service is neither a valid invocation ID nor unit name.
Failed to get properties: Unit name wireplumber@.service is neither a valid invocation ID nor unit name.
