Yesterday dnfdragora upgraded several items. I saw the list showing a lot of things concerning Cinnamon.
Before shutting down the computer I let dnfdragora update all of those, then I went to bed.
Looks like the update introduced a regression. Would be good to find out what packages got updated and then file a bug against the one that causes the error.
sudo dnf history info last
tells you more about the last transaction. sudo dnf history info last-1 for the previous one and so on. sudo dnf history info 25 for transaction no. 25.
sudo dnf history
gives you the whole history of transactions.
Use
sudo dnf history undo last
to undo the last transaction. If that fixes the problem, update the packages one by one and check which one introduces the error (or if you post a list of updates packages, we may be able to tell which one could cause this behaviour).
Bunch of cinnamon updates, no idea which one is responsible.
I took a very brief look on the Cinnamon bug tracker (assuming this is the right one), and it looks like this bug has been reported. Subscribe to the bug to get updates on fixing the issue or temporary workarounds.
Yes, this package is working its way through the system. Note that this affects only the Cinnamon Spin (Fedora Workstation=GNOME, not Cinnamon). It was actually an upstream problem and not caused by the Fedora maintainer.
Note that in this case, the maintainer has set ‘Stable by Karma = 1’ which is very unusual (usually it’s 3) but this is a very simple fix. So if just one person leaves (positive) karma, the fix will get pushed to the stable repository so that everyone will get it within a day or so rather than having to wait a week (‘days to stable = 7’ which is how long to wait before stable if no one leaves karma).