[Testing Update] 2018-11-22 - Kernels

update
testing

#1

Hi community,

Welcome to another testing update. So what do we have with this one?

  • We mostly updated our kernels. Also, linux418 is now marked EOL. We recommend to move over to linux419 series.

We hope with all these changes Manjaro to be more efficient for you all.


The Iconic Spitfire: Now Quad-Core!

jpg%3Alarge

Visit StationX now!


Manjaro v18.0.1 Preview2 released!

If you are curious about the latest Manjaro-Illyria 18.0.1 release, you now have the opportunity to download XFCE Edition with the latest 4.13 packages, aswell as our most recent styling efforts. Our KDE fans may try our KDE Edition with the latest KDE v5.14 instead. And our GNOME fans may try our Gnome Edition with the latest GNOME v3.30.


Current supported Kernels

  • linux316 3.16.61
  • linux318 3.18.126 [EOL]
  • linux44 4.4.164
  • linux49 4.9.138
  • linux414 4.14.82
  • linux417 4.17.19 [EOL]
  • linux418 4.18.20 [EOL]
  • linux419 4.19.3
  • linux414-rt 4.14.78_rt47
  • linux416-rt 4.16.18_rt11
  • linux418-rt 4.18.16_rt9

Sync Package Updates (Tue Nov 13 07:29:01 CET 2018)

:: Different overlay package(s) in repository core x86_64

-------------------------------------------------------------------------------
                             PACKAGE           2018-11-18           2018-11-22
-------------------------------------------------------------------------------
                            linux316            3.16.59-1            3.16.61-1
                    linux316-headers            3.16.59-1            3.16.61-1
                            linux414            4.14.81-1            4.14.82-1
                    linux414-headers            4.14.81-1            4.14.82-1
                            linux418            4.18.19-1            4.18.20-1
                    linux418-headers            4.18.19-1            4.18.20-1
                            linux419             4.19.2-1             4.19.3-1
                    linux419-headers             4.19.2-1             4.19.3-1
                             linux44            4.4.163-1            4.4.164-1
                     linux44-headers            4.4.163-1            4.4.164-1
                             linux49            4.9.137-1            4.9.138-1
                     linux49-headers            4.9.137-1            4.9.138-1


:: Different overlay package(s) in repository extra x86_64

-------------------------------------------------------------------------------
                             PACKAGE           2018-11-18           2018-11-22
-------------------------------------------------------------------------------
                  linux316-acpi_call             1.1.0-46             1.1.0-47
                   linux316-bbswitch               0.8-45               0.8-46
                linux316-broadcom-wl      6.30.223.271-25      6.30.223.271-26
                   linux316-catalyst     1:15.201.1151-34     1:15.201.1151-35
                linux316-ndiswrapper              1.61-25              1.61-26
                     linux316-nvidia           1:410.73-1           1:410.78-2
               linux316-nvidia-340xx            340.107-4            340.107-5
               linux316-nvidia-390xx             390.87-3             390.87-4
                   linux316-nvidiabl              0.88-35              0.88-36
                      linux316-r8168          8.045.08-11          8.045.08-12
                  linux316-rt3562sta        2.4.1.1_r4-25        2.4.1.1_r4-26
                        linux316-spl             0.7.11-1             0.7.11-2
                   linux316-tp_smapi              0.41-45              0.41-46
                linux316-vhba-module          20161009-25          20161009-26
   linux316-virtualbox-guest-modules             5.2.22-1             5.2.22-2
    linux316-virtualbox-host-modules             5.2.22-1             5.2.22-2
                        linux316-zfs             0.7.11-1             0.7.11-2
                  linux418-acpi_call             1.1.0-14             1.1.0-15
                   linux418-bbswitch               0.8-14               0.8-15
                linux418-broadcom-wl      6.30.223.271-14      6.30.223.271-15
                   linux418-catalyst     1:15.201.1151-14     1:15.201.1151-15
                linux418-ndiswrapper              1.61-14              1.61-15
                     linux418-nvidia           1:410.73-5           1:410.78-2
               linux418-nvidia-340xx           340.107-14           340.107-15
               linux418-nvidia-390xx            390.87-14            390.87-15
                   linux418-nvidiabl              0.88-14              0.88-15
                      linux418-r8168          8.045.08-14          8.045.08-15
                        linux418-spl             0.7.11-7             0.7.11-8
                   linux418-tp_smapi              0.41-14              0.41-15
                linux418-vhba-module          20161009-14          20161009-15
   linux418-virtualbox-guest-modules             5.2.22-3             5.2.22-4
    linux418-virtualbox-host-modules             5.2.22-3             5.2.22-4
                        linux418-zfs             0.7.11-7             0.7.11-8
                  linux419-acpi_call              1.1.0-2              1.1.0-3
                   linux419-bbswitch                0.8-2                0.8-3
                linux419-broadcom-wl       6.30.223.271-2       6.30.223.271-3
                   linux419-catalyst      1:15.201.1151-2      1:15.201.1151-3
                linux419-ndiswrapper               1.61-2               1.61-3
                     linux419-nvidia           1:410.73-2           1:410.78-2
               linux419-nvidia-340xx            340.107-2            340.107-3
               linux419-nvidia-390xx             390.87-2             390.87-3
                   linux419-nvidiabl               0.88-2               0.88-3
                      linux419-r8168           8.045.08-2           8.045.08-3
                        linux419-spl             0.7.11-2             0.7.11-3
                   linux419-tp_smapi               0.41-2               0.41-3
                linux419-vhba-module           20161009-2           20161009-3
   linux419-virtualbox-guest-modules             5.2.22-2             5.2.22-3
    linux419-virtualbox-host-modules             5.2.22-2             5.2.22-3
                        linux419-zfs             0.7.11-2             0.7.11-3
                   linux44-acpi_call            1.1.0-115            1.1.0-116
                    linux44-bbswitch              0.8-115              0.8-116
                 linux44-broadcom-wl      6.30.223.271-85      6.30.223.271-86
                    linux44-catalyst    1:15.201.1151-115    1:15.201.1151-116
                 linux44-ndiswrapper              1.61-83              1.61-84
                      linux44-nvidia           1:410.73-2           1:410.78-2
                linux44-nvidia-340xx           340.107-20           340.107-21
                linux44-nvidia-390xx             390.87-9            390.87-10
                    linux44-nvidiabl             0.88-115             0.88-116
                       linux44-r8168          8.045.08-37          8.045.08-38
                   linux44-rt3562sta        2.4.1.1_r4-83        2.4.1.1_r4-84
                         linux44-spl             0.7.11-5             0.7.11-6
                    linux44-tp_smapi             0.41-115             0.41-116
                 linux44-vhba-module          20161009-83          20161009-84
    linux44-virtualbox-guest-modules             5.2.22-2             5.2.22-3
     linux44-virtualbox-host-modules             5.2.22-2             5.2.22-3
                         linux44-zfs             0.7.11-5             0.7.11-6
  • 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:


#2

Known issues and solutions

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


Items from previous update sets

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.


#3

i have the same error for nvidia drivers in unstable branch

sudo pacman -Syyu
:: Synchronisation des bases de données de paquets…
 core                     146,9 KiB  10,2M/s 00:00 [######################] 100%
 extra                   1785,3 KiB  37,1M/s 00:00 [######################] 100%
 community                  5,0 MiB  35,2M/s 00:00 [######################] 100%
 multilib                 183,8 KiB  25,6M/s 00:00 [######################] 100%
:: Début de la mise à jour complète du système…
résolution des dépendances…
avertissement : impossible de résoudre « nvidia-utils=1:410.78 », une dépendance de « linux418-nvidia »
avertissement : impossible de résoudre « nvidia-utils=1:410.78 », une dépendance de « linux419-nvidia »
:: Les paquets suivants ne peuvent être mis à jour à cause de dépendances insolubles :
      linux418-nvidia  linux419-nvidia

:: Voulez-vous ignorer les paquets ci-dessus pour cette mise à jour ? [o/N] 

#4

Phil,
do you know what’s going on with those new BFQ patches, and if there are plans to integrate them in 4.19?
https://groups.google.com/forum/#!topic/bfq-iosched/KpsIayINEAU


#5

I already have them integrated since the beginning. We only use CFQ by default. You may switch it as usual. Didn’t had time yet to test if they are stable again.


#6

nvidia-utils-1:410.78 is missing from the repos.


#7

Oh okay.
I thought that Manjaro uses sirjan’s patchset from 1st November, and Paolo’s patches were sent by email only on 12th?
Or I’m probably just confused.


#8

No problem with:

Packages (2) linux419-4.19.3-1  linux419-nvidia-340xx-340.107-3

#9

ok mirrors testing is updated


#10

Fixed here too.


#11

all good for me:
linux419+gnome+nvidia+zfs


#12

all good for 419

419 series
sudo journalctl -b0 | grep sched
nov. 22 22:22:48 mjro kernel: io scheduler noop registered
nov. 22 22:22:48 mjro kernel: io scheduler deadline registered
nov. 22 22:22:48 mjro kernel: io scheduler cfq registered (default)
nov. 22 22:22:48 mjro kernel: io scheduler mq-deadline registered
nov. 22 22:22:48 mjro kernel: io scheduler kyber registered
nov. 22 22:22:48 mjro kernel: io scheduler bfq registered
nov. 22 22:22:48 mjro kernel: io scheduler bfq-sq registered
nov. 22 22:22:48 mjro kernel: BFQ I/O-scheduler: v9 (with cgroups support)
nov. 22 22:22:48 mjro kernel: sched_clock: Marking stable (852797889, -3034902)->(853715751, -3952764)

blkcg_policy_register: BLKCG_MAX_POLS too small ( block/blk-cgroup error )

414 series 
sudo journalctl -b -1 | grep sched
nov. 22 22:21:16 mjro kernel: io scheduler noop registered
nov. 22 22:21:16 mjro kernel: io scheduler deadline registered
nov. 22 22:21:16 mjro kernel: io scheduler cfq registered
nov. 22 22:21:16 mjro kernel: io scheduler mq-deadline registered
nov. 22 22:21:16 mjro kernel: io scheduler kyber registered
nov. 22 22:21:16 mjro kernel: io scheduler bfq registered
nov. 22 22:21:16 mjro kernel: io scheduler bfq-sq registered (default)
nov. 22 22:21:16 mjro kernel: BFQ I/O-scheduler: v8r12 (with cgroups support)
nov. 22 22:21:16 mjro kernel: io scheduler bfq-mq registered
nov. 22 22:21:16 mjro kernel: BFQ I/O-scheduler: v8r12 (with cgroups support)
nov. 22 22:21:16 mjro kernel: sched_clock: Marking stable (486281111, 0)->(490154912, -3873801)


49 series 
sudo journalctl -b -2 | grep sched
nov. 22 22:17:04 mjro kernel: io scheduler noop registered
nov. 22 22:17:04 mjro kernel: io scheduler deadline registered
nov. 22 22:17:04 mjro kernel: io scheduler cfq registered
nov. 22 22:17:04 mjro kernel: io scheduler bfq registered (default)
nov. 22 22:17:04 mjro kernel: BFQ I/O-scheduler: v8r12 (with cgroups support)

#13

all good for 419 + Vbox + Steam ( opengl )

419 series
sudo journalctl -b0 | grep sched
nov. 22 22:22:48 mjro kernel: io scheduler noop registered
nov. 22 22:22:48 mjro kernel: io scheduler deadline registered
nov. 22 22:22:48 mjro kernel: io scheduler cfq registered (default)
nov. 22 22:22:48 mjro kernel: io scheduler mq-deadline registered
nov. 22 22:22:48 mjro kernel: io scheduler kyber registered
nov. 22 22:22:48 mjro kernel: io scheduler bfq registered
nov. 22 22:22:48 mjro kernel: io scheduler bfq-sq registered
nov. 22 22:22:48 mjro kernel: BFQ I/O-scheduler: v9 (with cgroups support)
nov. 22 22:22:48 mjro kernel: sched_clock: Marking stable (852797889, -3034902)->(853715751, -3952764)

414 series 
sudo journalctl -b -1 | grep sched
nov. 22 22:21:16 mjro kernel: io scheduler noop registered
nov. 22 22:21:16 mjro kernel: io scheduler deadline registered
nov. 22 22:21:16 mjro kernel: io scheduler cfq registered
nov. 22 22:21:16 mjro kernel: io scheduler mq-deadline registered
nov. 22 22:21:16 mjro kernel: io scheduler kyber registered
nov. 22 22:21:16 mjro kernel: io scheduler bfq registered
nov. 22 22:21:16 mjro kernel: io scheduler bfq-sq registered (default)
nov. 22 22:21:16 mjro kernel: BFQ I/O-scheduler: v8r12 (with cgroups support)
nov. 22 22:21:16 mjro kernel: io scheduler bfq-mq registered
nov. 22 22:21:16 mjro kernel: BFQ I/O-scheduler: v8r12 (with cgroups support)
nov. 22 22:21:16 mjro kernel: sched_clock: Marking stable (486281111, 0)->(490154912, -3873801)

49 series 
sudo journalctl -b -2 | grep sched
nov. 22 22:17:04 mjro kernel: io scheduler noop registered
nov. 22 22:17:04 mjro kernel: io scheduler deadline registered
nov. 22 22:17:04 mjro kernel: io scheduler cfq registered
nov. 22 22:17:04 mjro kernel: io scheduler bfq registered (default)
nov. 22 22:17:04 mjro kernel: BFQ I/O-scheduler: v8r12 (with cgroups support)

49 errors
nov. 22 22:17:04 mjro kernel: cgroup: cgroup2: unknown option "nsdelegate"
nov. 22 22:17:04 mjro kernel: elevator: type bfq-sq not found
nov. 22 22:17:04 mjro kernel: elevator: switch to bfq-sq failed



#14
    It is recommend to move on to linux419-series.
    Use followed cmd to do that: 'sudo mhwd-kernel -i linux419'

the last sentence is grammatically incorrect and should read “Use the following cmd to do that…”

apart from the very minor grammar issue in the warning message, the update itself of course works fine :wink:


#15

One should, at the very least, attempt to be grammatically correct when correcting other people’s grammar. In future, please take care of punctuation marks and capitalisation.

P.S. : “very minor”, really?


#16

That’s hilarious, nice try but there’s nothing wrong with describing something as very minor. Neither with my capitalisation or punctuation

this is a forum thread and not an official document or warning message


#17

The rules of punctuation would beg to differ. By the way, neither is followed by nor, not or- a “very minor” mistake, i am sure.

Precisely my point!


#18

The erroneous warning is on the PC during installation of the last 4.18 kernel. That does need correcting regardless of your points about my grammar here


#19

Mind you, “very minor” is a “very minor issue”, and no, not

because is a “very minor argument”
Any more “technical” advice to correct “semantics” ?
:slight_smile:


#20

Please, this forum is used by many people who are not native english speakers. What are you doing here? Harassing people who make mistakes in writing english? We do not need that. I think it is totally unappropriate. … Or shall I say “inappropriate”?