New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Qubes systray pop-up is too short #3369

Closed
tutaleedoo opened this Issue Dec 7, 2017 · 2 comments

Comments

Projects
None yet
2 participants
@tutaleedoo

Qubes OS version:

Qubes release 4.0 (R4.0)

Affected TemplateVMs:

dom0


Steps to reproduce the behaviour:

  1. Start 2 or more VMs
  2. Left-click or right-click the Qubes icon in the systray

Expected behaviour:

  • As many VMs are displayed as possible (limited only by the height of the screen)
  • The pop-up is scrollable only if the list of VMs cannot fit within the height of the screen

Actual behaviour:

  • The behaviour is inconsistent, but usually the pop-up is scrollable and only displays one or two items at a time

General notes:

  • It's difficult to work with the systray pop-up when only one or two items are displayed at a time
  • Scrolling is done by mouseover, and it's very easy to scroll past items when the pop-up height is tiny

Related issues:

@tutaleedoo

This comment has been minimized.

Show comment
Hide comment
@tutaleedoo

tutaleedoo Dec 7, 2017

To better illustrate my point, I've attached a screen shot
systray

To better illustrate my point, I've attached a screen shot
systray

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Dec 15, 2017

Member

This appears to be a duplicate of #2970. If you believe this is not really a duplicate, please leave a comment briefly explaining why. We'll be happy to take another look and, if appropriate, reopen this issue. Thank you.

Member

andrewdavidwong commented Dec 15, 2017

This appears to be a duplicate of #2970. If you believe this is not really a duplicate, please leave a comment briefly explaining why. We'll be happy to take another look and, if appropriate, reopen this issue. Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment