The officially official Devuan Forum!

fanderal

Member

Registered: 2017-01-14

Posts: 80  

elogind update problem

Running Ceres and did an update in aptitude. Was on fluxbox desktop when xorg quit and dropped to the console. Got no response from the keyboard and had to do a hard reboot. After reboot, no problem logging in or running X.

No display mgr; a console login with .xinitrc and .xserverrc to start X.

This is a week old Beowulf netinstall upgraded to Ceres. Xserver-xorg-core is installed with xorg's dependencies, but not xorg. Xserver-xorg-input-evdev is installed but not xserver-xorg-input-mouse or -keyboard.

If it matters: both /var/log and ~/.local Xorg.0.log files show a USB-PS/2 connection for the Logitech mouse and keyboard, but both are normal USB connections and there are no PS/2 ports on the mobo.

If more info is needed please let me know.

/var/log/aptitude

Aptitude 0.8.13: log report
Wed, Oct 27 2021 07:31:55 -0700

Will install 5 packages, and remove 0 packages.
========================================
[UPGRADE] elogind:amd64 246.10-2 -> 246.10-3
[UPGRADE] libelogind0:amd64 246.10-2 -> 246.10-3
[UPGRADE] libpam-elogind:amd64 246.10-2 -> 246.10-3
[UPGRADE] libxapian30:amd64 1.4.18-3 -> 1.4.18-4
[UPGRADE] rsyslog:amd64 8.2108.0-2+devuan1 -> 8.2110.0-1+devuan1
========================================

Log complete.

In console when X stopped

Fatal server error
(EE) systemd-logind disappeared (stopped/restarted?)
(EE) Please also check the log file at "/home/me/.local/share/xorg/Xorg.0.log"
(EE) (II) AIGLX: suspending AIGLX clients for VT switch
(EE) Server terminated with error (1). Closing log file.
XIO: fatal IO error 104 (Connection reset by peer) on X server ":0"

~/.local/share/xorg/Xorg.0.log
https://pastebin.com/RpWU1S0X

ending lines in /var/log/Xorg.0.log

[ 75916.451] (II) No input driver specified, ignoring this device.
[ 75916.451] (II) This device may have been added with another device file.
[ 75942.318] (II) evdev: Logitech USB-PS/2 Optical Mouse: Close
[ 75942.318] (II) UnloadModule: "evdev"
[ 75942.318] (II) systemd-logind: releasing fd for 13:67
[ 75942.353] (II) evdev: Logitech Logitech Illuminated Keyboard Consumer Control: Close
[ 75942.353] (II) UnloadModule: "evdev"
[ 75942.353] (II) systemd-logind: releasing fd for 13:66
[ 75942.373] (II) evdev: Logitech Logitech Illuminated Keyboard: Close
[ 75942.373] (II) UnloadModule: "evdev"
[ 75942.373] (II) systemd-logind: releasing fd for 13:65
[ 75942.389] (II) evdev: Sleep Button: Close
[ 75942.389] (II) UnloadModule: "evdev"
[ 75942.389] (II) systemd-logind: releasing fd for 13:69
[ 75942.405] (II) evdev: Power Button: Close
[ 75942.405] (II) UnloadModule: "evdev"
[ 75942.405] (II) systemd-logind: releasing fd for 13:68
[ 75942.421] (II) evdev: Video Bus: Close
[ 75942.421] (II) UnloadModule: "evdev"
[ 75942.421] (II) systemd-logind: releasing fd for 13:64
[ 75942.453] (II) evdev: Power Button: Close
[ 75942.453] (II) UnloadModule: "evdev"
[ 75942.453] (II) systemd-logind: releasing fd for 13:70
[ 75942.512] (II) Server terminated successfully (0). Closing log file.

Debuser2018

Member

From: Muvattupuzha

Registered: 2018-01-24

Posts: 117  

Website

Re: elogind update problem

Seatd is already available in Dadalus. Is it ready for replacing elogind?

Head_on_a_Stick

Member

From: London

Registered: 2019-03-24

Posts: 3,125  

Website

Re: elogind update problem

Running Ceres

Then why are you booted into chimaera's kernel version? Looks like the "upgrade" didn't work properly...

After reboot, no problem logging in or running X

So X wouldn't start immediately after the update but it's fine now? Seems a bit silly to start a thread about a problem you are no longer experiencing. What are you hoping to acheive here, exactly?

Last edited by Head_on_a_Stick (2021-10-27 18:57:25)

---

Brianna Ghey — Rest In Power

fanderal

Member

Registered: 2017-01-14

Posts: 80  

Re: elogind update problem

Seatd is already available in Dadalus. Is it ready for replacing elogind?

I don't know, but thanks for the tip.

fanderal

Member

Registered: 2017-01-14

Posts: 80  

Re: elogind update problem

Running Ceres

Then why are you booted into chimaera's kernel version? Looks like the "upgrade" didn't work properly...

More for vanity at the moment... the 4.19.X kernel series boots to the desktop at 85MB while the 5.10.x and 5.14.x boot to 105MB and 110MB. The modules keep growing in number and size. One example:

module   4.19.0-18    5.10.0-9     5.14.0-3
i915     1736704     2711552     2965504

Kernel modules aren't my forte but I'm looking into what I might do.

So X wouldn't start immediately after the update but it's fine now? Seems a bit silly to start a thread about a problem you are no longer experiencing. What are you hoping to acheive here, exactly?

I got dropped to the console (Server terminated with error) as aptitude completed the install. At that point, in the console and without a working keyboard, I had to reboot. Booted to the OS and all was working again.

Might seem silly, yes, but I never had an update knock out the desktop... not in the years with Debian and not for the last several years with Devuan. It didn't seem to qualify as a bug and too involved for chat, so I posted it for whatever it's worth. Maybe something, maybe nothing.

Magnus

Member

From: Stockholm, Sweden

Registered: 2020-03-14

Posts: 54  

Website

Re: elogind update problem

This happens to me every time I upgrade Elogin on Ceres. The latest time was yesterday or the day before. But I agree that it's a little annoying to have to do a hard reboot. But I have never had any problems due to hard reboot. If it is possible to avoid a hard reboot I will be pleased.