[Stable Update] 2019-07-09 – Qt5, Cinnamon, XFCE, Deepin, Palemoon, Firefox – Stable Updates

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

If in case you have this file conflict, we advocate to use the command-line interface for this time and use the –overwrite choice. In a command-line interface, use the following command or any equal of your selection:

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

The primary configuration file moved from /and so forth/mysql/my.cnf (and its embrace directory /and so forth/mysql/my.cnf.d/ ) to /and so on/my.cnf (and /and so forth/my.cnf.d/ ). Be certain that 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 every service. A block should look one thing like this:

Like each mariadb function update this requires the info listing to be up to date. With the new configuration in place run:

Gadgets from earlier replace sets

XFCE four.14-pre2 : I don’t 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 4.14-pre2.

Kvantum theme reset

In case you are utilizing the Matcha theme in kvantum chances are you’ll expertise a theme reset. Merely install kvantum-theme-matcha if not happend yet and choose the new offered variants. Manjaro 18.1 releases will ship with the brand new themes by default.

Points with Octopi

Presently a number of customers report totally different issues for Octopi. So for those who encounter some of them, you might change to pamac for now: sudo pacman -Syu pamac

(Notice that sudo pacman -Syu pamac will each set up Pamac and upgrade all upgradable packages on your system on 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 3.eight.2 fixes the dependency error. As and when DisplayCAL 3.8.2 reaches secure branch you possibly can remove python2-dbus as it doesn’t require it. Only take away python2-dbus again should 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 associated to Vega GPUs to a previous version. You must now have the ability to use Linux 4.19 appropriately.

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

linux-firmware 20190514-711d329-1 introduced a regression that may make the system unbootable on methods 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:
Manjaro forum: Most recent secure branch replace drawback
Manjaro discussion board: Manjaro update prevents system booting
Manjaro forum: ‘linux-firmware 20190514.711d329-1’ update prevents my system booting.

In case you are affected by this difficulty, you could have primarily two decisions: both use a unique kernel or downgrade linux-firmware. Probably the most most popular technique is the primary one because it doesn’t contain protecting a package deal to an older version. Both method, 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 every answer steered under, we’ll suppose that you’ll want to do a chroot; skip the chroot half should you handle to succeed in an usable command line interface.

For the first answer, as far as we all know, it really works nice on Linux 5.1 and supposedly additionally 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. You might achieve this mechanically with manjaro-chroot -a. On more complicated system where manjaro-chroot might merely fail, you might have to do a guide chroot.;
  • Upon getting chrooted in your system, use mhwd-kernel -i linux51 to put in Linux 5.1 and all additional modules needed in your system. You might also attempt with Linux 5.0 (exchange linux51 with linux50), although Linux is predicted to be End of Life soon.

(When you’ve got a number of kernels put in in your machine, you could need to boot with other kernels earlier than making an attempt to put in a new one.)

For the second:

  • 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 obtainable in your native cache, use pacman -U as an alternative.

(Observe that if you understand how to use downgrade, you might also use downgrade.)
(Keep in mind that downgrading a package deal is merely a short lived answer, don’t maintain the package deal to a previous version endlessly.)

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

Replace manjaro-keyring first. For more options learn this thread:

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

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

Yes. The package deal identify modified. Settle for the alternative.

Linux 5.1 – Which additional modules are presently missing?

As stated in the announcement, while the most recent Linux model has been released in this update set, not every additional modules are presently obtainable in our official repositories. Before leaping on Linux 5.1, please confirm if you do not want any of these lacking additional modules on your system.

(Final verification: Might 26, 2019)
The following additional modules are missing:

The next additional modules are available:

  • ACPI name (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 obtained faraway from our repositories.

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

COMMAND-NOT-FOUND error throughout replace/installation

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

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

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

The KDE Updates Can Trigger The Screenlocker To Crash

Should you update from inside a GUI session and use screenlock (e.g. it kicks in whereas the massive replace is being processed), it should crash the screenlocker.

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

Then sort in 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 could also be needed

TLP 1.2.1 obtained launched in [Stable Update] 2019-04-20 replace set, changing TLP 1.1. Subsequently, in case you have custom-made your configuration file for TLP (/and so on/default/tlp), a .pacnew file can 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 shall be stored as it is and you will have to merge related part the brand new configuration file manually with a textual content editor. Steerage can’t actually be more precise since every individual has its own configuration.

You might use a device reminiscent of Meld (package deal: meld) with a purpose to examine your previous configuration file with the .pacnew file and see the variations more simply.

In case you haven’t modified your configuration file for TLP, normally, you’ll routinely go on the new configuration file for TLP offered in the package deal with none guide intervention wanted.

Should you use the present version of TLPUI (tlpui r109.703bade-1), it might complain with the following error with some settings: “expected item missing in config file.” It’s most probably as a result of some new parameters launched with TLP 1.2.1 will not be in /and so forth/default/tlp. To eliminate these messages, you will want to do some merges between your previous configuration information and the .pacnew information and manually add all these new settings, even if you end up using the default value for these settings.

TLPUI can’t be launched

There was a bug in a previous model of TLPUI (confirmed on tlpui r89.d6363f0-1) that modified the permissions of /and so on/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 as a result of it doesn’t have the fitting permissions for /and so on/default/tlp. TLPUI have to be allowed to read that file so as to launch.

First, confirm if the permissions of /and so on/default/tlp are set appropriately. Chances are you’ll verify that with ls -l /and so on/default/tlp in a terminal. Right here’s an instance of how the output will appear to be:

$ ls -l /and so forth/default/tlp
-rw-r–r– 1 root root 14238 Apr 11 15:26 /and so forth/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. Chances are you’ll achieve this within the terminal with sudo chmod 644 /and so on/default/tlp.

As soon as it is finished, TLPUI ought to work correctly.

“Spring cleanup” on Arch Linux: influence on Manjaro

Lately, Arch Linux did a “spring cleanup” of their Group repository (see the complete dialogue on the mailing listing and seach for “spring”). Many package deal obtained 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 received removed from our repositories too. Here’s a non-exhaustive record of packages that received removed:

  • cherrytree – Hierarchical notice taking software that includes rich textual content and syntax highlighting

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

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

  • medit – GTK+ textual content editor

  • thermald – The Linux Thermal Daemon program from

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

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

You might try to do a package deal request in this category, but word that there’s a excessive probability that your demand can be refused.