[Testing Update] 2019-06-20 – Kernels, KDE Plasma, Browsers, Mesa, Qt5 – Testing Updates

This can be a wiki publish; please edit as crucial.
Please, think about subscribing to the Testing Updates Bulletins RSS feed

In case you are utilizing the Matcha theme in kvantum chances are you’ll experience a theme reset. Simply set up kvantum-theme-matcha if not happend but and select the new offered variants. Manjaro 18.1 releases will ship with the brand new themes by default.

Presently several users report totally different issues for Octopi. So in case you encounter some of them, you could change to pamac for now: sudo pacman -Sy pamac

Gadgets from previous update sets

Small cleanup of Manjaro official repositories

Please notice that the next packages obtained faraway from our repositories.

  • chromium-chromevox
  • gimp-gtk3
  • pamac-classic
  • pamac-dev
  • pamac-dev-tray-appindicator

ZFS zero.eight fails to import ZFS pool during boot

As noted for testing update 2019-05-29, it may be completely fastened
by removing and re-adding the pool’s cachefile :

zpool set cachefile=none
zpool set cachefile=/and so on/zfs/zpool.cache

Extra details in [Testing Update] 2019-05-29 – Kernels, XFCE, Deepin, Mesa, Nvidia, KDE-Dev (seek for ‘ZFS’ there)

Gnome Three.32: Two extensions faraway from our repos.

We now have dropped two packages that shipped further extensions for Gnome: gnome-shell-extensions-topicons-plus-huttli and gnome-shell-extensions-taskbar. We gained’t keep Topicons Plus and Taskbar anymore.

Those extensions aren’t in lively improvement anymore and should not work properly (or not work at all) on Gnome 3.32. Notably, it has been reported that utilizing Topicons Plus on Gnome 3.32 might leads to very high CPU utilization.

We strongly advocate you to disable these extensions if they are enabled (Tweaks > Extensions) and take away those packages together with your favourite package deal supervisor. To stop potential problems with the subsequent model of Gnome, you could do those steps (or a minimum of the first one) earlier than upgrading your system.

Gnome Three.32: Numerous issues

There’s at present a number of problems with Gnome 3.32. Here’s what we all know up to now.

1. Risk of damaged extensions
Damaged extensions is one thing to anticipate when transitioning between major variations of Gnome, particularly in case you are utilizing extensions that are not shipped by default on Manjaro Gnome. When you have a broken extension taken from elsewhere than Manjaro official repositories, you will have to contact the maintainer on the source you have got taken the extension from to get extra help. You might also need to report the issue to the developer(s) of the extension (if not the same individual/group).

It’s potential that extensions turn into so broken on Gnome Three.32 that it makes Gnome Shell crash utterly when making an attempt to log in, thus making Gnome utterly unusable. For example, we’ve a report of such difficulty with a third-party extension (that doesn’t come from Manjaro’s official repositories) referred to as Extensions.

To decrease the danger of breakage (particularly if operating Gnome extensions that doesn’t come from Manjaro official repositories) and make the upgrade smoother, you’ll be able to disable all Gnome extensions (Tweaks > Extensions) earlier than upgrading your system, then enable them one after the other only after being logged in a totally new session on Gnome 3.32.

2. Utilizing world clocks can break Gnome Shell utterly
If in case you have configured world clocks in Gnome, it might make Gnome Shell segfaults and crashes when making an attempt to log in for a graphical session, making Gnome unusable. If it occurs, you’ll need to reset your parameters for world clocks with the next command (do it in TTY): dbus-launch gsettings reset org.gnome.clocks world-clocks.
See this Arch Linux thread and this ticket from upstream.

3. Gnome Shell might crash utterly when resuming from sleep when you use Wayland
In case you are using Wayland (as an alternative of, Gnome Shell might crash when resuming from sleep. Upstream is aware of this concern. As a workaround, you might use as an alternative of Wayland for now.

Four. Miscellaneous
Some packages don’t get targeted after being launched. Reported to upstream and confirmed for distributions aside from Manjaro too.

Yaourt: Rest in peace

Yaourt has been removed from our repositories utterly. We gained’t keep the yaourt package deal anymore, which signifies that you will not obtain any updates from us for this package deal. A very previous package deal named yaourt-gui-manjaro has been removed on the similar time too.

In case you are still using Yaourt, we strongly encourage you to modify to an alternate like Pamac CLI (package deal: pamac-cli), Trizen (package deal: trizen), Yay (package deal: yay) or Pacaur (package deal: pacaur); and uninstall Yaourt out of your system.

Along with that, we now have dropped help for several packages that trusted yaourt: allservers, pacli and pacli-jwm. Those packages has been faraway from the official repositories utterly.

vlc-nightly has been dropped

The vlc-nightly package deal, which was actually helpful in a time when VLC Three was not formally out but, has been dropped on our aspect and is not within the official repositories anymore. Should you still have this package deal and you want the newest secure version of VLC media participant, remove vlc-nightly, then set up the vlc package deal.

In any other case, you possibly can proceed to make use of vlc-nightly from the AUR (however you’ll need to compile it yourself).

Kodi 18.1: extensions might not work properly.

Kodi 18.1 is now out there in our repositories. Since this can be a major model change, extensions for Kodi (when you use some) might cease working properly. Builders of these extensions might want to make them suitable with Kodi 18.

If Kodi 18.1 doesn’t work correctly for you and also you absolutely want to make use of your extensions, you might use the previous kodi package deal in /var/cache/pacman/pkg in an effort to downgrade Kodi to version 17.6. Please word that it’s a momentary workaround and that the software offered in the previous kodi package deal might cease working properly in the future too. You shouldn’t hold the downgrade ceaselessly.

Notifications wanting bizarre in XFCE

Because the package deal dunst consists of now dunstfy in the primary package deal notifications might not displayed correctly in XFCE. Please uninstall that package deal to unravel that challenge. Normally not wanted in that version.

Plasma won’t reboot from the Software Launcher

In the event you replace from within Plasma (e.g. from the konsole), you might have to situation a systemctl reboot to reboot.

I can’t open Nemo with elevated privileges (as root)

Workaround discovered: Use the dbus-x11 package deal as an alternative of the regular dbus package deal. This package deal is obtainable within the official repositories and supplies dbus compiled without the –without-x choice.

To exchange dbus with dbus-x11 package deal, merely set up dbus-x11 together with your favourite package deal supervisor: dbus can be replaced by dbus-x11.

Pamac: “Failed to commit transaction – Transaction not prepared” at the finish

Up to now, it has only been a false alarm: updates are applied successfully.

AMD-Ucode introduction

Until you’ve already achieved this previously, All users of AMD-APUs/CPUs should install this replace like this:

sudo pacman -Syyu
sudo pacman -S amd-ucode
sudo pacman -R intel-ucode
sudo update-grub

Step 3 is optionally available.

Rebuilding fontconfig cache: failed to put in writing cache

Please ignore this message. Upstream already works on an answer. Extra concerning the concern here.

LibreOffice has no window ornament in KDE

New line export SAL_USE_VCLPLUGIN=gtk3_kde5, once merged into present /and so on/profile.d/ , fixes a moderately longterm concern. If it doesn’t be just right for you, you could use gtk as an alternative of gtk3_kde5 as UI framework.

Installing glibc (2.28-4) breaks the dependency “glibc=2.27” required by lib32-glibc

Set up the replace both:

  • from terminal: sudo pacman -Syu or;
  • with Octopi as an alternative of Pamac.

Something utilizing Perl/Python/glibc broke

Rebuilds wanted!

  • If it’s an AUR package deal, try to reinstall it from AUR. It almost definitely must be rebuilt.
  • If it’s a repo package deal, please report and examine back repeatedly for updates.

I’ve misplaced a Thunderbird addon/function

Thunderbird 60 disables incompatible addons by default. There’s an about:config change do you have to need to force-enable the addon, but many addons merely won’t work with the newer Quantum-based Thunderbird.

Learn more about Thunderbird 60 here: Thunderbird 60

Firefox – WebGL not working anymore

You might attempt the next answer:

Open about:config and set safety.sandbox.content material.read_path_whitelist to /sys/.

libutf8proc>=2.1.1-Three update might require guide intervention

This could normally be mechanically fastened by way of manjaro-system replace.

The libutf8proc package deal previous to model 2.1.1-Three had an incorrect soname link. This has been fastened in 2.1.1-3, so the improve might want to overwrite the untracked soname link created by ldconfig. In the event you get an error

libutf8proc: /usr/lib/ exists in filesystem

when updating, use

pacman -Suy –overwrite usr/lib/

to perform the improve.

Pamac: “Invalid or corrupted package.”

Should you obtain an “Invalid or corrupted package.” error message with Pamac and if the small print accommodates an output just like the next:

DetailsSynchronizing package deal databases…
Starting full system improve…

Getting ready…
Resolving dependencies…
Checking inter-conflicts…
Downloading manjaro-system-20180716-1-any.pkg.tar.xz…
Checking keyring…
Checking integrity…
Loading packages information…
Checking file conflicts…
Checking obtainable disk area…
Upgrading manjaro-system (20180702-1 -> 20180716-1)…
==> Repair libutf8proc upgrade …
resolving dependencies…
in search of conflicting packages…

Packages (1) libutf8proc-2.1.1-Four

Complete Download Measurement: 0.05 MiB
Complete Installed Measurement: zero.32 MiB
Internet Upgrade Measurement: zero.00 MiB

:: Proceed with set up? [Y/n] :: Retrieving packages…
downloading libutf8proc-2.1.1-4-x86_64.pkg.tar.xz…
checking keyring…
checking package deal integrity…
loading package deal information…
checking for file conflicts…
checking out there disk area…
:: Processing package deal modifications…
upgrading libutf8proc…
:: Operating post-transaction hooks…
(1/1) Arming ConditionNeedsUpdate…
Operating post-transaction hooks…
Arming ConditionNeedsUpdate…
Warning: lock file lacking /var/lib/pacman/db.lck
Beginning full system improve…
Resolving dependencies…
Checking inter-conflicts…
Error: couldn’t open file /var/lib/pacman/local/libutf8proc-2.1.1-2/information: No such file or directory
Warning: couldn’t absolutely load metadata for package deal libutf8proc-2.1.1-2

Failed to organize transaction:
invalid or corrupted package deal

Attempt the following steps: close Pamac window first, then launch it once more and begin the replace procedure once more. It ought to proceed from where it left off.

Issues with folder view widget in KDE v5.13

KDE introduced a brand new setting for icon sizes. Now you’re capable of outline also the dimensions in your panel. When you have a high-DPI show, you could need to improve the worth. This can fix the display challenge with given widget.


Pulseaudio modifications

With this replace we have now a /and so forth/pulse/ It might be necessary to merge (some strains associated to “GSettings” in /and so on/pulse/ ) if ‘’ has been customised.

File conflict engrampa.tap

thunar-archive-plugin: /usr/lib/xfce4/thunar-archive-plugin/engrampa.tap exists in filesystem (owned by engrampa-thunar-plugin)

thunar-archive-plugin has added native help for the Engrampa archive supervisor. engrampa-thunar-plugin is not needed. Take away engrampa-thunar-plugin to continue with the update.