[Testing Update] 2018-06-16 - Kernels, KDE Plasma, Firefox, Haskell, Python

Hi community,

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


  • KDE Plasma got updated to version 5.13.0
  • Another Firefox Development Update
  • Some kernels got updated
  • Usual upstream rebuilds

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

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:

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

Current supported Kernels

  • linux316 3.16.56
  • linux318 3.18.113 [EOL]
  • linux41 4.1.52 [EOL]
  • linux44 4.4.137
  • linux49 4.9.108
  • linux414 4.14.49
  • linux415 4.15.18 [EOL]
  • linux416 4.16.15
  • linux417 4.17.1
  • linux418 4.18-rc0 (early preview)
  • linux414-rt 4.14.40_rt30
  • linux416-rt 4.16.12_rt5

Package Updates (Sat Jun 16 07:41:17 CEST 2018)

Sync Packages

  • testing core x86_64: 1 new and 1 removed package(s)
  • testing multilib x86_64: 4 new and 4 removed package(s)
  • testing extra x86_64: 83 new and 77 removed package(s)
  • testing community x86_64: 303 new and 301 removed package(s)

Overlay Packages

  • testing core x86_64: 8 new and 7 removed package(s)
  • testing extra x86_64: 55 new and 55 removed package(s)
  • testing community x86_64: 6 new and 6 removed package(s)

A detailed 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:


Known issues and solutions

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

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.

Items from previous update sets

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.

The update overwrites /etc/bash.bashrc without keeping a .pacsave copy. I had to restore my customizations from backup.

Other than that the update went well: linux417+zfs+nvidia+cinnamon

that's why you should modify only ~/.bashrc


This is obviously not Manjaro's fault, instead it's upstream with KDE, but i just found my updated Testing KDE VM now also suffers this bug; Plasma 5.13 Network Connections GUI broken

I know it's Phil's distro but I would have waited a bit longer before bringing Plasma 5.13 to Testing. I think it's too early seeing all the posts about it in Unstable. The KDE bug web page is filled with bugreports. I think waiting for 5.13.1 would have been better. But that's my personal opinion.
And yes, I do know it's released in Testing and NOT in Stable yet. But that is the next step and I really believe 5.13 is not ready for that.


Agree. Whilst saddening, it's not actually inconvenient for me that my Testing KDE VM's NM widget is broken, but if that flows on into Stable & thus afflicts my Lappy & Tower it will be really disruptive. I interact with that widget very frequently, given my VPN usage & need/desire to change servers.

1 Like

Same as @Kadee and some others here.... huge icons in Network-Manager applet. I use the breath (dark) theme. I have clean the cache (saw this as a possible fix in another thread) but it didn't help. Apart this, the rest of the update seems smooth.

it's a theme bug. Oxygen appears to be deprecated or on its way to that. Breath on the other hand needs some fixing by Manjaro.

Well, the poll in OP looks like every other testing update poll with major changes in its package list. Nothing special here.

This is so easy to do now:
That just shows how unreliable polls can be.

The amount of problems described here in several threads and the huge increase in bugs on the bugs.kde.org website say something different. Just hoping for the best.

I can confirm that the Network GUI bug is a theme related. I was using arc-dark and the icons were huge. I just changed the Desktop theme (systemsettings -> workspace theme -> desktop theme -> breeze dark|light) and all is good. I guess this is the time to rethink using other themes than the default ones.
And the bashrc replacement, sucks. Just replaced it, without notification for replacement or at least backing up my old config. No bueno. If someone uses the global bashrc or not it's up to user (the argument that I should use local one, is not an argument at all). But the system should not delete the config without user interaction or warning.
Everything else is good.


I confirm that switching from Breath to Breeze fixed the icons bug in KDE Network-Manager for me. Good workaround for now.

KDE Blur login (logout too?), reminds me of Deepin, who invented it ? :wink:

[Update in Deepin is fine unless you've been messing with your own desktop backgrounds] (Deepin Wallpaper Chooser Bug) :smiley:
Thx for updates, deepin-image-viewer is working again.

Noooooooooooooooooooo, Breeze sucks razor blades & boulders, don't wanna use it no way no how no time. For years, for my tastes, Oxygen has had the least-sucky icons, & they even half-look like the intended Actions. The Breeze ones IMO are iconography at its worst [ok, maybe not worst, but still really crappy].

1 Like

nope, that just shows how easily individual perception can differ from the actual facts.

Every major change has bugs, thats how software works. That's also how the testing branch works. If you are not prepared for bugs, you should switch to stable.
It's actually surprising that so few bugs come to testing.

there are a lot of other themes out there, not just the preinstalled ones.
If you really want to keep using oxygen, and don't want to wait for the dev's to fix it, you can always fix it yourself - that's the big feature of opensource software. In theory, everyone can be a dev.

Yeah, that.

hahahaah :smiley: @Kadee well, I just changed the Desktop theme. I use papirus-dark icons and arc-dark application theme. But, I just can't take it how every time other themes fall behind with kde plasma development and changes.

The good thing is that if someone does not like it, they can just change it :slight_smile:

No, that is not correct.

1.) ~/.bashrc is not good for systemwide changes for all users. It is not recommended to mess around with ~/.bashrc of other users.
2.) pacman provides the .pacsave mechanism to prevent issues like that. It is a miss of the package creator not enabling that feature for /etc/bash.bashrc.

It seems fine with Plasma. The only (theme/icon) issue is the App Launcher (kickstart) icon gets huge when you have a thick panel (wide for vertical panel). Notice Manjaro logo:

I suggest we also add "frownies" and "dislike" buttons to the forum. :wink:

Forum kindly sponsored by