[Unstable Update] 2018-12-25 - KDE Frameworks, KDE Apps, Deepin, ZFS, LibreOffice, QT, Mesa, Systemd

unstable
update

#1

Hi community,

Welcome to another unstable update. :stuck_out_tongue:
So what do we have with this one?

  • Deepin and Cinnamon updates
  • We updated QT5 to 5.12 LTS; please tell us if some is still broken
  • Latest linux-firmware. Post if you have issues with your AMD GPU.
  • Systemd is now at v240, but seems to be unstable. See for regressions here.
  • KDE Frameworks are at 5.53.0
  • KDE Apps are at 18.12.0
  • Mesa got updated to 18.3.1
  • LibreOffice got updated to 6.1.4
  • ZFS is now at 0.7.12
  • all the regular haskell, php and python updates

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


Partnership with FCS Linux Aarhus

We are happy to announce a new partnership with FCS Linux Aarhus owned by @fhdk. This enables us to offer you Laptops with Manjaro pre-installed and Manjaro Stickers you can use on your own hardware or gift them to a friend. For each sale FCS will donate a percentage to the Manjaro project.



Manjaro v18.0.1 released!

It took us almost two months of development to update Manjaro Illyria. It comes with refreshed packages and updated tools. You may want to download our XFCE Edition with the latest 4.13 packages, aswell as our most recent styling efforts. Our KDE fans may try our KDE Edition with the latest KDE v5.14 instead. And our GNOME fans may try our Gnome Edition with the latest GNOME v3.30.


Current supported Kernels

  • linux316 3.16.62
  • linux318 3.18.131 [EOL]
  • linux44 4.4.167
  • linux49 4.9.147
  • linux414 4.14.90
  • linux417 4.17.19 [EOL]
  • linux418 4.18.20 [EOL]
  • linux419 4.19.12
  • linux420 4.20.0
  • linux414-rt 4.14.78_rt47
  • linux416-rt 4.16.18_rt11
  • linux418-rt 4.18.16_rt9

Sync Package Updates (Tue Dec 25 12:57:29 CET 2018)

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:


#2

Updated to see if linux420 fixes my startup problems detailed here: Problems with Manjaro Linux on a HP Elitebook 755 G5 with Ryzen 7 and Vega 10. I still have freezes, and now the /var/log/Xorg.0.log.old file is empty, so I can not see why the previous startup failed.

Otherwise, when I indeed manage to start successfully everything looks OK.


#3

OpenGL still doesn’t work properly in KDE

UPD It was Option “TearFree” “true” in Section “Device” of /etc/X11/mhwd.d/intel.conf
I commented it out and set Option “DRI” “3” instead “2”
Everything is OK. No fragmentation, no tearing, no freezes


#4

A pedantic note about a name :
“QT” is Apple QuickTime
Qt is “Qt”

Apparently they say it as ‘kyut’ (like english ‘cute’)
not as ‘kyu ti’ (english ‘Q.T.’)
https://wiki.qt.io/Qt_for_Beginners#Introduction_to_Qt


#5

I do not have that config file on my system and do not have problems with OpenGL on KDE Plasma.
Is it “a must” to have that file and is there a downside of not having it?


#6

I don’t know. I discovered it when I decided to reinstall xf86-video-intel . After installation, it said I needed to fix Option “DRI”.


#7

So far everything works great except I can’t get Plank to work, of all things. I didn’t install it until today.
Xfce4… Plank cannot autostart no matter if I add it manually or not and if I try to drag and drop icons the dock crashes.

Everything else works great.


#8

Great Christmas Gift!

Clean upgrade. On the first re-boot there was a two-minute shutdown pause (seemingly while waiting on some lock to be released), but only on the first re-boot.


[Testing Update] 2019-01-19 - Kernels, Mesa, Browsers, Nvidia, Deepin, VirtualBox
#9

With systemd 240.1-7 :
Receive this message(truncated) with kernel 4.19 and kernel 4.20:

Dec 27 00:57:52 xmg systemd[1]: Stopping User Manager for UID 992...
Dec 27 00:57:52 xmg systemd[3057]: Stopped target Default.
Dec 27 00:57:52 xmg systemd[3057]: Stopping D-Bus User Message Bus...
Dec 27 00:57:52 xmg systemd[3057]: dbus.service: Succeeded.
Dec 27 00:57:52 xmg systemd[3057]: Stopped D-Bus User Message Bus.
Dec 27 00:57:52 xmg systemd[3057]: Stopped target Basic System.
Dec 27 00:57:52 xmg systemd[3057]: Stopped target Timers.
Dec 27 00:57:52 xmg systemd[3057]: Stopped target Paths.
Dec 27 00:57:52 xmg systemd[3057]: Stopped target Sockets.
Dec 27 00:57:52 xmg systemd[3057]: p11-kit-server.socket: Succeeded.
Dec 27 00:57:52 xmg systemd[3057]: Closed p11-kit server.
Dec 27 00:57:52 xmg systemd[3057]: gpg-agent-browser.socket: Succeeded.
Dec 27 00:57:52 xmg systemd[3057]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).

On systemd 239.6-2 wth it held back, no problems. Although, some might call that a “partial” upgrade.

