tumultuary Hey everyone all replies are GREATLY appreciated. I recently went out of my way to buy a new Thinkpad a W500 with Libreboot on it.. And i decided to install Solus on it since it's my favorite distro.. But after updating Solus GNOME all the way to catch up on the packages i needed when i entered my encryption key and tried booting into Solus it gave me a white screen that said "Oh no! Something has gone wrong." to make sure it wasn't just my new computer i tried a few other distros and even tried installing Solus on my other computers even my gaming one and they all resulted in the same way.. Does anyone have any advice for me? I've never dealt with this before I'm surprised it happened across 4 computers.. I tried installing budgie as a alternative since it probably has the most support and is also my 2nd favorite DE but it wouldn't even boot into live disk mode apparently.. I haven't used Solus in about 4 months or so but i don't remember having any issues prior to this occurring it's always worked out of the box pretty much.. I dug through some Solus documentation but I'm kinda lost.. As stated above all replies are GREATLY appreciated thank you so much <3
Staudey Did you do a full update (i.e. checked all boxes in the Software Center, or ran sudo eopkg up in the terminal)? Partial updates (picking and choosing which packages to update) are not recommended and can lead to all sorts of problems.
tumultuary Staudey I did a full update yes.. I updated everything i possibly could basically i didn't pick and choose anything.. And no i didn't run "sudo eopkg up" in the terminal i did it via the software center
nolan possibly a failed update caused by software center?, try by terminal, if it fails you will know it sudo eopkg up -y
nolan I forgot, wen you power on your lap, in the screen that shows you "Oh no! Something has gone wrong." press ctl+alt+f2 then login with your user name and password and update from there. Then reboot with reboot
tumultuary nolan Wow i didn't know you could do this! I tried it and it updated a bunch of stuff.. But sadly to no effect it still goes to a white screen that says "Oh no! Something has gone wrong."
brent It's not a great message---I've had it before. Fixed in live iso once reading solus' boot rescue page. Another time I chasesd some github/reddit leads that lead to a happy restoration (all display manager related). 2 times I went down in flames and had to fresh install. BUT I have never duplicated your sequence: boot into tty sudo eopkg up eopkg tells me in terminal that package upgrade was a success I do nothing and then poof! carried out of terminal into white OOPS screen. Always one or the other. if sudo eopkg check or sudo eopkg check | grep Broken | awk '{print $4}' | xargs sudo eopkg it --reinstall do nothing for you then you have to check the status(es) of systemctl services and enable or restart. do a search here for restart lightdm or gdm or whatever you got --- some service checks to try--I don't have in my brain at the end of this day but can be found in a search here.
tumultuary brent Jeez i tried this as well.. Everything checked out absolutely fine.. I'm genuinely starting to think i'm just insanely unlucky but thank you for giving me some resources to try and look further into what i can do <3
brent tumultuary also---of my 4 oops times described above, I was reckless twice and had to reinstall. the solus boot rescue helped once. But in the 'reddit/DM' scenario I remembered it was also NVIDIA/Noveau related: food for thought as far as troubleshooting
njakes There are some notes here when GNOME 40 was in unstable. Perhaps it is worth a read through. https://dev.getsol.us/T9683 If you use Budgie and GNOME and encounter the grey "Something happened" fullscreen window after a reboot and attempt to login, switch to a TTY (typically Ctrl+Alt+F2-9, pick one), login and run sudo usysconf run -f then reboot (sudo reboot). This is associated with the upgrade while on unstable. However, it might be worth running that command.
shingamba If things were working before the update try this: https://getsol.us/articles/package-management/history-and-rollback/en/