Known issues and solutions
This is a wiki post; please edit as necessary.
Please, consider subscribing to the Stable Updates Announcements RSS feed
" Replace xorg-mkfontdir with extra/xorg-mkfontscale? [Y/n]"
Accept the replacement.
Linux kernel 5.0.X available. Early problems reported.
The newest kernel series is now available for everyone. Please note that some issues has been reported with version 5.0.1 such as having a long delay at shutdown and losing sound output when using suspend. It is still available for the early adopters. You are free to install and use it or not.
As reported by some users, if you use WireGuard, you may have to manually run
sudo dkms autoinstall in a terminal to get the kernel module working properly with Linux 5.0.1.
More info about
dkms autoinstall (and DKMS in general) here.
Kodi 18.1: extensions may not work properly.
Kodi 18.1 is now available in our repositories. Since this is a major version change, extensions for Kodi (if you use some) may stop working properly. Developers of those extensions will need to make them compatible with Kodi 18.
If Kodi 18.1 doesn’t work properly for you and you absolutely need to use your extensions, you may use the old
kodi package in
/var/cache/pacman/pkg in order to downgrade Kodi to version 17.6. Please note that it is a temporary workaround and that the software provided in the old
kodi package may stop working properly in the future too. You should not keep the downgrade forever.
projectm-qt, file conflict with /usr/share/pixmaps/prjm16-transparent.svg
Starting with version 3.1.0 of ProjectM, there are now only three packages instead of six and the QT part has been merged to the
projectm-qt package before upgrading your system.
If you have not kept up with [Stable Update] 2019-02-19 yet, please read the information below too.
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!
sudo rm /var/lib/pacman/db.lck && sudo pacman -Su
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
Workaround for LibreOffice 6.2.0: you may force Libre Office to use a different VCL by editing /etc/profile.d/libreoffice-fresh.sh, uncommenting the VCL you want to use, and rebooting.
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
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
dbus-x11 package, simply install
dbus-x11 with your favorite package manager:
dbus will be replaced by
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
Step 3 is optional.