[Testing Update] 2025-09-27 - Kernels, Plasma 6.4.5, GNOME 49.0, Cosmic 1.0b1

I also get gnome-shell systemd dumps. First time booting after the upgrade, just a frozen desktop. I restarted gdm and it got back to non frozen desktop, as in the the cursor moves, but with no menu/dock. Pretty unusable.

I think I’ll have to rollback and troubleshoot this tomorrow, not even a lot in the logs to go by.

(I have been running Wayland for sometime, and my /etc/gdm/custom.conf is identical.)

Sep 27 10:38:15 mbox systemd-coredump[3623]: [🡕] Process 2166 (gnome-shell) of user 1000 dumped core.                 
                                                                                                                      
                                             Stack trace of thread 2166:                                              
                                             #0  0x00007fd1cc5d3a92 XGetWindowProperty (libX11.so.6 + 0x22a92)        
                                             #1  0x00007fd1cc5d44e9 XGetWMSizeHints (libX11.so.6 + 0x234e9)
                                             #2  0x00007fd1cd8b20ee n/a (libshell-17.so + 0x2b20ee)                   
                                             #3  0x00007fd1ccd22ca4 n/a (libmutter-17.so.0 + 0x122ca4)
                                             #4  0x00007fd1ccd27a12 n/a (libmutter-17.so.0 + 0x127a12)                
                                             #5  0x00007fd1cd2a5f4d n/a (libglib-2.0.so.0 + 0x5ef4d)                  
                                             #6  0x00007fd1cd2a7617 n/a (libglib-2.0.so.0 + 0x60617)                  
                                             #7  0x00007fd1cd2a79d7 g_main_loop_run (libglib-2.0.so.0 + 0x609d7)
                                             #8  0x00007fd156700df8 pamac_updates_checker_check_updates (libpamac.so >
                                             #9  0x00007fd1cbf56ac6 n/a (libffi.so.8 + 0x7ac6)
... 
(And a few more pages of this stack trace.)                      

My config already looks like this. Should I delete everything under /usr/share/xsessions then? Fyi, I was running Wayland on this machine from the beginning though :thinking:

No, as another package other than gnome-session probably owns that folder.

pacman -Qo /usr/share/xsessions/

Ok, I am a dummy :man_facepalming:, I accidentally switch off Wayland before the update instead of the GNOME extensions. Now I got GNOME running. Thanks!

1 Like

All went well. KDE, AM5 AMD CPU/Navi 31 GPU, Acer Spin 3 and Acer Spin 5.

1 Like

So, what’s the steps we should take if we’re Gnome users? From what I’m hearing:

  1. Timeshift Backup.
  2. Disable / Stop all extensions.
  3. Update to Gnome 49.0.
  4. Profit?

For those that maybe want to wait a bit, do we just skip this update until the next release? Just want to make sure I’m not fighting issues for too long.

Thanks!

Oh, no Star Trek Names anymore?

Interesting :smiley:

I am working nearly the whole day on my updated Gnome Notebook. Agree, the missing extensions are a pain. And there are still some functionalities of extensions (dash2panel) in the working ones, that (at least on two of my systems) are not working.
I did find workarounds. Other extensions that are nearly the same as the ones that are currently not working. And - ok, some are still not there (my learning for me: do I really need all this stuff ?!)

My summary after a working day with Gnome 49: I do not want to wait or switch back to Gnome 48!
Gnome 49 is so smooth, it feels so much better and faster - you can see the difference in “reaction time” in nearly each of the programs I use …

Edit: I would add one topic to your list (at least I tried this / did this / do this in a TTY prior to major gnome updates : rm -Rf ~/.cache.

Very minor issue here, and I presume it’s related to the Gnome issues people are having? I use KDE, but of course Firefox uses GTK to draw its window control buttons (I know I can give up screen real estate to have a system drawn title bar). This update blanks those 3 buttons out, and I’ve tried everything to get them back. Is that related to the Gnome issues and I should just wait it out?

Might you have a 3rd party GTK theme? All 3 users in my house with this update use Firefox with KDE and experienced no problems. You’re referring to the Maximize, Minimize and Close buttons I believe?

I’m not aware that I’m using a 3rd party GTK theme or that I’m doing anything non-standard with GTK. The first thing I tried was going to the KDE System Settings → Application Style, and then selected the Configure GNOME/GTK Application Style window. It was initially set to the default Breeze, but “Default” itself, Adwaita, or indeed anything else doesn’t make any difference. It’s a minor problem and one I’m not going to lose sleep over, but it is definitely related to this update. Timeshifting back fixes it. Reapplying the update breaks it. Haven’t noticed any other applications having issues other than Firefox.

A minor thing I realized: The new HDR brightness slider does not preserve its setting. After a reboot the adjustment is gone.