[Stable Update] 2018-09-18 - Kernels, Pamac, LibInput



Hi community,

Welcome to another stable update. So what do we have with this one?

  • latest updates to some of our kernels
  • Pamac got updated to v7.1.0-rc3
  • We added a fix for some touchpads in libinput

We hope with all these changes Manjaro to be more efficient for you all.

The Iconic Spitfire: Now Quad-Core!


Visit StationX now!

#beta-release - 18.0 will be available in late October!

If you are curious about the latest state of development for the upcoming Manjaro-Illyria 18.0 release, you now have the opportunity to download a beta-build of Manjaro-Xfce 18.0 including the latest xfce-gtk3 packages aswell as our most recent styling efforts. Our KDE fans may try our beta-build with the latest KDE v5.13 instead. And our GNOME fans may try our beta-build with the latest GNOME v3.28.

Current supported Kernels

  • linux316 3.16.57
  • linux318 3.18.122 [EOL]
  • linux44 4.4.156
  • linux49 4.9.127
  • linux414 4.14.70
  • linux417 4.17.19 [EOL]
  • linux418 4.18.8
  • linux419 4.19-rc4
  • linux414-rt 4.14.63_rt40
  • linux416-rt 4.16.18_rt11

Package Updates (Mon Sep 10 20:46:48 CEST 2018)

  • stable core x86_64: 10 new and 10 removed package(s)
  • stable extra x86_64: 35 new and 34 removed package(s)
:: Different overlay package(s) in repository core x86_64

                             PACKAGE           2018-09-13           2018-09-18
                            linux414            4.14.69-1            4.14.70-1
                    linux414-headers            4.14.69-1            4.14.70-1
                            linux418             4.18.7-1             4.18.8-2
                    linux418-headers             4.18.7-1             4.18.8-2
                      linux419 4.19rc3.0912.g5e33554-1 4.19rc4.0916.g7876320-1
              linux419-headers 4.19rc3.0912.g5e33554-1 4.19rc4.0916.g7876320-1
                             linux44            4.4.155-1            4.4.156-1
                     linux44-headers            4.4.155-1            4.4.156-1
                             linux49            4.9.126-1            4.9.127-1
                     linux49-headers            4.9.126-1            4.9.127-1

:: Different overlay package(s) in repository extra x86_64

                             PACKAGE           2018-09-13           2018-09-18
                  linux418-acpi_call              1.1.0-3              1.1.0-4
                   linux418-bbswitch                0.8-3                0.8-4
                   linux418-catalyst      1:15.201.1151-3      1:15.201.1151-4
                linux418-ndiswrapper               1.61-3               1.61-4
                     linux418-nvidia           1:396.54-3           1:396.54-4
               linux418-nvidia-340xx            340.107-3            340.107-4
               linux418-nvidia-390xx             390.87-3             390.87-4
                   linux418-nvidiabl               0.88-3               0.88-4
                      linux418-r8168           8.045.08-3           8.045.08-4
                        linux418-spl             0.7.10-1             0.7.10-2
                   linux418-tp_smapi               0.41-3               0.41-4
                linux418-vhba-module           20161009-3           20161009-4
   linux418-virtualbox-guest-modules             5.2.18-3             5.2.18-4
    linux418-virtualbox-host-modules             5.2.18-3             5.2.18-4
                        linux418-zfs             0.7.10-1             0.7.10-2
                  linux419-acpi_call           1.1.0-0.16           1.1.0-0.17
                   linux419-bbswitch             0.8-0.16             0.8-0.17
                   linux419-catalyst   1:15.201.1151-0.16   1:15.201.1151-0.17
                linux419-ndiswrapper            1.61-0.16            1.61-0.17
                     linux419-nvidia        1:396.54-0.16        1:396.54-0.17
               linux419-nvidia-340xx         340.107-0.16         340.107-0.17
               linux419-nvidia-390xx          390.87-0.16          390.87-0.17
                   linux419-nvidiabl            0.88-0.16            0.88-0.17
                      linux419-r8168        8.045.08-0.16        8.045.08-0.17
                        linux419-spl          0.7.10-0.16          0.7.10-0.17
                   linux419-tp_smapi            0.41-0.16            0.41-0.17
                linux419-vhba-module        20161009-0.16        20161009-0.17
   linux419-virtualbox-guest-modules          5.2.18-0.16          5.2.18-0.17
    linux419-virtualbox-host-modules          5.2.18-0.16          5.2.18-0.17
                        linux419-zfs          0.7.10-0.16          0.7.10-0.17
                               pamac              7.0.1-5           7.1.0rc3-1
             pamac-tray-appindicator              7.0.1-5           7.1.0rc3-1
                            libinput                    -           1.12.0-1.1
  • No issue, everything went smoothly
  • Yes there was an issue. I was able to resolve it myself.(Please post your solution)
  • Yes i am currently experiencing an issue due to the update. (Please post about it)

0 voters

Check if your mirror has already synced:


Known issues and solutions

This is a wiki post; please edit as necessary.
Please, consider subscribing to the Stable Updates Announcements RSS feed

AMD-Ucode introduction

Unless you’ve already done this previously, All users of AMD-APUs/CPUs should install this update like this:

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

Step 3 is optional.

Rebuilding fontconfig cache: failed to write cache

Please ignore this message. Upstream already works on a solution. More about the issue here.

LibreOffice has no window decoration in KDE

New line export SAL_USE_VCLPLUGIN=gtk3_kde5, once merged into existing /etc/profile.d/libreoffice-fresh.sh , fixes a moderately longterm issue. If it doesn’t work for you, you may use gtk instead of gtk3_kde5 as UI framework.

Items from previous update sets

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

Install the update either:

  • from terminal: sudo pacman -Syu or;
  • with Octopi instead of Pamac.

Something using Perl/Python/glibc broke

Rebuilds needed!

  • If it’s an AUR package, try to reinstall it from AUR. It most likely needs to be rebuilt.
  • If it’s a repo package, please report and check back regularly for updates.

I’ve lost a Thunderbird addon/feature

Thunderbird 60 disables incompatible addons by default. There’s an about:config switch should you want to force-enable the addon, but many addons simply will not work with the newer Quantum-based Thunderbird.

Read more about Thunderbird 60 here: Thunderbird 60

Firefox - WebGL not working anymore

You may try the following solution:

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

libutf8proc>=2.1.1-3 update may require manual intervention

This should normally be automatically fixed via manjaro-system update.

The libutf8proc package prior to version 2.1.1-3 had an incorrect soname link. This has been fixed in 2.1.1-3, so the upgrade will need to overwrite the untracked soname link created by ldconfig. If you get an error

libutf8proc: /usr/lib/libutf8proc.so.2 exists in filesystem

when updating, use

pacman -Suy --overwrite usr/lib/libutf8proc.so.2

to perform the upgrade.

Pamac: “Invalid or corrupted package.”

If you receive an “Invalid or corrupted package.” error message with Pamac and if the details contains an output similar to the following:

Synchronizing package databases...
Starting full system upgrade...

Resolving dependencies...
Checking inter-conflicts...
Downloading manjaro-system-20180716-1-any.pkg.tar.xz...
Checking keyring...
Checking integrity...
Loading packages files...
Checking file conflicts...
Checking available disk space...
Upgrading manjaro-system (20180702-1 -> 20180716-1)...
==> Fix libutf8proc upgrade ...
resolving dependencies...
looking for conflicting packages...

Packages (1) libutf8proc-2.1.1-4

Total Download Size:   0.05 MiB
Total Installed Size:  0.32 MiB
Net Upgrade Size:      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 integrity...
loading package files...
checking for file conflicts...
checking available disk space...
:: Processing package changes...
upgrading libutf8proc...
:: Running post-transaction hooks...
(1/1) Arming ConditionNeedsUpdate...
Running 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/files: No such file or directory
Warning: could not fully load metadata for package libutf8proc-2.1.1-2

Failed to prepare transaction:
invalid or corrupted package

Try the following steps: close Pamac window first, then launch it again and start the update procedure again. It should continue from where it left off.

Issues with folder view widget in KDE v5.13

KDE introduced a new setting for icon sizes. Now you’re able to define also the size for your panel. If you have a high-DPI display, you may want to increase the value. This will fix the display issue with given widget.


Pulseaudio changes

With this update we have a /etc/pulse/default.pa.pacnew. It may be necessary to merge (some lines related to “GSettings” in /etc/pulse/default.pa ) if ‘default.pa’ 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 support for the Engrampa archive manager. engrampa-thunar-plugin is no longer needed. Remove engrampa-thunar-plugin to continue with the update.

Make ucode installation automatic with MHWD

Serious pamac fakeroot bug, please consider this: Strange fakeroot problem with all AUR


