This can be a wiki publish; please edit as vital.
Please, think about subscribing to the Testing Updates Announcements RSS feed
Gadgets from previous update units
- 1 Gnome Three.32: Two extensions removed from our repos.
- 2 Gnome Three.32: Numerous issues
- 3 Yaourt: Rest in peace
- 4 vlc-nightly has been dropped
- 5 Kodi 18.1: extensions might not work correctly.
- 6 Notifications wanting weird in XFCE
- 7 Plasma won’t reboot from the Software Launcher
- 8 I can’t open Nemo with elevated privileges (as root)
- 9 Pamac: “Failed to commit transaction – Transaction not prepared” on the end
- 10 AMD-Ucode introduction
- 11 Rebuilding fontconfig cache: failed to write down cache
- 12 LibreOffice has no window decoration in KDE
- 13 Putting in glibc (2.28-Four) breaks the dependency “glibc=2.27” required by lib32-glibc
- 14 One thing utilizing Perl/Python/glibc broke
- 15 I’ve lost a Thunderbird addon/function
- 16 Firefox – WebGL not working anymore
- 17 libutf8proc>=2.1.1-Three replace might require guide intervention
- 18 Pamac: “Invalid or corrupted package.”
Gnome Three.32: Two extensions removed from our repos.
We’ve got 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.
These extensions usually are not in lively improvement anymore and should not work properly (or not work at all) on Gnome Three.32. Notably, it has been reported that using Topicons Plus on Gnome Three.32 might leads to very high CPU utilization.
We strongly advocate you to disable these extensions if they’re enabled (Tweaks > Extensions) and take away these packages together with your favourite package deal supervisor. To stop potential issues with the subsequent model of Gnome, you could do these steps (or at the very least the first one) before upgrading your system.
Gnome Three.32: Numerous issues
There’s at present several problems with Gnome Three.32. Here’s what we know up to now.
1. Risk of damaged extensions
Broken extensions is one thing to anticipate when transitioning between main variations of Gnome, particularly in case you are using extensions that are not shipped by default on Manjaro Gnome. In case you have a broken extension taken from some place else than Manjaro official repositories, you will have to contact the maintainer on the source you will have taken the extension from to get more help. You might also need to report the problem to the developer(s) of the extension (if not the same individual/group).
It’s potential that extensions grow to be 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 example, we’ve got a report of such challenge with a third-party extension (that doesn’t come from Manjaro’s official repositories) referred to as Extensions.
To decrease the danger of breakage (particularly if operating Gnome extensions that doesn’t come from Manjaro official repositories) and make the improve smoother, you possibly can disable all Gnome extensions (Tweaks > Extensions) before upgrading your system, then enable them one by one only 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’ll need 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 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 difficulty. 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.
Yaourt: Rest 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 really previous package deal named yaourt-gui-manjaro has been eliminated at the similar time too.
In case you are still utilizing 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 out of your system.
Along with that, we now have dropped help for several packages that trusted yaourt: allservers, pacli and pacli-jwm. These packages has been removed from the official repositories utterly.
vlc-nightly has been dropped
The vlc-nightly package deal, which was really helpful in a time when VLC Three was not formally out yet, has been dropped on our aspect and is not within the official repositories anymore. When you nonetheless have this package deal and you need the newest secure version of VLC media player, remove vlc-nightly, then install the vlc package deal.
Otherwise, you’ll be able to proceed to use 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 obtainable in our repositories. Since this can be a main model change, extensions for Kodi (in the event you use some) might cease working properly. Developers of these extensions will need to make them suitable with Kodi 18.
If Kodi 18.1 doesn’t work properly for you and you completely need to use your extensions, you might use the previous kodi package deal in /var/cache/pacman/pkg with a purpose to downgrade Kodi to model 17.6. Please observe that it’s a momentary workaround and that the software offered within the previous kodi package deal might cease working correctly sooner or later 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. Usually not needed in that edition.
Plasma won’t reboot from the Software Launcher
In case you replace from inside Plasma (e.g. from the konsole), you could have to problem 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 in the official repositories and offers dbus compiled without the –without-x choice.
To switch dbus with dbus-x11 package deal, simply install dbus-x11 together with your favorite package deal supervisor: dbus can be replaced by dbus-x11.
Pamac: “Failed to commit transaction – Transaction not prepared” on the end
Up to now, it has only been a false alarm: updates are utilized successfully.
Until you’ve already carried out this previously, All users of AMD-APUs/CPUs should install this replace like this:
sudo pacman -Syyu
sudo pacman -S amd-ucode
sudo pacman -R intel-ucode
Step Three is elective.
Rebuilding fontconfig cache: failed to write down cache
Please ignore this message. Upstream already works on an answer. More concerning the difficulty here.
LibreOffice has no window decoration in KDE
New line export SAL_USE_VCLPLUGIN=gtk3_kde5, as soon as merged into present /and so forth/profile.d/libreoffice-fresh.sh , fixes a moderately longterm difficulty. If it doesn’t be just right for you, chances are you’ll use gtk as an alternative of gtk3_kde5 as UI framework.
Putting in glibc (2.28-Four) breaks the dependency “glibc=2.27” required by lib32-glibc
Install the replace both:
- from terminal: sudo pacman -Syu or;
- with Octopi as an alternative of Pamac.
One thing utilizing Perl/Python/glibc broke
- If it’s an AUR package deal, attempt to reinstall it from AUR. It almost certainly needs to be rebuilt.
- If it’s a repo package deal, please report and examine back recurrently 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 simply won’t work with the newer Quantum-based Thunderbird.
Learn extra about Thunderbird 60 right here: Thunderbird 60
Firefox – WebGL not working anymore
Chances are you’ll attempt the next answer:
Open about:config and set safety.sandbox.content.read_path_whitelist to /sys/.
libutf8proc>=2.1.1-Three replace might require guide intervention
This should usually be mechanically fastened by way of manjaro-system replace.
The libutf8proc package deal prior to version 2.1.1-Three had an incorrect soname link. This has been fastened in 2.1.1-Three, so the improve might want to overwrite the untracked soname link created by ldconfig. For those who get an error
libutf8proc: /usr/lib/libutf8proc.so.2 exists in filesystem
when updating, use
pacman -Suy –overwrite usr/lib/libutf8proc.so.2
to carry out the upgrade.
Pamac: “Invalid or corrupted package.”
In the event you obtain an “Invalid or corrupted package.” error message with Pamac and if the small print accommodates an output just like the following:
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)…
==> Fix libutf8proc improve …
in search of conflicting packages…
Packages (1) libutf8proc-2.1.1-4
Complete Download Measurement: zero.05 MiB
Complete Put in Measurement: 0.32 MiB
Internet Improve Measurement: zero.00 MiB
:: Proceed with installation? [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: could not absolutely load metadata for package deal libutf8proc-2.1.1-2
Failed to organize transaction:
invalid or corrupted package deal
Attempt the next steps: shut Pamac window first, then launch it again and start the update procedure once more. It should proceed from the place it left off.
Points with folder view widget in KDE v5.13
KDE introduced a brand new setting for icon sizes. Now you’re capable of outline additionally the dimensions on your panel. When you have a high-DPI show, you could need to improve the worth. It will fix the show difficulty with given widget.
With this replace we’ve got a /and so forth/pulse/default.pa.pacnew. It might be necessary to merge (some strains associated to “GSettings” in /and so forth/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. Remove engrampa-thunar-plugin to proceed with the update.