This can be a wiki submit; please edit as vital.
Please, think about subscribing to the Stable Updates Announcements RSS feed
Might 21st, 2019: A essential bug has been found in Linux 5.1. It’s associated to TRIM commands issued on SSDs. Official announcement here.
It is unclear who is affected precisely, as info given on sources doesn’t match properly. Nevertheless, when you use an SSD, you’re not sure in case you are affected or not and you don’t want to take any probability, we strongly advocate you to modify to another kernel similar to Linux 5.zero or Linux 4.19 instantly for now.
If you do not use Linux 5.1 and planned to do leap on it, in fact, we advocate not to use Linux 5.1 for now.
Might 22, 2018: We added a patch with a purpose to remedy this difficulty in our linux51 5.1.4-1 package deal. For now, it is just in Testing and Unstable.
Might 26, 2019: linux51 5.1.Four-1 is now on Stable, launched in an replace set revealed at this time. See announcement right here. Please replace your system.
Update manjaro-keyring first. For more choices read this thread:
As stated in the announcement, while the most recent Linux version has been released on this update set, not every additional modules are at present obtainable in our official repositories. Before leaping on Linux 5.1, please verify if you do not want any of these lacking additional modules on your system.
Gadgets from previous replace sets
- 1 COMMAND-NOT-FOUND error throughout replace/set up
- 2 Kaffeine: Digital television doesn’t work anymore
- 3 The KDE Updates Can Cause The Screenlocker To Crash
- 4 XPlayer removing
- 5 TLP 1.2.1, .pacnew file: Merges could also be needed
- 6 TLPUI can’t be launched
- 7 MComix 1.2.1: Can’t launch after the upgrade
- 8 “Spring cleanup” on Arch Linux: influence on Manjaro
- 9 Gnome Three.32: Two extensions removed from our repos.
- 10 Gnome 3.32: Numerous problems
- 11 My icon theme isn’t utilized anymore for packages like Gnome Terminal, System Monitor, Gnome Screenshot, Gnome Disks, File Roller, and so forth.
- 12 Yaourt: Relaxation in peace
- 13 “Replace pamac with extra/pamac-gtk? [Y/n]”
- 14 vlc-nightly has been dropped
- 15 “NOTE, 4.20.17 was the last maintenance release by Greg Kroah-Hartman.; It is recommend to move on to linux50-series.” What should I do?
- 16 ” Substitute xorg-mkfontdir with additional/xorg-mkfontscale? [Y/n]”
- 17 Linux kernel 5.zero.X obtainable. Early problems reported.
- 18 Kodi 18.1: extensions might not work correctly.
- 19 ProjectM: projectm-pulseaudio v.s. projectm-qt, file conflict with /usr/share/pixmaps/prjm16-transparent.svg
COMMAND-NOT-FOUND error throughout replace/set up
Throughout improve/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) installing 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 issue.
Kaffeine: Digital television doesn’t work anymore
Unfortunately, this functionality of Kaffeine is at present broken with v4l-utils 1.16.5-1.
It has already been reported to the Arch Linux bugtracker, see this: https://bugs.archlinux.org/task/62402
Based on this ticket, Manjaro and Arch Linux will not be the only distros affected by an analogous difficulty.
As a short lived workaround, chances are you’ll attempt to downgrade the v4l-utils package deal from 1.16.5-1 to 1.16.Three-1. You might achieve this graphically with Pamac (with Set up Local Package deal on /var/cache/pacman/pkg/v4l-utils-1.16.Three-1-x86_64.pkg.tar.xz) utilizing or with the command-line interface with pamac install /var/cache/pacman/pkg/v4l-utils-1.16.Three-1-x86_64.pkg.tar.xz, sudo pacman -U /var/cache/pacman/pkg/v4l-utils-1.16.Three-1-x86_64.pkg.tar.xz or any equal.
Please word that this is merely a short lived workaround and never a definitive answer. Don’t maintain this package deal downgraded perpetually as holding downgraded packages for too lengthy might turn out to be a problem in itself.
The KDE Updates Can Cause The Screenlocker To Crash
In the event you replace from within a GUI session and use screenlock (e.g. it kicks in while the massive replace is being processed), it’s going to crash the screenlocker.
To revive 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.
Because XPlayer doesn’t work anymore alongside GStreamer 1.16.0, the next packages obtained faraway from official repositories: xplayer and xplayer-plparser. Upstream is aware of the difficulty, but we have no idea when it is going to be fastened. These packages might come again ultimately.
We advise using options reminiscent of VLC media player (package deal: vlc).
TLP 1.2.1, .pacnew file: Merges could also be needed
TLP 1.2.1 received released 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 might be created when the tlp package deal might be upgraded. This .pacnew file is the new default configuration file offered by the package deal. Your previous configuration file gained’t be edited or replaced routinely; by default, your previous configuration file will probably be stored as it is and you’ll have to merge relevant half the new configuration file manually with a textual content editor. Steerage can’t really be more precise since each individual has its personal configuration.
You might use a device resembling Meld (package deal: meld) to be able 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, usually, you will routinely go on the new configuration file for TLP offered within the package deal with none guide intervention needed.
Should you use the present version of TLPUI (tlpui r109.703bade-1), it might complain with the next error with some settings: “expected item missing in config file.” It’s almost definitely because some new parameters introduced with TLP 1.2.1 aren’t in /and so forth/default/tlp. To eliminate those messages, you will want 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 worth for these settings.
TLPUI can’t 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’s more than likely that TLPUI doesn’t launch as a result of it doesn’t have the correct permissions for /and so forth/default/tlp. TLPUI have to be allowed to learn that file in an effort to launch.
First, verify if the permissions of /and so on/default/tlp are set appropriately. You might verify that with ls -l /and so forth/default/tlp in a terminal. Here’s an instance 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
When you’ve got -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.
Once it’s accomplished, TLPUI ought to work correctly.
MComix 1.2.1: Can’t launch after the upgrade
This can be a recognized challenge that is because of breaking modifications introduced in python2-pillow 6.0.0 (see this doc). It is a package deal imported from Arch Linux and the difficulty has already been reported on Arch Linux aspect. See this ticket on the bug tracker: https://bugs.archlinux.org/task/62242
A true repair requires to do modifications in the source code of MComix.
Since python2-pillow (and python-pillow) is used by many packages, comparable problems might occur with different software program too.
“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 record and seach for “spring”). Many package deal acquired removed 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 obtained faraway from our repositories too. Right here’s a non-exhaustive listing of packages that received removed:
cherrytree – Hierarchical observe taking software featuring rich text and syntax highlighting
docky – Full fledged dock software that makes opening widespread purposes and managing home windows simpler and quicker
mate-menu – Advanced 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 01.org
wine-staging-nine has been removed / changed with wine-nine. In case it’s put in, it ought to be eliminated manually. http://archlinux.2023198.n4.nabble.com/Removing-wine-staging-nine-replaced-with-wine-nine-td4722447.html
If you wish to continue to make use of these packages, you’ll have to use the AUR any further.
Chances are you’ll attempt to do a package deal request on this class, but word that there is a excessive probability that your demand shall be refused.
Gnome Three.32: Two extensions removed from our repos.
We’ve dropped two packages that shipped further extensions for Gnome: gnome-shell-extension-topicons-plus-huttli and gnome-shell-extension-taskbar. We gained’t keep Topicons Plus and Taskbar anymore.
These extensions aren’t in lively improvement anymore and should not work properly (or not work in any respect) on Gnome 3.32. Notably, it has been reported that using Topicons Plus on Gnome 3.32 might results in very high CPU usage.
We strongly advocate you to disable those extensions if they are enabled (Tweaks > Extensions) and take away those packages together with your favorite package deal manager. To stop potential problems with the subsequent version of Gnome, you might do these steps (or at the very least the primary one) earlier than upgrading your system.
Gnome 3.32: Numerous problems
There’s presently a number of issues with Gnome Three.32. Here’s what we all know thus far.
1. Risk of broken extensions
Damaged extensions is something to anticipate when transitioning between main versions of Gnome, especially in case you are utilizing extensions that aren’t shipped by default on Manjaro Gnome. In case you have a broken extension taken from some other place than Manjaro official repositories, you will have to contact the maintainer on the source you’ve taken the extension from to get extra help. You might also need to report the issue to the developer(s) of the extension (if not the same individual/group).
It is potential that extensions develop into so broken on Gnome Three.32 that it makes Gnome Shell crash utterly when making an attempt to log in, thus making Gnome utterly unusable. For instance, we have now a report of such problem with a third-party extension (that doesn’t come from Manjaro’s official repositories) referred to as Extensions.
To lower the danger of breakage (particularly if operating Gnome extensions that does not come from Manjaro official repositories) and make the upgrade smoother, you’ll be able to disable all Gnome extensions (Tweaks > Extensions) before upgrading your system, then allow them one by one solely after being logged in a totally new session on Gnome 3.32.
2. Utilizing world clocks can break Gnome Shell utterly
In case you have configured world clocks in Gnome, it might make Gnome Shell segfaults and crashes when making an attempt to log in for a graphical session, making Gnome unusable. If it happens, you will have to reset your parameters for world clocks with the next command (do it in TTY): dbus-launch gsettings reset org.gnome.clocks world-clocks.
See this Arch Linux thread and this ticket from upstream.
3. Gnome Shell might crash utterly when resuming from sleep in the event you use Wayland
In case you are using Wayland (as an alternative of X.org), Gnome Shell might crash when resuming from sleep. Upstream is conscious of this concern. As a workaround, you might use X.org as an alternative of Wayland for now.
Some packages don’t get targeted after being launched. Reported to upstream and confirmed for distributions aside from Manjaro too. (Ought to be fastened by now.)
My icon theme isn’t utilized anymore for packages like Gnome Terminal, System Monitor, Gnome Screenshot, Gnome Disks, File Roller, and so forth.
With version 3.32 of those packages, upstream changed the icon used for many packages part of the Gnome Purposes. As an alternative of utilizing a generic icon shared by many packages, they selected to ship a brand new icon and use it. Subsequently, launchers situated in /usr/share/purposes (.desktop information) for these packages has been modified to use the brand new icon as an alternative of the generic one. Here’s an instance with Gnome Terminal.
Since your icon theme most certainly doesn’t have an icon named org.gnome.X, it falls again to the hicolor theme as an alternative. For this reason the icon modified after the system improve and “your theme is not applied anymore for those programs.”
There’s nothing you possibly can actually do for now, besides dwelling with it for some time. Icon theme designers should adapt their theme to the modifications made by Gnome developers.
Yaourt: Relaxation in peace
Yaourt has been faraway from our repositories utterly. We gained’t keep the yaourt package deal anymore, which signifies that you will not receive any updates from us for this package deal. A very previous package deal named yaourt-gui-manjaro has been eliminated on the similar time too.
In case you are still using Yaourt, we strongly encourage you to modify to an alternate like Pamac CLI (package deal: pamac-cli), Trizen (package deal: trizen), Yay (package deal: yay) or Pacaur (package deal: pacaur); and uninstall Yaourt from your system.
In addition to that, we’ve dropped help for several packages that trusted yaourt: allservers, pacli and pacli-jwm. These packages has been removed from the official repositories utterly.
“Replace pamac with extra/pamac-gtk? [Y/n]”
Settle for the alternative. The unique pamac package deal is now cut up into three packages: pamac-gtk, pamac-cli and pamac-common.
vlc-nightly has been dropped
The vlc-nightly package deal, which was actually useful in a time when VLC Three was not officially out but, has been dropped on our aspect and isn’t in the official repositories anymore. When you nonetheless have this package deal and you need the newest secure model of VLC media participant, simply set up the vlc package deal (the vlc-nightly package deal must be removed at the similar time, in the same transaction).
Otherwise, you’ll be able to proceed to use vlc-nightly from the AUR (but you’ll need to compile it your self).
“NOTE, 4.20.17 was the last maintenance release by Greg Kroah-Hartman.; It is recommend to move on to linux50-series.” What should I do?
Linux Four.20 (which is not an LTS kernel) is now marked as End Of Life (EOL), so if you want to proceed to make use of an non-LTS kernel, you must consider using Linux 5.zero, and in addition uninstall kernel 4.20 soon.
Preserving EOL kernel put in in your system for too lengthy can lead as much as problems for future upgrades (especially if using NVIDIA drivers). When using non-LTS kernel, you have to do maintenance/cleanup extra typically.
” Substitute xorg-mkfontdir with additional/xorg-mkfontscale? [Y/n]”
Accept the alternative.
Linux kernel 5.zero.X obtainable. Early problems reported.
The most recent kernel collection is now out there for everyone. Please notice that some issues has been reported with model 5.0.1 similar to having an extended delay at shutdown and dropping sound output when using droop. It’s still obtainable for the early adopters. You’re free to install and use it or not.
As reported by some users, should you use WireGuard, you could have to manually run sudo dkms autoinstall in a terminal to get the kernel module working correctly with Linux 5.zero.1.
Extra information about dkms autoinstall (and DKMS usually) here.
Kodi 18.1: extensions might not work correctly.
Kodi 18.1 is now out there in our repositories. Since this can be a major model change, extensions for Kodi (for those who use some) might cease working correctly. Developers of those extensions might want to make them suitable with Kodi 18.
If Kodi 18.1 doesn’t work correctly for you and also you absolutely need to make use of your extensions, you might use the previous kodi package deal in /var/cache/pacman/pkg to be able to downgrade Kodi to model 17.6. Please notice that it is a short-term workaround and that the software offered in the previous kodi package deal might stop working properly in the future too. You shouldn’t hold the downgrade ceaselessly.
Starting with model 3.1.0 of ProjectM, there at the moment are solely three packages as an alternative of six and the QT half has been merged to the projectm-pulseaudio package deal.
Take away the projectm-qt package deal before upgrading your system.