What would you like to see improved in Qubes OS?

[fsflover]

@Hawk

I don’t understand why there are so many anti-sudo comments in the Qubes community.

I am not anti-sudo. I am anti-sudo-by-default.

@Hawk

Developers should build mechanisms that make sudo easily available without security bugs.
With these options, users might choose to have sudo without a password.

I agree.

The corresponding topic:

Passwordless sudo, SELinux - understanding security logic

Hi, I know there are many old threads in which this has been discussed. I have spent quite a few hours trying to find the answers to my own questions in them, but it seems I can’t. So, I hope it is OK to ask what interests me in particular. Please note, I am not questioning the authority or the expertise of the author. Not at all. I am willing to understand the logic of all that, as I am not an expert. Please also note that I have already read multiple times the well-known answers “you can di…

[rustybird]

@alimirjamali

This will also show the outdated sign for unnamed (disp*) disposables. Doesn’t it? Which might make user believe that its name (or even worse, its private volume) might somehow survive the restart.

Yes, with that pull request the Domains widget would show the outdated volume status for all disposables - same as Qube Manager. IMO it’s important to pass this information to the user, e.g. consider a browsing session in a disp1234 disposable that hasn’t picked up a security patch for the browser.

Maybe there’s a better icon for something being outdated/stale/old than ? Something that doesn’t imply a restart. (Although even with the PR, the Domains widget still wouldn’t offer the Restart action for disp1234 disposables - same as Qube Manager again.)

[alimirjamali]

It is possible to exclude unnamed dips* qubes via something like:

if vm.klass == "DispVM" and vm.auto_cleanup:
    # do not show icon code here

Overall. this is a mildly debated issue which is hard to keep everyone satisfied. Power users are usually comfortable with this since they properly understand the under-hood mechanism with or without the icon. Let’s see what decision the core team takes on this.

[kenosen]

@rzg

with other options like Journalist AppVM

My understanding, from the Qubes Summit, is that additional templates, packages, and VMs could potentially bloat an already large ISO. That is why additions like extra templates and specific AppVMs are best provided through Salt scripts from external, trusted sources like FPF.

[mparsa]

Back to KDE.

I think KDE Activities is a more convenient way to handle Qubes’s compartmentalization.

It’s a pain having to install with XFCE and then install KDE.

At least there should be the option to choose between XFCE or KDE during installation.

[barrulus]

you can create in memory disk, templates and appvms.
Create a RAM drive on startup, give it a btrfs filesystem, create a sub volume on it, set up a storage pool and clone template to the ram disk and then create appvm. Everything is now on RAm for that vm. copy the file system to use in
reboot script. QubesVM manager will pick it up as son as it’s all copied back in. (sounds complex but it’s no different to adding a new drive)