Page MenuHomeSolus

Meta: GNOME 3.32 Feedback and Testing Task
Open, Unbreak Now!Public

Description

With the availability of the GNOME 3.32 stack on the unstable repository, I'd like to have this task be designated as the primary task for providing feedback and validating various functionality, apps, etc.

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

  • Changes to Budgie Desktop (if something is blatantly broken however that is part of budgie-desktop, that should be filed on its dedicated issue tracker)
  • Changes to GNOME Shell
  • GNOME Applications
  • IBUS / Internationalization (Ibus saw an update)
  • MATE Desktop (May be affected by GNOME Stack Upgrade items such as GTK, libsoup, GLIB, etc)
  • Networking (Updated Network Manager)

We 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, Global Maintainers, Triage Team) can reference in this task.

We also welcome you to post a comment if an application which is not on the list, or is on the list but not marked off as completed / tested yet, continues to function as intended / similar to before this GNOME 3.32 stack upgrade.

Regardless, it'll give us a good idea on what further items need to be looked at and what our test coverage of this stack is.

Tested

  • Bluetooth
    • Tested with Bluetooth pairing in GNOME Control Center with Bluetooth speakers.
  • Desktops
    • Budgie Desktop
      • GDM (when co-installed with GNOME Shell)
      • LightDM + slick-greeter
    • GNOME Shell
      • GDM
    • MATE
  • Geolocation
    • Tested with GNOME Clocks, GNOME Maps, GNOME Weather
  • IBUS
  • Networking
    • Shares (Samba via Nautilus)
    • Wireless
    • Wired
  • Application
    • Aisleriot
    • Baobab (Disk Usage Analyzer)
    • Evince
    • Evolution
    • Firefox
    • Four-in-a-Row
    • GEdit
    • GIMP
    • GNOME 2048
    • GNOME Calculator
    • GNOME Calendar
    • GNOME Clocks
    • GNOME Control Center
      • About
      • Applications
      • Background
      • Bluetooth
      • Date & Time
      • Devices
        • Color
        • Displays
        • Keyboard
        • Mouse & Touchpad
        • Printers
        • Removable Media
        • Thunderbolt
      • Networking
        • Wi-Fi
        • Wired
      • Notifications
      • Online Accounts (Tested with Google Account)
      • Power
      • Privacy
      • Region & Language
      • Search
      • Sharing
      • 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 Documents
    • GNOME Help / Yelp
    • GNOME Music
    • 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 Twitch
    • GNOME Tweaks
    • GNOME Videos (Totem)
    • GNOME Web (Epiphany)
    • Glade
    • Hexchat
    • Liferea
    • Lollypop
    • Nautilus (3.26.x)
    • Polari
    • Rhythmbox
    • Seahorse
    • Shotwell
    • Solus Software Center
    • psensor

Known Issues

  • "Open In Software" in Applications tries to open GNOME Software. Needs to remove the button entirely.
  • Clock shows date by default in Budgie. This is likely the result of a defaults change in gsettings-desktop-schemas or gnome-desktop schemas and will be resolved in a follow-up update.
  • Natural Scrolling changed to be...unnatural. Needs to be fixed.
  • GNOME Multi-Writer cannot detect or write to USB. This is an upstream issue.

To Investigate

  • @alecbcs reported transparency level change in GNOME Terminal. Need to investigate that and ensure the new transparency level doesn't negatively impact readability and revert if that is indeed the case.
There are a very large number of changes, so older changes are hidden. Show Older Changes

Sorry if I'm not clear enough, if I turn on high contrast option it changes to High Contrast theme. After that if I turn off the option it will change my theme to Plata-Noir. Usually I use Plata-Compact so it's kinda strange.

@yursan9 I wonder if it is just defaulting to whatever the original default value in the schema was. That would explain it overriding your previous value, since it is effectively changing the user-set value rather than the default value to 'HighContrast'.

  • Printer settings in Gnome Control Center is OK for me. Printer is visible, I can interact with it.
  • Shotwell works too, no trouble so far with keyboard shortcut and manual launch
