Unable to reboot successfully
Every time I try to reboot through any method, the computer hangs at shutdown with a cursor at the top left of one screen.
It will remain like this indefinitely, until I hard shut down the computer.
Because of this, any rpm-ostree changes like reset or rollback will not take effect because the reboot never successfully finishes.
It is also unable to complete any updates since August 19th due to this.
I've tried key combinations while the cursor is on screen, but to no avail.
50 Replies
Rebooted into ostree:1, and that was able to reboot after hanging at the cursor screen for a minute. I tried running System Update from ostree:1, and now while updating to make it take effect, its hung. Has been for about 10 minutes.
Still able to boot into Ostree:1 as it was. No update took place.
Now I'm too low energy to do TOO much. But after one of the failed reboots you should be able to use
ujust get-logs to see if maybe something was caught in the previous boot cycle which may have something related to the failed reboot. My guess is something to do with the state of the image. Either the layering or using topgrade without the script.
Hard to tell. There're definitely solutions. The problem is finding out the state it's in. (And someone with more energy to help than a slug rolling around in salt i.e. myself atm)I'll get these logs as soon as I'm home from work.
https://paste.centos.org/view/70dc35a4
Finally got the logs... did it right after a failed reboot
can you give an
rpm-ostree status?Unless they changed it should be the middle entry here.
https://discord.com/channels/1072614816579063828/1087140957096517672/1424216406618013716
The top one was their first attempt to reset the ostree so it would start updating again.
hmmm
The reboot issues started then I think. There's some additional context around that post.
if that is present, I don't see any reason that it wouldn't reboot
-# wait why is my dude layering xinput💀
I assume
systemctl reboot has been tried?We were going to fix that after we managed to get him reset.
Like how to brew adb
I don't know actually.
tbf probably would be the same outcome as just pressing reboot in the de
Honestly I'm wondering if one option is to try a rebase if a rebase would wipe the tree out.
Could rebase to the latest update.
well in theory the image will always be byte for byte identical
rpm-ostree reset should already wipe everything
I wonder if its syncthing and/or kde connect
and maybe plasma printmanager
I wonder...you know what's worth a shot?
Logging out and THEN rebooting
yeah, might be worth a shot too
Have plasma already down
-# watch it be stuck in logging out haha
That would at least narrow the problem down to something trapping plasma shutdown!
Which is still better than where we are now :>
very true
Now we just have to wait for them to get home and try it.
And hope that things aren't still running post logout before restart.
@FinnFann @皇家海星 Okay sorry for not being attentive and replying! Yes, systemctl reboot has been tried. I have not tried logging out first, but I can try that. Also, I have noticed oddities with THAT pc not updating with Syncthing the same as my other bazzite device. I can try removing it if the other steps don't work.
I do think it is logging out, based on the state it reaches with the single cursor...
I'm also not opposed to this, as this headache has made me consider wiping and trying a debian distro again. Or Cachy lol
Honestly I just think that the rpm layering went wrong in some fashion.
That's why it's usually discouraged is if it touches too many files god knows what might go wrong with updates.
Usually doesn't go this bad from what I've seen, though.
Yeah... I think I really only NEEDED to do it for icedtea-web, and the others were out of desperation
One of my work programs opens JNLP files to connect to remote devices, and that's... convoluted on bazzite
got an idea
what if you boot
skipping the graphical login & stuff alltogether
How would I go about that
well first go to grub
pres E on the entry you wanna boot
go down to the line starting with
linux
press ctrl+e
this takes you to the end
hit space
add systemd.unit=multi-user.target
hit ctrl+x to boot
this will do it
take you to the text login
no SDDM no plasma no any of that
here you log in do whatever reboot
hopefully worksI greatly appreciate you. I'll try it once I'm home today
Has this been solved? Ive got thr same issue :c
I'm testing right now
And I swear to God it might be the dumbest thing
Will report back soon
Wait, what button do we use to get into grub 😭
Can you get into the uefi? Some dude said his boot order was messed up
It is in fact the stupidest thing. Bazzite can't log out in the reboot process. If I log out, then reboot, it works.
What the fuck.
@FinnFann what in the fuck
resetting rpm-ostree to see if that lets it reboot normally again.
My boot order didn't change anything for this issue. It literally couldn't log itself out.
I havent been able to get into any of the menus yet
You shouldn't need to
Ive rebooted the puter multiple times..
Can you get into Bazzite if you hard shut down and boot up?
No?
Then I don't think you have the same issue this thread is about
This started because I tried to reboot after the screen was flickering
So what is your current issue? For me, I could boot and use Bazzite 100% normally, but I couldn't upgrade or make changes that required rebooting because it would get stuck while shutting down
I turn the puter on
Its that screen.
Lil white blip
Trying to get into the uefi though.
That's different, unfortunately... Yours is getting stuck while booting up, not shutting down. While its booting try spamming F2, F8, F11
One of them will get you into either boot selection or uefi
Maybe if I spam the power button itll work lmfao
That won't do anything
Itll bring hope
Tbh I just dont think my keyboard knows it should be doing somthing
Sounds like on yours, @StuckInAWell SOMETHING in the config got messed up and it causes plasma to hang on logout...
Given the layered packages who knows what might be causing a hang.
BUT if it let you rpm-ostree reset it MAY work properly now
I -think- layered packages can touch root stuff to a very small degree on install.
you cam always
sudo loginctl terminate-user $USER
this should always log you outJust so y'all know... This is still happening after updating. I regularly have to log out before I reboot or shut down, or else it won't actually finish logging out. I'm thinking I may just distro hop to Zorin or something
@皇家海星
looking back at the chat log, my guess is syncthing might be preventing log out
Hmmmm I'll have to try closing it out before I reboot.
Id it helps I just unplugged all my peripherals and it
Worked..
For some reason idfk
Interesting
NGL I installed cachyos on my other nvme and I've been testing that out, and its been so much better. Even runs games better... I'll likely just be sticking with that and wiping out my Bazzite install.