You are not logged in.
Hi,
i have a desktop-pc which runs arch since late 2018. Its an AMD-Ryzen 5-2600 with 32G RAM and a NVidia 1050TI.
Yesterday i made an update with pacman as usual, and after reboot i get a white Screen with a sad monitor telling me, that there is an unrecoverable error.
I looked with jounalctl, and it showed me that the gnome-desktop is causing this error.
I tried to make a downgrade of the Packages that had been updated, but with no luck until now.
Has anyone else having this errors after upgrading, has anyone a solution how to get back to a running system without a complete new installation?
Thanks a lot for your tipps!
Last edited by Minihawk (2022-04-11 17:14:37)
Offline
Bricked because your DE won't start? Ok, sure...
As with every major GNOME upgrade, disable all extensions and themes and see what happens. If that doesn't work, check the log.
Offline
If the above doesn't help, please share the journal from a failed session, as well as your pacman.log -- 'last update' is meaningless in a rolling release distribution. Also please change your topic title to actually describe the problem.
Mod note: moving to NC.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
Hi,
thanks for your answers.
I tried to get Arch running the saturday, with no success, and yesterday i started a new install.
It was very successfull, my home-directory lives on an own partition of a harddisk, so almost anything is working, mails are all there, logins, passwords, and web-browser also has all infos like favourites and login data.
Arch-Linux has so much advantages to a Windows-System, did not spend time on finding download-locations for software and have almost any software installed.
I think of the time i had to use for software-download for the windows-system of my wife... ![]()
Hopefully this installed version will life long and prosper... ![]()
Offline
Thanks for updating your title to be descripitve - this is a good title. But now you could edit it again to prepend [SOLVED] if your reinstall has suitably worked around the issue.
Note that reinstalling for such purposes is generally not advised as it prevents you from learning about the actual cause of the problem, and that learning would likely help you avoid similar problems in the future. Reinstalling likely just kicks the can down the road further and you'll be back with a similar problem soon enough.
Additionally, it can also be a bit frustrating for anyone who has tried to offer help as their efforts are effectively flushed down the toilet. This shouldn't be your primary concern: it's your system, and the primary goal is to have it work. But this is another reason to avoid too quickly "giving up" and reinstalling.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
Its a thing to rescue a system, i have done it several times since my first arch-linux in beginning 2015, and an other thing to get a system running as soon as possible cause ideas are born for new youtube-videos that need to be recorded and broadcasted.
So, please, have this in mind when answering.
Offline