JoshStrobl updated the task description. (Show Details)Apr 25 2019, 2:05 PM

Fixed natural scrolling and clock format showing date by default.

JoshStrobl updated the task description. (Show Details)Apr 25 2019, 2:05 PM

Able to reproduce the font issue in GNOME Terminal now. Working on fixes.

Jacek added a comment.Apr 25 2019, 3:30 PM

Issue with Papirus icon set.
A lot of Gnome apps (terminal, system monitor, disk usage, screenshot, etc,) use default Icons instead of Papirus.

Yea, just re-run usysconf: sudo usysconf run -f

JoshStrobl added a comment.EditedApr 25 2019, 3:44 PM

GNOME Terminal fonts are now correct.

You will likely see changed fonts across your system if you have installed from Solus 4 Fortitude. This is actually the result of the fonts now being correctly applied, which they weren't apparently at release.

JoshStrobl updated the task description. (Show Details)Apr 25 2019, 3:50 PM
Jacek added a comment.Apr 25 2019, 4:05 PM

Yea, just re-run usysconf: sudo usysconf run -f

Thanks that was it. So will it happen automagicially for people on stable? If so, why didn't it on my machine?

In T7902#149334, @Jacek wrote:

Yea, just re-run usysconf: sudo usysconf run -f

Thanks that was it. So will it happen automagicially for people on stable? If so, why didn't it on my machine?

I can force it to trigger just by bumping an icon theme like Papirus, which wasn't the case on unstable. That's easy-peasy :D

Using Sardi-flat as icon theme.The icon for the teksteditor Write should look round with a white pen centered , After the update it has changed to https://i.imgur.com/tOxZBcp.png .
Dit run sudo usysconf run -f , and rebooted, but no effect

That's something you need to consult the Sardi icon theme devs about. They changed the icon and desktop file to org.gnome.gedit, which is the appropriate namespace path.

Gnome thunderbolt settings appear to be functioning as expected after installing bolt from the software center.

Jacalz added a subscriber: Jacalz.EditedApr 25 2019, 7:26 PM

I am fully up to date on Mate and using gnome-terminal. After the stack upgrade it has a really weird starting size and wrong fonts. I don't know if the fonts are related to font issues mentioned above, but this is how it looks:


Terminal size might be standard size, but the size is just horrible. We have widescreen monitors and not tallscreen monitors. I really hope there is something wrong here...

Mate Desktop Branding needs to be updated to set document and monospace fonts for the gnome schema paths.

Or you can use the actually supported terminal on MATE because I don't have an interest in adding Cantarell fonts as a rundep of GNOME Terminal just because of MATE.

Gnome thunderbolt settings appear to be functioning as expected after installing bolt from the software center.

That's great to hear. I'll add it as a rundep of GNOME Control Center.

@Jacalz A package update for mate-desktop-branding is incoming (or has already landed by the time you take a look at this) that may address it. Please update and reboot, then test the font(s). If it isn't fixed, I'll see about applying a GNOME schema.

@Jacalz A package update for mate-desktop-branding is incoming (or has already landed by the time you take a look at this) that may address it. Please update and reboot, then test the font(s). If it isn't fixed, I'll see about applying a GNOME schema.

Thanks, but it doesn't seem to fix the issue for me. I also checked a couple other terminals and it looks like tilix and roxterm also run in to the same issue (might be more terminals with this issue).

chax added a subscriber: chax.Apr 26 2019, 8:25 AM
This comment was removed by JoshStrobl.
This comment was removed by JoshStrobl.

Deleted comments. As stated in the task, file the Budgie issues on its tracker.

@Jacalz A package update for mate-desktop-branding is incoming (or has already landed by the time you take a look at this) that may address it. Please update and reboot, then test the font(s). If it isn't fixed, I'll see about applying a GNOME schema.

