This can be a wiki submit; please edit as crucial.
Please, contemplate subscribing to the Testing Updates Bulletins RSS feed
At present a number of customers report totally different issues for Octopi. So should you encounter some of them, you might change to pamac for now: sudo pacman -Sy pamac
As famous for testing update 2019-05-29, it can be completely fastened
by removing and re-adding the pool’s cachefile :
Gadgets from earlier update sets
- 1 Gnome 3.32: Two extensions faraway from our repos.
- 2 Gnome Three.32: Numerous problems
- 3 Yaourt: Rest in peace
- 4 vlc-nightly has been dropped
- 5 Kodi 18.1: extensions might not work correctly.
- 6 Notifications wanting bizarre 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 put in writing 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 Something utilizing Perl/Python/glibc broke
- 15 I’ve lost a Thunderbird addon/function
- 16 Firefox – WebGL not working anymore
- 17 libutf8proc>=2.1.1-3 update might require guide intervention
- 18 Pamac: “Invalid or corrupted package.”
Gnome 3.32: Two extensions faraway from our repos.
We now have 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 aren’t in lively improvement anymore and should not work properly (or not work at all) on Gnome 3.32. Notably, it has been reported that utilizing Topicons Plus on Gnome 3.32 might results in very excessive CPU usage.
We strongly advocate you to disable those extensions if they’re enabled (Tweaks > Extensions) and take away these packages together with your favorite package deal manager. To stop potential issues with the subsequent model of Gnome, you could do those steps (or no less than the primary one) earlier than upgrading your system.
Gnome Three.32: Numerous problems
There’s at present several problems with Gnome 3.32. Here’s what we know to date.
1. Risk of broken extensions
Damaged extensions is one thing to anticipate when transitioning between main versions of Gnome, especially in case you are using extensions that are not shipped by default on Manjaro Gnome. When you have a broken extension taken from some place else than Manjaro official repositories, you’ll have to contact the maintainer on the supply you could 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 identical individual/group).
It is attainable 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 example, we now have 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 (particularly if operating Gnome extensions that doesn’t 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. Utilizing world clocks can break Gnome Shell utterly
When 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.
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 situation. As a workaround, you could 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 faraway from our repositories utterly. We gained’t keep the yaourt package deal anymore, which signifies that you will not obtain any updates from us for this package deal. A really previous package deal named yaourt-gui-manjaro has been removed 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 out of your system.
Along with that, we’ve dropped help for several packages that trusted yaourt: allservers, pacli and pacli-jwm. These packages has been faraway 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 yet, has been dropped on our aspect and is not within the official repositories anymore. Should you still have this package deal and also you want the newest secure version of VLC media participant, remove vlc-nightly, then install the vlc package deal.
Otherwise, you’ll be able to proceed to make use of vlc-nightly from the AUR (however you’ll should compile it yourself).
Kodi 18.1: extensions might not work correctly.
Kodi 18.1 is now out there in our repositories. Since this can be a major version change, extensions for Kodi (for those who use some) might stop working correctly. Builders of those extensions will need to make them suitable with Kodi 18.
If Kodi 18.1 doesn’t work correctly for you and also you absolutely want to make use of your extensions, you might use the previous kodi package deal in /var/cache/pacman/pkg with a purpose 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 stop working correctly sooner or later too. You should not hold the downgrade ceaselessly.
Notifications wanting bizarre in XFCE
Because the package deal dunst consists of now dunstfy in the primary package deal notifications might not displayed correctly in XFCE. Please uninstall that package deal to unravel that problem. Usually not wanted in that version.
Plasma won’t reboot from the Software Launcher
For those who update 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 discovered: Use the dbus-x11 package deal as an alternative of the common dbus package deal. This package deal is accessible within the official repositories and offers dbus compiled without the –without-x choice.
To exchange dbus with dbus-x11 package deal, merely set up dbus-x11 together with your favourite package deal supervisor: dbus can be changed by dbus-x11.
Pamac: “Failed to commit transaction – Transaction not prepared” on the end
Up to now, it has solely been a false alarm: updates are applied efficiently.
Until you’ve already executed this previously, All customers of AMD-APUs/CPUs should set up this replace like this:
sudo pacman -Syyu
sudo pacman -S amd-ucode
sudo pacman -R intel-ucode
Step 3 is optionally available.
Rebuilding fontconfig cache: failed to put in writing cache
Please ignore this message. Upstream already works on an answer. More concerning the challenge 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 reasonably longterm concern. If it doesn’t be just right for you, you could 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 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 probably needs to be rebuilt.
- If it’s a repo package deal, please report and verify again frequently 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, however 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 might attempt the next answer:
Open about:config and set security.sandbox.content material.read_path_whitelist to /sys/.
libutf8proc>=2.1.1-3 update might require guide intervention
This could normally be mechanically fastened by way of manjaro-system update.
The libutf8proc package deal previous to version 2.1.1-3 had an incorrect soname hyperlink. This has been fastened in 2.1.1-3, so the improve might want to overwrite the untracked soname link created by ldconfig. Should 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 carry out the improve.
Pamac: “Invalid or corrupted package.”
For those who obtain 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 upgrade…
Loading packages information…
Checking file conflicts…
Checking out there disk area…
Upgrading manjaro-system (20180702-1 -> 20180716-1)…
==> Fix libutf8proc upgrade …
in search of conflicting packages…
Packages (1) libutf8proc-2.1.1-4
Complete Download Measurement: 0.05 MiB
Complete Installed Measurement: zero.32 MiB
Internet Upgrade 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 missing /var/lib/pacman/db.lck
Beginning full system improve…
Error: couldn’t open file /var/lib/pacman/native/libutf8proc-2.1.1-2/information: No such file or listing
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 following steps: shut Pamac window first, then launch it again and begin the update procedure once more. It should continue from the place it left off.
Issues with folder view widget in KDE v5.13
KDE introduced a new setting for icon sizes. Now you’re capable of outline additionally the dimensions in your panel. When you’ve got a high-DPI show, you might need to improve the value. This can fix the display problem with given widget.
With this update we’ve got a /and so on/pulse/default.pa.pacnew. It might be essential to merge (some strains associated to “GSettings” in /and so on/pulse/default.pa ) if ‘default.pa’ has been customised.
File battle engrampa.faucet
thunar-archive-plugin: /usr/lib/xfce4/thunar-archive-plugin/engrampa.tap 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 needed. Take away engrampa-thunar-plugin to proceed with the update.