[Testing Update] 2019-02-14 - Kernels, Systemd, Browsers, Calamares, Firmware, Plasma5, KDE Framework

update
testing

#1

Hi community,

Welcome to our sixth testing update for 2019. These are additional package needed to our last update. So what do we have with this one?

  • we updated systemd to v241 - report any issues with it
  • lot of new features got into Calamares 3.2.4 - featured in upcoming Manjaro v18.0.3
  • further packaging fixes for LibreOffice 6.2
  • most browsers and firmwares got updated
  • Plasma5 is now at 5.15.0
  • KDE Framework is now at 5.55.0
  • the usual Python and Haskell updates/rebuilds

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


CLT19

Manjaro will take part on the Chemnitz Linux Days in March this year. You may want to visit our booth with the latest Manjaro hardware and Core Developers present to answer your questions. Feel free to bring your devices if you want to have Manjaro installed on them or problems fixed from our experts.

Partnership with FCS Linux Aarhus

We are happy to announce a new partnership with FCS Linux Aarhus owned by @fhdk. This enables us to offer you Laptops with Manjaro pre-installed and Manjaro Stickers you can use on your own hardware or gift them to a friend. For each sale FCS will donate a percentage to the Manjaro project.

Manjaro v18.0.2 released!

To end the year with a high note we updated our flagship ISOs of Manjaro Illyria with the latest packages. It comes with refreshed packages and updated tools. You may want to download our 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.62
  • linux318 3.18.134 [EOL]
  • linux44 4.4.167 [FZN]
  • linux49 4.9.156
  • linux414 4.14.99
  • linux419 4.19.21
  • linux420 4.20.8
  • linux414-rt 4.14.93_rt53
  • linux418-rt 4.18.16_rt9

Package Updates (- linux316 3.16.62

  • linux318 3.18.134 [EOL]
  • linux44 4.4.167 [FZN]
  • linux49 4.9.156
  • linux414 4.14.99
  • linux419 4.19.21
  • linux420 4.20.8
  • linux414-rt 4.14.93_rt53
  • linux418-rt 4.18.16_rt9

A detailed list of all package changes can 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:


19 February 2019 system update: issues which I encountered
#2

Known issues and solutions

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

Need to merge configurations with pacdiff

This update brings some changes in system configuration files. Use sudo pacdiff to review and merge properly.

Notifications looking weird in XFCE

Since the package dunst includes now dunstfy in the main package notifications may not displayed properly in XFCE. Please uninstall that package to solve that issue. Normally not needed in that edition.

Plasma will not reboot from the Application Launcher

If you update from within Plasma (e.g. from the konsole), you may need to issue a systemctl reboot to reboot.


Items from previous update sets

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.


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:

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

Preparing...
Resolving dependencies...
Checking inter-conflicts...
Downloading...
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.

icon-kde-513

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.


#3

I voted as no issue, but for those that will freak out about Latte-Dock not showing the previews, it was already reported and will be a fix in the 0.8.6 version
https://bugs.kde.org/show_bug.cgi?id=404234

For those that want that earlier, just edit
/usr/share/plasma/plasmoids/org.kde.latte.plasmoid/contents/ui/main.qml
starting line 544 from

        onVisibleChanged: {
            if (visible) {
                windowsPreviewCheckerToNotShowTimer.start();
            }
        }

to

        onVisibleChanged: {
            if (visible) {
                windowsPreviewCheckerToNotShowTimer.start();
            }
            
            mainItem.visible = visible;
        }

Edit UPDATE:
See bellow


#4

No problems, thanks Team.
bob@Manjaro-Testing
OS: Manjaro 18.0.3-pre2 Illyria
Kernel: x86_64 Linux 4.20.8-1-MANJARO
Uptime: 1m
Packages: 1149
Shell: bash 5.0.0
Resolution: 1920x1080
DE: Xfce4
WM: Xfwm4
WM Theme: Agua
GTK Theme: Clearlooks [GTK2]
Icon Theme: gnome
Font: Noto Sans 11
CPU: Intel Core i5-4460 @ 4x 3.4GHz [44.0°C]
GPU: GeForce GT 720
RAM: 479MiB / 7908MiB

[2019-02-14 14:25] [ALPM] upgraded systemd-sysvcompat (239.303+really+239.6-1 -> 241.0-1.1)


#5

Moment of truth bois, will we finally be able to get a real systemd upgrade that isn’t painful?

Hope so.

At least we know that the fix will come soon. :slight_smile:


#6

fixed in latte-dock-0.8.5.r3.g58887ca7-1

… we have to see about that. On my end it didn’t crash.


#7

Can happily report that on my end (T450s) it was uneventful - everything works as it did before after reboot =D


#8

Upgraded my manjaro mate testing… And everything worked. Yes! At least, systemd upgrade worked :slight_smile:


#9

Updated and undergone the biggest fail in a very very long time. Don’t even remember all error-messages I got when trying to boot the system. All I could do was boot from DVD, chroot into my installation and install systemd from stable (and some other packages to resolve dependencies).


#10

Can you be more specific? Which desktop environment do you use?


#11

I use i3wm with some parts of xfce, but I never got so long as to the DE. It was somewhere in the midth of the boot-process I got stuck and landed in emergency-mode ( You know the one where you can type Control-D to continue the boot-process, but all the time go back to the same point) I should have taken a photo of the screen, but was to stressed to solve my problem.

EDIT: I maybe should name, that my home-partition is encrypted and I saw something about unable to unlock this partition somewhere between all error messages.


#12

We are fighting for a longer period now to get systemd updated. So we will see how it goes this time. Having additional encrypted data makes it also harder to check. Let’s see what the feedback from others will be regarding this update …


#13

In any case, I did downgrade the whole system to stable now while we communicated and will wait to the next testing-update to test if it is safe for the stable user to update next time.


#14

one of the pc with /home encrypted with luks does not start with systemd 241
works with systemd 240.95-2 even without downgrading systemd-libs and systemd-sysvcompat

other pc without luks started without any problem

Kernel 4.19.21
xfce
nvidia nonfree

Error Details
● systemd-cryptsetup@luks\x2dfd3ca2ab\x2d849f\x2d472a\x2db4d6\x2dd382887b7e76.service - Cryptography Setup for luks-fd3ca2ab-849f-472a-b4d6-d382887b7e76
   Loaded: loaded (/etc/crypttab; generated)
   Active: failed (Result: exit-code) since Fri 2019-02-15 00:04:06 CET; 4min 34s ago
     Docs: man:crypttab(5)
           man:systemd-cryptsetup-generator(8)
           man:systemd-cryptsetup@.service(8)
  Process: 475 ExecStart=/usr/lib/systemd/systemd-cryptsetup attach luks-fd3ca2ab-849f-472a-b4d6-d382887b7e76 /dev/disk/by-uuid/fd3ca2ab-849f-472a-b4d6-d382887b7e76 /crypto_keyfile.bin luks (code=exited, status=1/FAILURE)
 Main PID: 475 (code=exited, status=1/FAILURE)

feb 15 00:04:06 GionnoLinux systemd[1]: Starting Cryptography Setup for luks-fd3ca2ab-849f-472a-b4d6-d382887b7e76...
feb 15 00:04:06 GionnoLinux systemd-cryptsetup[475]: Set cipher aes, mode xts-plain64, key size 512 bits for device /dev/disk/by-uuid/fd3ca2ab-849f-472a-b4d6-d382887b7e76.
feb 15 00:04:06 GionnoLinux systemd-cryptsetup[475]: Failed to open key file.
feb 15 00:04:06 GionnoLinux systemd-cryptsetup[475]: Failed to activate with key file '/crypto_keyfile.bin': Invalid argument
feb 15 00:04:06 GionnoLinux systemd[1]: systemd-cryptsetup@luks\x2dfd3ca2ab\x2d849f\x2d472a\x2db4d6\x2dd382887b7e76.service: Main process exited, code=exited, status=1/FAILURE
feb 15 00:04:06 GionnoLinux systemd[1]: systemd-cryptsetup@luks\x2dfd3ca2ab\x2d849f\x2d472a\x2db4d6\x2dd382887b7e76.service: Failed with result 'exit-code'.
feb 15 00:04:06 GionnoLinux systemd[1]: Failed to start Cryptography Setup for luks-fd3ca2ab-849f-472a-b4d6-d382887b7e76.


#15

Full disk encryption on the other hand works on my end. / as a whole is encrypted, no seperate partitions


#16

Sour update for me. x session crashed again. Appears to be related to this error. Something happened just after updating systemd that terminated the update process…was like ~5/38 steps and something called like “Terminateddnsmasq 5/38” – or something to that effect, dropped me back into the $ prompt and then session crashed 5 seconds later with that error listed above. I then dropped to a TTY, removed the db.lck, finished updating, but suspect I have at least 1 corrupt package/database since the warning:
error: could not open file /var/lib/pacman/local/dnsmasq-2.80-3/desc: No such file or directory
…when running an -Syu (although the updates did finish) and also querying any package. I suspect the new dnsmaq package is corrupted since doing a sudo pacman -Syu dnsmasq results in a weird error:

warning: could not fully load metadata for package dnsmasq-2.80-3
error: failed to prepare transaction (invalid or corrupted package)
$

…there’s no “.part” files in /var/cache/pacman/pkg so how do I go about reinstalling this package? -Qi shows it’s installed but the install size is 0.00 B lol. I feel like rebooting now would ■■■■■ the system again.


[Testing Update] 2019-02-16 - Kernels, Systemd, Vulkan, Firefox
#17

I’ve got weird systemd-udevd warnings since latest systemd v241 update. There weren’t there on the RCs.

journalctl
feb 15 02:44:32 manjaro systemd-udevd[228]: /usr/lib/udev/rules.d/50-udev-default.rules:18: Invalid GROUP operation
feb 15 02:44:32 manjaro systemd-udevd[228]: /usr/lib/udev/rules.d/50-udev-default.rules:19: Invalid GROUP operation
feb 15 02:44:32 manjaro systemd-udevd[228]: /usr/lib/udev/rules.d/50-udev-default.rules:20: Invalid GROUP operation
feb 15 02:44:32 manjaro systemd-udevd[228]: /usr/lib/udev/rules.d/50-udev-default.rules:21: Invalid GROUP operation
feb 15 02:44:32 manjaro systemd-udevd[228]: /usr/lib/udev/rules.d/50-udev-default.rules:22: Invalid GROUP operation
feb 15 02:44:32 manjaro systemd-udevd[228]: /usr/lib/udev/rules.d/50-udev-default.rules:23: Invalid GROUP operation
feb 15 02:44:32 manjaro systemd-udevd[228]: /usr/lib/udev/rules.d/50-udev-default.rules:24: Invalid GROUP operation
feb 15 02:44:32 manjaro systemd-udevd[228]: /usr/lib/udev/rules.d/50-udev-default.rules:25: Invalid GROUP operation
feb 15 02:44:32 manjaro systemd-udevd[228]: /usr/lib/udev/rules.d/50-udev-default.rules:27: Invalid GROUP operation
feb 15 02:44:32 manjaro systemd-udevd[228]: /usr/lib/udev/rules.d/50-udev-default.rules:29: Invalid GROUP operation
feb 15 02:44:32 manjaro systemd-udevd[228]: /usr/lib/udev/rules.d/50-udev-default.rules:32: Invalid GROUP operation
feb 15 02:44:32 manjaro systemd-udevd[228]: /usr/lib/udev/rules.d/50-udev-default.rules:33: Invalid GROUP operation
feb 15 02:44:32 manjaro systemd-udevd[228]: /usr/lib/udev/rules.d/50-udev-default.rules:34: Invalid GROUP operation
feb 15 02:44:32 manjaro systemd-udevd[228]: /usr/lib/udev/rules.d/50-udev-default.rules:35: Invalid GROUP operation
feb 15 02:44:32 manjaro systemd-udevd[228]: /usr/lib/udev/rules.d/50-udev-default.rules:36: Invalid GROUP operation
feb 15 02:44:32 manjaro systemd-udevd[228]: /usr/lib/udev/rules.d/50-udev-default.rules:37: Invalid GROUP operation
feb 15 02:44:32 manjaro systemd-udevd[228]: /usr/lib/udev/rules.d/50-udev-default.rules:39: Invalid GROUP operation
feb 15 02:44:32 manjaro systemd-udevd[228]: /usr/lib/udev/rules.d/50-udev-default.rules:40: Invalid GROUP operation
feb 15 02:44:32 manjaro systemd-udevd[228]: /usr/lib/udev/rules.d/50-udev-default.rules:43: Invalid GROUP operation
feb 15 02:44:32 manjaro systemd-udevd[228]: /usr/lib/udev/rules.d/50-udev-default.rules:47: Invalid GROUP operation
feb 15 02:44:32 manjaro systemd-udevd[228]: /usr/lib/udev/rules.d/50-udev-default.rules:48: Invalid GROUP operation
feb 15 02:44:32 manjaro systemd-udevd[228]: /usr/lib/udev/rules.d/50-udev-default.rules:49: Invalid GROUP operation
feb 15 02:44:32 manjaro systemd-udevd[228]: /usr/lib/udev/rules.d/50-udev-default.rules:50: Invalid GROUP operation
feb 15 02:44:32 manjaro systemd-udevd[228]: /usr/lib/udev/rules.d/50-udev-default.rules:52: Invalid GROUP operation
feb 15 02:44:32 manjaro systemd-udevd[228]: /usr/lib/udev/rules.d/50-udev-default.rules:53: Invalid GROUP operation
feb 15 02:44:32 manjaro systemd-udevd[228]: /usr/lib/udev/rules.d/50-udev-default.rules:54: Invalid GROUP operation
feb 15 02:44:32 manjaro systemd-udevd[228]: /usr/lib/udev/rules.d/50-udev-default.rules:55: Invalid GROUP operation
feb 15 02:44:32 manjaro systemd-udevd[228]: /usr/lib/udev/rules.d/50-udev-default.rules:56: Invalid GROUP operation
feb 15 02:44:32 manjaro systemd-udevd[228]: /usr/lib/udev/rules.d/50-udev-default.rules:57: Invalid GROUP operation
feb 15 02:44:32 manjaro systemd-udevd[228]: /usr/lib/udev/rules.d/50-udev-default.rules:59: Invalid GROUP operation
feb 15 02:44:32 manjaro systemd-udevd[228]: /usr/lib/udev/rules.d/50-udev-default.rules:60: Invalid GROUP operation
feb 15 02:44:32 manjaro systemd-udevd[228]: /usr/lib/udev/rules.d/50-udev-default.rules:61: Invalid GROUP operation
feb 15 02:44:32 manjaro systemd-udevd[228]: /usr/lib/udev/rules.d/50-udev-default.rules:62: Invalid GROUP operation
feb 15 02:44:32 manjaro systemd-udevd[228]: /usr/lib/udev/rules.d/50-udev-default.rules:63: Invalid GROUP operation
feb 15 02:44:32 manjaro systemd-udevd[228]: /usr/lib/udev/rules.d/50-udev-default.rules:64: Invalid GROUP operation
feb 15 02:44:32 manjaro systemd-udevd[228]: /usr/lib/udev/rules.d/50-udev-default.rules:66: Invalid GROUP operation
feb 15 02:44:32 manjaro systemd-udevd[228]: /usr/lib/udev/rules.d/50-udev-default.rules:67: Invalid GROUP operation
feb 15 02:44:32 manjaro systemd-udevd[228]: /usr/lib/udev/rules.d/50-udev-default.rules:68: Invalid GROUP operation
feb 15 02:44:32 manjaro systemd-udevd[228]: /usr/lib/udev/rules.d/50-udev-default.rules:69: Invalid GROUP operation
feb 15 02:44:32 manjaro systemd-udevd[228]: /usr/lib/udev/rules.d/50-udev-default.rules:70: Invalid GROUP operation
feb 15 02:44:32 manjaro systemd-udevd[228]: /usr/lib/udev/rules.d/50-udev-default.rules:71: Invalid GROUP operation
feb 15 02:44:32 manjaro systemd-udevd[228]: /usr/lib/udev/rules.d/50-udev-default.rules:72: Invalid GROUP operation
feb 15 02:44:32 manjaro systemd-udevd[228]: /usr/lib/udev/rules.d/50-udev-default.rules:73: Invalid GROUP operation
feb 15 02:44:32 manjaro systemd-udevd[228]: /usr/lib/udev/rules.d/50-udev-default.rules:82: Invalid GROUP operation

#18

The information about the package has been lost because of the crash in the middle of the update.

(!) Warning: I’m really not sure about what I’ll suggest. My methods looks pretty messy, and may be dangerous and not applicable in all situations too. If someone has a better and cleaner method to do, please suggest it. (!)

Perhaps something you could do is:

  • Force the removal of the package without considering dependencies.
    sudo pacman -Rdd dnsmasq

  • Install the package again (with --overwrite, because since it has lost all information about the package, the package manager couldn’t remove the files that were supposed to belong to this package).
    sudo pacman -S dnsmasq --overwrite '*'

(I’m not sure about the exact syntax of --overwrite. Feel free to correct me.)
(Using --overwrite like this is not a good idea in general, but considering the massive amount of file conflicts you’ll have, and that it’s already messed up anyway, it’ll do the job way faster. Feel free to suggest a cleaner method.)

  • Perhaps verify again if there’s update to do or not right after.
    sudo pacman -Syu

  • Perhaps you should also check if you could install anything to verify that pacman works correctly. Install any random application that you don’t have yet.

Hopefully it does the trick.


[Stable Update] 2019-02-19 - Kernels, KDE, LibreOffice, Systemd, VirtualBox, Deepin, Qt, Firmwares, Wine
#19

It went fine for me, unstable branch user here. works like it did before. All of you dudes did get and apply correctly the transition to systemd-libs, yes?


#20

Looks like that worked, I probably also should have reinstalled systemd again for good measure, but it looks like the system booted after a 2 min stop job. Going through journalctl here’s the first sign of trouble as soon as systemd was being updated:

systemd[13449]: /usr/lib/systemd/system-generators/ostree-system-generator failed with exit status 127.
dbus-daemon[535]: Unknown username “systemd-timesync” in message bus configuration file
dbus-daemon[535]: [system] Unable to reload configuration: (null)
dbus-daemon[535]: Unable to reload configuration: (null)
dbus-daemon[535]: Unknown username “systemd-timesync” in message bus configuration file
…[dbus-daemon segfaults]…

in pacman.log, here’s how far the update process went before everything terminated:

[ALPM] removed libsystemd (239.303+really+239.6-1)
[ALPM] installed systemd-libs (241.0-1.1)
[ALPM] upgraded cryptsetup (2.0.6-1 -> 2.1.0-1)
[ALPM] upgraded libidn2 (2.1.0-1 -> 2.1.1-2)
[ALPM] upgraded systemd (239.303+really+239.6-1 -> 241.0-1.1)
[ALPM] upgraded crda (4.14-1 -> 4.14-2)
[ALPM] upgraded libpsl (0.20.2-3 -> 0.20.2-5)
[ALPM] upgraded curl (7.64.0-1 -> 7.64.0-3)

In pacman.log, it’s simply listed as pacman -S --overwrite * dnsmasq


[Testing Update] 2019-02-16 - Kernels, Systemd, Vulkan, Firefox