Thanks, but it doesn't seem to fix the issue for me. I also checked a couple other terminals and it looks like tilix and roxterm also run in to the same issue (might be more terminals with this issue).

Noted. I'll update it to include a schema for GNOME then.

JoshStrobl updated the task description. (Show Details)Apr 26 2019, 10:53 AM

Tested on a new VM with MATE updated to 1.22.1 and I haven't faced any problem.
Notifications are working and the fonts (in MATE terminal) are fine. I'll make some more tests later and I'll give a try to GNOME terminal too.

This comment was removed by watpi.
Christoph3 added a comment.EditedApr 26 2019, 8:27 PM
  • Gnome-calendar - i checked one error that only occurs for fresh install of solus and upgrade to unstable repo. The error is this . I have gnome-calendar installed but if go to the defautl apps i dont have the change to select gnome-calendar in "calendar app". I thought it might be a problem of my machine and did a fresh install of solus in virtualbox , checked the clock applet and entered the calendar without problems, after this i removed the solus repo / added the unstable one and upgraded the system, after did the same test and it opens two windows of gedit. The problem its in the .desktop file "/usr/share/applications/org.gnome.Calendar.desktop" the mimetype was removed from there, i had to put it manually and do a sudo usysconf run -f , after that i the clock applet "calendar" working again.
  • Menulibre does not work after the upgrade (like before , fresh install + unstable repo upgrade) , it gives this error https://hastebin.com/acezevupeq.sql . (i also tested this in real machine + virtualbox install )

Note - i check the eopkg Gnome calendar in the unstable repo and decompressed it and it misses the mimetype in the .desktop file. In a fresh install of Solus the mimetype is there.

  • Menulibre does not work after the upgrade (like before , fresh install + unstable repo upgrade) , it gives this error https://hastebin.com/acezevupeq.sql . (i also tested this in real machine + virtualbox install )

Does work on my install.

This comment was removed by Christoph3.
In T7902#149429, @watpi wrote:
  • Menulibre does not work after the upgrade (like before , fresh install + unstable repo upgrade) , it gives this error https://hastebin.com/acezevupeq.sql . (i also tested this in real machine + virtualbox install )

Does work on my install.

Fresh install of solus + unstable repo upgrade ?

Reinstalled a couple days ago and upgraded unstable when the gnome testing was announced so yeah, pretty fresh.

This comment was removed by Christoph3.
In T7902#149431, @watpi wrote:
In T7902#149429, @watpi wrote:
  • Menulibre does not work after the upgrade (like before , fresh install + unstable repo upgrade) , it gives this error https://hastebin.com/acezevupeq.sql . (i also tested this in real machine + virtualbox install )

Does work on my install.

Fresh install of solus + unstable repo upgrade ?

Reinstalled a couple days ago and upgraded unstable when the gnome testing was announced so yeah, pretty fresh.

Did you made the initial update after the fresh install using the stable repo ? I'm asking this because i did a fresh install but didnt update it with the stable repo, removed it , added the unstable , sudo eopkg ur & sudo eopkg up

Guess I did.

This comment was removed by Christoph3.

Please don't keep quoting to reply to messages. This is becoming a matrioska.

JoshStrobl added a comment.EditedApr 26 2019, 10:59 PM

I concur. Please stop. Thanks.

Besides that point, menulibre is fundamentally broken. It has been for some time. This is not actually new. Use mozo, it ships in the ISO. If we need to sort out Brisk Menu to call it, we can. If anything we should nuke menulibre.

Removed the quotes, its hard sometimes to response to someone without the context before but ok. Regarding gnome-calendar, im sorry about the big text before, but i was showing to other users (that might had the same problem as me) the solution.

@Christoph3 You can do that without quoting the entire thing every time. And that was a short enough exchange to be able to read the previous posts for context.

everyday learning . do you need that i remove my original post also ? thanks

If something needs to be removed, we will take care of it. You're fine, just take it easy with quoting :p

@Christoph3 It's look like menulibre found invalid utf-8 character in .desktop files. Try moving all local desktop file from $HOME/.local/share/applications, then open menulibre.

@yursan9 dont have files there.

@Christoph3 dang, I'm stuck. Maybe some packages provided invalid utf-8 character, because I don't have the error on my Budgie installation.

Staudey added a subscriber: Staudey.EditedApr 27 2019, 11:09 AM

Seems like it could be a general problem with menulibre and languages other than English:

https://bugs.launchpad.net/menulibre/+bug/1825817

edit: and this bug report includes a patch for it:

https://bugs.launchpad.net/menulibre/+bug/1817885

@Staudey thanks , this

fixes the menulibre app, it works now.

I confirm the font problem in Termnials on MATE. Only the MATE terminal looks fine. When I change the fixed width font in the settings only MATE terminal is impacted.

JoshStrobl added a comment.EditedApr 28 2019, 10:01 AM

I know, I already stated I'd fix it. It's the weekend man, didn't get any downtime last weekend because of these pesky little GNOMES.

https://dev.getsol.us/T7902#149367

Sorry @JoshStrobl, I missed that and I put the point in my to-check list

Anyone want to patch the menulibre? I can do it tomorrorw

Anyone want to patch the menulibre? I can do it tomorrorw

Here it is D6138. I added the patch but it did not fix anything on MATE so I guess the easiest workaround is to exclude MATE from it. There are working alternatives.

gnome-multi-writer crashes here whenever a flashdrive is inserted, including if the flashdrive was inserted before gnome-multi-writer was launched.

@moriel5 Issue was reported here but nobody provided them details on it.

moriel5 added a comment.EditedApr 28 2019, 7:44 PM

Thanks, I'll try to diagnose the situation.
As for Maté notifications, I'll try looking into it afterwards.

Update: It appears that the reason for the crash is due to GNOME MultiWriter being unable to assert anything in relation to the removable drive.
I'll post my STrace in that issue after I make an account on GNOME's GitLab instance.

Update2: I have commented and uploaded my STrace results to that issue.

pat-san added a subscriber: pat-san.EditedApr 29 2019, 8:29 AM

Hi,
Same problem here with GnomeMultiWriter, I can launch it if there is no USB flash drive plugged in, but as soon as I plug in one, the GMW window closes. Also, it is impossible to launch it if a USB flash drive is already connected.

GMW opened via terminal, inserting a usb key:

(gnome-multi-writer:4703): GLib-GObject-CRITICAL **: 14:54:41.198: g_object_ref: assertion 'old_val > 0' failed

(gnome-multi-writer:4703): Gmw-CRITICAL **: 14:54:41.198: gmw_device_set_order_process: assertion 'GMW_IS_DEVICE (self)' failed

(gnome-multi-writer:4703): Gmw-CRITICAL **: 14:54:41.198: gmw_device_get_block_path: assertion 'GMW_IS_DEVICE (self)' failed

(gnome-multi-writer:4703): GLib-GObject-CRITICAL **: 14:54:41.198: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Erreur de segmentation

A problem with hibernation that worked very well before, but it doesn't work anymore since I went to unstable repo to test. After putting my laptop back on, I end up with a black screen with white pixels that invade the entire screen.

@kyrios123 @Jacalz Can you both please re-test the terminals against mate-desktop-branding (shouldn't matter if you're using the legacy / shared package, material, or fortitude) rel 43?

@pat-san Please provide your strace at this issue like @moriel5 did. This is not a Solus-specific issue and should be handled upstream with the respective project.

