[Testing Update] 2018-08-26 - Kernels, Firefox, Systemd, AMD-Ucode, Mesa

update
testing

#1

Hi community,

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

  • we updated our most of our kernels
  • linux44 and linux49 should boot now again (fixed issues with L1TF)
  • newer systemd snapshot
  • latest firefox-dev package
  • introducing of AMD-Ucode (install via pacman -S amd-ucode after upgrade)
  • the usual upstream rebuilds/updates

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

For more info about L1TF please watch this video:


Currently we are working on a new Manjaro-Hardware project, the Bladebook Fall 2018. It will be powered by Manjaro KDE v18.0 and the latest Intel Apollo Lake Quad-Core HD APU. Having a fanless metal material (cassis either silver or gold-rose) and eMMC as storage (additional M2-SSD possible), it will have a long battery life. Find out more on our hardware page.

If you are curious about the latest state of development for the upcoming Manjaro-Illyria 18.0 release, you now have the opportunity to download a beta-build of Manjaro-Xfce 18.0 including the latest xfce-gtk3 packages aswell as our most recent styling efforts. Our KDE fans may try our beta-build with the latest KDE v5.13 instead. And our GNOME fans may try our beta-build with the latest GNOME v3.28.


Latest information about the intel-cpu-bug risk and our efforts can be found here.


Current supported Kernels

  • linux316 3.16.57
  • linux318 3.18.119 [EOL]
  • linux44 4.4.152
  • linux49 4.9.124
  • linux414 4.14.67
  • linux417 4.17.19 [EOL]
  • linux418 4.18.5
  • linux419 4.19-rc0
  • linux414-rt 4.14.52_rt34
  • linux416-rt 4.16.18_rt11

Package Updates (Sun Aug 26 11:45:17 CEST 2018)

  • testing community x86_64: 220 new and 219 removed package(s)
  • testing core x86_64: 18 new and 18 removed package(s)
  • testing extra x86_64: 112 new and 111 removed package(s)
  • testing multilib x86_64: 7 new and 7 removed package(s)

Current list of changes can 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:


Ready for Stable ?!?

  • We are ready to move this to our stable branch
  • I still see some issues (post about them)

0 voters


#2

Known issues and solutions

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


AMD-Ucode introduction

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.


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.


Something using Perl/Python/glibc broke

Rebuilds needed! If it’s an AUR package, rebuild it. If it’s a repo package, please report and check back regularly for rebuilds.


Items from previous update sets

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.


Kernel 4.9 issues

Seems on rare conditions you may face a faulty boot with linux49. It results in messages similar like this: <module> likely not compiled with -mcmodel=kernel. Also you will land in the emergency console.

We recommend to install at least another kernel as backup. You may follow this post to recover. v4.9.107-2 is known to be working.


:: alpm-octopi-utils: installing “pacman” (5.1.0-2) breaks the dependency with «pacman <5.1»

Make sure your mirrors are up-to-date. All package management tools should be compatible with pacman 5.1


:: ffmpeg2.8: installing x265 (2.8-1) breaks dependency ‘libx265.so=151-64’

ffmpeg2.8 is no longer in the repos. Remove it, and if you need it, rebuild/reinstall it from the AUR.


gcc54 and gcc5 are in conflict

For those using CUDA, if this error comes up, run the update from terminal
sudo pacman -Syyu
and type YES to replace gcc5 with gcc54


Extension “Workspace to Dock” is bugged

Be careful like there is a bug if you use the Extension “Workspace to Dock”. You need to update/install this version in ~/.local/share/gnome-shell/extensions/ for not have desktop freeze after reboot : https://github.com/passingthru67/workspaces-to-dock/archive/master.zip

Thanks for nabd who have solved this issue : [Testing Update] 2018-05-11 - Kernels, GCC8, Gnome 3.28.2, Cinnamon, KDE Apps 18.04.1, LibreOffice


I see a lot of pacnew files

Well, there is no manual intervention needed for pacnew files coming from filesystem package. The best thing you can do is, do nothing.

Never, ever, ever, ever, ever merge the pacnew file for /etc/{passwd,shadow,gshadow,group}, unless you want to make the new comments match aesthetically with your in-use user accounts database. The only practical difference that merging can ever cause is to accidentally delete users or mangle the whole file’s syntax and render your computer maybe unbootable.

More advice in this regard you may find here.


Nvidia drivers and Fermi support

With the current Nvidia driver release v396.24, support for the old Fermi cards got dropped. Please switch either over to Nouveau driver or downgrade to v390xx driver series.

Bumblebee users follow:

sudo mhwd -r pci video-hybrid-intel-nvidia-bumblebee
sudo mhwd -i pci video-hybrid-intel-nvidia-390xx-bumblebee

Normal users follow:

sudo mhwd -r pci video-nvidia
sudo mhwd -i pci video-nvidia-390xx

To switch to opensource drivers do:

sudo mhwd -r pci video-nvidia
sudo mhwd -i pci video-linux


Changes made to Glibc

The new version of glibc removes support for NIS and NIS+. The default /etc/nsswitch.conf file provided by filesystem package already reflects this change. Please make sure to merge pacnew file if it exists prior to upgrade.

NIS functionality can still be enabled by installing libnss_nis package. There is no replacement for NIS+ in the official repositories.


Changes made to PAM

pam 1.3.0-2 no longer ships pam_unix2 module and pam_unix_*.so compatibility symlinks. Before upgrading, review PAM configuration files in the /etc/pam.d directory and replace removed modules with pam_unix.so. Users of pam_unix2 should also reset their passwords after such change. Defaults provided by pambase package do not need any modifications.

Check grep -rn 'pam_unix[2_]' /etc/pam.d, if no output, you need to do nothing.


Samba units renamed

Note: In samba 4.8.0-1, the units were renamed from smbd.service and nmbd.service to smb.service and nmb.service.

To provide basic file sharing through SMB start/enable smb.service and/or nmb.service services. See the smbd(8) and nmbd(8) man pages for details, as the nmb.service service may not always be required.


Directory permissions differ

Directory permissions differ on /var/lib/samba/private/
filesystem: 755 package: 700

sudo chmod 700 /var/lib/samba/private/


Samba - Error 255: net usershare add: cannot convert name “Everyone” to a SID.

Currently there seems to be an issue when using group = sambashare with Samba 4.8.1-1, which is used by default in thesmb.conf provided by Manjaro. Changing it to group = +sambashare or force group = +sambashare resolves this. However, we might fill out a bug report, to see why that is currently needed.

Commenting/removing group = sambashare is also a viable solution.


Long delay for starting Desktop Environment

There’s a bug which is exhausting the entropy pool. This is refilled over time through e.g. disk activity and mouse movement. You can increase the fill rate with a software solution:

sudo pacman -S haveged
sudo systemctl enable haveged
sudo systemctl start haveged

An alternative method if activating the haveged service is not something you want to do is to press the shift key 8-10 times in succession.


#3

Linux44 is booting fine again.
cheers


#4

So it’s not part of the kernel-firmware anymore?

https://git.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/linux-firmware

I’m really not amazed about that change. Is there a reason for this I just can’t find?


#5

It was always part of linux-firmware and not the kernels.


#6

I don’t get it. Why a different package? It is split from linux-firmware?


#7

Unrelated, but I think you guys should get rid of EOL kernels as they happen


#8

Update without problems.
After reboot is all good.


#9

To preload them similar as we do for Intel CPUs.


#10

Is that not possible when they’re in linux-firmware? Is it that they have to be in /boot ?


#11

Please read-up on microcode.


#12

That’s Fun:

BlockquoteNOTE, 4.17.19 is the last release of the 4.17.y kernel.
It is now end-of-life.
It is recommend to move on to linux416-series.
Use followed cmd to do that: ‘sudo mhwd-kernel -i linux418’

Linu74


#13

and it will as I won’t fix the package cos of that typo. most wont read it anyway …


#14

Done, Sorry.

Linu74


#15

Indeed it’s changed. So it didn’t get loaded by the bootloader before?


#16

All our build-tools are now adopted amd-ucode. Only the v17.1 profiles still need the patch from v18.0 series.

https://lists.manjaro.org/pipermail/manjaro-packages/Week-of-Mon-20180820/018698.html
https://lists.manjaro.org/pipermail/manjaro-packages/Week-of-Mon-20180820/018700.html


#17

I’ve installed amd-ucode
but how to verify?

$ dmesg | grep microcode
[    0.878900] microcode: CPU0: patch_level=0x06003106
[    0.878937] microcode: CPU1: patch_level=0x06003106
[    0.878942] microcode: CPU2: patch_level=0x06003106
[    0.878952] microcode: CPU3: patch_level=0x06003106
[    0.879017] microcode: Microcode Update Driver: v2.2.

Am I allright? The package version is not really helpful

Name            : amd-ucode    
Version         : 20180821.1d17c18-3

#18

One should only take care that the kernel config has CONFIG_MICROCODE_AMD=y. But I would think it is the case with kernels which got updated with this testing update.


#19

Yep, since linux316 :wink:


#20

On 4.19 upowerd gives “unhandled action ‘bind’” warnings for my roccat devices. (upower is flagged out of date on arch since 2 days ago.) Not sure if this is connected to my previous problem. Will retry with a cold boot tomorrow.

No problems with the 4.18 kernel. :grinning:

Edit: With the 4.19 kernel from this update my previous problems with boot and shutdown are gone (but I remain none the wiser…).