Unfortunately the useful stack trace is to the right of what you quoted from the journal. Can you try again to get the full stack trace? You can use --no-pager to avoid opening it in less if that would help. Maybe something like journalctl -e --no-pager | tail. There’s probably a better way…
Communicating with Fedora Legal is impractical for Fedora contributors, so what I would do is just ask Fedora Council and expect them to do so if required. If Council says this documentation would be permitted, then let’s do it.
Different vm, same result. journalctl -e --no-pager | tail shows:
Mar 26 21:29:59 vbox-f42 gnome-shell[2226]: endSessionDialog: No XDG_SESSION_ID, fetched from logind: 2
Mar 26 21:30:04 vbox-f42 gnome-session-binary[2148]: Entering running state
Mar 26 21:30:04 vbox-f42 gnome-shell[2226]: Gio.IOErrorEnum: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dio_2derror_2dquark.Code19: Vorgang wurde abgebrochen
Stack trace:
asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:114:23
@resource:///org/gnome/shell/ui/init.js:21:20
However, on the other vm, which currently doesn’t boot (different topic), I am sure there was nothing else open. I report back if I get the “first” vm to boot.
This is a bug in gnome-shell. It’s unfortunate that the stack trace isn’t very good, but you do have the full stack trace, so that’s enough for a bug report. The issue tracker is here; please report it if you can’t find anything similar reported previously. Thank you!
I’ve noticed that very occasionally that my laptop with Fedora 42 Beta will look like it shutdown but when I take it out of the backpack the next day the battery is completely empty. The display turns off and it looks “off” but I suspect some small piece of hardware is still using power. The only fix I have it to watch the shutdown text scroll and make sure I see the actual “hardware will power down now” or whatever that final message is. I think if I actually see that then it does shutdown entirely.
The stronger fix I have is to shutdown, then repower up, press Esc to get into the Grub menu and then power off again. That proves that the OS is not involved at all and that I’m powering off via the hardware only (using the physical off switch).
Yes, both machines are updated daily.
I was able to reproduce the bug on my “first” vm.
Machine is not shutting down, gnome-session-inhibit -l says:
No inhibitors
BTW, I think what you experienced with existing inhibitor is also a bug (maybe the [same) - my understanding was that you can still hit the “Shutdown” button and override the inhibitor (for example unsaved text files).