[Stable Update] 2018-10-25 - Linux 4.19, KDE Plasma 5.14.2, Xorg 1.20.3, Gnome 3.30.2, Deepin, Grub

update
stable

#1

Hi community,

Welcome to another stable update. Since this update is huge we recommend to install it from within a terminal: pamac upgrade or sudo pacman -Syu

So what do we have with this one?

  • The kernel is now at v4.19.0 and got some BFQ fixes
  • grub gained functionality to automatically hide the menu as needed and will replace grub-quiet
  • Pamac is now at v7.2.0 and supports PKGUILD editing
  • KDE Plasma is now at 5.14.2
  • A security update for xorg-server
  • More Gnome 3.30.2 packages got added
  • We updated most of Deepin packages
  • We added the second beta release of Firefox v64
  • The usual upstream updates incl. python and haskell

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!


#rc-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 rc-build of Manjaro-Xfce 18.0 including the latest 4.13 packages, aswell as our most recent styling efforts. Our KDE fans may try our rc-build with the latest KDE v5.14 instead. And our GNOME fans may try our rc-build with the latest GNOME v3.30.


Current supported Kernels

  • linux316 3.16.59
  • linux318 3.18.124 [EOL]
  • linux44 4.4.162
  • linux49 4.9.135
  • linux414 4.14.78
  • linux417 4.17.19 [EOL]
  • linux418 4.18.16
  • linux419 4.19.0
  • linux414-rt 4.14.71_rt44
  • linux416-rt 4.16.18_rt11
  • linux418-rt 4.18.12_rt7-1

Package Updates (Thu Oct 25 21:54:42 CEST 2018)

  • stable community x86_64: 401 new and 372 removed package(s)
  • stable core x86_64: 10 new and 12 removed package(s)
  • stable extra x86_64: 256 new and 349 removed package(s)
  • stable multilib x86_64: 14 new and 19 removed package(s)

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


Changes made to pamac

With v7.2.0, Pamac has the ability to edit build files in both pamac-gtk and pamac-cli.

But it’s not the only one improvement, pamac-cli is now a complete AUR helper and an advanced build tool:

  • Tracking build files:
    It now keeps all build files in the configured pamac build dir that is now
    /var/tmp/pamac-build-<username> by default.
    This way it can track when a new version is available from AUR or if changes were made by yourself and propose you to view the diff.

  • Build tool:
    Pamac now has a clone action and build has a --no-clone option. They permit to ease building a package when you want to do important manual modifications.
    How to use it ?
    If a standard pamac build foo does all automatically you can do it step by step:
    Clone the build files with all dependencies : pamac clone --recurse foo
    Edit them as you want, then : pamac build --no-clone foo
    Or go the foo directory and run: pamac build --no-clone

  • Development tool:
    You can even create your own PKGBUILD files and build them with:
    pamac build --no-clone --builddir /my/build/dir <pkgname>
    or in the PKGBUILD directory:
    pamac build --no-clone
    If there are dependencies to build, all files must be in the same directory with one subdir per package.
    All dependencies will be checked and the correct build order will be found.

Changes made to grub package

1. What is the GRUB hidden menu change?

The main motivation for adding this is, to get to a fully flickerfree boot.

2. How to enable hidden GRUB menu?

On new Manjaro v18.0 installs this will be enabled by default. If your system has been upgraded to v18.0 from an older release, you can enable it by running these commands:

  • install linux418 or linux419: pamac install linux41[x]
  • check that you have quiet loglevel=3 rd.systemd.show_status=auto rd.udev.log-priority=3 in /etc/default/grub under GRUB_CMDLINE_LINUX_DEFAULT or GRUB_CMDLINE_LINUX and remove any background settings configured there.
  • sed -i -e 's|fsck||g' /etc/mkinitcpio.conf and pamac install systemd-fsck-silent
  • sudo mkinitcpio -P
  • sudo grub-editenv - set menu_auto_hide=1
  • sudo update-grub
  • reboot your system

Note the grub-update will overwrite any manual changes you’ve made to your grub.cfg (normally no manually changes are done to this file).

If your system has Windows on it, but you boot it only once a year so you would still like to hide the GRUB menu, you can tell GRUB to ignore the presence of Windows by running:

sudo grub-editenv - set menu_auto_hide=2

3. How to disable hidden GRUB menu

To permanently disable the auto-hide feature run:

