This can be a wiki publish; please edit as vital.
Please, contemplate subscribing to the Stable Updates Bulletins RSS feed
You gained’t see explicitly four.14-pre1 anyplace on our xfce-gtk3 packages. We comply with the versioning used by upstream. Here’s the record of all elements which are a part of XFCE four.14-pre1.
In case you are utilizing the Matcha theme in kvantum you could expertise a theme reset. Simply install kvantum-theme-matcha if not happend yet and choose the brand new offered variants. Manjaro 18.1 releases will ship with the new themes by default.
At present a number of users report totally different issues for Octopi. So when you encounter some of them, you might change to pamac for now: sudo pacman -Syu pamac
(Observe that sudo pacman -Syu pamac will each install Pamac and upgrade all upgradable packages in your system at the similar time.)
DisplayCAL three.8.1.1 – Missing python2-dbus causes failure to launch software.
Answer – Set up the python2-dbus package deal for now. Version 3.8.2 fixes the dependency error. As and when DisplayCAL 3.8.2 reaches secure branch you’ll be able to take away python2-dbus as it doesn’t require it. Only take away python2-dbus again when you put in it specifically for DisplayCAL.
Gadgets from previous update units
- 1 Regression with Linux firmwares on machine operating Vega GPUs.
- 2 signature from “Helmut Stult (schinfo) ” is marginal trust
- 3 substitute steam-devices with group/game-devices-udev?
- 4 Linux 5.1 – Which additional modules are presently missing?
- 5 Small cleanup of Manjaro official repositories
- 6 COMMAND-NOT-FOUND error during update/installation
- 7 The KDE Updates Can Cause The Screenlocker To Crash
- 8 TLP 1.2.1, .pacnew file: Merges may be wanted
- 9 TLPUI cannot be launched
- 10 “Spring cleanup” on Arch Linux: influence on Manjaro
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 model. It is best to 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 techniques that use a AMD Vega GPUs (for instance: Vega 64, Vega 56, Vega 10) and Linux 4.19.
It is a regression that affects each Manjaro and Arch Linux. Right here’s some links.
Arch Linux bugtracker: https://bugs.archlinux.org/task/62666
Manjaro discussion board: Most recent secure department update drawback
Manjaro forum: Manjaro update prevents system booting
Manjaro forum: ‘linux-firmware 20190514.711d329-1’ replace prevents my system booting.
In case you are affected by this challenge, you’ve gotten primarily two decisions: both use a unique kernel or downgrade linux-firmware. Probably the most most popular technique is the primary one since it doesn’t involve preserving a package deal to an older version. Both approach, if your system is completely unbootable (not even with a command line interface), you will want to do a chroot to repair your system. For every answer advised under, we’ll suppose that it is advisable 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 know, it really works positive on Linux 5.1 and supposedly additionally on Linux 5.0. Comply with these steps so as to be able to set up a new kernel:
- Launch a reside session with an set up medium;
- Open a terminal;
- Chroot your system. You might achieve this mechanically with manjaro-chroot -a. On more complicated system the place manjaro-chroot might simply fail, you’ll have to do a guide chroot.;
- After you have chrooted in your system, use mhwd-kernel -i linux51 to install Linux 5.1 and all additional modules wanted in your system. You might also attempt with Linux 5.0 (exchange linux51 with linux50), though Linux 5.zero is predicted to be End of Life quickly.
(In case you have multiple kernels installed on your machine, you could need to boot with different kernels earlier than making an attempt to install a new one.)
For the second:
- Chroot to your system from a reside session;
- Downgrade the linux-firmware package deal to model 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 native cache, use pacman -U https://archive.archlinux.org/packages/l/linux-firmware/linux-firmware-20190424.4b6cf2b-1-any.pkg.tar.xz as an alternative.
(Notice 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, do not maintain the package deal to a previous model perpetually.)
signature from “Helmut Stult (schinfo)
” is marginal trust
Replace manjaro-keyring first. For extra options learn this thread:
Points with “signature is marginal trust” or “invalid or corrupted package”
substitute steam-devices with group/game-devices-udev?
Sure. 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 on this update set, not each additional modules are at present obtainable in our official repositories. Earlier than jumping on Linux 5.1, please confirm if you do not want any of these missing additional modules on your system.
(Final verification: Might 26, 2019)
The following additional modules are lacking:
The next additional modules can be found:
- ACPI call (linux51-acpi_call);
- BBSwitch (linux51-bbswitch);
- Broadcom wireless 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 removed from our repositories.
COMMAND-NOT-FOUND error during update/installation
Throughout improve/set up the package deal command-not-found tries to sync its database with a mirror that seems to be at present (or permanently ?) offline, resulting in 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 Cause The Screenlocker To Crash
In case you replace from inside a GUI session and use screenlock (e.g. it kicks in whereas the massive update is being processed), it’ll crash the screenlocker.
To revive entry, press CTRL+ALT+F2 to modify to a different 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 again to a now unlocked KDE desktop.
TLP 1.2.1, .pacnew file: Merges may be wanted
TLP 1.2.1 acquired 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 shall be created when the tlp package deal shall 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 routinely; by default, your previous configuration file might be stored as it is and you will have to merge related part the new configuration file manually with a textual content editor. Steerage can’t actually be more exact since every individual has its own configuration.
Chances are you’ll use a device corresponding to Meld (package deal: meld) with a purpose to examine your previous configuration file with the .pacnew file and see the variations more simply.
For those who haven’t modified your configuration file for TLP, normally, you’ll routinely go on the brand new configuration file for TLP offered within the package deal with none guide intervention wanted.
In the event you use the current version of TLPUI (tlpui r109.703bade-1), it might complain with the next error with some settings: “expected item missing in config file.” It is almost definitely because some new parameters introduced with TLP 1.2.1 aren’t in /and so on/default/tlp. To eliminate these 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 if you find yourself utilizing the default worth for those settings.
TLPUI cannot be launched
There was a bug in a earlier model 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 most probably that TLPUI doesn’t launch because it doesn’t have the correct permissions for /and so forth/default/tlp. TLPUI have to be allowed to read that file so as to launch.
First, verify if the permissions of /and so on/default/tlp are set appropriately. You could verify that with ls -l /and so on/default/tlp in a terminal. Right here’s an example of how the output will seem like:
$ 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 turns into readable to the group and others too. You might achieve this within the terminal with sudo chmod 644 /and so forth/default/tlp.
Once it is finished, TLPUI should 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 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 because they have been imported from Arch Linux received faraway from our repositories too. Right here’s a non-exhaustive listing of packages that obtained removed:
cherrytree – Hierarchical word 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+ text editor
thermald – The Linux Thermal Daemon program from 01.org
wine-staging-nine has been removed / changed with wine-nine. In case it is installed, it ought to be removed manually. http://archlinux.2023198.n4.nabble.com/Removing-wine-staging-nine-replaced-with-wine-nine-td4722447.html
If you wish to proceed to make use of those packages, you’ll have to use the AUR any more.
You could attempt to do a package deal request in this class, but notice that there is a high probability that your demand will probably be refused.