[Testing Update] 2019-05-22 - Kernels, XFCE 4.14-pre1, Virtualbox, LibreOffice

Hello community,

I am happy to announce another Testing Update!

This update holds the following changes:

  • We updated most of our kernels. Remember that linux318 now really had it's last build!
  • Another set of KDE-git packages
  • Virtualbox is now at 6.0.8
  • KDE Frameworks got updated to 5.58.0
  • XFCE is now at 4.14-pre1. Checkout our new ISO!
  • Latest Mozilla apps got added: Thunderbird & Firefox (incl. dev)
  • LibreOffice is now at 6.2.4
  • Haskell and other packages got updated to their latest build

Give us the usual feedback and let us know what you think about this update.


Current supported Kernels

  • linux316 3.16.67
  • linux318 3.18.140 [EOL] (it is now really EOL!)
  • linux44 4.4.180 (no legacy nvidia-340 module!)
  • linux49 4.9.178
  • linux414 4.14.121
  • linux419 4.19.45
  • linux420 4.20.17 [EOL]
  • linux50 5.0.18
  • linux51 5.1.4 (zfs modules still don't build)
  • linux51 5.2-rc1 (few extramodules build, but not all yet!)
  • linux419-rt 4.19.37_rt19
  • linux50-rt 5.0.14_rt9

Package Updates (Wed May 22 20:35:21 CEST 2019)

  • testing community x86_64: 590 new and 583 removed package(s)
  • testing core x86_64: 30 new and 30 removed package(s)
  • testing extra x86_64: 598 new and 684 removed package(s)
  • testing multilib x86_64: 7 new and 7 removed package(s)

A list of all package changes may be found here.

  • No issue, everything went smoothly
  • Yes there was an issue. I was able to resolve it myself.(Please post your solution)
  • Yes i am currently experiencing an issue due to the update. (Please post about it)

0 voters

Check if your mirror has already synced:

7 Likes

Known issues and solutions

This is a wiki post; please edit as necessary.
Please, consider subscribing to the Testing Updates Announcements RSS feed

Small cleanup of Manjaro official repositories

Please note that the following packages got removed from our repositories.

  • chromium-chromevox
  • gimp-gtk3
  • pamac-classic
  • pamac-dev
  • pamac-dev-tray-appindicator

Items from previous update sets

Gnome 3.32: Two extensions removed from our repos.

We have dropped two packages that shipped additional extensions for Gnome: gnome-shell-extensions-topicons-plus-huttli and gnome-shell-extensions-taskbar. We won't maintain Topicons Plus and Taskbar anymore.

Those extensions are not in active development anymore and may not work properly (or not work at all) on Gnome 3.32. Notably, it has been reported that using Topicons Plus on Gnome 3.32 may leads to very high CPU usage.

We strongly recommend you to disable those extensions if they are enabled (Tweaks > Extensions) and remove those packages with your favorite package manager. To prevent potential problems with the next version of Gnome, you may do those steps (or at least the first one) before upgrading your system.

Gnome 3.32: Various problems

There is currently several problems with Gnome 3.32. Here is what we know so far.

1. Possibility of broken extensions
Broken extensions is something to expect when transitioning between major versions of Gnome, especially if you are using extensions that are not shipped by default on Manjaro Gnome. If you have a broken extension taken from somewhere else than Manjaro official repositories, you will have to contact the maintainer on the source you have taken the extension from to get more support. You may also want to report the problem to the developer(s) of the extension (if not the same person/group).

It is possible that extensions become so broken on Gnome 3.32 that it makes Gnome Shell crash completely when trying to log in, thus making Gnome completely unusable. For example, we have a report of such issue with a third-party extension (that doesn't come from Manjaro's official repositories) called Extensions.

To decrease the risk of breakage (especially if running Gnome extensions that does not come from Manjaro official repositories) and make the upgrade smoother, you can disable all Gnome extensions (Tweaks > Extensions) before upgrading your system, then enable them one by one only after being logged in a completely new session on Gnome 3.32.

2. Using world clocks can break Gnome Shell completely
If you have configured world clocks in Gnome, it may make Gnome Shell segfaults and crashes when trying to log in for a graphical session, making Gnome unusable. If it happens, you will 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.

3. Gnome Shell may crash completely when resuming from sleep if you use Wayland
If you are using Wayland (instead of X.org), Gnome Shell may crash when resuming from sleep. Upstream is aware of this issue. As a workaround, you may use X.org instead of Wayland for now.

4. Miscellaneous
Some programs don't get focused after being launched. Reported to upstream and confirmed for distributions other than Manjaro too.


Yaourt: Rest in peace

Yaourt has been removed from our repositories completely. We won't maintain the yaourt package anymore, which means that you will not receive any updates from us for this package. A very old package named yaourt-gui-manjaro has been removed at the same time too.

If you are still using Yaourt, we strongly encourage you to switch to an alternative like Pamac CLI (package: pamac-cli), Trizen (package: trizen), Yay (package: yay) or Pacaur (package: pacaur); and uninstall Yaourt from your system.

In addition to that, we have dropped support for several packages that depended on yaourt: allservers, pacli and pacli-jwm. Those packages has been removed from the official repositories completely.


vlc-nightly has been dropped

The vlc-nightly package, which was really useful in a time when VLC 3 was not officially out yet, has been dropped on our side and is not in the official repositories anymore. If you still have this package and you want the latest stable version of VLC media player, remove vlc-nightly, then install the vlc package.

Otherwise, you can continue to use vlc-nightly from the AUR (but you'll have to compile it yourself).

Kodi 18.1: extensions may not work properly.

Kodi 18.1 is now available in our repositories. Since this is a major version change, extensions for Kodi (if you use some) may stop working properly. Developers of those extensions will need to make them compatible with Kodi 18.

If Kodi 18.1 doesn't work properly for you and you absolutely need to use your extensions, you may use the old kodi package in /var/cache/pacman/pkg in order to downgrade Kodi to version 17.6. Please note that it is a temporary workaround and that the software provided in the old kodi package may stop working properly in the future too. You should not keep the downgrade forever.

Notifications looking weird in XFCE

Since the package dunst includes now dunstfy in the main package notifications may not displayed properly in XFCE. Please uninstall that package to solve that issue. Normally not needed in that edition.

Plasma will not reboot from the Application Launcher

If you update from within Plasma (e.g. from the konsole), you may need to issue a systemctl reboot to reboot.

I can't open Nemo with elevated privileges (as root)

Workaround found: Use the dbus-x11 package instead of the regular dbus package. This package is available in the official repositories and provides dbus compiled without the --without-x option.

To replace dbus with dbus-x11 package, simply install dbus-x11 with your favorite package manager: dbus will be replaced by dbus-x11.


Pamac: "Failed to commit transaction - Transaction not prepared" at the end

So far, it has only been a false alarm: updates are applied successfully.


AMD-Ucode introduction

Unless you've already done this previously, All users of AMD-APUs/CPUs should install this update like this:

sudo pacman -Syyu
sudo pacman -S amd-ucode
sudo pacman -R intel-ucode
sudo update-grub

Step 3 is optional.


Rebuilding fontconfig cache: failed to write cache

Please ignore this message. Upstream already works on a solution. More about the issue here.


LibreOffice has no window decoration in KDE

New line export SAL_USE_VCLPLUGIN=gtk3_kde5, once merged into existing /etc/profile.d/libreoffice-fresh.sh , fixes a moderately longterm issue. If it doesn't work for you, you may use gtk instead 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 instead of Pamac.

Something using Perl/Python/glibc broke

Rebuilds needed!

  • If it's an AUR package, try to reinstall it from AUR. It most likely needs to be rebuilt.
  • If it's a repo package, please report and check back regularly for updates.

I've lost a Thunderbird addon/feature

Thunderbird 60 disables incompatible addons by default. There's an about:config switch should you want to force-enable the addon, but many addons simply will not work with the newer Quantum-based Thunderbird.

Read more about Thunderbird 60 here: Thunderbird 60


Firefox - WebGL not working anymore

You may try the following solution:

Open about:config and set security.sandbox.content.read_path_whitelist to /sys/.


libutf8proc>=2.1.1-3 update may require manual intervention

This should normally be automatically fixed via manjaro-system update.

The libutf8proc package prior to version 2.1.1-3 had an incorrect soname link. This has been fixed in 2.1.1-3, so the upgrade will need to overwrite the untracked soname link created by ldconfig. If 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."

If you receive an "Invalid or corrupted package." error message with Pamac and if the details contains an output similar to the following:

Details
Synchronizing package databases...
Starting full system upgrade...

Preparing...
Resolving dependencies...
Checking inter-conflicts...
Downloading...
Downloading manjaro-system-20180716-1-any.pkg.tar.xz...
Checking keyring...
Checking integrity...
Loading packages files...
Checking file conflicts...
Checking available disk space...
Upgrading manjaro-system (20180702-1 -> 20180716-1)...
==> Fix libutf8proc upgrade ...
resolving dependencies...
looking for conflicting packages...

Packages (1) libutf8proc-2.1.1-4

Total Download Size:   0.05 MiB
Total Installed Size:  0.32 MiB
Net Upgrade Size:      0.00 MiB

:: Proceed with installation? [Y/n] 
:: Retrieving packages...
downloading libutf8proc-2.1.1-4-x86_64.pkg.tar.xz...
checking keyring...
checking package integrity...
loading package files...
checking for file conflicts...
checking available disk space...
:: Processing package changes...
upgrading libutf8proc...
:: Running post-transaction hooks...
(1/1) Arming ConditionNeedsUpdate...
Running post-transaction hooks...
Arming ConditionNeedsUpdate...
Warning: lock file missing /var/lib/pacman/db.lck
Starting full system upgrade...
Resolving dependencies...
Checking inter-conflicts...
Error: could not open file /var/lib/pacman/local/libutf8proc-2.1.1-2/files: No such file or directory
Warning: could not fully load metadata for package libutf8proc-2.1.1-2

Failed to prepare transaction:
invalid or corrupted package

Try the following steps: close Pamac window first, then launch it again and start the update procedure again. It should continue from where it left off.


Issues with folder view widget in KDE v5.13

KDE introduced a new setting for icon sizes. Now you're able to define also the size for your panel. If you have a high-DPI display, you may want to increase the value. This will fix the display issue with given widget.

icon-kde-513

Pulseaudio changes

With this update we have a /etc/pulse/default.pa.pacnew. It may be necessary to merge (some lines related to “GSettings” in /etc/pulse/default.pa ) if 'default.pa' has been customised.

File conflict engrampa.tap

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 support for the Engrampa archive manager. engrampa-thunar-plugin is no longer needed. Remove engrampa-thunar-plugin to continue with the update.

Seamless upgrade via tty.
Kernel 5.0.x, KDE, btrfs, luks, nVidia 418.74, Virtualbox

A little time before this update I had changed to unstable repo and everything went well. Now I received kernel updates and yes all is working. Hope so.
Thanks Manjaro team! :+1:

Is there people courageous enough to go on Linux 5.1.4 and see if the new patch doesn't introduce regressions in itself, especially people who have LVM on SSD?

It would be really important to see if this kernel is working properly, especially with the new patch.

Is Windows 7 VM boot issue with VirtualBox already fixed on 6.0.8?

Xfce ( Gtk+) + Kernel 5.1.4 + Steam(OpenGL) + Virtualbox(ok ) +video(youtube 1080p x 60fps ok )
only xfce& xorg cpu upper since 15/05

microcode: microcode updated early to revision 0xcc, date = 2019-04-01
microcode: sig=0x506e3, pf=0x2, revision=0xcc
microcode: Microcode Update Driver: v2.2.
MDS: Mitigation: Clear CPU buffers
MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.
Linux version 5.1.4-1-MANJARO (builduser@development) (gcc version 8.3.0 (GCC)) #1 SMP PREEMPT Wed May 22 17:56:21 UTC 2019
found SMP MP-table at [mem 0x000fcc90-0x000fcc9f]
Using ACPI (MADT) for SMP configuration information
smpboot: Allowing 8 CPUs, 0 hotplug CPUs
Freeing SMP alternatives memory: 32K
smpboot: CPU0: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz (family: 0x6, model: 0x5e, stepping: 0x3)
smp: Bringing up secondary CPUs ...
x86: Booting SMP configuration:
 smp: Brought up 1 node, 8 CPUs
smpboot: Max logical packages: 1
 smpboot: Total of 8 processors activated (64153.00 BogoMIPS)

--> nosmt will lead to 32 000 BogoMips 50% loss

i cant activate result without HT ( mitigations=full,nosmt )

No problems updating two KDE Testing laptops, but isn't KDE-git for KDE-Dev Unstable?

Is it normal way that dmsg needs root privilege anymore ?

$ dmesg
dmesg: échec de lecture du tampon de noyau: Opération non permise

That means core buffer reading failure: Operation not allowed

$ inxi -b
System:
Host: steph-tour Kernel: 5.0.18-1-MANJARO x86_64 bits: 64
Desktop: Xfce 4.13.4git-2a9104 Distro: Manjaro Linux
Machine:
Type: Desktop Mobo: Gigabyte model: GA-A55M-S2HP serial:
BIOS: Award v: F2 date: 07/13/2011
CPU:
Dual Core: AMD A4-3300 APU with Radeon HD Graphics type: MCP
speed: 881 MHz min/max: 800/2500 MHz
Graphics:
Device-1: NVIDIA GF119 [GeForce GT 610] driver: nvidia v: 390.116
Display: tty server: X.Org 1.20.4 driver: nvidia
resolution: 1920x1080~60Hz
OpenGL: renderer: GeForce GT 610/PCIe/SSE2 v: 4.6.0 NVIDIA 390.116
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
driver: r8168

Yes, it is now the new default: dmesg needs elevated privileges to be used. It has been the new default for more than 14 days on Testing.

On a user that is a member of the wheel group (i.e. an administrator of the system on a standard Manjaro system), you may use journalctl -k to see kernel messages without having to type your password everytime. It also works if your user is a member of adm or systemd-journal; being a member of one of these groups is enough.

Quote from man journalctl.

All users are granted access to their private per-user journals.
However, by default, only root and users who are members of a few
special groups are granted access to the system journal and the
journals of other users. Members of the groups "systemd-journal",
"adm", and "wheel" can read all journal files. Note that the two latter
groups traditionally have additional privileges specified by the
distribution. Members of the "wheel" group can often perform
administrative tasks.

2 Likes

It's normal, you can control it via kernel.dmesg_restrict=1 or 0 to turn off.

1 Like

All good for me.:grinning:
LXQT+ Kernel 5.1
Thanks!

Typo?

Easy to override this new default, if you wish.

Anything in particular you want people to check out? Or more like general errors in dmesg / journalctl?
I am running the below setup and would be happy to upgrade to 5.1 later this morning. No LVM though.
KDE, btrfs, luks, nVidia 418.74, Virtualbox

I remember I did have issues when I tried a while ago, after 5.1 became available, but can't remember what they were.

There is a patch for a major kernel bug, fstrim on 5.1 systems + luks (+ lvm?) could cause massive data loss.

There is already a thread on it.

Can the Wine-Staging package be rebuilt? Some patches have been added to since it was built (See: Wine and Gallium Nine Standalone)

Updating without issues from Terminal, KDE and Kernel 5.1

Oops? Looking out for a massive data loss...we'll, that doesn't sound encouraging :slight_smile:
I feel I am in good shape with my snapshots/backups so could handle a breakdown fairly quickly but maybe I better wait for this patch to find it's way to Manjaro.

However, if I can help the team with my testing I will switch over.

This package is taken from Arch. If the problem can be replicated on an Arch system then ask there to rebuild.