GUIs always add complexity to troubleshooting. What you show doesn’t provide evidence and isn’t conclusive either.
- Show the following as I suggested ALREADY above:
erlangen:~ # systemctl list-unit-files lvm*
UNIT FILE STATE PRESET
lvm2-lvmpolld.service static -
lvm2-monitor.service disabled enabled
lvm2-lvmpolld.socket disabled enabled
3 unit files listed.
erlangen:~ #
- Show the full journal of the failing boot by running
journal --boot ..... and pasting both the command line and the output.
systemctl list-unit-files lvm*
UNIT FILE STATE PRESET
lvm2-lvmpolld.service static -
lvm2-monitor.service disabled enabled
lvm2-lvmpolld.socket enabled enabled
3 unit files listed.
journal --boot
If ‘journal’ is not a typo you can use command-not-found to lookup the package that contains it, like this:
cnf journal
Please be more specific regarding the command you wish me to run. It seems that journal --boot is not correct. Had you intended this command?:
journalctl -b -1 -u init.scope -g ‘Start|Stop’ -o short-monotonic --n
o-pager --boot
If so, please look at this paste:
https://paste.opensuse.org/pastes/83bcc02a7f5e
In the event you intended this:
journalctl --boot -b -1 -u init.scope -g ‘Start|Stopped’ -o short-monotonic --no-pager
here is the output
https://paste.opensuse.org/pastes/06048f81d132
Sorry. I meant journalctl --boot -1.
journalctl --boot -1
May 10 11:13:52 localhost kernel: microcode: updated early: 0x42 → 0xf0, date = 2021-11-12
May 10 11:13:52 localhost kernel: Linux version 6.3.1-1-default (geeko@buildhost) (gcc (SUSE >
May 10 11:13:52 localhost kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.3.1-1-default root>
May 10 11:13:52 localhost kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating poin>
May 10 11:13:52 localhost kernel: x86/fpu: Supporting XSAVE feature 0x002: ‘SSE registers’
May 10 11:13:52 localhost kernel: x86/fpu: Supporting XSAVE feature 0x004: ‘AVX registers’
May 10 11:13:52 localhost kernel: x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds regist>
May 10 11:13:52 localhost kernel: x86/fpu: Supporting XSAVE feature 0x010: ‘MPX CSR’
May 10 11:13:52 localhost kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
May 10 11:13:52 localhost kernel: x86/fpu: xstate_offset[3]: 832, xstate_sizes[3]: 64
May 10 11:13:52 localhost kernel: x86/fpu: xstate_offset[4]: 896, xstate_sizes[4]: 64
May 10 11:13:52 localhost kernel: x86/fpu: Enabled xstate features 0x1f, context size is 960 >
May 10 11:13:52 localhost kernel: signal: max sigframe size: 2032
May 10 11:13:52 localhost kernel: BIOS-provided physical RAM map:
May 10 11:13:52 localhost kernel: BIOS-e820: [mem 0x0000000000000000-0x0000000000057fff] usab>
May 10 11:13:52 localhost kernel: BIOS-e820: [mem 0x0000000000058000-0x0000000000058fff] rese>
May 10 11:13:52 localhost kernel: BIOS-e820: [mem 0x0000000000059000-0x000000000009efff] usab>
May 10 11:13:52 localhost kernel: BIOS-e820: [mem 0x000000000009f000-0x00000000000fffff] rese>
May 10 11:13:52 localhost kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000c6617fff] usab>
May 10 11:13:52 localhost kernel: BIOS-e820: [mem 0x00000000c6618000-0x00000000c6618fff] ACPI>
May 10 11:13:52 localhost kernel: BIOS-e820: [mem 0x00000000c6619000-0x00000000c6619fff] rese>
May 10 11:13:52 localhost kernel: BIOS-e820: [mem 0x00000000c661a000-0x00000000ce679fff] usab>
May 10 11:13:52 localhost kernel: BIOS-e820: [mem 0x00000000ce67a000-0x00000000ce9dffff] rese>
May 10 11:13:52 localhost kernel: BIOS-e820: [mem 0x00000000ce9e0000-0x00000000cea11fff] ACPI>
Well, that didn’t post correctly. Try this instead.
https://paste.opensuse.org/pastes/1aff01d6836c
Hi,
I’ve been 2000 miles away from home working for three months since my last post, so I haven’t used my desktop computer with this shutdown problem for that period of time. I’m home now, and it still doesn’t always shut down correctly. I was counting on the gurus on the forum to come up with a solution in the meantime, but there hasn’t been a single idea proposed.
I would like to fix this problem so the computer shuts down correctly, and I will need the forum’s help to do so. Please send along some fresh ideas.
@Munguasafiwe Welcome back 
So, have you upgraded to the latest snapshot (zypper -vvv dup) and tested it’s still not working?
If you open a terminal and switch to root user and run systemctl poweroff does the system shutdown?
If still not shutting down, the need for you to look at the shutdown in reverse to see the last messages… or paste say the last 30 or so with journalctl -r -b -1 | head -n 30 | susepaste
You’ve been gone for three months. It’s possible your “pastes” have expired.
When shutting down, press ESC key to see what’s on screen … may show something.
Hi,
here’s some answers to the questions asked in the previous posts.
When I press the escape key when the computer won’t shut down, it has locked on the final GUI shutdown screen and the escape key has no effect. I have attempted to try and repeat the test several times in order to try to press the escape key at the very split second that the GUI shutdown screen is presented. However, the computer doesn’t always lockup, it sometimes shuts down normally, just to be perverse and cause difficulties in troubleshooting. I’ll keep trying.
Since I returned home, and before contacting the forum again, I had done a zypper dup a few times over the course of the 1 1/2 weeks I have been home. It had no effect on the shutdown problem. Since receiving the instruction in your post to zypper -vvv dup I have done this twice. I haven’t had the computer lockup on shutdown since, but then that is nothing new. It is a hit or miss thing, as sometimes it locks up and other times it shuts down. I’ll have to let you know when I begin having the problem and provide more pertinent readouts.
Here is the link with the journal readouts for journalctl -r -b -1 | head -n 30 | susepaste
https://paste.opensuse.org/d1d673a4783e
It is only programmed to last an hour before going to oblivion, so here is the readout copied and pasted to susepaste and designated to last for one month. But it seems to be a normal shutdown journal and may not provide the answers you are looking for.
https://paste.opensuse.org/pastes/c0d54400c4e9
I just shut the computer down for the evening, and it refused to shut off. I hit the escape key just as the GUI shutdown screen appeared, and the screen went black for a second then went back to the GUI shutdown screen. It was locked up, and pressing the escape key had no effect. So no luck there trying to get info for a solution.
Here’s the readout for the jounalctl command:
https://paste.opensuse.org/pastes/3c932ab56f68
As before, that susepaste is destined to go to oblivion in 24 hours. So here is the paste copied to produce a paste that will last for a month:
https://paste.opensuse.org/pastes/7b46a2838b8e