Page MenuHomeSolus

Meta: GNOME 40 Stack Testing and Feedback
Closed, ResolvedPublic

Description

GNOME 40 Stack Upgrade Notes

WARNING: Please read this task in its entirety before commenting or upgrading. Seriously.

As is tradition, I'm opening up a task for everyone to report their issues with the GNOME 40 stack upgrade. It's absolutely important we maintain focus on reporting issues which are specifically related to this stack upgrade so we can best work to helping validate and resolve these issues. I welcome you to post a comment if an application is suddenly not working and you strongly believe it is the result of the new stack upgrade, such as it suddenly missing libraries or ones which may warrant a rebuild. If necessary, we may request you file a separate issue so we may obtain further detailed information, which we (#core_team_org, Triage Team) can reference in this task.

NOTE: This task content can only be modified by members of the Core Team or Global Maintainers. We will update the task as comments / feedback are received.

The objective of this task is to facilitate technical discussions around changes which have occurred in the GNOME Stack, such as:

  • Updates made to Budgie Desktop to facilitate the new stack upgrade, primarily Mutter 8 and GNOME Settings Daemon 40 changes.
  • Changes to GNOME Shell 40
  • GNOME Applications

This testing is being performed on the unstable repository and may also involve or require real-time communication via our development IRC channel. If you are not in IRC, use any supported IRC client that we provide in the repo (e.g. Hexchat, weechat, irssi, Konversation) and look at our Getting Involved Page for connection details.

If you are not on the unstable repository and wish to help test, assuming you understand that the intent of unstable is to be the place where we break stuff and operate under the assumption you check IRC to know when not to update, you can run the below mentioned command to switch to the unstable repository:

sudo eopkg ar Solus https://mirrors.rit.edu/solus/packages/unstable/eopkg-index.xml.xz

Upgrading Properly

Do not run any commands until you fully read this section. Thank you.

I cannot stress enough the importance of ensuring you upgrade properly and fully. If you are not on unstable already, you should fully upgrade your system by opting in to every package update available via the Software Center or running sudo eopkg up then reboot before switching over to unstable.

If you are on the unstable repository, likewise perform a full upgrade via either the Software Center or the Terminal, then reboot. If you use Budgie and GNOME and encounter the grey "Something happened" fullscreen window after a reboot and attempt to login, switch to a TTY (typically Ctrl+Alt+F2-9, pick one), login and run sudo usysconf run -f then reboot (sudo reboot).

If you are using GNOME Shell, you need to run the following command after the upgrade if you use GNOME Shell to properly reset your extensions back to the stock configuration:

gsettings reset org.gnome.shell 'enabled-extensions'

Seriously, be sure to disable any extensions which we do not provide / have enabled out-of-the-box. Otherwise you may have a completely broken GNOME Shell experience, or worse it'll crash and you'll have to go through loads of hoops such as hand modifying dconf key values and nuking some extension contents, etc. It is not my responsibility nor the responsibility of GNOME to ensure those extensions are maintained and updated against newer GNOME Shell APIs. If they break, you'll need to talk to the extension developer. Additionally ensure you are not updating the extensions we support and directly provide, such as Tray Icons Reloaded, through any software such as Extensions app and website It may result in a broken installation. If you "upgraded" extensions through that manner, it's suggested you uninstall them and reinstall the package equivalent if possible.

WARNING: Like I said earlier, reboot your system after upgrading. For realsies.

Budgie

This GNOME Stack upgrade features a pre-release of Budgie 10.5.3. Budgie 10.5.3 will be a minor release focused on bug fixes and GNOME 40 support, I am not blocking the release with any of the features and architectural changes I originally was going to do for .3, those can get in for .4.

Changelog:

  • Don't filter device added / removed notifications.
  • Enable ability to click on panel icon to toggle lock keys.
  • Filter out Audacious notifications so they don't clutter up Raven.
  • Fix application icons not scaling in Notification Group headers.
  • Fix issue with VirtualBox not displaying in IconTaskList
  • GNOME Settings Daemon 40 fixes for font antialiasing and hinting
  • Multiple X error handling and stability improvements for Carbon Tray.
  • Mutter 8 support.
  • Resolve issues with fullscreen tracking.
  • Optimizations in MPRIS (eliminating of unnecessary idles) and Notification rendering / positioning
  • Use IconSize.DIALOG instead of IconSize.INVALID for various parts of Notifications and only scale if height isn't already 48px

GNOME Shell

GNOME Shell 40 predictably has a fundamentally changed user experience. I am shipping a slightly less modified GNOME Shell with this stack upgrade and some default theme changes for it.

  1. Dash to Dock is temporarily deprecated from the Solus repositories and is longer enabled by default via our desktop branding. I will reintroduce Dash-to-Dock support when the current merge request for GNOME 40 support, which introduces some instability and is "very much WIP" (exact quote), is merged in and a release is tagged around it.
  2. The remaining extensions enabled by default, like Tray-Icons-Reloaded, are still supported and enabled.
  3. Plata Theme has been swapped out for Materia GTK Theme. Plata Theme has not seen developed since the GNOME 3.38 stack release, which has meant considerable breakages under 40, alongside GTK4. Materia GTK Theme provides a very similiar look and feel, so I am comfortable with this switch (even though I generally avoid changing icon themes and gtk themes out from under folks). If you changed your GTK or Shell theme to not being Plata-Noir, run the commands below:
gsettings reset org.gnome.desktop.interface 'gtk-theme'

Known Issues or WIPs

GNOME Shell

As with any desktop environment, there are wide range of issues with GNOME Shell. I would advise checking https://gitlab.gnome.org/GNOME/gnome-shell/issues before reporting them here. If there is a patch and we don't have it yet, I'll see about getting it added.

Mutter

I currently have a couple patches in our Mutter to fix some issues I noticed with the WM becoming a stuttery mess, however git builds are otherwise pretty broken (really bad artifacting), so we are using a fairly barebones Mutter 40 release this time around. If you have issues with Mutter, please post them to https://gitlab.gnome.org/GNOME/mutter/issues/

Deprecations / Held Back

There are several deprecations and packages held back (permanently) this cycle.

Deprecations:

  • Various docs packages that are very unlikely to be used and not worth the extra effort to keep enabled. No drama on this one.
  • epiphany: We have multiple alternative and objectively better web browsers in our repos. Epiphany has been held back for some time due to libhandy and I am more comfortable with deprecating it at this point. You can always get it from Flatpak.
  • gnome-clocks: Used libhandy but actual deprecation reason is it does not support new gweather APIs.
  • goocanvas1 and pygoocanvas: No longer needed for anything, really old packages. No drama on this one.
  • libzapojit: Nothing uses it anymore. Should have actually been deprecated during the GNOME 3.38 stack. No drama on this one.
  • nemiver: Has not been developed for a number of years by GNOME and they have other debugging utilities like what you can get via sysprof and Builder. No drama on this one.

Held Back:

  • Due to libhandy library requirement, which we're not allowing into the repo (it's a mobile-focused graphics library being shoehorned into GNOME apps), the following packages are held back to their last pre-libhandy release:
    • Unchanged from previous stack upgrades: deja-dup, geary, gnome-calendar, gnome-screenshot, gnome-tweaks, seahorse
    • New: baobab, gnome-disk-utility, gnome-maps

