I’ve been running Tumbleweed on this computer for several months. There has been a persistent but intermittent problem on shutdown, where Tumbleweed will hang on the last screen before shutdown with the Gigabyte Motherboard screen displaying with the Tumbleweed logo at the bottom, and will never shutdown. I’ve tried to remedy this by researching on the internet and haven’t yet hit on the complete solution. I added the last two parameters to the grub configuration, as such:
They made the problem better, but the computer still hangs with the Gigabyte Motherboard screen displaying with Tumbleweed at the bottom and won’t shut down, just less frequently.
I’m running:
Tumbleweed 20230502
KDE Plasma version 5.27.4
KDE Frameworks Version 5.105.0
Qt Version 5.15.9
Kernel Version 6.2.12-1-default (64bit)
Graphics Platform X11
I look forward to the forum’s help to fix this.
Mark
tags last evening, but haven’t been able figure out how to get them to work with a bash console readout. I’ve created a paste of the readout which I hope will provide the information you requested, in a similar format.
To use PRE tags, click the </> icon above the input window.
There’s nothing in inxi output that I recognize would cause the problem.
You might try appending plymouth=0 or noplymouth or plymouth.enable=0 to the linu line at the Grub menu after striking the E key, to keep boot and shutdown in framebuffer text mode, to see if it helps. If it works, uninstall plymouth, or append it to the GRUB_CMDLINE_LINUX_DEFAULT= line in /etc/default/grub so that next grub.cfg regeneration (via grub2-mkconfig, or YaST, or kernel removal or installation), will include it.
Can you please switch all nvidia services to manual and reboot.
Mine is a bit different from what you have because i installed the nvidia-persistenced.
I’m not sure what you were referring to regarding not posting commands. In the paste https://paste.opensuse.org/pastes/90e6cc5283bc
please note that the command inxi -Faz is included as the first line on the paste.
In the other two pastes showing the plymouth logs, I opened the two logs up in Dolphin. I individually did a “select all” from the drop-down list, then I copied them to paste them in susepaste. There were no commands to produce the output, it was information already present in the logs.
Results from after the computer failed to shutdown. I had to shutoff power to the computer because it hung on the Motherboard manufacturer display screen with the Tumbleweed logo at the bottom.
As User
~> journalctl --user -b -1 -u init.scope -g ‘Start|Stopped’ -o short-monotoni
c --no-pager
A quick question. How much time have you given it to shut down? In Leap and now only recently in Tumbleweed I sporadically get a delayed shutdown that I have never been able to trace, even with considerable troubleshooting instruction. The system runs a 90 second timer while trying to shut down something that is not shutting down normally (apparently). Once the 90 second timer ends, shutdown proceeds normally. I’m not asking for assistance. Just pointing out a possibility if you have not given it considerable time to shut down.
Yea, I’m seeing that behaviour too on one of our [four] TW machines. It’s sporadic, and there’s nothing obvious, so I just turn my attention elsewhere - it shuts down without issue, about 60 second later.
.
.
To @Munguasafiwe … have you tapped the ESC key at GUI shutdown screen to see the terminal output ?
How long have I waited for it to shut down?
Sometimes I haven’t caught the failure to completely shutdown because I was tired and went to bed immediately upon shutting down the computer. When I looked at the computer 6-10 hours later it still hadn’t completely shutdown, remaining hung up on the Motherboard Manufacturer’s Logo Screen with the Tumbleweed name and logo at the bottom of the screen. I’ve tried to wait to see if the computer would shutdown when this problem first started happening, but found no matter how long I waited it wouldn’t shut down.
Have I tapped the ESC key at GUI shutdown screen to see the terminal output?
I think I have some months ago, but I don’t remember for sure. I’ll try it again the next time I get a boot failure and post the results here.
If you wait until the boot failure, the system may not respond to the ESC key. It’s best to tap ESC as soon as you see the GUI-based Shutdown screen (usually displayed within a couple seconds of confirming the shutdown).
That way you can watch the detailed scrolling shutdown output at a console screen … and hopefully the last few lines at lock up might provide a clue.
