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

passive popups sent from VMs look weird #1267

Closed
adrelanos opened this issue Oct 4, 2015 · 2 comments
Closed

passive popups sent from VMs look weird #1267

adrelanos opened this issue Oct 4, 2015 · 2 comments
Labels
C: core R: duplicate Resolution: Another issue exists that is very similar to or subsumes this one. T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality.
Milestone

Comments

@adrelanos
Copy link
Member

Currently if Debian [or Fedora] VMs dispatch passive popups... Examples:

  • kdialog --passivepopup test
  • notify-send test

These look weird.

Feature Request:
Integrate them with Qubes Manager. Show these popups like the usual starting vm-name alike popups as dispatched as usual by Qubes VM Manager.

Security Considerations:

  • Would that be secure?
  • If not, how else this could be designed to stay user friendly?

This is important for Qubes-Whonix usability. However, it looks like a general Qubes issue. Unspecific to Whonix.


Background:

At the Tor summer dev meeting, I discussed with @bnvk, that in future the only popups by Whonix should be the following.

  • 1.: starting sys-whonix (dispatched as usual by Qubes VM Manager)
  • 2.: sys-whonix started (dispatched as usual by Qubes VM Manager)
  • 3.: Tor bootstrap in progress. (dispatched by sys-whonix whonixcheck)
  • 4.: Tor bootstrap done. (dispatched by sys-whonix whonixcheck)

@bnvk, @mfc agreed, that those should use the same notification mechanism as Qubes uses.

@qubesuser
Copy link

Regarding Whonix in particular, it might be a good idea in general to only popup messages in case there is a problem, as opposed to the current behavior of having both whonixcheck and timesync popup dialogs unconditionally.

In the "normal" Whonix case it's not much of an issue, but with 10+ Whonix VMs it becomes annoying.

@marmarek
Copy link
Member

marmarek commented Oct 4, 2015

This seems to be a duplicate of #889. There is even a prototype of such service.

@marmarek marmarek closed this as completed Oct 4, 2015
@marmarek marmarek added R: duplicate Resolution: Another issue exists that is very similar to or subsumes this one. T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality. C: core labels Oct 4, 2015
@marmarek marmarek added this to the Release 3.1 milestone Oct 4, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C: core R: duplicate Resolution: Another issue exists that is very similar to or subsumes this one. T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality.
Projects
None yet
Development

No branches or pull requests

3 participants