Testing List

Testing Notes:

  1. This list may not be comprehensive. Feel free to report other things!
  2. Phabricator may indicate something is complete even if it isn't explicitly checked off. Ignore that and only look for the checkbox.
  3. There are numerous sections within GNOME Control Center (Settings) that are only applicable to GNOME Shell. If something does not work under Budgie, it does not necessarily mean that functionality is actually broken, but rather it may be the unfortunate result of the functionality targeting a specific desktop environment.
  • Bluetooth
    • Tested with Bluetooth pairing in GNOME Control Center with phone.
  • Desktops
    • Budgie Desktop
      • GDM (when co-installed with GNOME Shell)
      • LightDM + slick-greeter
    • GNOME Shell
      • GDM
    • MATE
  • Geolocation
    • Tested with GNOME Weather
  • IBUS
  • Networking
    • Shares (Samba via Nautilus)
    • Wireless
    • Wired
  • Applications
    • Abiword
    • Aisleriot
    • Baobab (Disk Usage Analyzer)
    • Bookworm (due to Granite update)
    • Claws Mail
    • Evince
    • Evolution
    • Four-in-a-Row
    • Gaupol
    • GEdit
    • GIMP
    • GNOME 2048
    • GNOME Calculator
    • GNOME Calendar
    • GNOME Control Center
      • About
      • Applications
      • Background
      • Bluetooth
      • Date & Time
      • Devices
        • Color
        • Displays
        • Keyboard
        • Mouse & Touchpad
        • Printers
        • Removable Media
      • Networking
        • Wi-Fi
        • Wired
      • Notifications
      • Online Accounts (Tested with a Google Account)
      • Power
      • Privacy
      • Region & Language
      • Search (only applies to GNOME Shell)
      • Sharing - Needs additional love. See T9407
      • Sound
      • Universal Access
        • Cursor Size
        • Hearing -> Visual Alerts
        • High Contrast
        • Large Text
        • Pointing -> Click Assist
        • Pointing -> Double-Click Delay
        • Pointing -> Mouse Keys
        • Screen Reader
        • Screen Keyboard
        • Sound Keys
        • Typing -> Repeat Keys
        • Typing -> Cursor Blinking
    • GNOME Disks
    • GNOME Help / Yelp
    • GNOME Nibbles
    • GNOME Photos
    • GNOME Pomodoro
    • GNOME Power Statistics (GNOME Power Manager)
    • GNOME Logs
    • GNOME MPV
    • GNOME Mahjongg
    • GNOME Maps
    • GNOME Music
    • GNOME Screenshot
    • GNOME Sudoku
    • GNOME Sound Recorder
    • GNOME Tweaks
    • GNOME Videos (Totem)
    • Glade
    • Gthumb
    • Lollypop
    • Lyx
    • Nautilus
    • Pitivi
    • Polari
    • Quodlibet
    • Rhythmbox
    • Seahorse
    • Simple Scan
    • Shotwell
    • Solus Software Center
    • Transmission
    • Vocal
    • budgie-extras applets if you happen to use them
    • deja-dup (held back, 42.x requires libhandy)
    • gtkhash (optionally the nautilus and caja extensions)

