[Stable Update] 2019-07-03 – Kernels, Systemd, Pamac 8.0, KDE, XFCE, Browser, QT – Stable Updates

This can be a wiki submit; please edit as vital.
Please, contemplate subscribing to the Stable Updates Bulletins RSS feed

The update to mariadb 10.four.6-1 and later modifications configuration format as really helpful by upstream.

The primary configuration file moved from /and so forth/mysql/my.cnf (and its embrace listing /and so forth/mysql/my.cnf.d/ ) to /and so forth/my.cnf (and /and so forth/my.cnf.d/ ). Make certain to maneuver your configuration.

Instantiated providers (like [email protected] ) are not configured in separate information (like /and so on/mysql/myfoo.cnf ). As an alternative move your configuration to configuration blocks with group suffix in most important configuration file, one for each service. A block should look one thing like this:

Like every mariadb function replace this requires the info listing to be updated. With the brand new configuration in place run:

Gadgets from earlier update units

XFCE 4.14-pre2 : I do not see XFCE four.14-pre2 within the repositories!?

You gained’t see explicitly four.14-pre2 anyplace on our xfce-gtk3 packages. We comply with the versioning utilized by upstream. Here’s the record of all elements which are part of XFCE four.14-pre2.

Kvantum theme reset

In case you are using the Matcha theme in kvantum you might expertise a theme reset. Simply install kvantum-theme-matcha if not happend but and choose the new offered variants. Manjaro 18.1 releases will ship with the new themes by default.

Issues with Octopi

At present a number of users report totally different points for Octopi. So when you encounter a few of them, you could change to pamac for now: sudo pacman -Syu pamac

(Word that sudo pacman -Syu pamac will both set up Pamac and upgrade all upgradable packages in your system at the similar time.)

Points with DisplayCAL

DisplayCAL three.8.1.1 – Lacking python2-dbus causes failure to launch software.

Answer – Set up the python2-dbus package deal for now. Model three.8.2 fixes the dependency error. As and when DisplayCAL 3.eight.2 reaches secure department you possibly can take away python2-dbus because it does not require it. Solely remove python2-dbus again in case you installed it particularly for DisplayCAL.

Regression with Linux firmwares on machine operating Vega GPUs.

June 2, 2019: We anticipate it to be fastened with linux-firmware 20190514-711d329-1.1. We downgraded the firmware related to Vega GPUs to a previous model. You need to now be capable of use Linux four.19 appropriately.

[Stable Update] 2019-05-26 – Kernels, XFCE 4.14-pre1, Virtualbox, LibreOffice

linux-firmware 20190514-711d329-1 launched a regression that can make the system unbootable on techniques that use a AMD Vega GPUs (for example: Vega 64, Vega 56, Vega 10) and Linux four.19.

It’s a regression that affects both Manjaro and Arch Linux. Here’s some hyperlinks.

Arch Linux bugtracker:
Manjaro forum: Most up-to-date secure branch replace drawback
Manjaro forum: Manjaro replace prevents system booting
Manjaro discussion board: ‘linux-firmware 20190514.711d329-1’ update prevents my system booting.

In case you are affected by this concern, you will have primarily two decisions: both use a unique kernel or downgrade linux-firmware. Probably the most most popular technique is the first one since it doesn’t contain preserving a package deal to an older version. Either approach, if your system is completely unbootable (not even with a command line interface), you will have to do a chroot to repair your system. For each answer advised under, we’ll suppose that you could do a chroot; skip the chroot half in the event you handle to succeed in an usable command line interface.

For the first answer, as far as we know, it works high quality on Linux 5.1 and supposedly also on Linux 5.0. Comply with these steps so as to have the ability to set up a new kernel:

  • Launch a stay session with an installation medium;
  • Open a terminal;
  • Chroot your system. Chances are you’ll achieve this mechanically with manjaro-chroot -a. On more complicated system the place manjaro-chroot might merely fail, you might have to do a guide chroot.;
  • After you have chrooted on your system, use mhwd-kernel -i linux51 to put in Linux 5.1 and all additional modules wanted in your system. You might also attempt with Linux (exchange linux51 with linux50), though Linux is predicted to be Finish of Life quickly.

(When you have multiple kernels put in on your machine, you could need to boot with different kernels before making an attempt to install a brand new one.)

For the second one:

  • Chroot to your system from a stay session;
  • Downgrade the linux-firmware package deal to version 20190424.4b6cf2b-1 with pacman -U /var/cache/pacman/pkg/linux-firmware-20190424.4b6cf2b-1-any.pkg.tar.xz. If the package deal isn’t out there in your local cache, use pacman -U as an alternative.

(Word that if you understand how to make use of downgrade, you might also use downgrade.)
(Keep in mind that downgrading a package deal is merely a short lived answer, don’t hold the package deal to a previous model eternally.)

signature from “Helmut Stult (schinfo) ” is marginal trust

Update manjaro-keyring first. For more choices learn this thread:

Issues with “signature is marginal trust” or “invalid or corrupted package”

exchange steam-devices with group/game-devices-udev?

Sure. The package deal identify changed. Accept the alternative.

Linux 5.1 – Which additional modules are presently missing?

As stated in the announcement, whereas the most recent Linux version has been launched in this replace set, not each additional modules are presently obtainable in our official repositories. Before leaping on Linux 5.1, please verify if you do not want any of those missing additional modules in your system.

(Final verification: Might 26, 2019)
The next additional modules are lacking:

