Skip to main content ↑ ↓
Topic: Sometimes Updating Restarts X (Read 1244 times) previous topic - next topic
0 Members and 2 Guests are viewing this topic.

Sometimes Updating Restarts X

Hello all,

I have been using Artix Linux s6 since January and have an issue that I didn't have with Artix Linux runit. Sometimes when updating, my desktop environment disconnects and, I'm not sure if it is technically a crash, brings me back to my DM. This happens whether I use a DM like lightdm, or if I use a console-based one like tbsm. When updating, the screen kicks me out of my desktop environment and shows me the initial TTY that you see when starting the computer from grub.

I'm not sure where to look and diagnose this issue, but it happens frequently enough that I now only update from a TTY where it seems this issue doesn't happen. What I'm worried about most is doing an update and then hurting my system because the terminal that was running the "pacman -Syu" command gets destroyed and failed to finish an update properly. I usually go to /var/log/pacman.log and reupdate/reinstall what I just updated to make sure things were properly installed.

Does anyone have any tips for fixing this or suggestions of where to look to diagnose? Thanks!

Re: Sometimes Updating Restarts X

Reply #2 –
I'm not sure, I haven't seen elogind or udev in the updates that cause the system to stop the X server. I will pay more attention to what is updated next time though and post here.

Is it normal for elogind and/or udev updates to restart things like the X server or DM?

Re: Sometimes Updating Restarts X

Reply #4 –
It's entirely possible that a service restart of elogind or lightdm would cause X to restart. However, this shouldn't actually be happening. I haven't updated those services or any of their dependencies since 2022 (when I change those, I try to make sure this doesn't happen).

If you have a /var/log/pacman.log snippet of an update when a restart happened, we could probably pinpoint what package caused it.

Re: Sometimes Updating Restarts X

Reply #5 –
I will update normally until this happens and then I will upload the /etc/pacman.log snippet. Thank you all very much for your help and hopefully I can find an example soon!

Re: Sometimes Updating Restarts X

Reply #6 –
Okay, I had the issue happen today after installing a package.

Here is a pastebin of pacman.log

Re: Sometimes Updating Restarts X

Reply #7 –
Is that really the full log? I don't see how anything there could cause this. Not even the udev hook should do it.

Re: Sometimes Updating Restarts X

Reply #8 –
/usr/share/libalpm/hooks/30-udev-reload.hook
calls
Exec = /usr/share/libalpm/scripts/udev-hook udev-reload
/usr/share/libalpm/scripts/udev-hook udev-reload
contains
Code: [Select]
udev-reload)
        udevd_live
        /usr/bin/udevadm control --reload
        /usr/bin/udevadm trigger
        /usr/bin/udevadm settle
    ;;
    *)
sudo /usr/bin/udevadm trigger
reliably kills Xorg here.

https://bbs.archlinux.org/viewtopic.php?id=285241
Links to a few bugs etc.

Gist seems to be it's affecting people with evdev entries in their xorg.conf files. Which is me.

This in the Xorg log
Quote
[ 91758.916] (II) LoadModule: "evdev"
[ 91758.916] (WW) Warning, couldn't open module evdev
[ 91758.916] (EE) Failed to load module "evdev" (module does not exist, 0)
[ 91758.916] (EE) No input driver matching `evdev'
[ 91758.916] (II) Falling back to input driver `libinput'

I'm just about to try commenting out the entries but I'll post now lest I kill X and lose what I've written.....

Edit:
Well there you go silly me.
I had evdev liberally splattered throughout xorg conf files that have followed me around for years (I use a separate layout for triple screen gaming so do need them).
And I didn't have xf86-input-evdev installed!

Installed it and the problem seems to be gone.

Re: Sometimes Updating Restarts X

Reply #9 –
Interesting find. If OP has that issue too, then in that case s6 isn't relevant at all and just a weird red herring.

Re: Sometimes Updating Restarts X

Reply #10 –
Quote from: Dudemanguy – on
Interesting find. If OP has that issue too, then in that case s6 isn't relevant at all and just a weird red herring.
Yeah I'd be surprised if S6 is relevant? It just happened to be the init OP uses. I'm fairly confident our problems are/were related.

It kicked in for me a good few days after I saw the first post above about it. But I'd done no updates for quite a while as I put them off waiting to see how the repo merging was going to pan out. Which was very well it seems.

Re: Sometimes Updating Restarts X

Reply #11 –
Quote from: Dudemanguy – on
Is that really the full log? I don't see how anything there could cause this. Not even the udev hook should do it.

Unfortunately, yes this is the full log of installing the package and bringing my xorg down.

As far as what gripped is saying, I did have success in bringing down xorg by running "sudo /usr/bin/udevadm trigger", but I could only do it once interestingly. It seems like it only happens sometimes when it's ran. Interestingly, I don't have that same error that gripped had in their Xorg log. I also don't really have any Xorg config files in my home directory (or at least, not that I know of).

EDIT: After reading what happened with https://bbs.archlinux.org/viewtopic.php?id=285369, I do have two files  (/usr/share/X11/xorg.conf.d/10-evdev.conf and /usr/share/X11/xorg.conf.d/10-quirks.conf) that reference evdev.

Maybe should I try to delete these files and see what happens? I can make backups before doing that.

Re: Sometimes Updating Restarts X

Reply #12 –
"10-quirks.conf" is a default file. That shouldn't be causing any problems. You can try getting rid of the 10-evdev.conf one. No idea where that came from.

In case it's not clear, "udevadm trigger" isn't supposed to crash xorg. :P

Re: Sometimes Updating Restarts X

Reply #13 –
Okay, I have moved it to a backups folder in case I need it back for any reason. I will keep updating and see if I still find an xorg crash. Thanks for the help!

Re: Sometimes Updating Restarts X

Reply #14 –
Quote from: brandflake11 – on
Okay, I have moved it to a backups folder in case I need it back for any reason. I will keep updating and see if I still find an xorg crash. Thanks for the help!
If you try running
Code: [Select]
sudo /usr/bin/udevadm trigger
multiple times and there is no crash you should be good.

If you want to be cautious then another alternative to switching to a tty to update is to do the update in a tmux session tmux. Then if X dies the update keeps running. That's what I started doing once the issue started.