Solved: Issue with systemd-235 package in Main-Testing repo

Colin · October 26, 2017, 4:13pm

Ok I was updating my base system not yet a new install.

ben79 · October 26, 2017, 4:28pm

And I forgot to mention that I was in a fresh install, fully updated except for the systemd packages. Installed from ISO # 1510.

FWIW: Once I got the systemd-235 install fixed system boots without issue. I did while I was in chroot run --replacepkgs and reinstall all of the systemd-235 packages just to be sure nothing was missed.

Colin · October 26, 2017, 4:30pm

Ben christann’s update crashed X too he is all Intel as I think you are. My box is AMD

ben79 · October 26, 2017, 4:32pm

Didn’t Intel used to be a good brand? Kidding, I think.

christopher_tanner · October 26, 2017, 4:35pm

My update crashed on 2 intel boxes. One with intel graphics and one with ATI.

Colin · October 26, 2017, 4:37pm

We can’t ship the iso’s with 235 unless we release it into the updates repo which means then we will start breaking peoples boxes.

Colin · October 26, 2017, 4:40pm

Ben your crash was quite serious and required post boot intervention; we can’t be having that.

ben79 · October 26, 2017, 4:51pm

That’s why I said in another thread “I’m in agreement with Colin, no blockers other than systemd-235.”

Edit: And as said in that thread fixing it is to much for regular users to be expected to do.

TPG · October 26, 2017, 7:29pm

Guys can you please make sure you first updated glib to 2.26-10 then run systemd update.

I need to be sure that issue is related to systemd package and not anything else.

ben79 · October 26, 2017, 8:02pm

I have been installing all other packages first before installing systemd-235.

TPG · October 26, 2017, 9:12pm

Ben can you please provide logs?

ben79 · October 26, 2017, 10:02pm

Yes, I’ll have to reproduce the problem but I can do. I’m guessing we want Xorg, journalctl, and the xorg.session.log. It seems like Xorg.0.log and xorg.session.log are similar or are they? That question is just for my training and education. I’ll post both.

May not get these done till tomorrow AM.

ben79 · October 27, 2017, 5:43pm

Um, I have a system installed on hardware ready to install the systemd-235 packages and when I attempted to install them I find they aren’t there (main-testing) any longer. Anyway I have a hardware system ready to test install these and gather logs.

On a positive note the main-testing repo obviously got cleaned up which was much needed.

christopher_tanner · November 2, 2017, 10:49am

Beware: when my PC updated systemd to version 235-5, the screen went black, and I had to reboot and complete the update by hand.

Chris

TPG · November 2, 2017, 6:35pm

Yes it still does changes the hostname…

ben79 · November 3, 2017, 12:13am

I had same type of crash with rapidly flashing screen and have to force reboot. Same behavior as before.

I did check hostname before install of systemd-235 and after reboot and it was not changed. Is it maybe changing hostname when I install it then hostname is changes back to what’s in /etc/hostname when I reboot?

TPG · November 3, 2017, 8:38am

I’ve set hostname to “openmandriva” everywere it is possible, added traces and now i can say this does not trigger sddm to flash.

Something revokes sddm authorization to Xserver. You can see it in logs.

Oct 23 17:05:16 openmandriva sddm[3991]: /usr/bin/xauth: (stdin):1:  bad "remove" command line
Oct 23 17:05:16 openmandriva sddm[3991]: /usr/bin/xauth: (stdin):2:  bad "add" command line

ben79 · November 3, 2017, 5:05pm

Yes, that has been the error from since this first reported. From yesterdays attempt that sequence is repeated over and over like that is exactly what is flashing, it disconnects, reconnects, disconnects, reconnects, and so on:

Nov 02 18:55:16 ben79-pc sddm[4542]: /usr/bin/xauth: (stdin):1:  bad "remove" command line
Nov 02 18:55:16 ben79-pc sddm[4542]: /usr/bin/xauth: (stdin):2:  bad "add" command line
Nov 02 18:55:16 ben79-pc sddm[4542]: QProcess: Destroyed while process ("/usr/libexec/sddm-helper") is still running.
Nov 02 18:55:16 ben79-pc acpid[3863]: client 9785[0:0] has disconnected
Nov 02 18:55:16 ben79-pc acpid[3863]: client connected from 9800[0:0]
Nov 02 18:55:16 ben79-pc acpid[3863]: 1 client rule loaded
Nov 02 18:55:16 ben79-pc sddm[4542]: /usr/bin/xauth: (stdin):1:  bad "remove" command line
Nov 02 18:55:16 ben79-pc sddm[4542]: /usr/bin/xauth: (stdin):2:  bad "add" command line
Nov 02 18:55:16 ben79-pc sddm[4542]: QProcess: Destroyed while process ("/usr/libexec/sddm-helper") is still running.
Nov 02 18:55:16 ben79-pc acpid[3863]: client 9800[0:0] has disconnected
Nov 02 18:55:16 ben79-pc acpid[3863]: client connected from 9815[0:0]
Nov 02 18:55:16 ben79-pc acpid[3863]: 1 client rule loaded

This is repeated approximately 6000 or so lines in journalctl log.

TPG · November 17, 2017, 8:15pm

Ok with dbus-1.12.2 this issue does not exist.
Can you please confirm ?

Steps to reproduce

