[Testing Update] 2019-06-10 – Kernels, KDE Frameworks, KDE-Git – Testing Updates

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

In case you are using the Matcha theme in kvantum chances are you’ll expertise 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 a number of customers report totally different issues for Octopi. So should you encounter a few of them, you might change to pamac for now: sudo pacman -Sy pamac

Gadgets from earlier replace units

Small cleanup of Manjaro official repositories

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

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

ZFS zero.eight fails to import ZFS pool throughout boot

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

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

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

Gnome 3.32: Two extensions faraway from our repos.

We have now 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.

These extensions aren’t in lively improvement anymore and should not work correctly (or not work in any respect) on Gnome Three.32. Notably, it has been reported that using Topicons Plus on Gnome 3.32 might leads to very high CPU usage.

We strongly advocate you to disable those extensions if they’re enabled (Tweaks > Extensions) and remove those packages together with your favourite package deal manager. To stop potential issues with the subsequent model of Gnome, you could do these steps (or a minimum of the primary one) earlier than upgrading your system.

Gnome Three.32: Numerous problems

There’s at present a number of problems with Gnome Three.32. Here’s what we all know to date.

1. Risk of damaged extensions
Broken 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 damaged extension taken from elsewhere than Manjaro official repositories, you will have to contact the maintainer on the supply you will have taken the extension from to get more help. You might also need to report the problem to the developer(s) of the extension (if not the same individual/group).

It’s attainable that extensions turn into so damaged on Gnome 3.32 that it makes Gnome Shell crash utterly when making an attempt to log in, thus making Gnome utterly unusable. For instance, we’ve got 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 (especially if operating Gnome extensions that doesn’t come from Manjaro official repositories) and make the improve smoother, you possibly can disable all Gnome extensions (Tweaks > Extensions) earlier than upgrading your system, then allow them one by one solely after being logged in a totally new session on Gnome 3.32.

2. Using world clocks can break Gnome Shell utterly
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 will want 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 for those who 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, chances are you’ll 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 faraway 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 eliminated at the similar time too.

In case you are nonetheless 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 from your system.

Along with that, we’ve got dropped help for a number of packages that trusted yaourt: allservers, pacli and pacli-jwm. These packages has been removed from the official repositories utterly.

vlc-nightly has been dropped

The vlc-nightly package deal, which was actually useful in a time when VLC Three was not officially out but, has been dropped on our aspect and isn’t in the official repositories anymore. When you nonetheless have this package deal and also you want the newest secure version of VLC media player, take away vlc-nightly, then install the vlc package deal.

In any other case, you’ll be able to proceed to use vlc-nightly from the AUR (however you’ll should compile it yourself).

Kodi 18.1: extensions might not work correctly.

Kodi 18.1 is now out there in our repositories. Since this can be a major version change, extensions for Kodi (in case you use some) might cease working correctly. Builders of those extensions will need to make them suitable with Kodi 18.

If Kodi 18.1 doesn’t work correctly for you and you absolutely want to make use of your extensions, chances are you’ll use the previous kodi package deal in /var/cache/pacman/pkg in an effort to downgrade Kodi to model 17.6. Please notice that it’s a momentary workaround and that the software offered in the previous kodi package deal might cease working properly sooner or later too. You shouldn’t maintain the downgrade ceaselessly.

Notifications wanting weird in XFCE

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

Plasma won’t reboot from the Software Launcher

Should you replace from within Plasma (e.g. from the konsole), you might have to problem 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 out there in the official repositories and offers dbus compiled without the –without-x choice.

To exchange dbus with dbus-x11 package deal, merely install dbus-x11 together with your favourite package deal manager: dbus will probably be replaced by dbus-x11.

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

To date, it has solely been a false alarm: updates are utilized successfully.

AMD-Ucode introduction

Until you’ve already achieved this beforehand, 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 Three is elective.

Rebuilding fontconfig cache: failed to write down cache

Please ignore this message. Upstream already works on a solution. More concerning the challenge here.

LibreOffice has no window ornament in KDE

New line export SAL_USE_VCLPLUGIN=gtk3_kde5, once merged into present /and so forth/profile.d/ , fixes a moderately longterm problem. If it doesn’t be just right for you, chances are you’ll 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

Install the replace both:

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

Something using Perl/Python/glibc broke

Rebuilds wanted!

  • If it’s an AUR package deal, try to reinstall it from AUR. It probably needs to be rebuilt.
  • If it’s a repo package deal, please report and verify back often for updates.

I’ve lost 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 extra about Thunderbird 60 here: Thunderbird 60

Firefox – WebGL not working anymore

Chances are you’ll attempt the next answer:

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

libutf8proc>=2.1.1-Three update might require guide intervention

This should normally be routinely fastened by way of manjaro-system replace.

The libutf8proc package deal prior to version 2.1.1-Three had an incorrect soname hyperlink. This has been fastened in 2.1.1-Three, so the upgrade will need to overwrite the untracked soname hyperlink 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 carry out 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…
Beginning full system upgrade…

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 out there disk area…
Upgrading manjaro-system (20180702-1 -> 20180716-1)…
==> Fix libutf8proc improve …
resolving dependencies…
on the lookout for conflicting packages…

Packages (1) libutf8proc-2.1.1-Four

Complete Obtain Measurement: zero.05 MiB
Complete Put in Measurement: 0.32 MiB
Internet Upgrade Measurement: 0.00 MiB

:: Proceed with installation? [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 obtainable 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 missing /var/lib/pacman/db.lck
Starting full system upgrade…
Resolving dependencies…
Checking inter-conflicts…
Error: could not open file /var/lib/pacman/local/libutf8proc-2.1.1-2/information: No such file or directory
Warning: could not absolutely load metadata for package deal libutf8proc-2.1.1-2

Failed to organize transaction:
invalid or corrupted package deal

Attempt the following steps: shut Pamac window first, then launch it again and start the update process once more. It ought to continue from where it left off.

Points with folder view widget in KDE v5.13

KDE launched a new setting for icon sizes. Now you’re capable of define additionally the dimensions on your panel. When you have a high-DPI show, you could need to improve the worth. It will repair the show concern with given widget.


Pulseaudio modifications

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

File battle engrampa.tap

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

thunar-archive-plugin has added native help for the Engrampa archive manager. engrampa-thunar-plugin is not wanted. Take away engrampa-thunar-plugin to proceed with the update.