you can always read the journal from its db manually too for me it looks similar on shutdown its very short time and basically i can not read anything there. If it seems to hang on shutdown it could be something that needs to get finished gracefully before powering down.
Thanks, yeah, I checked the previous reboot/poweroff logs via sudo journalctl -b -1 and there were no unusual problems recorded during the reboot/poweroff procedure, while as we can see there is something that is not quite right. 
Just tested this on Tumbleweed (which is not based on arch) would that have a config regression too (would be very strange don’t you think) 
journalctl -b -1 -e for the shutdown… 
and see thats a full boot shutdown cycle on my machine (sry no capture card )
Luckily I also used TW and there wasn’t a bug similiar to this one..
-e I know, it just simply jumps to the end of the pager, I like to page it up and down manually, for better control over inspection.
Yeah, that’s the thing I don’t see on my main PC. For 1sec your computer printed out logs during shutdown so, thats what I want to achieve No idea of how or why it works on my testing machine (and on yours aswell), but not for my main PC and for @keescase 's, seems the installs are incosistent then, even if we clearly see its identical? o.O
Sorry I am out of here before I say something very nasty.
1 Like
I do not think so, the difference is basically about what exactly is running while you shut down and related to hardware.
One time i see some logs the next it goes straight to off the process running a shutdown is never the exact same. it follows only the same procedure and stop services properly before powering down the hardware.
Yeah I gotchu. Still it is odd, I mean, for me all of the shutdown procedures go straight to off. I’ve posted this on reddit also, and people also confirm that they’re experiencing similiar odd behaviors lately with the latest updates o.O"
Edit, marking my own answer as solved, to close this thread down, because apparently no one knows what this is… and I’m tired of it.
I do not see anything odd.
Could be simple a change on systems or kernel to faster power down. You could go researching about or go to diff power down journals from 23 times of power down your hardware to find something related
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.