[Stable Update] 2018-11-07 - Kernels, Calamares, LibreOffice, Cinnamon, Deepin, Pamac

Hi community,

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

  • We updated most of our kernels
  • Updated curl
  • Pamac-Dev introduces following features:
    • introduce parallel downloads with an option to set max parallel downloads
    • dialog to choose opt deps
    • dialog to import the required PGP keys when building a package from AUR
    • option to check updates of AUR VCS packages (-git, -svn,…)
    • cli now follows /etc/pamac.conf (no need to use --aur option if AUR support is enabled in pamac.conf)
    • “checkupdates” action in cli now reports AUR outofdate packages (if check AUR updates is enabled)
    • “search” action in cli now search in dbs and in AUR at the same time (if AUR support is enabled)
    • allow PKGBUILDs to launch subprocesses
  • Cinnamon get prepared for v4.0 release
  • Deepin got serveral package updates
  • Firefox-Dev is now on its sixth beta release
  • Fixes to firefox-kde
  • small fixes to our Manjaro-Tools in ISO generation
  • We updated LibreOffice
  • The usual upstream haskell, and python rebuilds/updates

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

The Iconic Spitfire: Now Quad-Core!


Visit StationX now!

Manjaro v18.0 released!

If you are curious about the latest Manjaro-Illyria 18.0 release, you now have the opportunity to download XFCE Edition with the latest 4.13 packages, aswell as our most recent styling efforts. Our KDE fans may try our KDE Edition with the latest KDE v5.14 instead. And our GNOME fans may try our Gnome Edition with the latest GNOME v3.30.

Current supported Kernels

  • linux316 3.16.59
  • linux318 3.18.124 [EOL]
  • linux44 4.4.162
  • linux49 4.9.135
  • linux414 4.14.79
  • linux417 4.17.19 [EOL]
  • linux418 4.18.17
  • linux419 4.19.1
  • linux414-rt 4.14.71_rt44
  • linux416-rt 4.16.18_rt11
  • linux418-rt 4.18.16_rt9

Package Updates (Tue Nov 6 18:02:34 CET 2018)

  • stable community x86_64: 823 new and 814 removed package(s)
  • stable core x86_64: 16 new and 16 removed package(s)
  • stable extra x86_64: 540 new and 698 removed package(s)
  • stable multilib x86_64: 14 new and 19 removed package(s)

A detailed list of all package changes may be found here.

  • 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:

Changes made to grub package

1. What is the GRUB hidden menu change?

The main motivation for adding this is, to get to a fully flickerfree boot.

2. How to enable hidden GRUB menu?

On new Manjaro v18.0 installs this will be enabled by default. If your system has been upgraded to v18.0 from an older release, you can enable it by running these commands:

  • update your system to get latest systemd
  • install linux418 or linux419: sudo pacman -S linux41[x]
  • check that you have quiet in /etc/default/grub under GRUB_CMDLINE_LINUX_DEFAULT or GRUB_CMDLINE_LINUX and comment out any GRUB_BACKGROUND settings.
  • sed -i -e 's|fsck||g' /etc/mkinitcpio.conf && sudo pacman -S systemd-fsck-silent
  • You may want to consider early kms and fastboot for intel hardware
  • sudo mkinitcpio -P
  • sudo grub-editenv - set menu_auto_hide=1
  • sudo update-grub
  • reboot your system

Note the grub-update will overwrite any manual changes you’ve made to your grub.cfg (normally no manually changes are done to this file).

If your system has Windows on it, but you boot it only once a year so you would still like to hide the GRUB menu, you can tell GRUB to ignore the presence of Windows by running:

sudo grub-editenv - set menu_auto_hide=2

3. How to disable hidden GRUB menu

To permanently disable the auto-hide feature run:

sudo grub-editenv - unset menu_auto_hide

That is it.

4.How to access the GRUB menu when hidden

If for some reason you need to access the GRUB menu while it is hidden there are multiple ways to get to it:

  1. While booting keep SHIFT pressed, usually you need to first press SHIFT when the vendor logo is shown by the firmware / when the firmware says e.g. “Press F2 to enter setup” if you press it earlier it may not be seen. Note this may not work on some machines.

  2. During boot press ESC or F8 while GRUB loads (simply press the key repeatedly directly after power on until you are in the menu).

  3. Force the previous boot to be considered failed:

    1. Press CTRL + ALT + DEL while booting so that the system reboots before hitting the display manager (lightdm, gdm, sddm)

    2. Press CTRL + ALT + F6 to switch away from your display manager, followed by CTRL + ALT + DEL.

    3. Press the power-button for 4 seconds to force the machine off. Either of these will cause the boot_success grub_env flag to not get set and the menu will show the next boot.

    4. Manually set the menu show once flag by running: "grub-set-bootflag menu_show_once" This will cause the menu to show for 60 seconds before continuing with the default boot-option.

4. When is a boot considered successful ?

The boot_success grub_env flag gets set when you login as a normal user and your session lasts at least 2 minutes.

So if you e.g. login, do something and then within 30 seconds type reboot in a terminal (instead of doing the reboot from the menu) then this will not count as a successful boot and the menu will show the next boot.


Known issues and solutions

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

i3 changed its default config path

It seems that (from version >= 4.16) i3 is looking for its configuration in ~/.config/i3/config instead of ~/.i3/config.
Copy your config to the new path and all should work as before. (reported from an i3-gaps user).

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

Workaround found: Use the dbus-x11 package instead of the regular dbus package. This package is available in the official repositories and provides dbus compiled without the --without-x option.

To replace dbus with dbus-x11 package, simply install dbus-x11 with your favorite package manager: dbus will be replaced by dbus-x11.

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

So far, it has only been a false alarm: updates are applied successfully.

Items from previous update sets

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.

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.

1 Like

Did bfq-mq get taken out of 4.19.1-1? Because it no longer loads. This message may be related.

kernel: blkcg_policy_register: BLKCG_MAX_POLS too small

(On 4.14.79-1, there is no such message.)

Also, what is (or was) the difference between bfq and bfq-mq on multi-queue frameworks?

In case you missed it.

Cinnamon 4.0 is obviously very new and a couple of applets/extensions have stopped working. In my case I’m having trouble with the Nemo extension for Insync, the CPU temp panel applet and the Stark start menu. Cinnamon users be cautious for now!

Cinnamon 4.19, all went OK, as mentioned, some applets (like Volume 150%) stopped working, menu has changed, but those are specifically Cinnamon related issues. Thanx for another great stable update!

The all new Grouped window list in cinnamon 4.0 looks nice but is buggy. App button dragging doesn’t work (even though I have enabled this option and removed and re-added the applet many times) and there isn’t an option to pin some apps (but there is an option to create shortcut instead, which, off course, does nothing).

Everything smooth as usual (XFCE & 4.18), thanks a lot!

The only thing that puzzles me: my XFCE is still all 4.12
Sole exception is libxfce4util 4.13.2-1
Anything I missed to do?

Xfce + 4.19, no issues to report


1 Like

Obviously this is what I missed, cheers.

i3 & 4.14 - ended up with default i3 look this morning.
Moving config file from .i3/ to .config/i3/ solved issue, up and running now.

No problems on KDE. Thanks to everyone involved!

Added the info in the Known issues and solutions, as it was also reported in Testing a while ago.

1 Like

Everything OK :muscle:

No problem whatsoever on xfce with kernel 4.19

XFCE, 4.19.1-1

Everything went smoothly! Thanks for all the hard work.

Qtile - Kernel 419
No problems here, only some logs reported since another update.
No issues.

A post was split to a new topic: Possible incompatible libdevmapper

Update, reboot, everything is running. :+1:
LXQT and XFCE with Kernel 4.19.

Update done, for now i haven’t encountered any issue😍. I’m using Manjaro KDE with kernel 4.19.

Yep, Cinnamon 4 is buggy on all sides. Ahem, there are some visual differences due to new functionality and defaults being set.

My biggest problem is that the lock screen does not show the password prompt anymore. Once you lock your screen, either manually or through the screensaver, you cannot log back in to your session.

Otherwise the lockscreen is fully active, I can drop down to tty, log in, etc. But not from the lock screen. This is a major GDPR compliance issue, since we are required to lock screen when leaving the keyboard.

1 Like

Forum kindly sponsored by