This can be a wiki publish; please edit as mandatory.
Please, think about subscribing to the Testing Updates Announcements RSS feed
EDIT: Shouldn’t be needed anymore with bubblewrap zero.3.3-2.1.
As stated in the error message, attempt to enable the function asked by setting the unprivileged_userns_clone kernel parameter to 1 (which means “yes” in that context) with the next command:
It’ll create a configuration file in /and so on/sysctl.d/userns.conf that may set this kernel parameter to 1 routinely at boot.
The replace to mariadb 10.4.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 listing /and so on/mysql/my.cnf.d/ ) to /and so forth/my.cnf (and /and so on/my.cnf.d/ ). Make certain to move your configuration.
Instantiated providers (like [email protected] ) are not configured in separate information (like /and so on/mysql/myfoo.cnf ). As an alternative transfer your configuration to configuration blocks with group suffix in essential configuration file, one for each service. A block should look something like this:
Like each mariadb function replace this requires the info directory to be updated. With the new configuration in place run:
In case you are using the Matcha theme in kvantum you might expertise a theme reset. Simply install kvantum-theme-matcha if not happend yet and select the new offered variants. Manjaro 18.1 releases will ship with the brand new themes by default.
At present several users report totally different issues for Octopi. So in case you encounter a few of them, you might change to pamac for now: sudo pacman -Sy pamac
Gadgets from earlier replace sets
- 1 Small cleanup of Manjaro official repositories
- 2 ZFS 0.8 fails to import ZFS pool during boot
- 3 Gnome Three.32: Two extensions removed from our repos.
- 4 Gnome Three.32: Numerous problems
- 5 Yaourt: Relaxation in peace
- 6 vlc-nightly has been dropped
- 7 Kodi 18.1: extensions might not work correctly.
- 8 Notifications wanting weird in XFCE
- 9 Plasma won’t reboot from the Software Launcher
- 10 I can’t open Nemo with elevated privileges (as root)
- 11 Pamac: “Failed to commit transaction – Transaction not prepared” on the end
- 12 AMD-Ucode introduction
- 13 Rebuilding fontconfig cache: failed to write down cache
- 14 LibreOffice has no window decoration in KDE
- 15 Installing glibc (2.28-4) breaks the dependency “glibc=2.27” required by lib32-glibc
- 16 Something utilizing Perl/Python/glibc broke
- 17 I’ve lost a Thunderbird addon/function
- 18 Firefox – WebGL not working anymore
- 19 libutf8proc>=2.1.1-3 update might require guide intervention
- 20 Pamac: “Invalid or corrupted package.”
Small cleanup of Manjaro official repositories
Please word that the next packages obtained faraway from our repositories.
ZFS 0.8 fails to import ZFS pool during boot
As noted for testing update 2019-05-29, it can be completely fastened
by removing and re-adding the pool’s cachefile :
zpool set cachefile=none
zpool set cachefile=/and so forth/zfs/zpool.cache
More details in [Testing Update] 2019-05-29 – Kernels, XFCE, Deepin, Mesa, Nvidia, KDE-Dev (seek for ‘ZFS’ there)
Gnome Three.32: Two extensions removed from our repos.
We have now dropped two packages that shipped further extensions for Gnome: gnome-shell-extensions-topicons-plus-huttli and gnome-shell-extensions-taskbar. We gained’t keep Topicons Plus and Taskbar anymore.
Those extensions usually are not in lively improvement anymore and should not work correctly (or not work in any respect) on Gnome Three.32. Notably, it has been reported that utilizing Topicons Plus on Gnome Three.32 might leads to very excessive CPU usage.
We strongly advocate you to disable these extensions if they are enabled (Tweaks > Extensions) and take away those packages together with your favorite package deal supervisor. To stop potential problems with the subsequent version of Gnome, you could do these steps (or no less than the first one) before upgrading your system.
Gnome Three.32: Numerous problems
There’s at present a number of problems with Gnome 3.32. Here is what we all know to date.
1. Risk of damaged extensions
Broken extensions is something to anticipate when transitioning between main variations of Gnome, particularly in case you are using extensions that aren’t shipped by default on Manjaro Gnome. When you’ve got a damaged extension taken from elsewhere than Manjaro official repositories, you will have to contact the maintainer on the supply you’ve got taken the extension from to get extra help. You might also need to report the problem to the developer(s) of the extension (if not the identical individual/group).
It’s potential that extensions turn into so damaged 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 challenge with a third-party extension (that doesn’t come from Manjaro’s official repositories) referred to as Extensions.
To lower the danger of breakage (especially 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 enable them one after the other solely after being logged in a totally new session on Gnome Three.32.
2. Using 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 occurs, you will want to reset your parameters for world clocks with the following command (do it in TTY): dbus-launch gsettings reset org.gnome.clocks world-clocks.
See this Arch Linux thread and this ticket from upstream.
Three. Gnome Shell might crash utterly when resuming from sleep when you use Wayland
In case you are utilizing Wayland (as an alternative of X.org), Gnome Shell might crash when resuming from sleep. Upstream is conscious of this challenge. As a workaround, chances are you’ll 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.
Yaourt: Relaxation in peace
Yaourt has been removed from our repositories utterly. We gained’t keep the yaourt package deal anymore, which signifies that you’ll not obtain any updates from us for this package deal. A very previous package deal named yaourt-gui-manjaro has been eliminated at 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.
Along with that, we have now dropped help for several packages that trusted yaourt: allservers, pacli and pacli-jwm. Those packages has been removed from the official repositories utterly.
vlc-nightly has been dropped
The vlc-nightly package deal, which was actually useful in a time when VLC 3 was not officially out but, has been dropped on our aspect and isn’t within the official repositories anymore. In the event you still have this package deal and also you want the newest secure model of VLC media player, remove vlc-nightly, then install the vlc package deal.
In any other case, you possibly can continue to make use of vlc-nightly from the AUR (however you’ll should compile it your self).
Kodi 18.1: extensions might not work correctly.
Kodi 18.1 is now out there in our repositories. Since this can be a main version change, extensions for Kodi (for those who use some) might stop working properly. Developers of those extensions will need to make them suitable with Kodi 18.
If Kodi 18.1 doesn’t work properly for you and also you completely need to use your extensions, you could use the previous kodi package deal in /var/cache/pacman/pkg as a way to downgrade Kodi to version 17.6. Please notice that it is a momentary workaround and that the software offered within the previous kodi package deal might cease working properly in the future too. You should not hold the downgrade ceaselessly.
Notifications wanting weird in XFCE
Because the package deal dunst consists of now dunstfy in the primary package deal notifications might not displayed properly in XFCE. Please uninstall that package deal to unravel that challenge. Normally not wanted in that edition.
Plasma won’t reboot from the Software Launcher
Should you update from within Plasma (e.g. from the konsole), chances are you’ll have to difficulty a systemctl reboot to reboot.
I can’t open Nemo with elevated privileges (as root)
Workaround found: Use the dbus-x11 package deal as an alternative of the regular dbus package deal. This package deal is on the market within the official repositories and offers dbus compiled with out the –without-x choice.
To exchange dbus with dbus-x11 package deal, merely set up dbus-x11 together with your favourite package deal manager: dbus will probably be replaced by dbus-x11.
Pamac: “Failed to commit transaction – Transaction not prepared” on the end
Thus far, it has only been a false alarm: updates are utilized efficiently.
Until you’ve already carried out this beforehand, All users of AMD-APUs/CPUs ought to install this update like this:
sudo pacman -Syyu
sudo pacman -S amd-ucode
sudo pacman -R intel-ucode
Step Three is optionally available.
Rebuilding fontconfig cache: failed to write down cache
Please ignore this message. Upstream already works on a solution. Extra concerning the situation here.
LibreOffice has no window decoration in KDE
New line export SAL_USE_VCLPLUGIN=gtk3_kde5, once merged into present /and so on/profile.d/libreoffice-fresh.sh , fixes a reasonably longterm challenge. If it doesn’t be just right for you, chances are you’ll use gtk as an alternative of gtk3_kde5 as UI framework.
Installing glibc (2.28-4) breaks the dependency “glibc=2.27” required by lib32-glibc
Install the update either:
- from terminal: sudo pacman -Syu or;
- with Octopi as an alternative of Pamac.
Something utilizing Perl/Python/glibc broke
- If it’s an AUR package deal, attempt to reinstall it from AUR. It almost definitely must be rebuilt.
- If it’s a repo package deal, please report and examine again commonly for updates.
I’ve lost a Thunderbird addon/function
Thunderbird 60 disables incompatible addons by default. There’s an about:config change do you have to need to force-enable the addon, but many addons merely won’t work with the newer Quantum-based Thunderbird.
Read more about Thunderbird 60 right here: Thunderbird 60
Firefox – WebGL not working anymore
You could attempt the next answer:
Open about:config and set safety.sandbox.content.read_path_whitelist to /sys/.
libutf8proc>=2.1.1-3 update might require guide intervention
This should normally be routinely fastened by way of manjaro-system replace.
The libutf8proc package deal prior to model 2.1.1-3 had an incorrect soname hyperlink. This has been fastened in 2.1.1-Three, so the improve will need to overwrite the untracked soname hyperlink created by ldconfig. In the event you get an error
libutf8proc: /usr/lib/libutf8proc.so.2 exists in filesystem
when updating, use
pacman -Suy –overwrite usr/lib/libutf8proc.so.2
to perform the upgrade.
Pamac: “Invalid or corrupted package.”
In the event you receive an “Invalid or corrupted package.” error message with Pamac and if the small print incorporates an output just like the next:
DetailsSynchronizing package deal databases…
Beginning full system improve…
Loading packages information…
Checking file conflicts…
Checking out there disk area…
Upgrading manjaro-system (20180702-1 -> 20180716-1)…
==> Repair libutf8proc upgrade …
on the lookout for conflicting packages…
Packages (1) libutf8proc-2.1.1-Four
Complete Download Measurement: 0.05 MiB
Complete Put in Measurement: 0.32 MiB
Internet Upgrade Measurement: zero.00 MiB
:: Proceed with set up? [Y/n]
:: Retrieving packages…
checking package deal integrity…
loading package deal information…
checking for file conflicts…
checking obtainable disk area…
:: Processing package deal modifications…
:: Operating post-transaction hooks…
(1/1) Arming ConditionNeedsUpdate…
Operating post-transaction hooks…
Warning: lock file lacking /var/lib/pacman/db.lck
Beginning full system improve…
Error: couldn’t open file /var/lib/pacman/local/libutf8proc-2.1.1-2/information: No such file or directory
Warning: couldn’t absolutely load metadata for package deal libutf8proc-2.1.1-2
Failed to organize transaction:
invalid or corrupted package deal
Attempt the following steps: close Pamac window first, then launch it once more and begin the update process again. It ought to proceed from where it left off.
Points with folder view widget in KDE v5.13
KDE launched a new setting for icon sizes. Now you’re capable of define additionally the dimensions on your panel. When you’ve got a high-DPI display, you might need to improve the value. It will fix the display situation with given widget.
With this replace we now have a /and so on/pulse/default.pa.pacnew. It might be necessary to merge (some strains related to “GSettings” in /and so on/pulse/default.pa ) if ‘default.pa’ has been customised.
File conflict engrampa.tap
thunar-archive-plugin: /usr/lib/xfce4/thunar-archive-plugin/engrampa.faucet exists in filesystem (owned by engrampa-thunar-plugin)
thunar-archive-plugin has added native help for the Engrampa archive supervisor. engrampa-thunar-plugin is not wanted. Take away engrampa-thunar-plugin to continue with the replace.