-more support for external mics 3.5m and thunder bolt type-c things like headsets
-Invidia supported template for graphic designers, I mean ability to use apps like davinci resolve on it
-poweroff device when laptop lid is closed
thanks a lot for devops and core-team
I’ll give this one a spin, next time i need it! I like the Big Red Button in my tray too
Would like to add another thing i forgot in my above list.
- in Qubes Manager View Columns we could use a Last Modified/Started/Access whatever Field.
Sometimes i do minor changes in lesser used AppVMs, like changing the AppVM Name and this would help tremendously to keep backups up to date and not miss such minor changes. (After all this years i have never had any need for restoring a backup but it does feel good to actually have them.)
This last suggestion would go a long way towards supporting an incremental backup. (I.e., a command that only backs up qubes that have been accessed (or modified) since the last backup.)
- Better performance like when Qubes 4.0 was around.
- Since I use i3wm, I would appreciate the possibility to install Qubes either without a window manager or with i3wm directly.
I would like qubesos to have a better/smoother integration with i3wm and awesomewm, too.
Another thing that i forgot,
- Qubes Updates (tray Sun icon) should update specific Templates first (whonix-gw) and optionally restart (sys-whonix) before proceeding with with any of the other dom0/template updates.
Just running to every motherboards. Everybody hate the HCL.
Improved support for potato hardware would be a nice bonus, specially when the CPU has to do two jobs for the price of one. I don’t need a GPU if it’s going to mess up my security. Then again they may have fixed this recently, I hear the new Qubes has xfce by default…
That is like saying, “i want to fly to the Moon with my Tricycle”. If the hardware does not support secure virtualization there is no real safe way currently to make this happen.
The GPU problematic is being worked on in the LINUX community but if the Hardware Manufacturer does not supply open source drivers you should voice your concerns with each of them, nothing Qubes OS can do about it.
You always have the option to passthrough GPU that though requires working IOMMU / secure virtualization able Hardware otherwise the point of secure compartmentalized Qubes VMs becomes pointless.
Do you really need to remove this ME stuff?
I run Qubes on 13980HX, and windows 10 VM feels very responsive and snappy. I guess im happy with it.
- Undervolting of CPU. Under Linux I can undervolt my CPU by -160mV and get +300Mhz performance boost. For a CPU-based OS, it is must have.
- More colors
- Screenshots inside VM
See this thread.
I’d like to see better changelogs, it’s currently hard to guess what changed between 4.1 and 4.2, and the item list in the RC announcements are really vague.
8 posts were split to a new topic: Install software in templates
- I will find it nice that the default’s icons of the XFCE templates will be the same as those of Dom0. Like that, we’ll find a similar desktop in the sys-gui and sys-gui-gpu sessions.
- Have the Documentation available in other languages (I’m from France and sometimes, it was difficult to understand it even with translation’s sites. I can help for that if you want.
I think a lot of people miss it! lol But from what I could understand, it seems quite difficult
Unfortunately, it seem very difficult for these reason:
for hardened sys-usb and sys-net check liteqube.
here is my wishlist. qubes is awesome btw , thanks for working on it
in order of importance
1- full support for machine sleep / standy using s0x sleep state (i believe this has upstream dependency on xen to support fully). many modern laptops don’t support s3 sleep so this is a must have.
2-fido support for login (hardware key)
3-improved change management for dom0 - snapshots, rollbacks, etc.
4-optimize backups (incremental vs full backup).
suspend/resume compatibility improved a lot in the incoming 4.2 release