The next additional modules are available:

  • ACPI call (linux51-acpi_call);
  • BBSwitch (linux51-bbswitch);
  • Broadcom wi-fi driver (linux51-broadcom-wl);
  • Catalyst drivers (linux51-catalyst);
  • Legacy NVIDIA 340.XX drivers (linux51-nvidia-340xx);
  • Legacy NVIDIA 390.xx drivers (linux51-nvidia-390xx);
  • NDIS wrapper (linux51-ndiswrapper);
  • Present NVIDIA drivers (linux51-nvidia);
  • NVIDIA backlight (linux51-nvidiabl);
  • Realtek 8168 drivers (linux51-r8168);
  • Realtek 8732bu drivers (linux51-rtl8732bu);
  • Thinkpad SMAPI (linux51-tp_smapi);
  • SCSI emulation (linux51-vhba-module);
  • VirtualBox visitor modules (linux51-virtualbox-guest-modules);
  • VirtualBox host modules (linux51-virtualbox-host-modules).

Small cleanup of Manjaro official repositories

Please notice that the following packages acquired removed from our repositories.

  • chromium-chromevox
  • gimp-gtk3
  • pamac-classic
  • pamac-dev
  • pamac-dev-tray-appindicator

COMMAND-NOT-FOUND error during update/installation

Throughout upgrade/set up the package deal command-not-found tries to sync its database with a mirror that seems to be at present (or completely ?) offline, leading to an error message

(1/1) putting in command-not-found [########################################] 100%
Could not download catalog file … aborting
error: command did not execute appropriately

I (oberon) have already opened a problem upstream about the problem.

The KDE Updates Can Cause The Screenlocker To Crash

When you update from inside a GUI session and use screenlock (e.g. it kicks in while the massive update is being processed), it’ll crash the screenlocker.

To restore entry, press CTRL+ALT+F2 to modify to another tty and log in together with your username.

Then sort within the following and press enter:

loginctl unlock-session 2

Press CTRL+ALT+F1 to modify back to a now unlocked KDE desktop.

TLP 1.2.1, .pacnew file: Merges may be wanted

TLP 1.2.1 obtained released in [Stable Update] 2019-04-20 replace set, replacing TLP 1.1. Subsequently, if in case you have custom-made your configuration file for TLP (/and so on/default/tlp), a .pacnew file will probably be created when the tlp package deal might be upgraded. This .pacnew file is the brand new default configuration file offered by the package deal. Your previous configuration file gained’t be edited or changed mechanically; by default, your previous configuration file might be stored as it’s and you will have to merge related part the new configuration file manually with a textual content editor. Steerage can’t really be extra precise since each individual has its own configuration.

Chances are you’ll use a software comparable to Meld (package deal: meld) with a purpose to examine your previous configuration file with the .pacnew file and see the variations more simply.

In the event you haven’t modified your configuration file for TLP, normally, you’ll routinely go on the new configuration file for TLP offered within the package deal without any guide intervention wanted.

When you use the current version of TLPUI (tlpui r109.703bade-1), it might complain with the following error with some settings: “expected item missing in config file.” It is more than likely as a result of some new parameters introduced with TLP 1.2.1 will not be in /and so on/default/tlp. To eliminate those messages, you will have to do some merges between your previous configuration information and the .pacnew information and manually add all those new settings, even when you end up utilizing the default value for these settings.

TLPUI cannot be launched

There was a bug in a earlier version of TLPUI (confirmed on tlpui r89.d6363f0-1) that modified the permissions of /and so forth/default/tlp to 600 (rw——-). The default permissions for this file is 644 (rw-r–r–).

It is almost definitely that TLPUI doesn’t launch because it doesn’t have the best permissions for /and so forth/default/tlp. TLPUI have to be allowed to learn that file as a way to launch.

First, verify if the permissions of /and so forth/default/tlp are set appropriately. You might verify that with ls -l /and so on/default/tlp in a terminal. Here’s an example of how the output will appear to be:

$ ls -l /and so on/default/tlp
-rw-r–r– 1 root root 14238 Apr 11 15:26 /and so on/default/tlp

If in case you have -rw——- as an alternative of -rw-r–r–, change the permissions of that file so this file becomes readable to the group and others too. You might achieve this in the terminal with sudo chmod 644 /and so on/default/tlp.

As soon as it’s carried out, TLPUI ought to work properly.

“Spring cleanup” on Arch Linux: influence on Manjaro

Just lately, Arch Linux did a “spring cleanup” of their Group repository (see the complete discussion on the mailing record and seach for “spring”). Many package deal received faraway from the Arch Linux official repositories and dropped to the AUR. Subsequently, it signifies that many packages that have been in our repositories as a result of they have been imported from Arch Linux acquired removed from our repositories too. Right here’s a non-exhaustive record of packages that obtained eliminated:

  • cherrytree – Hierarchical notice taking software featuring rich text and syntax highlighting

  • docky – Full fledged dock software that makes opening widespread purposes and managing windows easier and quicker

  • mate-menu – Advanced menu for MATE Panel, a fork of MintMenu (Not to be confused with mate-menus)

  • medit – GTK+ text editor

  • thermald – The Linux Thermal Daemon program from

  • wine-staging-nine has been eliminated / replaced with wine-nine. In case it’s installed, it ought to be removed manually.

If you wish to proceed to make use of these packages, you will have to use the AUR any more.

You might try to do a package deal request on this class, but observe that there’s a high probability that your demand will probably be refused.