This is a discussion topic for the following Common Issue:
You can discuss the problem and its solutions here, but please note that debugging and technical feedback should primarily go to the issue trackers (e.g. Bugzilla) linked in the Common Issue, because that’s the place that developers watch, not here.
If there are any updates/changes/amendments for the Common Issue description, which you believe should be performed, please post it here.
Please see the Common Issue for solution/workarounds:
I hardly see this as a solution, a workaround at most.
What I want is to get the OS like it was before: I never had a shutdown interruped/blocked since day 1 when I installed F38.
You mention april 15. Here, it started yesterday, may the 29th and possibly is related to F42, cinnamon, systemd or the kernel 6.14.6.
The bugzila report is more than 1 month old and still this bug hasn’t been fixed.
$ shutdown now
Operation inhibited by "user" (PID 2693 "cinnamon-sessio", user user), reason is "user session inhibited".
Please retry operation after closing inhibitors and logging out other users.
'systemd-inhibit' can be used to list active inhibitors.
Alternatively, ignore inhibitors and users with 'systemctl poweroff -i'.
$ uname -a
Linux user 6.14.6-300.fc42.x86_64 #1 SMP PREEMPT_DYNAMIC Fri May 9 20:11:19 UTC 2025 x86_64 GNU/Linux
How do you close inhibitors anyway?
What other users?
If systemd had put in place a way to inhibit something, it must have an easy way to revert it.