Reg Tiangha: > On 06/15/2017 01:53 PM, Zrubi wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA256 >> >> On 06/15/2017 06:34 PM, Reg Tiangha wrote: >> >>> Curious: For those apps that exhibit that behavior, are they >>> running on Debian 9 or Fedora 25 templates? >> Nope. >> Fedora 24 mainly, and Debian 8 >> The later is only for sys-net, so all my taskbar icons coming from a >> F24 based template. >> > Thanks. I don't really use Fedora, but I'll set up a test VM once my > laptop is finished converting this Debian 8 template to 9. Can you list > some apps that this happens with so I can test across a variety of > templates? I'm still leaning towards an X issue, but maybe it's always > been there since Fedora 24, even under kernel 4.9. But I would assume if > that was the case, then more people would have spoken up by now. >>> Since it works fine in Debian 8 (I haven't tested much with any >>> Fedoras), I'm wondering if it's less a kernel issue and more of an >>> issue with newer X or how Qubes integrates with newer X (but I >>> guess if it works properly on 4.4, it may be a combination of the >>> three; don't know how to fix it though). >> Maybe it is a know issue, but: >> online netvm change on a disposable VM is also broken on the latest >> 4.9 VM kernel. (Qubes Manager shows it is changed, but not working in >> practice) >> > I've *never* ever had this work for me (although it might have worked > once in R3.0 or something old like that); I've always had to shut down > the Disp VM first, alter the dvm template, and then start up a new one > in order to change NetVMs.
I have no problem with this myself. 3.2, kernels 4.4, 4.9, 4.10. The difference I think is that my dvm templates net-vm is set to none, so each dispvm I start which requires net access is set manually. Is it common for you or others to change a given dispvms net-vm more than once? Im just curious. >>> I can't play around with this until later today, but in the >>> meantime, what graphics hardware are you running, Zrubi? And which >>> version of 4.4 are you running where things work fine? And finally >>> if you can, if it's an Intel card, can you try booting with this >>> kernel option to see if it makes a difference? >>> >>> i915.preliminary_hw_support=0 >> I believe this setting will not affect this chipset. But will try if I >> have a chance. (This is my only Qubes Laptop atm and using it for >> production) >> >> HW details: >> >> Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz >> Intel Corporation Broadwell-U Host Bridge -OPI [8086:1604] (rev 09) >> Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 >> >> SW versions: >> Qubes 3.2 >> xen: 4.6.5 >> kernel: 4.4.62-12 >> > It might; if you could try it in both dom0 and vm (and maybe different > combinations if you have the time), that'd be useful to help rule things > out. It's toggled on by default to work around this: > > https://www.phoronix.com/scan.php?page=news_item&px=intel-skl-prelim-support > > but maybe it's no longer an issue with 4.9. > > > -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/b40cbfad-5eb1-3c2d-802f-6b62e5521f45%40riseup.net. For more options, visit https://groups.google.com/d/optout.