sudo grub-editenv - unset menu_auto_hide

That is it.

4.How to access the GRUB menu when hidden

If for some reason you need to access the GRUB menu while it is hidden there are multiple ways to get to it:

  1. While booting keep SHIFT pressed, usually you need to first press SHIFT when the vendor logo is shown by the firmware / when the firmware says e.g. “Press F2 to enter setup” if you press it earlier it may not be seen. Note this may not work on some machines.

  2. During boot press ESC or F8 while GRUB loads (simply press the key repeatedly directly after power on until you are in the menu).

  3. Force the previous boot to be considered failed:

    1. Press CTRL + ALT + DEL while booting so that the system reboots before hitting the display manager (lightdm, gdm, sddm)

    2. Press CTRL + ALT + F6 to switch away from your display manager, followed by CTRL + ALT + DEL.

    3. Press the power-button for 4 seconds to force the machine off. Either of these will cause the boot_success grub_env flag to not get set and the menu will show the next boot.

    4. Manually set the menu show once flag by running: "grub-set-bootflag menu_show_once" This will cause the menu to show for 60 seconds before continuing with the default boot-option.

4. When is a boot considered successful ?

The boot_success grub_env flag gets set when you login as a normal user and your session lasts at least 2 minutes.

So if you e.g. login, do something and then within 30 seconds type reboot in a terminal (instead of doing the reboot from the menu) then this will not count as a successful boot and the menu will show the next boot.


If you have issues please use this thread:


eXploit X: Save us from doom [CVE-2018-14665]
Enable hidden GRUB menu help
#2

Known issues and solutions

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

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.


Items from previous update sets

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

Immer noch das gleiche Problem (wie ich nach dem letzten Update schon anmerkte): Momentan ist es nicht möglich, bei KDE Programm- oder Fensterregeln (Individuelles Fensterverhalten) festzulegen. Die Einstellungen lassen sich nicht speichern.
Systemklänge (Warnmeldungen etc.) stumm, obwohl der Sound wie gewohnt funktioniert.


#4

Bitte mit v18.0-rc4 probieren, wenn die ISO online ist.


#5

Guess today I played Sax from the Mars trilogy. Good update, thanks to the Majaro team.

System:
  Host: orphaned-inode Kernel: 4.18.16-1-MANJARO x86_64 bits: 64 
  Console: tty 0 Distro: Manjaro Linux 
Machine:
  Type: Desktop Mobo: ASUSTeK model: TUF Z270 MARK 1 v: Rev 1.xx 
  serial: <filter> UEFI [Legacy]: American Megatrends v: 1301 
  date: 03/14/2018 
CPU:
  Topology: Quad Core model: Intel Core i7-7700 bits: 64 type: MT MCP 
  L2 cache: 8192 KiB 
  Speed: 800 MHz min/max: 800/4200 MHz Core speeds (MHz): 1: 794 2: 800 
  3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 
Graphics:
  Device-1: NVIDIA GM107 [GeForce GTX 750 Ti] driver: nvidia v: 410.66 
  Display: server: X.Org 1.20.3 driver: nvidia 
  resolution: 1920x1080~60Hz, 1920x1080~60Hz 
  OpenGL: renderer: GeForce GTX 750 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 410.66 


#6


Is this important?


#7

Only one error but booted ok.

Oct 25 13:17:52 sam-pc systemd[409]: grub-boot-indeterminate.service: Failed to execute command: No such file or directory
Oct 25 13:17:52 sam-pc systemd[409]: grub-boot-indeterminate.service: Failed at step EXEC spawning /usr/bin/grub2-editenv: No such file or directory
Oct 25 13:17:52 sam-pc systemd[1]: Failed to start Mark boot as indeterminate.

#8

Partly. Fixed in grub-2.03.0-12.


#9

It will be on next update? I see there is installed on my system grub-2.03.0-10 .


#11

the new update removes grub-quite and installs grub should i do it


#12

I also faced this, and would like to know if this is intentional.


#13

now, grub rev “12” is in stable , wait mirror


#14

I don’t see that package in either stable, testing or unstable.

I guess it solves this:

-- Logs begin at Thu 2018-06-28 17:09:50 WEST, end at Thu 2018-10-25 18:20:56 WEST. --
out 25 18:20:26 mocho-desktop systemd[440]: grub-boot-indeterminate.service: Failed to execute command: No such file or directory
out 25 18:20:26 mocho-desktop systemd[440]: grub-boot-indeterminate.service: Failed at step EXEC spawning /usr/bin/grub2-editenv: No such file or directory
-- Subject: Process /usr/bin/grub2-editenv could not be executed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The process /usr/bin/grub2-editenv could not be executed and failed.
-- 
-- The error number returned by this process is 2.
out 25 18:20:26 mocho-desktop systemd[1]: Failed to start Mark boot as indeterminate.
-- Subject: Unit grub-boot-indeterminate.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit grub-boot-indeterminate.service has failed.
-- 
-- The result is RESULT.
[mbb@mocho-desktop ~]$ systemctl status grub-boot-indeterminate.service
● grub-boot-indeterminate.service - Mark boot as indeterminate
   Loaded: loaded (/usr/lib/systemd/system/grub-boot-indeterminate.service; static; vendor preset: disabled)
   Active: failed (Result: exit-code) since Thu 2018-10-25 18:20:26 WEST; 1min 38s ago
  Process: 440 ExecStart=/usr/bin/grub2-editenv - incr boot_indeterminate (code=exited, status=203/EXEC)
 Main PID: 440 (code=exited, status=203/EXEC)

out 25 18:20:26 mocho-desktop systemd[1]: Starting Mark boot as indeterminate...
out 25 18:20:26 mocho-desktop systemd[440]: grub-boot-indeterminate.service: Failed to execute command: No such file or directory
out 25 18:20:26 mocho-desktop systemd[440]: grub-boot-indeterminate.service: Failed at step EXEC spawning /usr/bin/grub2-editenv: No such file or directory
out 25 18:20:26 mocho-desktop systemd[1]: grub-boot-indeterminate.service: Main process exited, code=exited, status=203/EXEC
out 25 18:20:26 mocho-desktop systemd[1]: grub-boot-indeterminate.service: Failed with result 'exit-code'.
out 25 18:20:26 mocho-desktop systemd[1]: Failed to start Mark boot as indeterminate.
[mbb@mocho-desktop ~]$ which grub2-editenv
which: no grub2-editenv in (/home/mbb/.bin:/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl)

Or is it the package:

core/grub-fedora 2.03.62.f29-4
    GNU GRand Unified Bootloader (fedora patched)

Also, the following section is no longer on the new /etc/default/grub

# Uncomment to enable Hidden Menu, and optionally hide the timeout count
GRUB_HIDDEN_TIMEOUT=1
GRUB_HIDDEN_TIMEOUT_QUIET=true

I guess the hidden menu has changed. But the above section is still working.


#15

Danke Philip, reicht da das Update auf die rc4 oder muss ich neu installieren?


#16

The grub menu once showed but since the update it doesn’t any longer and I need to load a different kernel. I once used shift during boot and that would bring up grub but not now. How do I access grub?


#17

The Update was fine, after shutdown and boot again, the desktop freeze. The yakuake was open, the network was connected, the message was there. No mouse, i have two at usb, one to game one vertical mouse cordless.

I do a hard reset because i can do nothing. After boot again, all went fine. I think we must look all log files, something is wrong here.

I take i picture …buzzi but you can see desktop freeze

sudo journalctl -p err
Okt 24 13:25:37 manjaro-pc systemd-coredump[22344]: Failed to send coredump datagram: Connection reset by peer
-- Reboot --
Okt 25 19:40:26 manjaro-pc systemd[1]: Failed to start Mark boot as indeterminate.
-- Reboot --
Okt 25 19:43:18 manjaro-pc systemd[1]: Failed to start Mark boot as indeterminate.



#18

i had the same issue as you … but my laptop start fine


#19

Ok, the package is there now. Thanks @philm

Try ESC

For those interested:

sudo grub-editenv - set menu_auto_hide=1
sudo grub-mkconfig -o /boot/grub/grub.cfg

You can now remove the section from /etc/default/grub and reboot.


#20

Thank you! Problem solved.


#21

Just a quick unrelated tip, since you are new to Manjaro and Linux I suggest you are not among the first ones doing system updates.

Let more experienced users check out first if everything is OK and if not, let other find out workarounds and solutions. Wait until some 100 users voted already and then update. Plus check announcements in first/second post if there is something specific you need to pay attention to. Plus, more users experienced some kind of problem, more you should be inclined to create a backup first.

And lastly, nice greetings to Albania :wink: