Skip to content
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

Menu enhancement in XFCE, window marking for templates. #9666

Closed
new-phone opened this issue Dec 24, 2024 · 2 comments
Closed

Menu enhancement in XFCE, window marking for templates. #9666

new-phone opened this issue Dec 24, 2024 · 2 comments
Labels
P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. R: duplicate Resolution: Another issue exists that is very similar to or subsumes this one.

Comments

@new-phone
Copy link

How to file a helpful issue

The problem you're addressing (if any)

Occasionally I have been in the 'Template' section of the XFCE Q menu, instead of the Apps section. Because named disposables have the same name, formatting and iconography, I have mistakenly launched and used the template, not a dispVM. That browsing is then inherited in any further use of the disposables generated -> privacy breach.

This happens because I am tired and distracted, i.e. human. It has also happened because there is no visual cue in the list of qubes to indicate you're in the App, Template or Services section.

Further, the Q menu does not return to the App section between activations - so you can e.g. open up the Fedora template to install software, then return a few minutes later to launch a dispvm and mistakenly launch the default-dvm from the Template menu instead of the App menu.

"default-dvm" looks exactly the same in Apps and Template menu: red two-box icon, lower case italics on a grey background. The launched qube itself offers very little distinction (e.g. a name in small text that can be too easily overlooked).

The solution cannot be "just be more careful". Qubes uses colored borders exactly to remind users what kind of qube they are using, (e.g. red for disposables) - this concerns the same logic.

The solution you'd like

I'd like a different background shade in each menu section, (App, Template, Services).

For example, the App menu could be as-is, the Template menu use a black background with light text, Services could also be dark but qubes could be outlined in a box.

My aestheics may not please everyone, but whatever it is, there should be a clear, emphatic tonal difference between these menu options, so it feels different to the user.

Another option that might be considered is an intentional dimming of template and service windows. Not too much to be annoying or prevent work, but to be clear to the user its a template window. Or a different border. Something special.

The value to a user, and who that user might be

Saves the privacy and security that Qubes offers from a very simple, easy-to-make mistake.

Completion criteria checklist

(This section is for developer use only. Please do not modify it.)

@new-phone new-phone added P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: enhancement labels Dec 24, 2024
@andrewdavidwong
Copy link
Member

Duplicate of #9655

@andrewdavidwong andrewdavidwong marked this as a duplicate of #9655 Dec 24, 2024
@andrewdavidwong andrewdavidwong added the R: duplicate Resolution: Another issue exists that is very similar to or subsumes this one. label Dec 24, 2024
Copy link

This issue has been closed as a "duplicate." This means that another issue exists that is very similar to or subsumes this one. If any useful information on this issue is not already present on the other issue, please add it in a comment on the other issue. Here are some common cases of duplicate issues:

  • The other issue is closed. The other issue being closed does not prevent this issue from duplicating it. We will examine the closed issue and, if appropriate, reopen it.
  • The other issue is for a different Qubes release. We usually maintain only one issue for all affected Qubes releases.
  • The other issue is very old. The mere age of an issue is not, by itself, a relevant factor when determining duplicates.

By default, the newer issue will be closed in favor of the older issue. However, we make exceptions when we determine that it would be significantly more useful to keep the newer issue open instead of the older one.

We respect the time and effort you have taken to file this issue, and we understand that this outcome may be unsatisfying. Please accept our sincere apologies and know that we greatly value your participation and membership in the Qubes community.

If anyone reading this believes that this issue was closed in error or that the resolution of "duplicate" is not accurate, please leave a comment below saying so, and we will review this issue again. For more information, see How issues get closed.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. R: duplicate Resolution: Another issue exists that is very similar to or subsumes this one.
Projects
None yet
Development

No branches or pull requests

2 participants