On Friday, November 4, 2016 at 6:34:57 PM UTC+1, John Maher wrote: > On Thursday, November 3, 2016 at 12:50:13 AM UTC-4, Andrew David Wong wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA512 > > > > On 2016-11-02 08:56, John Maher wrote: > > > On Thursday, October 27, 2016 at 12:42:18 AM UTC-4, Andrew David Wong > > > wrote: > > > On 2016-10-26 15:53, Gaijin wrote: > > >>>> On 2016-10-26 13:38, John Maher wrote: > > >>>>> On Wednesday, October 26, 2016 at 9:05:48 AM UTC-4, Gaijin wrote: > > >>>>>> On 2016-10-26 12:43, John Maher wrote: > > >>>>>>> I'm getting the strangest thing on my screen. I'll be working and > > >>>>>>> the > > >>>>>>> XScreenSaver dialog pops up (indicating the screen is locked) and > > >>>>>>> the > > >>>>>>> screen goes black. However, the screen is not locked. I have to > > >>>>>>> move a > > >>>>>>> window around to redraw my screen. This has always happened since I > > >>>>>>> started using Qubes about 3 weeks ago. There appears to be no > > >>>>>>> pattern > > >>>>>>> that prompts this response. Bizarre! Any thoughts? > > >>>>>>> > > >>>>>>> Thanks. > > >>>>>>> > > >>>>>>> John > > >>>>>> > > >>>>>> Yeah. I had the same thing happen when I upgraded to R3.2 as well. I > > >>>>>> asked the same thing but nobody replied. > > >>>>>> https://groups.google.com/forum/#!topic/qubes-users/xjHi2TcYBAQ > > >>>>>> > > >>>>>> It still happens from time to time. Seems to happen less if I have a > > >>>>>> lot > > >>>>>> of free memory. Closing down some memory hungry AppVMs seems to > > >>>>>> lessen > > >>>>>> it, but I haven't been able to specifically replicate it. > > >>>>> > > >>>>> Interesting, because I think I have more than enough memory (32 GB). > > >>>>> Thanks. > > >>>> > > >>>> I've got 16GB myself. It's not that the memory is full, but it seems > > >>>> to happen more when I have a lot of VMs open in one desktop. That may > > >>>> just be a coincidence though. > > >>>> > > >>>> I'm glad to see it wasn't just me though. I never had this happen with > > >>>> earlier versions of Qubes on the same hardware. Not sure if it might > > >>>> be the XFCE or a video driver issue. (I've never installed the nVidia > > >>>> drivers.) > > >>>> > > > > > > Thank you both for reporting this. Gaijin, I'm sorry I missed your thread. > > > > > > Just to confirm: Are you both using Xfce4? > > > > > > Tracking the issue here: > > > > > > https://github.com/QubesOS/qubes-issues/issues/2399 > > > > > > > > > Sorry for the delay in responding. I used the default install for 3.2. > > > > > > I also just noticed that it appears that memory is not being purged when > > > apps are closed. Today when I "woke up" the screen from one of these odd > > > screen saver like issues, it very briefly displayed a browser window with > > > a site I was on yesterday. I looked carefully and confirmed that I did > > > not actually have that window open on my system. It's as if something > > > from yesterday's memory was sent to the screen and then closed. Rather > > > disconcerting. > > > > > > John > > > > > > > I don't think that should necessarily be disconcerting. The Qubes security > > model does not include or rely upon purging memory at any particular time > > interval. It assumes that you, the authentic single user, should be the > > only one with access to dom0's screen content. So, the fact that you're > > allowed to see your screen content from yesterday doesn't constitute any > > violation of the security model. You're still the same trusted user as you > > were yesterday. (If I've misunderstood your concern, please let me know.) > > > > - -- > > Andrew David Wong (Axon) > > Community Manager, Qubes OS > > https://www.qubes-os.org > > -----BEGIN PGP SIGNATURE----- > > > > iQIcBAEBCgAGBQJYGsH3AAoJENtN07w5UDAwKtIP/2vblyc4Rf9uwU3M+WGv2K7V > > T7VoTDfGjB8XWyX6LZW/TrtameFmAj/Rb0bINOrIWpkrP9RdNUm+0/BR10NkcLul > > FqaxMOcl2u2Tk775VjYtC+Z7y1ycJDQjaMvtqrdDQkeGhMumzcDOHD9RufTFSIRm > > 8ke7GxfMQBH7R0DJ5E26B7HZJg73k1RKFT5BbpmKrfHxBBEaJTUALeNFZnp2ekl+ > > HrRV4u8+T/Tbwzha5e/iTvJEVTMcMxzD4uziaN+TfiK2Iwp40w0W8IdmRjPzdkLI > > +PDhAfjpQCEcZIPT/V+u6GsMhUDJo5ABPs/as17YY4b8VMwm9F7/J2Oo6nfwl/Rh > > gOnwVLFQKUtq3iaNbORDzAjBSEny6wYKlfvpL3IWGAHhH0mbP5j1ivSJoF+navuD > > qPMvMyAuhFh7hSsTPJ0CTMrDZYTGVlSryLrvXUwl5Lf6zplXRxO6uGu3ruUnepxR > > 9izVXApPBv/Cc41G3wrCUGN3deE1OpzNSxhQS+NK4B3kJSGAm4+Zi/F/B8yiR6Lt > > L/DiLI04X1LZ/XW+ZrKKiQbqVKAzeDqkDPW1D4POEckQnEfPqMcc32LzQVf6ORvX > > Xzjn+UhUcdTzINAuISwYeBdvBTk6Wk80T80nChZJdnSdWi6klvbcof96UNdD3sja > > swBLAb3aU4hobRxFAcL7 > > =Fv0E > > -----END PGP SIGNATURE----- > > If the memory that temporarily renders to the screen is as isolated from > other appvms as expected rendered content (like an open windows), then, yes, > I'm not concerned about leakage from one environment to another. > > I will say that it is simply disconcerting to see it display, security > implications aside. More important to me, though, is the hope that this > "screen saver" triggering will go away on future updates. Let me know if > there is anything I can do to help that process. > > John
Hi all, I'm having the exact same issue both on my previous qubes installation and the current one. It seems to get worse when I have browser windows open, and it continues even if I disable hardware acceleration. There is a bug tracker entry for this issue: https://github.com/QubesOS/qubes-issues/issues/2399 The screenshot shows exactly what I'm seeing too. It's very annoying and probably not an issue with graphics drivers. If there is anything I can do to help solve it, I'd be happy to do so. --Opal -- 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/f3423c30-70c7-4270-a469-6c730d3ffb1c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