IgnorePkg = lib32-systemd libsystemd systemd systemd-sysvcompat

I was receiving a lot of audit messages on boot:

Dec 27 01:47:52 xmg audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-setup-dev comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 27 01:47:52 xmg audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-setup-dev comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 27 01:47:52 xmg audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-sysusers comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 27 01:47:52 xmg audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-sysusers comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 27 01:47:52 xmg audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-remount-fs comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 27 01:47:52 xmg audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-remount-fs comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'

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

Since they’re fluff messages and all successes as usual, I disabled with adding audit=0 to grub and masking systemd-journald-audit.socket.


#10

Latest systemd update …

[ALPM] upgraded libsystemd (240.1-7 -> 240.6-1)

Caused the following udev errors on boot.

systemd-udevd[373]: Failed to wait spawned command '/usr/bin/set-wireless-regdom': Input/output error
systemd-udevd[361]: Failed to wait spawned command 'mtd_probe /dev/mtd0ro': Input/output error
systemd-udevd[433]: Failed to wait spawned command 'mtd_probe /dev/mtd1ro': Input/output error
systemd-udevd[408]: Failed to wait spawned command '/usr/bin/tlp auto': Input/output error

These didn’t occur with 240.1-7.

Boot also took quite a bit longer too, I thought I was experiencing a “black screen”, but sddm login screen showed eventually.


#11

I’m getting also the following warning in the journal after the systemd 240.1-2 until now 240.6-1:

systemd-udevd[464]: Failed to wait spawned command '/usr/bin/alsactl restore 1': Input/output error
systemd-udevd[446]: Failed to wait spawned command '/usr/bin/alsactl restore 0': Input/output error

I managed to resolve it by following the instructions from here although I’m not sure if it’s a real fix or a workaround.

Exactly the same here on my gnome desktop with gdm.


[Unstable Update] 2019-01-04 - Deepin, Certbot, Systemd, Haskell, Python
#12

If you have issues with systemd you may switch to testing. On unstable we try to fix issues as we get updates from upstream


#13

This is the sort of crap we have to put up with now being crash test dummies for Fedora / Red Hat?

Not good.

An Arch base is more stable, all because of some silly “clean” boot Fedora’s inherent experimental instability is being forced upon us.


#14

Well, I won’t start arguing on how we manage our packages. We work with upstream close together and try stuff as needed. Also we offer three branches. Unstable is our testbed. There we play with everything we want to do. It was always that case. Normally only us developers use unstable. Users should stick to testing or stable. Maybe I’ll bring back xperimental branch, but for now systemd development works just fine and that extra branch is not yet needed.


#15

I don’t want to argue either, just simply stating the facts.

Since aligning more closely with upstream Fedora and packaging systemd it has been a complete mess.

We don’t get the benefit of upstream stability testing anymore for arguably the most crucial package in a distro. Everything is reactive, number of issues experienced by users has increased significantly.

We understand, it is your distro and you can do what you like, but just don’t pretend that going down this route is not going to weaken Manjaro as a distro.

Manjaro’s number one advantage was its rock solid upstream Arch base, which meant stability.

Manjaro doesn’t have the technical userbase size or competence to be a Fedora systemd test distro as well.


#16

We should probably create a separate topic for this but here’s how things work…

Red Hat = The Borg (you will be assimilated)
Fedora = Borg Development Arm
n Linux Distro = Assimilated

Red Hat, acting as a somewhat Benevolent Dictator, determines what happens–what direction–ALL major and most minor Linux Distributions take. There’s not much choice–it’s either that or run Windows/MacOS–or ChromeOS (hah!).

There’s Devuan, AntiX, Void, and a few other packaged distros but nothing mainstream other than possibly AntiX.

Absolutely. And few have any other choice (see above).

Arch Stable systemd is still in 239 (240 in Testing) and the current kernel went to 4.20 only late yesterday. Arch Stable, to experienced users, is at least as “stable” as Manjaro Stable and even more so than Manjaro Unstable (because that’s where the metal meets the meat).

As an individual Linux user, if not running Arch Stable I would choose to run Manjaro Stable. I believe that is@philm’s point–if you want stabiliity, run Stable.

Both true and not true. Manjaro Unstable users are a nifty testbed for Arch Testing. Using SystemD 240 against kernel 4.20 etc. is of inestimable benefit to myself and others running Arch. All that hard work will eventually coalesce and filter down to Manjaro Stable.

Thank you! :wink:


#17

You can always follow the development of systemd thru the following channels:

And be sure, that Manjaro tries to get the best mixture out of it for sure.


#18

Looks like wpa_supplicant-1:2.7-1 broke my wi-fi… Broadcom Wl DKMS…downgrade restores functionality…


#19

fwupd 1.2.2-1 seems to have some issues. I get systemd errors that the service couldn’t start. Downgrade to 1.2.1-1 fixes it.


#20

Seems already reported: https://bugs.archlinux.org/task/61241. Can you please check if 1.2.2-1.1 fixes your issue?


[Unstable Update] 2019-01-02 - Pacman, Pamac, Budgie, Deepin, Systemd, Haskell, Python