Event Timeline

JoshStrobl triaged this task as High priority.
JoshStrobl created this task.
JoshStrobl moved this task from Backlog to Improvement on the Software board.
Harvey added a subscriber: Harvey.Sun, Apr 18, 2:41 AM

Just updated on Budgie. Was able to login, lock screen, change theme without issue 👍

algent added a subscriber: algent.Sun, Apr 18, 3:53 AM

budgie-extras applets if you happen to use them

Who isn't? :D
All supported applets are working fine.

Harvey removed a subscriber: Harvey.Sun, Apr 18, 3:53 AM
sangheeta added a subscriber: sangheeta.EditedSun, Apr 18, 5:04 AM

Budgie here, so far so good, I feel that the session is opening faster :)
sleep & hibernate are ok.

Katoa added a subscriber: Katoa.Sun, Apr 18, 1:05 PM
JoshStrobl updated the task description. (Show Details)Sun, Apr 18, 1:50 PM

Items tested and working:

  • Abiword
  • Claws Mail
  • Polari
  • Quod Libet
  • gtkhash

Tested Transmission, downloaded an iso without issue

JoshStrobl updated the task description. (Show Details)Sun, Apr 18, 3:22 PM

Tested IBUS with the following keyboards/character pickers:

  • English
  • Spanish
  • Russian
  • Japanese (had to launch ibus-daemon with the panel)
  • Emoji
  • Unicode
JoshStrobl updated the task description. (Show Details)Sun, Apr 18, 3:43 PM

gThumb open and edit an image using the tools crop, rotate and resize.
bookworm open an ebook and a PDF file. Increase/Decrease font size, align lines right and left, dark mode and try different profiles.

Staudey added a subscriber: Staudey.EditedSun, Apr 18, 4:04 PM

Budgie: After the update I noticed that some of my applets were gone. I tried to open Budgie Desktop Settings, which restarted the panel. Trying to open it again showed the "Oh no, something went wrong!" screen and forced me to log out.
I get these messages when trying to open Budgie Desktop Settings:

Apr 18 17:58:00 solus-pc budgie-panel[2524]: Settings schema 'com.solus-project.budgie-wm' does not contain a key named 'pause-notifications-on-fullscreen'
Apr 18 17:58:00 solus-pc audit[2524]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=2 subj=unconfined pid=2524 comm="budgie-panel" exe="/usr/bin/budgie-panel" sig=5 res=1
Apr 18 17:58:00 solus-pc kernel: traps: budgie-panel[2524] trap int3 ip:7fa497f3fee7 sp:7ffc9ef4d4c0 error:0 in libglib-2.0.so.0.6800.1[7fa497f02000+8b000]
Apr 18 17:58:00 solus-pc gnome-session[2309]: gnome-session-binary[2309]: WARNING: Application 'budgie-panel.desktop' killed by signal 5
Apr 18 17:58:00 solus-pc gnome-session-binary[2309]: WARNING: Application 'budgie-panel.desktop' killed by signal 5

On the other hand I just played a round of Gnome Mahjongg without issues :)

JoshStrobl added a subscriber: serebit.EditedSun, Apr 18, 5:34 PM

If you tried opening up Budgie Desktop Settings and it crashed, as well as seeing the below mentioned log item, then that's curious indeed. The respective schema was correctly added by @serebit in this commit, so it would have the schema. Is it possible you're not running our Budgie somehow, ever compiled it from source yourself? That would explain the Budgie Desktop Settings crashing the panel, since that happens if you are using a Budgie Desktop that isn't compiled against the new gsettings-desktop-schemas and gnome-settings-daemon, since I have a patch in our Budgie which uses the right keys from the right schema for font-hinting and font-antialiasing.

Apr 18 17:58:00 solus-pc budgie-panel[2524]: Settings schema 'com.solus-project.budgie-wm' does not contain a key named 'pause-notifications-on-fullscreen'

It'd also run counter to @algent's testing of budgie-extras applets. I've personally tested the screenshot applet and it functions, didn't see any missing and our ABI has not changed.

JoshStrobl updated the task description. (Show Details)Sun, Apr 18, 5:36 PM
davidjharder added a comment.EditedSun, Apr 18, 6:42 PM

Tested Vocal, added podcasts from iTunes search and directly from URL, played podcasts without issue. Scrolling through audio, skip button working as expected.

I noted that the mouse-over text in the taskbar is weird. See image. I don't have a second Budgie machine to confirm this on, someone else will need to try it.

serebit added a comment.EditedSun, Apr 18, 6:48 PM

Notes on the new Budgie sync for those testing this upgrade:

  • If you notice the Budgie panel crashing at any point (which can be either restarting or vanishing entirely), report it with any journalctl logs from budgie-panel from the time of the crash.
  • If you use the existing "Disable Night Light mode when windows are fullscreen" or the new "Pause notifications when windows are fullscreen" settings, please report if you find an application that does not properly trigger either of these.

If you encounter these issues, report them on the Budgie issue tracker. They are unlikely to be Solus-specific.

Staudey added a comment.EditedSun, Apr 18, 7:03 PM

@JoshStrobl So I did a eopkg it --reinstall budgie-desktop and restarted. While I had to re-add most of my applets, everything works fine now. Guess there might have been some leftover from when I built my own Budgie for testing. Sorry for the confusion!

