Recently when updating via yay, sometimes when an update is installed I get booted back to the login screen. It only seems to happen when it’s a regular pacman update as opposed to an AUR package, and even then I don’t think it’s every time.
I haven’t been able to figure out a pattern yet, but it’s definitely happening during the pacman part of the update as the AUR packages are left untouched and I have to run the update process a second time after logging back in.
I’m using the latest version of KDE Plasma as my DE, and login is handled by SDDM.
Have same issue, which sucks, recent log-out during update/upgrade screwed up my system - initramfs not found when boot Now - switching sadly to Manjaro for more stable system, or if that too fails, simple Arch. Cheers
EndeavourOS is pretty much the same as “simple Arch”, just with a GUI installer that configures stuff for you with rather sane defaults (apart from soystemd-boot and dracut, which are the only opinionated deviations from “vanilla”).
Manjaro is much more opinionated, and I would say, much less “stable”, especially if you’re using the AUR, since the repos on Manjaro are retarded.
So did you hijack this thread just to tell us that or are you actually wanting to get help with your issue?
only time my system has ever logged out on its own is when my power management did it. so there could be other factors going on that just happen to co-inside with an update. maybe posting your logs and giving more information about the issue would help get it resolved. But please enjoy your stay with Manjaro if that is what you feel is best for you.
instead of discussing to switch Distro caused by a random error we could try find out what is the actual issue
if this is causing it ?
pacman -Qi desktop-file-utils
Name : desktop-file-utils
Version : 0.27-1
Description : Command line utilities for working with desktop entries
Architecture : x86_64
URL : https://www.freedesktop.org/wiki/Software/desktop-file-utils
Licenses : GPL
Groups : None
Provides : None
Depends On : glib2 libglib-2.0.so=0-64
Optional Deps : None
Required By : gtk2 gtk3 gtk4 handbrake libreoffice-fresh mpv openoffice-bin simplescreenrecorder
softmaker-office-2024-bin thunar
Optional For : None
Conflicts With : None
Replaces : None
Installed Size : 204,35 KiB
Packager : Jan Alexander Steffens (heftig) <heftig@archlinux.org>
Build Date : Sa 07 Okt 2023 01:33:36 CEST
Install Date : Di 10 Okt 2023 15:11:43 CEST
Install Reason : Installed as a dependency for another package
Install Script : No
Validated By : Signature
or something else… never had such thing (but i am also fully on dracut only)
would be intersting to know the used Desktop too.
Well, since this was the only topic on the issue on the internet, wasnt too old, and wasnt solved despite logs provided, yes, thought i’d highjack it.
I have fresh install 2 weeks old.
Its been sharply and suddenly logging me off during updates before as well, even right after clean install… but since i didnt look what was going on in terminal, i dont know exactly at what point during the process.
This time though it managed to mess up whole system. I can resolve it, sure, but … yeah.
from my short research it could be update-desktop-database.hook causing kde to crash ? there are some mimetype implementation issues lately on kde caused by some general updates.
In case possible to catch the journal from the timepoint of the logout…
In my case it happens also when simply installing app, for example yay -S audacious, and it did finish the install, so why log out at the end, no idea.
There were a few releases during 2023 so this tells us absolutely nothing.
You fail to follow any directions anyone has given you. How are we supposed to help you solve your issue if you continue to disregard any advice given?
If you want any help ask a question and give good information about what exatcly done when the issue happen.
If you do not know how ask how to provide the needed info.
But stop to post without providing any useful info.
This is not a general issue. The initial post is 2 month old already…
System was up to date before installing audacious?
Any changes to the default install done?
You do have EndeavourOS installed at all at the moment?
Yeh, sorry, anyway … I managed to gather some focus to put together this log file: http://ix.io/4MAW
It happened during audacious install (and later during deadbeef install as well, if my memory is correct)
System is pretty much very up to date yes
Changes to the default install? … no i dont think so, very basic
Yes I am still on Endeavour, I like it. I did arch-chroot into it, and reinstall ‘linux’, quick fix
Now - switching sadly to Manjaro for more stable system, or if that too fails, simple Arch. Cheers