I never really paid attention to pamac since I only use it to look up package descriptions. But why are pamac updates fast tracked into stable? There doesn’t seem to be a very long window for testing new versions, if any. Shouldn’t there be more stringent checks on Manjaro’s package manager?

Or maybe the problem is very few people in unstable and testing actually use pamac as their package updater/installer. :thinking:


No I think just people thinks in testing that’s just errors due to a bad package. And not testing compiling by gui and by cli.


Currently we have updated the engine of pamac a lot. For distros other than Manjaro, we currently recommend v7.0.1 release. Beginning with commit 6dd2f8c, we started to do a rework of our pamac-lib. Based on our changelog this took a while to stabilize again. Currently we have pamac v7.1.0-rc3 released to all our branches.

I was able to update my system in mixed settings via pamac-cli and pamac-updater just fine. I might do another test via pamac-manager. However, so far I can’t reproduce the issue with fakeroot.

Here my current last update log.


Thanks, all fine with Manjaro Xfce and Kernel 4.18.8-2.

Nice: My Problem with systemd and /oldroot is gone, hurray! Cf. previous Stable Update Threads since a month or more. Side remark: You removed bpfilter from the Kernel, didn‘t you? That indeed was the problem, wasn‘t it?


After this update pamac no longer freezes.
The icon remains green though as if there would be another update, but there is not.

Hoovering over the icon also tells me that there are 6 updates.


Periodic system crashes when using VirtualBox and parallel compiling in Qt Creator. Before this update, everything was OK. XFCE.

  1. Try refreshing your mirrors. Your mirror may be partially synced.

  2. Then force refresh your database cache
    sudo pamac update --force-refresh
    sudo pacman -Suyy


KDE running perfectly on my I7 , w/Nvidia 1060 on kernel 4.19 .


Unfortunately, refreshing the d.dase didn’t change anything.


Maybe OT :wink:

Not bad the bladebook, but there is just one thing, who is this girl? :wink:
Tell me :smiley:


Did you refresh mirrors?

Refresh mirrors. Refresh databases. Reboot also maybe.

Also you did not even bother to read the link about partially synced mirrors before replying. It leads to an entire thread about this issue. You can follow more links and read more about this issue yourself and understand it better. But you did not. You just write “it not work.” I am sad. :crying_cat_face:


Where did I write that?
I know of syncing mirrors, refreshing databases etc.

And it is not about fakeroot, just a remaining green icon, which seems to turn white after reboot.

And don’t cry…


I used to have 4.18 and 4.14 LTS installed. But upgrading didn’t work with kernel 4.14.
I always $ sudo pacman-mirrors -f 0 && sudo pacman -Syyu, this time I got the output

error: failed to commit transaction (conflicting files)
linux414: /boot/linux414-x86_64.kver exists in filesystem
linux414: /boot/vmlinuz-4.14-x86_64 exists in filesystem
linux414: /usr/lib/modules/extramodules-4.14-MANJARO/version exists in filesystem
linux414: /usr/share/libalpm/hooks/60-linux414.hook exists in filesystem
linux414: /usr/share/libalpm/hooks/90-linux414.hook exists in filesystem
Errors occurred, no packages were upgraded.

I uninstalled 4.14 and then upgraded 4.18 successfully. However, I can’t reinstall 4.14, trying so I get just exactly the same output. Why do I still have this existing 4.14 parts?
For safety reasons I installed 4.9 LTE which was successful.


How did you uninstall?
Output from

ls /boot
ls /usr/lib/modules/
ls /usr/share/libalpm/hooks/


Fakeroot? There is nothing about fakeroot in the thread I linked. Also I do not have a green icon related to pamac and I use Xfce also.

We must me talking about different things…

I will stop crying now. :smiley_cat:


Thank you for your questions, @SGS .
I get this:

ls /boot


ls /usr/lib/modules


ls /usr/share/libalpm/hooks/


There is quite a lot with “4.14” left, even if the kernel and everything else related is uninstalled, as far as I understand it. I used the Manjaro settings manager to uninstall the 4.14 kernel. Upgrades I do always like mentioned in my posting with pacman-mirrors && pacman.
I will not be at my computer until tomorrow.
Maybe this has nothing to do with the update?
Thanks again!


It does not work with the reinstall because these files are still in the appropriate folders. If you don’t know your way around as well as I do :wink: then wait for competent feedback from specialists here.

Before you delete something wrong.