On Sat, Apr 11, 2020 at 12:03:42AM -0700, Foppe de Haan wrote:
> I'm running Qubes 4.1. My experience with the KDE version (and display
> stack) included with Qubes 4.0 /fedora 25 wasn't that great either. :)
I see. Thanks!
/Sven
--
public key: https://www.svensemmler.org/0x8F541FB6.asc
On Saturday, April 11, 2020 at 2:01:05 AM UTC, Sven Semmler wrote:
>
> On Fri, Apr 10, 2020 at 02:54:01AM -0700, Foppe de Haan wrote:
> > I may prefer my meagerly hardware accelerated KDE 5.17/18 in dom0 until
> > it's clear under which circumstances GPU virtualization works properly.
>
>
On Fri, Apr 10, 2020 at 02:54:01AM -0700, Foppe de Haan wrote:
> I may prefer my meagerly hardware accelerated KDE 5.17/18 in dom0 until
> it's clear under which circumstances GPU virtualization works properly.
Forgive me from taking this off-topic from the original thread. I have
tried and
sounds promising. :)
One question: (when) will the gui-domain be made 'mandatory' in qubes 4.1?
I may prefer my meagerly hardware accelerated KDE 5.17/18 in dom0 until
it's clear under which circumstances GPU virtualization works properly.
--
You received this message because you are
Amazing. :-D
Can we have control of audio output from appvms from Qubes Manager? For
example, to create new appvms by default with audio off and to switch it
on/off from Qubes Manager GUI? I'm about attack vector to our 3th party
devices like mobile phones near Qubes machine when some appvm
