(regression) 6.4 allows to accidentally hibernate twice, and hibernation takes much longer

[calestyo]

Distribution

Debin unstable

Package version

6.4.5

Graphics hardware in use

Intel Alder Lake

Frequency

Always

Bug description

Hey.

I've just upgraded on Debian from previously Cinnamon 6.2 to 6.4 and quite quickly stumbled over the following:

The "shutdown dialogue" is all new (and unfortunately not only better[0]):

Previously when I clicked "Hibernate", it went immediately into hibernation... not for some unknown reason it takes 10-20 seconds till it starts (not till it finishes) with the hibernation (which one can easily recognise on my system as the screen goes off once and CPU goes up)

Because of this, I clicked several times on "Hibernate",... eventually it did hibernate, but when I resumed this morning, it went right back into hibernation after a few seconds.

First I though it crashed, but when I booted again, it resumed again.

So the bugs here are:

1. It takes considerably longer to even start with the hibernation process
2. It allows to queue hibernations, whereas it should discard any further clicks.

Thanks,
Chris.

[0] Why the GNOME style?! It was much better before when it was a proper window that could be left open, while one could still interact with other windows, and that had a title bar with which it could be moved.

Steps to reproduce

see above

Expected behavior

see above

Additional information

No response

[fnetX]

Aside / reply to your footnote remark

Hi there,

while I am not involved with the Cinnamon or Linux Mint development, maybe you want to consider this from a usability perspective to understand why this behaviour change was added. I initially thought that I'd agree to your comment and that having a proper window had advantages, but upon thinking a little, I see little reason for this. On the contrary.

It was much better before when it was a proper window that could be left open, while one could still interact with other windows, and that had a title bar with which it could be moved.

Feel free to elaborate (we could switch to a private chat or a discussion to not clutter this conversation) about your need to interact while the dialog is open.

In general, it is very useful to let dialogs draw all the attention, because otherwise, you end up with typical issues like:

• A dialog is opened but hides below another window (or another window pops over it) so the user doesn't find it.
• Users inadvertently open a dialog without noticing, which is especially dangerous if there is e.g. a shutdown timer, or if they inadvertently press "Enter" on the wrong focused window.
• Users get distracted before they are able to complete an operation. Maybe not for the system shutdown dialog, but this can happen for others. For example if a dialog asks for a confirmation, a message just pops in, you reply to the message and forget what you initially wanted. I have witnessed this behaviour in the past and interface design tries to find solutions to avoid user distractions very often.

On the other side, what is the issue with closing the dialog again when you still want to interact with something? It reduces the danger to inadvertently interrupt this (e.g. when pressing a key on the wrong focused window which can happen due to workspace switching, password manager autotype, or otherwise when doing mistakes during manual focus switching?

Why do you need the dialog to remain open rather than close it and reopen when you are done with the work?

I hope you can get used to the new design.