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

update
stable

#1

Hi community,

Welcome to our sixth stable update for 2019, which marks also the release of Manjaro v18.0.3 to all our branches. This is again a major update to Manjaro itself. It took us a while to get this update stable enough. Please keep attention also to our troubleshoot section to avoid caveats during updating your system. Deepin users should pay extra attention, as we expect breakage.

So with no further ado, what do we have with this update?

  • we updated systemd to v241 - it has issues with encrypted devices (upstream needs your feedback to solve it properly). However, we added 159 additional patches so far to v241 series. It is critical to accept the replacement of libsystemd with systemd-libs during this update
  • most of our kernels got updated
  • Plasma5 is now at 5.15.0
  • KDE Framework is now at 5.55.0
  • KDE Apps got needed fixes in 18.12.2
  • with Qt 5.12.1 more than 300 issues got solved. Get more information about it from here
  • all the new features you may find in LibreOffice 6.2
  • lot of new features got into Calamares 3.2.4 - featured in our Manjaro v18.0.3
  • VirtualBox 6.0.4 has some needed fixes
  • the development UI Gambas got a new release
  • wine is now at 4.2
  • wine-staging is now at 4.2
  • wine-staging-nine is now at 4.1
  • we updated the brave browser to its latest release in standard and beta release series
  • Firefox got its sixth beta release of v66 series
  • a newer texlive snapshot got added
  • we added the latest grub and vulkan packages
  • most firmwares got updated
  • some deepin packages got renewed. We expect breakage, so update your Deepin version of Manjaro with caution and report issues ASAP in a separat thread in our community support section!
  • 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.3 released!

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.15 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.158
  • linux414 4.14.101
  • linux419 4.19.22
  • linux420 4.20.10
  • linux414-rt 4.14.93_rt53
  • linux418-rt 4.18.16_rt9

Package Updates (Tue Feb 19 10:20:57 CET 2019)

  • stable community x86_64: 1453 new and 1467 removed package(s)
  • stable core x86_64: 48 new and 48 removed package(s)
  • stable extra x86_64: 1147 new and 1235 removed package(s)
  • stable multilib x86_64: 41 new and 46 removed package(s)

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
Announcement of the latest Stable update?
Tips for installing Manjaro Deepin on SSD
Announcement of the latest Stable update?
[Stable Update] 2019-03-12 - Kernels, KDE, Deepin, LibreOffice, Nvidia, Browsers, Calamares
[Solved] No working terminal or network manager after update
[SOLVED]Error while trying to install Virtualbox
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 Stable Updates Announcements RSS feed

How do I do updates via TTY-terminal?

This is a really major update release, with a lot of changes. To limit the risk of breakage in the middle of an system upgrade (which could lead to a broken system that will need to be repaired), you may want to do the system upgrade within a minimalist command-line environment. To do so:

  • Press CTRL+ALT+F2 (or F3, F4, F5, F6) to go into a pure command line interface.
  • Log in with your credentials.
  • Once logged in, you’ll have access to a CLI shell, like if you were using a terminal. Use sudo pacman -Syyu to update your system.

To go back to your regular desktop, press CTRL+ALT+F7. On some systems, it can be CTRL+ALT+F1 instead.

Systemd v241 series update

We tried to update systemd several times now in the last couple of month. Now we were certain to have a good snapshot, which works on most of Manjaro installations. When you are asked to replace libsystemd with systemd-libs please accept this request, otherwise your system may break!


“A stop job is running for User Manager for UID 1000” at shutdown/reboot, what should I do?

Stopping of the User Manager job may take 2 minutes due to the systemd update. Simply wait and let it go. It usually goes away at next boot.


Update is not proceeding due file conflicts

It is a common issue time to time to get errors like this:

python-pyqt5: /usr/lib/python3.7/site-packages/PyQt5/pycache/init.cpython-37.pyc already exists in filesystem

Especially with pycache files, you shouldn’t worry about. Simply delete the conflicting file(s) or use the overwrite function of pacman to continue the update.

sudo pacman -S python-pyqt5 --overwrite ‘*’


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.


KDE Plasma5 may crash with this update

Due to our long-term testing of v5.15.0 release on some rare edge cases your Plasma5 may crash during this update. If that happens you have to switch to a TTY (Ctrl+ALT+F3), login and check with a cli-package-manager if your update is fully updated!

Pacman

sudo rm /var/lib/pacman/db.lck && sudo pacman -Su

Pamac

sudo rm /var/lib/pacman/db.lck && pamac upgrade


Various issues when using LibreOffice 6.2.0 on KDE Plasma 5 (can’t copy+paste, can’t use backspace in Calc, etc.)

Unfortunately, it seems that the new upstream VCL plugin for integration in KDE5 Plasma (see this notice from LibreOffice) isn’t perfectly functional yet. Upstream is aware of the situation and fixes will come in future versions of LibreOffice.

Examples of related bug reports from the Document Foundation
https://bugs.documentfoundation.org/show_bug.cgi?id=122689
https://bugs.documentfoundation.org/show_bug.cgi?id=122238

Workaround for LibreOffice 6.2.0: you may force Libre Office to use a different VCL by editing /etc/profile.d/libreoffice-fresh.sh and uncommenting the VCL you want to use.
More info about VCL: https://wiki.archlinux.org/index.php/LibreOffice#Theme

You may also consider to switch from LibreOffice Fresh to LibreOffice Still, the latter being at version 6.1.5.

Items from previous update sets

Can’t update with linux417 or/and linux418 present

Since we have completely removed those kernel series you should remove those kernels before you upgrade. Most likely you will notice that as you may have extramodules like nvidia installed. Those got updated and therefore complain about dependency issues.


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.


Potential issues with dunstify-1.3.2-1 package

Upstream decided to include dunstify now in the dunst package. However, they didn’t add any replace, conflicts tags to that package, as Arch never packaged dunstify before. Therefore we try to remove dunstify automatically via manjaro-system package. On rare cases however, a manual user invention might be needed to remove the package. If that is the case, please issue the following command manually on your system: sudo pacman -Rdd dunstify && sudo pacman -Syu


Warning: PACKAGE: directory permissions differ on FILENAME

A file or directory on your system has a set of permissions which is different to those in the new package. You can either ignore it (because you changed it yourself) or you can change them so they match.

For example, for this message:

Warning: blueman: directory permissions differ on /usr/share/polkit-1/rules.d/filesystem: 750  package: 755

you can change the local file to match the package with:

sudo chmod 755 /usr/share/polkit-1/rules.d/filesystem

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.


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/.


Failed System Update
Last update screwed up my machine
Warning: blueman: directory permissions differ on /usr/share/polkit-1/rules.d/filesystem: 750 package: 755
Software update stalled, blank screen, had to reboot, now Network Manager fails, hangs on boot
Issues in Libreoffice : cannot copy and paste from Kate to LO - guess i need an update of 6.2.0.3 to newest version
Error message pyqt5
Upgrade does not run through because of "/usr/lib/python3.7/..." in file system
Cant paste text copied from Writer
#3

I got the update yesterday, updated with Pamac, no issues whatsoever!


#4
(195/195) Prüfe Schlüssel im Schlüsselring                                                                                [##########################################################################] 100%
(195/195) Überprüfe Paket-Integrität                                                                                      [##########################################################################] 100%
(195/195) Lade Paket-Dateien                                                                                              [##########################################################################] 100%
(195/195) Prüfe auf Dateikonflikte                                                                                        [##########################################################################] 100%
Fehler: Konnte den Vorgang nicht durchführen (In Konflikt stehende Dateien)
python-pyqt5: /usr/lib/python3.7/site-packages/PyQt5/__pycache__/__init__.cpython-37.pyc existiert im Dateisystem
Fehler sind aufgetreten, keine Pakete wurden aktualisiert.

Seems like that I have some problems with pyqt5.
Actually installed packages for pyqt5 on my Notebook:
pyqt5-common
python-pyqt5
python-sip-pyqt5

Any idea?


#5

After the update JuffEd does not start anymore.

[asus@asus-pc ~]$ juffed
juffed: error while loading shared libraries: libqscintilla2_qt5.so.13: cannot open shared object file: No such file or directory

My solution

downgrade qscintilla-qt5

Otherwise no problems.
LXQT with Kernel 4.20
XFCE with Kernel 4.20
Thanks!


#6

Updated five DELL intel machines KDE through a tty.
No issues to report. :+1:

Alex


#7

You’ll need to remove the conflicting file. I edited the wikipost since it is a common issue.


#9

Sorry guys. I was a bit too fast :slight_smile: …thank you, I’ll remove it.


#10

Everything went smoothly apart from a few minor quirks:

  1. Pacman complained about lib/python3.7/site-packages/PyQt5/__pycache__/__init__.cpython-37.pyc

Solution: I checked with pacman -Qo which returned that the file didn’t belong to any package so I just deleted it (the folder name ‘cache’ influenced my decision)

  1. The download from my local mirror was fast (10mb/s) but once it reached 97% (downloading a mesa 32 something package) it crawled down to like 80kb/sec and took over 20 minutes to finish. Why am I reporting this? Because I initially thought it was my internet provider’s fault, then the mirror’s… but today I updated another system on a 1GB line with a different mirror and here the update stalled exactly at the same point. It might not be internet related after all. It’s a friendly warning not to interrupt the entire process. Just let it run. It will finish.

  2. On reboot, all updated systems timed out while shutting down something on behalf of user ID 1000. Didn’t seem to affect anything but it’s another friendly warning to let the system do its thing.

Everything is working fine for now.


#11

thanks for release!


#12

Am I reading correctly that this affects an encrypted /home directory only?

I have an unencrypted boot and encrypted root partition. I unlock that before the system reaches systemd.


#13

I’m a bit hesitant - has anyone with full disk encryption (no seperate /boot - using keyfile in /etc/mkinitcpio.conf and a second disc with the same keyfile in fstab ) successfully updated yet?
On github only encrypted /home is specifically mentioned?


#14

Update on 12 Systems and 1 VB without Problems.

DK3


#15

in the unstable forum has been discussed and there are some work arounds…
but it’s better if you decrypt for the time being…


#16

Somehow libidn2 broke during the update stopping pacman from working, so I had to do follow this guide: https://wiki.archlinux.org/index.php/pacman#Pacman_crashes_during_an_upgrade


#17

i’ve seen a lot of post and problems with systemd breaking manjaro… and all of those whom have had those problems done it with the GUI updater (Pamac).
Try to update from the terminal guys/girls.

In terminal

sudo pacman -Syyu

#18

Bei mir leider nicht ohne Fehler. Ich zitiere mich mal selbst aus einem Post, welchen ich gestern im deutschen Teil des Forums schrieb:

Seit dem letzten Update, welches Manjaro (KDE) auf Version 18.03 gebracht hat, läuft meine Maus (eine Microsoft Intellipoint 3.0) nur noch mit einer sehr niedrigen Auflösung. Es fühlt sich an, als ob sie auf dem Screen klebt. Die Maus läuft ohne weitere Treiber, also keine Möglichkeit, die Auflösung über den Treiber wieder zu ändern. Mausbeschleunigung erhöhen hat nichts gebracht. Wenn ich die 18.02 von der Live-DVD boote, läuft die Maus flüssig, wie gewohnt, auch noch nach der Neuinstallation von 18.2. Sobald aber die angefallenen Updates durch sind (danach Neustart), hängt die Maus mit ner gefühlten Auflösung von 200 dpi fest. Habe dann mal XFCE installiert, um auszuschließen, dass es am neuen KDE 5.15 liegt, aber auch da gleiches Problem nach Update auf 18.03. Was ist da schief gelaufen? Habe jetzt erst mal zum Arbeiten Mint installiert, bis es eine Lösung für das Problem gibt …

Ich will dieses Mint gerne wieder los werden, aber so kann ich Manjaro derzeit nicht nutzen. Neinstallation mit der kommenden 18.03 Iso?


#19

Hey guys, I know thats a lot of work and I’m sure you really love it, because since ~6 years I’m using manjaro and during the time it evolved pretty well and with each release you guys are showing how much you like to develop it.

A BIG THANK YOU!!! :slight_smile:

Keep going on!!!


#20

Gnome edition. Dell Optiplex 5050. Updated twice through gui, both times computer dumped to dell logo, and after reboot got stuck on a blinking _

Restored both of those with timeshift

Switched to tty command line with ctrl alt f3, ran update from that, got to setting up hooks, then it dumped to a blinking _, I hit the power button once, let the computer shut down on its own, after reboot, everything seems good. If anyone wants me to check on something to shed more light on what caused the problem for others, I can go digging, but I don’t know my way around under the hood as the more advanced users.


#21

Hi Termy,
I’m not sure I have exactly the same setup as you do, but I wanted to mention this anyway.

I have two systems with LLVM-on-LUKS, where the LUKS volume contains an LLVM containing /home, /, and swap, and there’s a separate partition for /boot/efi (unencrypted, contains grub). I had no issues with this update.

(I accidentally installed it before I knew encryption might cause problems, and I guess I was lucky)

Hope this helps someone!