Skip to content

Allow end-users to customize GUI event buffering in Qube ManagerΒ #9861

@ArrayBolt3

Description

@ArrayBolt3

How to file a helpful issue

The problem you're addressing (if any)

Event buffering is now a feature of the GUI daemon, which can be set by modifying the gui-events-max-delay feature for any qube that uses the GUI daemon. Currently this feature can only be used by advanced users who know where to find the documentation for the feature (a blurb in /etc/qubes/guid.conf, which isn't even used by the GUI daemon anymore) and who are willing to fiddle with the qvm-features command in a Dom0 terminal. Whonix-Workstation VMs will hopefully come with the feature set to a reasonable default value of 100 ms once QubesOS/qubes-core-admin-addon-whonix#20 is merged, but just like kloak (the application that inspired the event buffering feature) is useful outside of Whonix, event buffering may be useful as well. Users need to be able to know the feature exists and how to configure it in order to use it.

The solution you'd like

We should provide some easy way to configure this setting, perhaps in Qube Manager.

The value to a user and who that user might be

Users can obfuscate keyboard rhythm biometrics from any VMs they want, regardless of OS, so long as they can interface with the GUI daemon.

Completion criteria checklist

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    C: Qubes GUI toolsThis issue pertains to Qubes GUI tools such as the Qube Manager and Qubes widgets.P: defaultPriority: default. Default priority for new issues, to be replaced given sufficient information.privacyThis issue pertains to privacy in Qubes OS or something controlled by the Qubes OS Project.uxThis issue pertains to the user experience (UX) in Qubes OS.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions