[Testing Update] 2019-06-24 – Kernels, KDE Plasma, Texlive, Haskell, Python – Testing Updates

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

In case you are using the Matcha theme in kvantum you might expertise a theme reset. Simply set up kvantum-theme-matcha if not happend yet and select the brand new offered variants. Manjaro 18.1 releases will ship with the new themes by default.

Presently a number of customers report totally different points for Octopi. So in the event you encounter a few of them, you might change to pamac for now: sudo pacman -Sy pamac

Gadgets from earlier replace sets

Small cleanup of Manjaro official repositories

Please word 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 replace 2019-05-29, it may be permanently fastened
by eradicating and re-adding the pool’s cachefile :

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

Extra particulars 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’ve got 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 correctly (or not work at all) on Gnome 3.32. Notably, it has been reported that utilizing Topicons Plus on Gnome 3.32 might results in very high CPU utilization.

We strongly advocate you to disable those extensions if they’re enabled (Tweaks > Extensions) and remove those packages together with your favourite package deal supervisor. To stop potential problems with the subsequent version of Gnome, you might do these steps (or at the very least the primary one) before upgrading your system.

Gnome Three.32: Numerous issues

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

1. Risk of broken extensions
Damaged extensions is one thing to anticipate when transitioning between main versions of Gnome, especially in case you are using extensions that are not shipped by default on Manjaro Gnome. In case you have a broken extension taken from some other place than Manjaro official repositories, you’ll have to contact the maintainer on the source you might have taken the extension from to get more 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 grow to be 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 challenge 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 upgrade smoother, you possibly can disable all Gnome extensions (Tweaks > Extensions) before upgrading your system, then allow them one by one only after being logged in a totally new session on Gnome Three.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 happens, you will have 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 in the event you use Wayland
In case you are using Wayland (as an alternative of, Gnome Shell might crash when resuming from sleep. Upstream is conscious of this challenge. As a workaround, you might use as an alternative of Wayland for now.

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

Yaourt: Relaxation in peace

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

In case you are still utilizing 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 a number of packages that trusted yaourt: allservers, pacli and pacli-jwm. Those 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 yet, has been dropped on our aspect and isn’t in the official repositories anymore. In the event you still have this package deal and also you want the newest secure version of VLC media player, remove vlc-nightly, then set up the vlc package deal.

Otherwise, you’ll be able to 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 correctly.

Kodi 18.1 is now obtainable in our repositories. Since this can be a major model change, extensions for Kodi (in the event you use some) might stop 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 also you completely want to make use of your extensions, you might use the previous kodi package deal in /var/cache/pacman/pkg with a view to downgrade Kodi to model 17.6. Please observe that it is a short-term workaround and that the software offered in the previous kodi package deal might stop working correctly in the future too. You shouldn’t hold the downgrade eternally.

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 concern. Usually not wanted in that edition.

Plasma won’t reboot from the Software Launcher

For those who replace from within Plasma (e.g. from the konsole), chances are you’ll have to concern 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 accessible in the official repositories and supplies dbus compiled with out the –without-x choice.

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

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

Thus far, it has only been a false alarm: updates are utilized successfully.

AMD-Ucode introduction

Until you’ve already carried out this previously, All customers of AMD-APUs/CPUs should set up 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. More concerning the difficulty here.

LibreOffice has no window decoration in KDE

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

Putting in 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 needed!

  • If it’s an AUR package deal, attempt to reinstall it from AUR. It most probably must be rebuilt.
  • If it’s a repo package deal, please report and examine 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, however many addons simply won’t work with the newer Quantum-based Thunderbird.

Read more about Thunderbird 60 right here: Thunderbird 60

Firefox – WebGL not working anymore

Chances are you’ll 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 routinely fastened by way of manjaro-system replace.

The libutf8proc package deal previous to model 2.1.1-3 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 case 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.”

When 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 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 out there 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-4

Complete Download Measurement: 0.05 MiB
Complete Installed Measurement: 0.32 MiB
Internet Improve Measurement: zero.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 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
Starting full system improve…
Resolving dependencies…
Checking inter-conflicts…
Error: couldn’t open file /var/lib/pacman/native/libutf8proc-2.1.1-2/information: No such file or listing
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 replace procedure once more. It should continue from the place 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 define also the dimensions in your panel. If in case you have a high-DPI display, you could need to improve the value. This can fix the display concern with given widget.


Pulseaudio modifications

With this update we now have 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 conflict engrampa.faucet

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 manager. engrampa-thunar-plugin is not wanted. Take away engrampa-thunar-plugin to proceed with the replace.