[OBSOLETE] The bunsenlabs 'exit' menu entry

xaos52 · 2016-04-02 12:17:46

This is a request for user feedback on the bunsenlabs exit functionality, more specifically the dialog window we show when selecting the exit option from the main menu.

As it is, we don't provide a 'Hibernate' functionalty.
If you are interested in this, and you want your opinion to count in a couple of decisions we have to make, please answer following questions;

Q1. Would you use that functionalty?

Q2. For 'Hibernate' to work, you need to set up adequate swap space.
When the swap space is not sufficient to hibernate, choose one of the options below:

1. I don't want to see the hibernate button.

2. I do want to see the hibernate button. When I click on it I want to see a dialog window
pop up with a short explanation as to why the function is not working. Pressing any key
will destroy both the popup window and the buttons window.

3. I do want to see the hibernate button. When I click on it, the screen with the buttons will
be destroyed, an error message will be written to $HOME/.xsession-errors, but there
will be no visual user feedback explaining why hibernate did not work.

4. I do want to see the hibernate button, but I want the button disabled (greyed out), not
clickable.

We would appreciate your feedback very much.

Thanks

Last edited by johnraff (2019-02-20 02:46:02)

kozimodo · 2016-04-02 14:03:55

Q1: I do not typically use hibernate

Q2: If I do not have enough swap space, I do not want to see the hibernate button.

tynman · 2016-04-02 14:19:52

Q1 - Yes

Q2 - option 1

Sector11 · 2016-04-02 15:20:51

Q1 - No

Q2 - 1. I don't want to see the hibernate button.

EDIT: Q2 - 1 is my option. I was going to suggest some of the suggestions that follow as well:

IE: should be visible.

If I may since I am not a programmer ...

Is it possible to have a "section in the "Welcome" script" that asks:

Do you want to use Hibernate: Yes | No
- You chose 'No' - Do you want to see the [Hibernate] button anyway (it will be deactivated): Yes | No

Just a thought.

Last edited by Sector11 (2016-04-02 18:27:39)

Horizon_Brave · 2016-04-02 15:22:49

Q1: Hmm I personally wouldn't need it, I VM most of my Bunsen boxes. And the one BunsenLabs I have install on actual hardware I have on a laptop. So usually I just shut the lid. xD BUT that being said, I think for others, who aren't in my use case scenario, should have the option to see the hibernate button. What is the good of hiding it? Who benefits from that?

Q2: It should be there for people to see, AND provide a clear explanation as to why it wouldn't work if they don't meet the minimum need for the swap space required amounts. The point should be to provide an option, as well as keeping the user informed as to what it actually happening and why it's happening, not to just show something and mask what it's doing. If they or us want that then move to Windows 10.

o9000 · 2016-04-02 17:32:31

Q1 I don't use hibernate

Q2 It should be there. Option 2 seems best.

damo · 2016-04-02 18:45:37

I don't use Hibernate.

Option 2 seems OK, if it only appears when Hibernate is a possibility.

ghorvath · 2016-04-02 18:47:49

I personally do not use hibernate that often, but I already rewrote bl-exit on all of my machines to have it if I need it. Thus

Q1: Yes, absolutely, please put in hibernate.

Q2: I know it was not among the options, but maybe greyed button and if mouse is hovered over it then some explanation on why that is not working.

Further: if the user realizes that they want to use hibernation but cannot because of insufficient swap space, it may already be too late. I know bunsenlabs uses the debian installer, but maybe it could be modified so somewhere the user could be notified to have enough space if want to use hibernation?

Sector11 · 2016-04-02 19:11:38

Actually ghorvath brings up a good point.

Better to have something and not need it than not have it and need it.

After all, it's only a [Button].

johnraff · 2016-04-03 06:05:20

xaos52 wrote:

Q1. Would you use that functionalty?

Maybe sometime in the future, on a laptop. I can't see any reason for a desktop to have Hibernate.

Q2. For 'Hibernate' to work, you need to set up adequate swap space.
When the swap space is not sufficient to hibernate, choose one of the options below:
1. I don't want to see the hibernate button.

This option please. I don't want to see a non-functioning button whenever I shut down.

damo wrote:

Option 2 seems OK, if it only appears when Hibernate is a possibility.

My understanding was that the options in the 2nd question were for what to offer when Hibernate is not a possibility.

Head_on_a_Stick · 2016-04-03 09:45:28

xaos52 wrote:

Q1. Would you use that functionalty?

No.

xaos52 wrote:

1. I don't want to see the hibernate button.

^ This.

Horizon_Brave · 2016-04-03 15:25:23

Again, what's the harm though, is displaying a hibernate button, as long as their is a reason explaining why a particular user can not use it? If anything it'll be more informative, perhaps aiding them in their decision for their next install, to use more swap if they want that sort of thing.

torq · 2016-04-03 15:54:06

Q1. Would you use that functionalty?
No.

Q2:
I don't want to see the hibernate button.

PackRat · 2016-04-03 21:02:27

ghorvath wrote:

I personally do not use hibernate that often, but I already rewrote bl-exit on all of my machines to have it if I need it. Thus
Q1: Yes, absolutely, please put in hibernate.
Q2: I know it was not among the options, but maybe greyed button and if mouse is hovered over it then some explanation on why that is not working.
Further: if the user realizes that they want to use hibernation but cannot because of insufficient swap space, it may already be too late. I know bunsenlabs uses the debian installer, but maybe it could be modified so somewhere the user could be notified to have enough space if want to use hibernation?

+1

Eraph · 2016-04-04 00:10:42

xaos52 wrote:

Q1. Would you use that functionalty?

I use suspend all the time, I might be inclined to use hibernate if I'm travelling so it would be good to know it's there.

xaos52 wrote:

Q2. For 'Hibernate' to work, you need to set up adequate swap space.

I'll go with:
2. I do want to see the hibernate button. When I click on it I want to see a dialog window
pop up with a short explanation as to why the function is not working. Pressing any key
will destroy both the popup window and the buttons window.

becker_11 · 2016-04-04 13:13:13

Answers

Q1: No
Q2: option 1

tknomanzr · 2016-04-04 19:43:39

I was wondering, would hibernate actually work in conjunction with light-locker? The whole purpose of hibernate to my way of thinking is to save session state, which will be lost anyway once light-locker kicks you back to the login screen.

To be fair, I can get hibernate to work but have yet to get my laptop to come resume back from a hibernate.

SO atm I don't care about hibernate and am of the opinion you don't show users options they dont have in any gui design.

Last edited by tknomanzr (2016-04-04 19:44:15)

johnraff · 2016-04-05 08:26:54

tknomanzr wrote:

I was wondering, would hibernate actually work in conjunction with light-locker? The whole purpose of hibernate to my way of thinking is to save session state, which will be lost anyway once light-locker kicks you back to the login screen.

I'm not sure if that's necessarily true. Suspend, for example, while requiring a password login, does return to the previous session as it was (at least on my laptop), so why not hibernate too?

That said, I agree about not showing users non-functional options. (if they prove to be non-functional)

xaos52 · 2016-04-05 09:36:34

I'm not sure if that's necessarily true. Suspend, for example, while requiring a password login, does return to the previous session as it was (at least on my laptop), so why not hibernate too?

That is correct.
Coming from hibernate state, your system reboots. Early in the reboot process it detects that it has to wake from hibernate, and it restores the memory image it has from the swap space - which includes your session state of course, and launches lightdm to ask for your password. There is no interaction/clash with light-locker.

That said, I agree about not showing users non-functional options. (if they prove to be non-functional)

Which means the program needs to test each option before it shows the gui. It is possible of course, but it means checking if a feature will work before you know which feature the user intends to use. Testing all buttons functionality while only one button can be clicked. And this testing has be done every time the bl-exit screen is shown.

There is also the inhibitor locks to take into account.
Which allows you to inhibit system reboot while for instance your system backup is running.
Do you want bl-exit not to show any of the buttons when an inhibitor has been taken?

Horizon_Brave · 2016-04-05 16:56:47

xaos52 wrote:

Which means the program needs to test each option before it shows the gui. It is possible of course, but it means checking if a feature will work before you know which feature the user intends to use. Testing all buttons functionality while only one button can be clicked. And this testing has be done every time the bl-exit screen is shown.

But what about running BL in a VM? If I put my Host PC to Sleep or perhaps hibernate, (or just closing the laptop lid) how will that effect the "test" to check for the functionality of the buttons?

#1 2016-04-02 12:17:46

[OBSOLETE] The bunsenlabs 'exit' menu entry

#2 2016-04-02 14:03:55

Re: [OBSOLETE] The bunsenlabs 'exit' menu entry

#3 2016-04-02 14:19:52

Re: [OBSOLETE] The bunsenlabs 'exit' menu entry

#4 2016-04-02 15:20:51

Re: [OBSOLETE] The bunsenlabs 'exit' menu entry

#5 2016-04-02 15:22:49

Re: [OBSOLETE] The bunsenlabs 'exit' menu entry

#6 2016-04-02 17:32:31

Re: [OBSOLETE] The bunsenlabs 'exit' menu entry

#7 2016-04-02 18:45:37

Re: [OBSOLETE] The bunsenlabs 'exit' menu entry

#8 2016-04-02 18:47:49

Re: [OBSOLETE] The bunsenlabs 'exit' menu entry

#9 2016-04-02 19:11:38

Re: [OBSOLETE] The bunsenlabs 'exit' menu entry

#10 2016-04-03 06:05:20

Re: [OBSOLETE] The bunsenlabs 'exit' menu entry

#11 2016-04-03 09:45:28

Re: [OBSOLETE] The bunsenlabs 'exit' menu entry

#12 2016-04-03 15:25:23

Re: [OBSOLETE] The bunsenlabs 'exit' menu entry

#13 2016-04-03 15:54:06

Re: [OBSOLETE] The bunsenlabs 'exit' menu entry

#14 2016-04-03 21:02:27

Re: [OBSOLETE] The bunsenlabs 'exit' menu entry

#15 2016-04-04 00:10:42

Re: [OBSOLETE] The bunsenlabs 'exit' menu entry

#16 2016-04-04 13:13:13

Re: [OBSOLETE] The bunsenlabs 'exit' menu entry

#17 2016-04-04 19:43:39

Re: [OBSOLETE] The bunsenlabs 'exit' menu entry

#18 2016-04-05 08:26:54

Re: [OBSOLETE] The bunsenlabs 'exit' menu entry

#19 2016-04-05 09:36:34

Re: [OBSOLETE] The bunsenlabs 'exit' menu entry

#20 2016-04-05 16:56:47

Re: [OBSOLETE] The bunsenlabs 'exit' menu entry

Board footer