Budgie issues should be reported on its own issue tracker @serebit, not here. We state it on the welcome section of Phabricator. Budgie issues may not be Solus specific.

@davidjharder Vocal reports its WM_NAME and _NET_WM_NAME as "com.github.needleandthread.vocal" instead of just Vocal, so it shows up as that. Once you pin, close, and re-launch it, Budgie will use the DesktopAppInfo. There is probably some refinements we can make around that in.

JoshStrobl updated the task description. (Show Details)Sun, Apr 18, 8:05 PM
serebit removed a subscriber: serebit.Sun, Apr 18, 8:46 PM

Sorry, I only added it to my previous comment at the bottom, but GNOME Mahjongg works correctly (played two games without any issues).

JoshStrobl updated the task description. (Show Details)Mon, Apr 19, 4:42 PM

I think it can already be updated next Saturday

Various fixes for GNOME Shell have been synced via R993:b917bf05685c: Sync with git.. If you use GNOME Shell, I encourage you to update and test.

I'd like to add that I use GNOME and have had no major issues with this upgrade. I haven't yet tried the new patches yet though.

Using Budgie and it seems like I am stuck with Night Light enabled at a specific temperature and with no way to turn it off, unfortunately. Could not use throwback without switching back to the stable repository, either, due to the removal of the epihany package.

Using Budgie and it seems like I am stuck with Night Light enabled at a specific temperature and with no way to turn it off, unfortunately. Could not use throwback without switching back to the stable repository, either, due to the removal of the epihany package.

It's configurable using both the Night Light section under the Display panel in GNOME Control Center, as well as more granular control using the Night Light applet. Working fine here. If you are having issues with it, I would appreciate if you could file a bug at https://github.com/solus-project/budgie-desktop/ with your journal content during the night mode setting temperature changing so I can see if there is an issue in GNOME Settings Daemon or Mutter for it (or a fix already in place).

Tested Lyx: Created a test document viewed the pdflatex output, used spellcheck. Works as expected.

@Phantop Any chance this was after some sort of power saving mode, like screen dimming enabling or wake-from-suspend? Seeing https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1835

Katoa added a comment.EditedThu, Apr 22, 12:42 PM

@Phantop I think i have the same issue, had a red/orange tint on the screen after updating, turning Night Light off did not change anything. Found that changing color profile for my screen, brought back the normal colors i was used to. In my 4 years on Solus the color profile have been the same (the name of my monitor), and i have not had this issue previously.

Settings > Colors - Remove your color profile, then try adding "Colorspace: sRGB".

Various fixes for GNOME Shell have been synced via R993:b917bf05685c: Sync with git.. If you use GNOME Shell, I encourage you to update and test.

After installing this update "gnome-shell is upgraded from 40.0-71-1-x86_64 to 40.0-72-1-x86_64 with delta", the background (wallpaper) turned black. Re-setting the wallpaper or switching it to a different one has no effect, it's black still.

algent added a comment.EditedThu, Apr 22, 1:59 PM

Instead of black background i get blue background. Tried to resintall gnome-shell but issue is not resolved. Can't change background from gnome-settings and gnome-tweeks too.

algent added a comment.EditedThu, Apr 22, 2:24 PM

I built gjs with this patch and fixed the background issue.

Thanks I'll get ours fixed @algent.

In T9683#183764, @Katoa wrote:

@Phantop I think i have the same issue, had a red/orange tint on the screen after updating, turning Night Light off did not change anything. Found that changing color profile for my screen, brought back the normal colors i was used to. In my 4 years on Solus the color profile have been the same (the name of my monitor), and i have not had this issue previously.
Settings > Colors - Remove your color profile, then try adding "Colorspace: sRGB".

Ah this fixed it! Yeah same, have been using Solus for 4 years and never had this issue before. Thanks for the help.

Katoa added a comment.Sat, Apr 24, 7:22 PM

