[Stable Update] 2018-08-06 - Kernels, Plasma, Jade, Deepin, Firefox, Haskell

update
stable

#1

Hi community,

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

  • we updated most of our kernels
  • Bernhard updated our RT-Kernelseries v4.14
  • KDE Plasma got updated to 5.13.4
  • firefox got a new development release
  • networkmanager got its point-release
  • deepin and xfce-gtk3 got new package updates
  • some fixes to pulseaudio
  • our Jade-Desktop packages switched to stable versions
  • Stefano updated our Adapta Themes
  • added Mesa 18.1.5
  • we updated pacman to 5.1.1
  • wine got updated to 3.13
  • pushed out a new linux-firmware to support more AMD-GPUs
  • the usual python/haskell rebuilds/updates

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


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.117 [EOL]
  • linux41 4.1.52 [EOL]
  • linux44 4.4.145
  • linux49 4.9.117
  • linux414 4.14.60
  • linux415 4.15.18 [EOL]
  • linux416 4.16.18 [EOL]
  • linux417 4.17.12
  • linux418 4.18-rc7
  • linux414-rt 4.14.52_rt34
  • linux416-rt 4.16.18_rt11

Package Updates (Sat Aug 4 20:19:38 CEST 2018)

  • stable community x86_64: 741 new and 718 removed package(s)
  • stable core x86_64: 22 new and 22 removed package(s)
  • stable extra x86_64: 245 new and 244 removed package(s)
  • stable multilib x86_64: 15 new and 15 removed package(s)

A list of all changes in details 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:


Unable to update system (manjaro-system is 20180716)
[Deepin] When trying to install Deepin-extra group, I got a conflict between 2 packages
#2

Known issues and solutions

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


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.


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.


Known Issues from Stable Updates Announcements
#4

Look out for pacman.conf.pacnew
cheers


#6

what about python 3.7?


#7

What is so important to have this new python version? We are about to sync it when it is available. It also will take a while to check our own packages against that version. Most likely it may take couple of weeks to be stable enough.


#8

nice and smooth update despite that i had a received an issue with chromium showing an error about corrupted package and i managed to fix it by reinstalling chromium


#9
Aug 06 14:37:40 StudioMB plasmashell[1286]: org.kde.plasmaquick: Applet "Anwendungs-Starter" loaded after 136 msec
Aug 06 14:37:40 StudioMB plasmashell[1286]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationDelegate.qml:119:22: Unable to assign [undefined] to QQmlListModel*
Aug 06 14:37:40 StudioMB plasmashell[1286]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationDelegate.qml:113: ReferenceError: appIcon is not defined
Aug 06 14:37:40 StudioMB plasmashell[1286]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationDelegate.qml:119:22: Unable to assign [undefined] to QQmlListModel*
Aug 06 14:37:40 StudioMB plasmashell[1286]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationDelegate.qml:113: ReferenceError: appIcon is not defined
Aug 06 14:37:40 StudioMB plasmashell[1286]: org.kde.plasma.pulseaudio: No object for name "alsa_output.pci-0000_00_1b.0.iec958-stereo.monitor"
Aug 06 14:37:55 StudioMB plasmashell[1286]: trying to show an empty dialog
Aug 06 14:38:08 StudioMB plasmashell[1286]: org.kde.plasmaquick: Applet "Netzwerke" loaded after 163 msec
Aug 06 14:38:08 StudioMB plasmashell[1286]: org.kde.plasmaquick: Increasing score for "Netzwerke" to 5
Aug 06 14:38:10 StudioMB kdeinit5[1240]: Service  "org.kde.StatusNotifierHost-1286" unregistered
Aug 06 14:38:16 StudioMB systemd-coredump[2036]: Process 1286 (plasmashell) of user 1000 dumped core.
                                                 Stack trace of thread 1286:
-- Subject: Speicherabbild für Prozess 1286 (@COREDUMP_COMM) generiert
- Process 1286 (plasma shell) has been aborted and
...........
Aug 06 14:38:16 StudioMB systemd-coredump[2036]: Process 1286 (plasmashell) of user 1000 dumped core.
                                                 
                                                 Stack trace of thread 1286:
                                                 #0  0x00007f615484286b n/a (n/a)
-- Subject: Speicherabbild für Prozess 1286 (@COREDUMP_COMM) generiert

Edit:
2018.08.07 Solution Proposed
Reinstalling all PLASMA - Packages


#10

What about perl 5.28?

@philm and all other devs and testers: Have fun!


#11

Got this while updating .do I have to figure out what to do ? or can I ignore it?
everything seems to work ok.

rEFInd UEFI application has been installed at /usr/share/refind/refind_.efi
Other UEFI applications have been installed at /usr/share/refind/tools_
/
UEFI drivers have been installed at /usr/share/refind/drivers_*/
Copy the efi application (according to your UEFI ARCH)
and /usr/share/refind/refind.conf-sample to a sub-directory of /EFI/
as refind.conf and add an entry to firmware boot menu using efibootmgr
or mactel-boot (for Macs)
rEFInd Icons have been installed at /usr/share/refind/icons/
rEFInd Fonts have been installed at /usr/share/refind/fonts/
HTML Documentation is available at /usr/share/refind/docs/html/
More info: https://wiki.archlinux.org/index.php/rEFInd


#12

Xorg 1.20 anywhere on the horizon? Being held up by Nvdia drivers I assume?


#13

You can always switch to unstable branch.


#14

No problems here. All computers are running now with kernel 4.18 :sunglasses:

happy summer
caho


#15

Manjaro Gnome: No issues whatsoever.


#16

So far so good, running XFCE…but I haven’t rebooted after updating it yet. I’m a procrastinator.


#17

Perfect Update.
LXQT and XFCE with Kernel 4.17.
Thanks!


#18

When update using Pamac GUI (Update Manager App), it shows message “Invalid or corrupted package”. But, it’s normal when execute on Terminal by type “sudo pacman -Syyu”.


#19

hi

the update has started well but now it is blocked

I’m afraid to restart the system

Found initrd fallback image: /boot/initramfs-4.14-x86_64-fallback.img

  -> Running build hook: [keymap]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-4.14-x86_64.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux414.preset: 'fallback'
  -> -k /boot/vmlinuz-4.14-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-4.14-x86_64-fallback.img -S autodetect
==> Starting build: 4.14.60-1-MANJARO
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-4.14-x86_64-fallback.img
==> Image generation successful
( 3/18) Updating Grub-Bootmenu
Création du fichier de configuration GRUB…
Arrière-plan trouvé : /usr/share/grub/background.png
Image Linux trouvée : /boot/vmlinuz-4.14-x86_64
Image mémoire initiale trouvée : /boot/intel-ucode.img /boot/initramfs-4.14-x86_64.img
Found initrd fallback image: /boot/initramfs-4.14-x86_64-fallback.img

after 30min

erreur : la commande n’a pas pu être exécutée correctement
( 4/18) Warn about old perl modules
( 5/18) Compiling GSettings XML schema files...
( 6/18) Updating icon theme caches...
( 7/18) Restore Linux kernel modules

==> Warning:
	 -> Kernel has been updated. Modules of the current kernel
	 -> have been backed up so you can continue to use your
	 -> computer. However, the new kernel will only work 
	 -> at next boot.
	
	
( 8/18) Install Gnome native extension for update
( 9/18) Configuring pacman-mirrors ...
.: INFO Downloading mirrors from repo.manjaro.org
hint: use `pacman-mirrors` to generate and update your pacman mirrorlist.
(10/18) Reloading system manager configuration...
(11/18) Updating udev hardware database...
(12/18) Creating system user accounts...
(13/18) Creating temporary files...
(14/18) Reloading device manager configuration...
(15/18) Arming ConditionNeedsUpdate...
(16/18) Updating the info directory file...
(17/18) Updating the desktop file MIME type cache...
(18/18) Updating the MIME type database...


#20

Pulseaudio gave me a little trouble, I had no audio after the reboot, pacmd error was “No PulseAudio daemon running, or not running as session daemon”, fixed by reinstalling pulseaudio and starting the daemon manually, after reboot everything was ok.


#21

sudo update-grub

Not sure why it failed.


#22

XFCE, 4.14.60

Everything updated just fine and is running correctly.

Thanks for the update and keep up the great work!