If you have this file conflict, we recommend to use the command-line interface for this time and use the
--overwrite option. In a command-line interface, use the following command or any equivalent of your choice:
Like every mariadb feature update this requires the data directory to be updated. With the new configuration in place run:
Items from previous update sets
XFCE 4.14-pre2 : I do not see XFCE 4.14-pre2 in the repositories!?
You won't see explicitly 4.14-pre2 anywhere on our
xfce-gtk3 packages. We follow the versioning used by upstream. Here's the list of all components that are part of XFCE 4.14-pre2.
Kvantum theme reset
If you are using the Matcha theme in kvantum you may experience a theme reset. Simply install kvantum-theme-matcha if not happend yet and select the new provided variants. Manjaro 18.1 releases will ship with the new themes by default.
Issues with Octopi
Currently several users report different issues for Octopi. So if you encounter some of them, you may switch to pamac for now:
sudo pacman -Syu pamac
sudo pacman -Syu pamac will both install Pamac and upgrade all upgradable packages on your system at the same time.)
Issues with DisplayCAL
DisplayCAL 184.108.40.206 - Missing python2-dbus causes failure to launch application.
Solution - Install the
python2-dbus package for now. Version 3.8.2 fixes the dependency error. As and when DisplayCAL 3.8.2 reaches stable branch you can remove python2-dbus as it does not require it. Only remove python2-dbus again if you installed it specifically for DisplayCAL.
Regression with Linux firmwares on machine running Vega GPUs.
June 2, 2019: We expect it to be fixed with linux-firmware 20190514-711d329-1.1. We downgraded the firmware related to Vega GPUs to a previous version. You should now be able to use Linux 4.19 correctly.
[Stable Update] 2019-05-26 - Kernels, XFCE 4.14-pre1, Virtualbox, LibreOffice
linux-firmware 20190514-711d329-1 introduced a regression that can make the system unbootable on systems that use a AMD Vega GPUs (for example: Vega 64, Vega 56, Vega 10) and Linux 4.19.
It is a regression that affects both Manjaro and Arch Linux. Here's some links.
Arch Linux bugtracker: https://bugs.archlinux.org/task/62666
Manjaro forum: Most recent stable branch update problem
Manjaro forum: Manjaro update prevents system booting
Manjaro forum: 'linux-firmware 20190514.711d329-1' update prevents my system booting.
If you are affected by this issue, you have essentially two choices: either use a different kernel or downgrade
linux-firmware. The most preferred method is the first one since it doesn't involve keeping a package to an older version. Either way, if your system is completely unbootable (not even with a command line interface), you will need to do a chroot to repair your system. For each solution suggested below, we will suppose that you need to do a chroot; skip the chroot part if you manage to reach an usable command line interface.
For the first solution, as far as we know, it works fine on Linux 5.1 and supposedly also on Linux 5.0. Follow these steps in order to be able to install a new kernel:
- Launch a live session with an installation medium;
- Open a terminal;
- Chroot your system. You may do so automatically with
manjaro-chroot -a. On more complex system where manjaro-chroot may simply fail, you may have to do a manual chroot.;
- Once you have chrooted on your system, use
mhwd-kernel -i linux51 to install Linux 5.1 and all extra modules needed for your system. You may also try with Linux 5.0 (replace
linux50), although Linux 5.0 is expected to be End of Life soon.
(If you have multiple kernels installed on your machine, you may want to boot with other kernels before trying to install a new one.)
For the second one:
- Chroot to your system from a live session;
- Downgrade the
linux-firmware package to version 20190424.4b6cf2b-1 with
pacman -U /var/cache/pacman/pkg/linux-firmware-20190424.4b6cf2b-1-any.pkg.tar.xz. If the package is not available in your local cache, use
pacman -U https://archive.archlinux.org/packages/l/linux-firmware/linux-firmware-20190424.4b6cf2b-1-any.pkg.tar.xz instead.
(Note that if you know how to use downgrade, you may also use downgrade.)
(Remember that downgrading a package is merely a temporary solution, do not hold the package to a previous version forever.)
signature from "Helmut Stult (schinfo) <email@example.com>" is marginal trust
manjaro-keyring first. For more options read this thread:
Issues with "signature is marginal trust" or "invalid or corrupted package"
replace steam-devices with community/game-devices-udev?
Yes. The package name changed. Accept the replacement.
Linux 5.1 - Which extra modules are currently missing?
As said in the announcement, while the newest Linux version has been released in this update set, not every extra modules are currently available in our official repositories. Before jumping on Linux 5.1, please verify if you do not need any of those missing extra modules on your system.
(Last verification: May 26, 2019)
The following extra modules are missing:
The following extra modules are available:
- ACPI call (
- BBSwitch (
- Broadcom wireless driver (
- Catalyst drivers (
- Legacy NVIDIA 340.XX drivers (
- Legacy NVIDIA 390.xx drivers (
- NDIS wrapper (
- Current NVIDIA drivers (
- NVIDIA backlight (
- Realtek 8168 drivers (
- Realtek 8732bu drivers (
- Thinkpad SMAPI (
- SCSI emulation (
- VirtualBox guest modules (
- VirtualBox host modules (
Small cleanup of Manjaro official repositories
Please note that the following packages got removed from our repositories.
COMMAND-NOT-FOUND error during update/installation
During upgrade/installation the package command-not-found tries to sync its database with a mirror that seems to be currently (or permanently ?) offline, resulting in an error message
(1/1) installing command-not-found [########################################] 100%
Could not download catalog file ... aborting
error: command failed to execute correctly
I (oberon) have already opened an issue upstream about the problem.
The KDE Updates Can Cause The Screenlocker To Crash
If you update from within a GUI session and use screenlock (e.g. it kicks in while the large update is being processed), it will crash the screenlocker.
To restore access, press CTRL+ALT+F2 to switch to another tty and log in with your username.
Then type in the following and press enter:
loginctl unlock-session 2
Press CTRL+ALT+F1 to switch back to a now unlocked KDE desktop.
TLP 1.2.1, .pacnew file: Merges may be needed
TLP 1.2.1 got released in [Stable Update] 2019-04-20 update set, replacing TLP 1.1. Therefore, if you have customized your configuration file for TLP (
/etc/default/tlp), a .pacnew file will be created when the
tlp package will be upgraded. This .pacnew file is the new default configuration file provided by the package. Your old configuration file won't be edited or replaced automatically; by default, your old configuration file will be kept as it is and you will have to merge relevant part the new configuration file manually with a text editor. Guidance can't really be more precise since each person has its own configuration.
You may use a tool such as Meld (package:
meld) in order to compare your old configuration file with the .pacnew file and see the differences more easily.
If you haven't modified your configuration file for TLP, normally, you will automatically go on the new configuration file for TLP provided in the package without any manual intervention needed.
If you use the current version of TLPUI (tlpui r109.703bade-1), it may complain with the following error with some settings: "expected item missing in config file." It is most likely because some new parameters introduced with TLP 1.2.1 are not in
/etc/default/tlp. To get rid of those messages, you will need to do some merges between your old configuration files and the .pacnew files and manually add all those new settings, even if you end up using the default value for those settings.
TLPUI cannot be launched
There was a bug in a previous version of TLPUI (confirmed on tlpui r89.d6363f0-1) that changed the permissions of
/etc/default/tlp to 600 (rw-------). The default permissions for this file is 644 (rw-r--r--).
It is most likely that TLPUI doesn't launch because it doesn't have the right permissions for
/etc/default/tlp. TLPUI must be allowed to read that file in order to launch.
First, verify if the permissions of
/etc/default/tlp are set correctly. You may verify that with
ls -l /etc/default/tlp in a terminal. Here's an example of how the output will look like:
$ ls -l /etc/default/tlp
-rw-r--r-- 1 root root 14238 Apr 11 15:26 /etc/default/tlp
If you have
-rw------- instead of
-rw-r--r--, change the permissions of that file so this file becomes readable to the group and others too. You may do so in the terminal with
sudo chmod 644 /etc/default/tlp.
Once it is done, TLPUI should work properly.
"Spring cleanup" on Arch Linux: impact on Manjaro
Recently, Arch Linux did a "spring cleanup" of their Community repository (see the full discussion on the mailing list and seach for "spring"). Many package got removed from the Arch Linux official repositories and dropped to the AUR. Therefore, it means that many packages that were in our repositories because they were imported from Arch Linux got removed from our repositories too. Here's a non-exhaustive list of packages that got removed:
cherrytree - Hierarchical note taking application featuring rich text and syntax highlighting
docky - Full fledged dock application that makes opening common applications and managing windows easier and quicker
mate-menu - Advanced menu for MATE Panel, a fork of MintMenu (Not to be confused with
medit - GTK+ text editor
thermald - The Linux Thermal Daemon program from 01.org
wine-staging-nine has been removed / replaced with
wine-nine. In case it is installed, it should be removed manually. http://archlinux.2023198.n4.nabble.com/Removing-wine-staging-nine-replaced-with-wine-nine-td4722447.html
If you want to continue to use those packages, you will have to use the AUR from now on.
You may try to do a package request in this category, but note that there is a high chance that your demand will be refused.