Looks like the color/ICC display profile issue has been reported, despite the post's headline this affects both AMD & Nvidia users.
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4071

The solution for now is to choose another profile than the default.

The boring thing is that when computer resume work after sleep, I have to put two times the password in login window. After entering password first time login window is loaded again, then you have to put the password for the second time.

The boring thing is that when computer resume work after sleep, I have to put two times the password in login window. After entering password first time login window is loaded again, then you have to put the password for the second time.

Yeah I can report this same issue on Budgie.

@algent and @Phantop, @YakoYakoYokuYoku was able to reproduce it when using Auto Suspend + lock when screen turns off. Unfortunately I have not yet been able to reproduce it. I tried validating on both my laptop (fully AMD) and desktop (AMD CPU + NVIDIA GPU). Could you folks let me know what hardware you're running on?

Found some issues filed in Mutter land related to resume from suspend, but they seem to be mostly related to Wayland and Intel:

After inspecting logs provided by YakoYako, the only thing I noticed was lines like gkr-pam: the password for the login keyring was invalid. , however in those cases the login password may have literally been invalid, and random Source ID ### was not found [...] which is a non-fatal GLib warning. In my case there was an immediate gkr-pam unlock on the keyring, then the usual pam_warn.

@algent and @Phantop, @YakoYakoYokuYoku was able to reproduce it when using Auto Suspend + lock when screen turns off. Unfortunately I have not yet been able to reproduce it. I tried validating on both my laptop (fully AMD) and desktop (AMD CPU + NVIDIA GPU). Could you folks let me know what hardware you're running on?

I'm using an Intel i7 6700 CPU and an XFX AMD RX 570 GPU on an HP 2B47 motherboard (OEM) on a desktop.

Unfortunately I have not yet been able to reproduce it. I tried validating on both my laptop (fully AMD) and desktop (AMD CPU + NVIDIA GPU). Could you folks let me know what hardware you're running on?

https://dev.getsol.us/P16 is my journalctl log since waking from sleep.

JoshStrobl added a subscriber: serebit.EditedTue, Apr 27, 2:41 PM

Thanks to some additional testing with @serebit and a sneaking suspicion it was related to a gnome-settings-daemon change, I asked @serebit to test if moving sudo mv /usr/share/dbus-1/services/org.gnome.ScreenSaver.ForBudgie.service ~/xyz resolved the issue after a reboot and at least the early report indicated it was.

Before I tag a new release of budgie-screensaver, @Phantop could you be a lovely hooman and try running the command above, rebooting, and seeing if it fixes the issue for you too?

Btw my hardware is:

$ lscpu
 Model name:          AMD Ryzen 7 2700 Eight-Core Processor
$ lspci
 1d:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Bonaire XTX [Radeon R7 260X/360] 
 1d:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Tobago HDMI Audio [Radeon R7 360 / R9 360 OEM]

sudo mv /usr/share/dbus-1/services/org.gnome.ScreenSaver.ForBudgie.service ~/xyz

@JoshStrobl I run that command and the issue was resolved after reboot.

Katoa added a comment.Tue, Apr 27, 8:07 PM

GNOME Pomodoro tested as i did in Gnome 3.38.

Issues:
Closing the program by clicking the X, will leave it open if you look in System Monitor. Closing it from the drop down menu by choosing quit, will close the program as expected. Cant find any open bug reports regarding this issue.

Not tested:
Plugins

Katoa added a comment.Tue, Apr 27, 8:10 PM
This comment was removed by Katoa.
Katoa added a comment.EditedTue, Apr 27, 8:13 PM

GNOME Maps tested (been using the program under Gnome 3.38)

Issues:
None

Not tested:
Set up OpenStreetMap Account

JoshStrobl updated the task description. (Show Details)Wed, Apr 28, 10:28 AM
JoshStrobl closed this task as Resolved.Fri, Apr 30, 4:38 PM

Thank you everybody that contributed to testing. You da real MVPs. Now that the stack has been deployed to stable, closing this.