update system, make sure you are running dbus-1.12.2 and sddm-0.16.0-4
urpmi.addmedia SYSTEMD http://abf-downloads.openmandriva.org/3.0/container/126098/x86_64/main/release/
urpmi --auto-update --media SYSTEMD
confirm installing systemd-235
Observe if sddm acts strange ?

Colin · November 17, 2017, 9:28pm

sudo urpmi.addmedia SYSTEMD http://abf-downloads.openmandriva.org/3.0/container/126098/x86_64/main/release/
[sudo] password for colin:
adding medium “SYSTEMD”
http://abf-downloads.openmandriva.org/3.0/container/126098/x86_64/main/release/media_info/20171102-080425-synthesis.hdlist.cz
[colin@itchka64 ~]$ urpmi --auto-update --media SYSTEMD

(urpmi:6753): Gtk-WARNING **: Unable to locate theme engine in module_path: “adwaita”,

(urpmi:6753): Gtk-WARNING **: Unable to locate theme engine in module_path: “adwaita”,
medium “SYSTEMD” is up-to-date
detecting looping forever while trying to resolve dependancies.
Aborting… Try again with ‘-vv --debug’ options at /usr/lib/perl5/vendor_perl/5.20.3/x86_64-linux-thread-multi/URPM/Resolve.pm line 1381.

upmi is not happy

So lets try
urpmi --auto-update

(urpmi:6784): Gtk-WARNING **: Unable to locate theme engine in module_path: “adwaita”,

(urpmi:6784): Gtk-WARNING **: Unable to locate theme engine in module_path: “adwaita”,
medium “main” is up-to-date
medium “main updates” is up-to-date
medium “Main32” is up-to-date
medium “Main32 Updates” is up-to-date
medium “contrib” is up-to-date
medium “contrib updates” is up-to-date
medium “contrib32” is up-to-date
medium “contrib32 updates” is up-to-date
medium “non-free” is up-to-date
http://abf-downloads.openmandriva.org/3.0/repository/x86_64/media/non-free/updates/media_info/20171117-210621-synthesis.hdlist.cz
updated medium “non-free updates”
medium “Non-free32” is up-to-date
medium “Non-free32 Updates” is up-to-date
medium “restricted” is up-to-date
medium “restricted updates” is up-to-date
medium “main32” is up-to-date
medium “main_testing” is up-to-date
medium “contrib_testing” is up-to-date
medium “contrib_testing32” is up-to-date
medium “restricted_testing” is up-to-date
medium “non-free_testing” is up-to-date
medium “SYSTEMD” is up-to-date
GOT: kernel-rc-desktop-4.6.0-0.rc7.1omv-1-1-omv2015.0.x86_64
GOT: kernel-rc-server-4.6.0-0.rc7.1omv-1-1-omv2015.0.x86_64
GOT: kernel-release-desktop-4.6.5-2omv-1-1-omv2015.0.x86_64
GOT: kernel-release-server-4.6.5-2omv-1-1-omv2015.0.x86_64
GOT: kernel-release-server-4.13.12-2omv-1-1-omv2015.0.x86_64
GOT: kernel-release-desktop-4.13.11-2omv-1-1-omv2015.0.x86_64
GOT: kernel-release-server-4.13.11-2omv-1-1-omv2015.0.x86_64
GOT: kernel-release-server-4.13.12-1omv-1-1-omv2015.0.x86_64
In order to satisfy the ‘kernel-rc-desktop-4.6.0-0.rc7.1omv|kernel-rc-server-4.6.0-0.rc7.1omv|kernel-release-desktop-4.6.5-2omv|kernel-release-server-4.6.5-2omv|kernel-release-server-4.13.12-2omv|kernel-release-desktop-4.6.5-2omv|kernel-rc-desktop-4.6.0-0.rc7.1omv|kernel-release-desktop-4.13.12-2omv|kernel-release-desktop-4.13.11-2omv|kernel-release-server-4.13.11-2omv|kernel-release-server-4.13.12-1omv’ dependency, one of the following packages is needed:
1- kernel-rc-desktop-4.6.0-0.rc7.1omv-1-1-omv2015.0.x86_64: Linux Kernel for desktop use with x86_64 (to install)
2- kernel-rc-server-4.6.0-0.rc7.1omv-1-1-omv2015.0.x86_64: Linux Kernel for server use with x86_64 (to install)
3- kernel-release-desktop-4.6.5-2omv-1-1-omv2015.0.x86_64: Linux Kernel for desktop use with x86_64 (to install)
4- kernel-release-server-4.6.5-2omv-1-1-omv2015.0.x86_64: Linux Kernel for server use with x86_64 (to install)
5- kernel-release-server-4.13.12-2omv-1-1-omv2015.0.x86_64: Linux Kernel for server use with x86_64 (to install)
6- kernel-release-desktop-4.13.11-2omv-1-1-omv2015.0.x86_64: Linux Kernel for desktop use with x86_64 (to install)
7- kernel-release-server-4.13.11-2omv-1-1-omv2015.0.x86_64: Linux Kernel for server use with x86_64 (to install)
8- kernel-release-server-4.13.12-1omv-1-1-omv2015.0.x86_64: Linux Kernel for server use with x86_64 (to install)
What is your choice? (1-8)

Not sure this is what is supposed to happen.

uname -a
Linux itchka64 4.13.12-desktop-2omv #1 SMP Tue Nov 14 14:40:28 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

Colin