Ubuntu 20.04 beta bugs and current state

gnome-software, ubuntu-software and snap-store disguised as ubuntu-software:

In this screen ubuntu-software and snap-store are running. When installing gnome-software the ubuntu-software logo is used instead of the gnome store one. Sometimes the snap-store (deguised as ubuntu-store) makes the original snap-store launcher to appear. 1 Dot on the dock is missing. the deb store launcher is tranlated but the snap-store launcher isn’t.

snap-store can’t find updates.
snap-store is still based on gnome-software 3.34


When you switch to deb archive (the buggy blank one lol) you can’t switch back to snap channels. + Icons of deb packages can’t be found.

snap-store is using too much RAM (memory leak ?)

gnome-shell is still 3.36.0 but the gnome-shell 3.36.1 has been released. Following bugs may already be fixed.

This menu is sometimes buggy. You can reproduce it: click on Activities, click on the 9 dots and scroll 1 time to the bottom.

Capture%20d%E2%80%99%C3%A9cran%20de%202020-04-09%2014-43-02 Some icons are distorted on the topbar and when using super+Tab.
Also distorted.
Memory leak ? (using AMD Radeon HD (Juniper) GPU)

Sometimes the cursor don’t change appearance (for exemple when draging a headerbar).

gnome-shell 3.36.1 is now in the repos.

Grub/Shim packages:

Currently I get the following error:

dpkg: Abhängigkeitsprobleme verhindern Triggerverarbeitung für shim-signed:
shim-signed hängt ab von grub-efi-amd64-signed | grub-efi-arm64-signed; aber:
Paket grub-efi-amd64-signed ist noch nicht konfiguriert.
Paket grub-efi-arm64-signed ist nicht installiert. 
dpkg: Fehler beim Bearbeiten des Paketes shim-signed (--configure):
Abhängigkeitsprobleme - Trigger bleiben unverarbeitet
Trigger für dbus (1.12.16-2ubuntu2) werden verarbeitet ...
Trigger für libc-bin (2.31-0ubuntu7) werden verarbeitet ...
Fehler traten auf beim Bearbeiten von:
E: Sub-process /usr/bin/dpkg returned an error code (1)

Is it safe to shutdown/reboot? Or should I better wait for new GRUB/Shim versions to be published?

amano@amano-desktop:~$ apt list --all-versions --installed *shim*
Auflistung... Fertig
shim-signed/now 1.41+15+1552672080.a4a1fbe-0ubuntu1 amd64 [Installiert,lokal]
shim-signed/focal 1.40+15+1533136590.3beb971-0ubuntu1 amd64

shim/now 15+1552672080.a4a1fbe-0ubuntu1 amd64  [Installiert,lokal]
shim/focal 15+1533136590.3beb971-0ubuntu1 amd64

amano@amano-desktop:~$ apt list --installed *grub* *shim*
Auflistung... Fertig
grub-common/now 2.04-1ubuntu24 amd64  [Installiert,lokal]
grub-efi-amd64-bin/now 2.04-1ubuntu24 amd64  [Installiert,lokal]
grub-efi-amd64-signed/now 1.139+2.04-1ubuntu24 amd64  [Installiert,lokal]
grub-efi-amd64/now 2.04-1ubuntu24 amd64  [Installiert,lokal]
grub2-common/now 2.04-1ubuntu24 amd64  [Installiert,lokal]
shim-signed/now 1.41+15+1552672080.a4a1fbe-0ubuntu1 amd64  [Installiert,lokal]
shim/now 15+1552672080.a4a1fbe-0ubuntu1 amd64  [Installiert,lokal]

I guess that the offending package was already deleted from the archive because I cannot trigger a reinstall:

amano@amano-desktop:~$ sudo apt reinstall shim
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.       
Statusinformationen werden eingelesen.... Fertig
Erneute Installation von shim ist nicht möglich,
es kann nicht heruntergeladen werden.
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.

In the Ubuntu forums Brett Bogert suggested it was due to a syntax error in a postinst script: https://ubuntuforums.org/showthread.php?t=2440393

An issue that was quickly fixed:


although as I type this the fixed package is still in -proposed. The bad package has been removed from the repositories.

Edit: fixed package now released.

1 Like

Thanks! Everything is fine now. Rebooting worked :wink:

For me gnome-weather is still very reluctant to give me the weather infos. A version 3.36.1 is now out: https://gitlab.gnome.org/GNOME/gnome-weather/-/commit/dd03f9bf309a05d92a225d7491c73d48294dd936

Is there any chance to have that updated for Focal, @jbicha, @seb128?

Or shall I file a bug?

amano@amano-desktop:~$ apt list gnome-weather
Auflistung... Fertig
gnome-weather/focal,focal,now 3.34.0-1 all  [installiert]

Sorry but I’m not working on that component and busy enough at the moment with what install in the default desktop, maybe Jeremy can help you there or you can always work on the update and add your work to launchpad and request for sponsoring

1 Like

I did a quick-and-dirty upload of 3.36.1 in Ubuntu only (currently in the focal upload queue). It appears to me to work more reliably.

1 Like

I am not able to get a X11 session with the latest Linux 5.4.0-21 kernel.
When I type my password on the login screen and press Enter, the screen goes black in an attempt to load GNOME Shell, but returns immediately back to the login screen.

I could not find something relevant in syslog or X.Org.0.log.

Bug report at https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1872123

I notice that in Ubuntu 20.04, the default input method has switched to ibus (it has always been none for most Latin, Greek, Cyrillic scripts).
I have tested this with Spanish and Greek.

This is in Settings→Region & Language→Manage installed languages, or run gnome-language-selector.

The usability change is that when you type using dead keys, you get the ibus visual hint as you type.
Previously, with none, the dead keys did not give any visual hint that you press them, and instantaneously you get the output character. It will take some time for someone typing fast to get used to this.

Is there a thread that discusses the background of this change?

That’s not true. The default input method has been IBus in Ubuntu for many cycles. For some flavors, OTOH, it has been - and still is - “none”. The latter is the case either due to an applicable im-config patch, or simply because no input method framework is installed by default.

Since there is no change, there is no recent discussion. :wink:

are you sure it isnt just a different default keyboard variant pre-selected in the installer (i remember such a switch happened for german a long time ago (“German” vs “German (nodeadkeys)” and i found it similarly irritating)

I installed an Ubuntu 20.04 daily (about 10 days before the release of the beta), and followed all the default installation steps to install using the Greek locale. This helped me with translating any remaining very-visible messages and fixing where a message could be phrased better.

My non-standard steps include installing with the ZFS experimental option, and switching system locale between Spanish/Greek as a way to figure out where a particular message comes from (from which package on Launchpad). I also switched between X11 and Wayland a few times. Perhaps one of these triggered IBus.

I am not against IBus, and if there was a switch to using it over XKB, I would be happy with it. But I would have liked to know some background in order to disseminate the new information to our users.

I’ll install the freshest daily ISO to test again, and also test whether the earlier issue with NVidia + 5.0.4-21 can be replicated.

So, I just installed Ubuntu 20.04 daily 20200412 AMD64 again, using the Greek locale (and still trying out the ZFS experimental feature).

  1. I was not able to replicate the issue not being able to login with Linux 5.4.0-21, X11 session and NVidia closed-source driver. Will likely close this bug report.

  2. IBus was enabled by default, when installing with the Greek locale. In 18.04 it was not enabled, and possibly the change was in a post-18.04 release. I’ll learn more about IBus and inform the users of the change. It is fine to have IBus enabled by default.

  3. While installing, I noticed that ubuquity-slideshow-ubuntu/-oem was now recommending the Shotcut video editor. The translation though still mentions the Pitivi Video editor. The source code does indeed mention Shotcut. Can the translation source messages get updated?

  4. The snap-store snap does not pull in the translations from Launchpad. I am filing a report on that on Launchpad.

Just a reminder:
Everyone please take care to not discuss bugs on this site. Instead please discuss them on Launchpad. You can create a bug there by running:

ubuntu-bug PACKAGENAME

or by clicking this link as a last resort.

1 Like

I can’t use ubuntu-bug for that crap snap-store https://bugs.launchpad.net/snap-store/+bug/1870184?_ga=2.11116596.128358601.1585980016-147966048.1585745330

To report bugs against snap-store you can use this link.

I reported the problem https://forum.snapcraft.io/t/snap-store-offers-only-snap-appl/16286
and got no answer

Please keep that discussion in the bug.