Unfortunately issue is still there :(

JoshStrobl updated the task description. (Show Details)Apr 29 2019, 1:08 PM
JoshStrobl updated the task description. (Show Details)
moriel5 added a comment.EditedApr 29 2019, 2:32 PM

I had just tested the Maté notification timeout issue here.
Changing either the notification theme or it's position yielded no changes, with the same exact timeout error message.

I had also tried invoking a notification from other applications (such as gnome-terminal), and notifications appeared.

@moriel5 Please test mate-notification-theme-slate release 9 (will require you to update and reboot your system). I've tested it prior to my fix and was able to reproduce your issue.

MATE Notification Theme Slate has been bumped to a new release, 6.0, which has MATE 1.22 support. I've also properly fixed (I swear, for realsies this time) fonts under MATE Desktop Branding.

Yes indeed, I can confirm that the fonts now look a lot better now 👍

Printers and Scanners still works fine here.

Jacalz added a comment.May 1 2019, 9:01 AM

I don't know if this is due to the Gnome 3.32 changes and the theme slate, but notifications seem to have a weird black shadow. None of the other themes show the same shadowy outline:

Hi there!

Running the unstable branch on my desktop and my worknotebook since Saturday the 4th.

Runs smooth and without major issue. In fact I only discovered 1 minor issue: once in a while my mousepointer locks, isn't usable or responding at all. Happens with both a mouse and trackpad.
Happens to me like once a day on my intel notebook and amd desktop running Solus unstable branch.

Current workaround I use is to switch to another terminal using CTRL+ALT+F2 and switch back, works fine after that.

Couldn't find anything in the logs, but to be honest I am not sure what to look for, so I just looked for "mouse" and "synaptics". Hope this helps, let me know if I can look for something in my logs.

Hi there!

Running the unstable branch on my desktop and my worknotebook since Saturday the 4th.

That's tomorrow !

People on Unstable are living the future NOW!

Jacek added a comment.May 3 2019, 1:07 PM

The only problem I noticed is a weird problem with waking up from hibernation. The whole desktop is unresponsive, but in a weird way. Notifications work, I can use shortcuts to e.g. disable touchpad and change brightness and get an according popup, but I can neither move the mouse nor use keyboard to navigate, so no ALT + TAB or Budgie Menu via Windows/Super key. And CTRL + ALT + F2 and then CTRL + ALT + F7 doesn't help, more so, I don't get login prompt when CTRL + ALT + F2.
So I don't know if that's important as my laptop has had pretty broken suspend anyways

Hi, I just updated to 3.32 stack on stable. I am using Budgie and flatpak icons are broken. Could this be a budgie specific bug?

As seen above the icons are not loaded in the task menu, only one strange icon appeared for the first flatpak app launched.

@Alexandru-Balan If you run sudo usysconf run -f, does the icon get replaced at all? If not, it may indeed be a new Budgie issue that I'll need to investigate.

@JoshStrobl I ran that and rebooted, everything seems normal now thanks. All the icons from flatpak apps appear as usual in the bar

Odd, Papirus should've triggered the usysconf trigger to clear the icon cache, not sure why it didn't for you. Glad your issue is fixed though!

Anyone having Firefox addon issues since this rolled out? Installed addons became unverifiable and new addons cannot be installed at all :/

Harvey added a subscriber: Harvey.May 4 2019, 3:11 AM

@nickrogovik Not a Solus / Gnome issue but a Mozilla screw up:
https://www.reddit.com/r/firefox/comments/bkfg00/also_had_all_my_addons_disabled_and_cant/

Mozilla are working on it.

@Harvey Thanks, I see that now. Bad timing I guess.

@nickrogovik Not a Solus / Gnome issue but a Mozilla screw up:
https://www.reddit.com/r/firefox/comments/bkfg00/also_had_all_my_addons_disabled_and_cant/

Mozilla are working on it.

Yeah this is totally unrelated and should have its own task if someone gets impacted (at the moment all my extensions are enabled and working fine and I just booted my PC a few minutes ago)