[Testing Update] 2018-09-25 - Gnome, Grub, Kernel 4.19-rc5, Plasma-Workspace

#1

Hi community,

So it took us some more days to push additional packages for the upcoming stable update-pack.

Mostly we focused on Gnome. Reported bugs should mostly be fixed. Also we have some great update on the user expirience in the works regarding booting up.

Here the brief overall changes with this update:

  • Gnome 3.30 got additional packages and fixes
  • Kernel v4.19-rc5 incl. preparation for vendor splash boot-up
  • Grub-Quiet v2.03 incl. automatic BootMenu hide
  • Readded the Hibernation option to the lockscreen of Plasma-Workspace
  • upstream fixes

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


#bladebook - shipping to Europe this fall!

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 gold-rose) and eMMC as storage (additional M2-SSD possible), it will have a long battery life. Find out more on our hardware page.


#beta-release - 18.0 will be available in late October!

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.30.


Current supported Kernels

  • linux316 3.16.57
  • linux318 3.18.122 [EOL]
  • linux44 4.4.157
  • linux49 4.9.128
  • linux414 4.14.71
  • linux417 4.17.19 [EOL]
  • linux418 4.18.9
  • linux419 4.19-rc4
  • linux414-rt 4.14.71_rt44
  • linux416-rt 4.16.18_rt11

Package Updates (Tue Sep 25 07:12:50 CEST 2018)

  • testing community x86_64: 156 new and 157 removed package(s)
  • testing core x86_64: 5 new and 5 removed package(s)
  • testing extra x86_64: 87 new and 94 removed package(s)
  • testing multilib x86_64: 7 new and 12 removed package(s)

A detailed list of all package 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:

3 Likes
#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

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.


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

That booting looks so good! I’d love to see that. I’m pretty sure I heard shim in there too!

#4

Especially when it boots into Fedora :smiley:

4 Likes
#5

Manjaro%20Update%202509
Finally, hybernate button is back. Thanks.

#6

The idea is good but when booting from encrypted partition there are few text messages preventing logo to be displayed. Does anyone know how to turn this kind of logging off?
I have GRUB_CMDLINE_LINUX="quiet", GRUB_ENABLE_CRYPTODISK=y in /etc/default/grub, /crypto_keyfile.bin included in initramfs, so a password is entered only once - when GRUB starts, then vendor logo is shown for a second and then those messages take over:
booting initital ram disk
starting version 239
Sep 25 19:16:38 vladimir-xmnbp systemd-fsck[405]: MANJARO: clean, 669354/2692800 files, 9184921/10802688 blocks
So no seamless transition yet.

Switched to this, no issues, looks better than before but I have a feeling that setting some parametres in /etc/default/grub may have the same effect isn’t it? I mean this could be enough if I am not mistaken:

GRUB_HIDDEN_TIMEOUT=3
GRUB_HIDDEN_TIMEOUT_QUIET=true
#7

Can i use this quiet boot with Manjaro KDE too? or does this only work with GDM?
How do i activate this?

#8

Running Manjaro 18.0 Beta 6 xfce with no problems.

#9
  1. sudo pacman -S grub-quiet
  2. either
    sudo grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=manjaro --recheck (in case of UEFI)
    or
    grub-install --recheck /dev/sda (in case of BIOS)
  3. sudo update-grub

-=>Restore GRUB<=-

1 Like
#10

I don’t know if it’s proper to ask here. but are u going to wait until the point release of gnome fully land in Arch upstream repos ? because gnome folks are going to release the point release today or tomorrow I’m not so sure.

Thank you
EDIT: after reviewing the packages that got into testing. it seems like it has a plenty of .1 for gnome

#11

I cannot update. Here is the error message:

error: failed to prepare transaction (could not satisfy dependencies)
:: installing iptables (1:1.6.2-3) breaks dependency 'ebtables' required by firewalld
#12

I found this on the forums, searched for “ebtables”:

1 Like
#13

Thank you! pacman -Syu firewalld solves this issue.

1 Like
#14

Okay now I know how to get rid of loading linux … and loading initial ramdisk messages. It’s a grub thing, so one should comment out 2 strings beginning with “echo” in /etc/grub.d/10_linux as follows:

  message="$(gettext_printf "Loading Linux %s ..." "${version}")"
  sed "s/^/$submenu_indentation/" << EOF
#	echo	'$(echo "$message" | grub_quote)'
	linux	${rel_dirname}/${basename} root=${linux_root_device_thisversion} rw ${args}
EOF
  if test -n "${initrd}" ; then
    # TRANSLATORS: ramdisk isn't identifier. Should be translated.
    message="$(gettext_printf "Loading initial ramdisk ...")"
    initrd_path=
    for i in ${initrd}; do
      initrd_path="${initrd_path} ${rel_dirname}/${i}"
    done
    sed "s/^/$submenu_indentation/" << EOF
#	echo	'$(echo "$message" | grub_quote)'
	initrd	$(echo $initrd_path)

And do an update-grub then, of course.
Now I only have to disable that strange “starting version 239” message (I guess it’s systemd-related, god I hate systemd!), and fsck messages for root partition - why are they present if “quiet” option is explicitly set in grub options? There is nothing except these ones.

#15

https://wiki.archlinux.org/index.php/silent_boot

Both systemd and fsck messages are covered there.

1 Like
[Testing Update] 2018-09-27 - Kernels, Gnome, Deepin, Grub, Calamares
#16

apart from the headline:

[Testing Update] 2018-08-25

no issues here :wink:

1 Like
#17

I’m closly working with Fedora on this one.

This how it looks like on encrypted disk when all is in place:

The #bladebook will use KDE. I’m working closely on the support for it too.

GRUB_CMDLINE_LINUX_DEFAULT=“quiet loglevel=3 vga=current rd.systemd.show_status=auto rd.udev.log-priority=3 vt.global_cursor_default=0”

1 Like
[Testing Update] 2018-09-27 - Kernels, Gnome, Deepin, Grub, Calamares
#18

Was tired of waiting for openssl 1.1.1 package in order to update Mega Sync, so I switched to Testing at my own risk.

So far, on my side, it seems to be okay.

But I have random crashes with Pamac 7.1.1, which has been deployed in Stable and Testing branches (and I suppose in Unstable too) on Manjaro Cinnamon and Manjaro XFCE. I managed to get crashes on VM and on real hardware. Reported in Gitlab here: https://gitlab.manjaro.org/applications/pamac/issues/488

I hope it’ll be fixed before the next big release of updates in Stable branch. I’ve been lucky this time: Pamac didn’t crash when I update my system after switching to Testing (I used Pamac in CLI, not GUI). I can’t confirm if Pamac can or can’t crash during updates, but it is something that could be possible, so I consider this a very critical issue.

Anyway, there’s a lot of 3.30.1 software from the GNOME project that has been published on Arch Linux, so additional Testing release might be a good idea.

#19

Thank you, it works. Looks like a good alternative to Plymouth and Bootsplash. However, it’s not so good looking when rebooting PC. For instance, I get several output messages like a bunch of “stopping %servicename% OK” followed by “watchdog0 did not stop” and “reboot: Restarting system”. What is the best way to suppress those messages from showing up I wonder?

EDIT (2018-10-09): Still don’t know how to get rid of these messages during reboot. Had to enable bootsplash in kernel options again.

closed #20

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.