On Monday, December 24, 2018 at 5:19:57 PM UTC-5, John Smiley wrote:
> Posting here in case anyone else has seen this:  
> 
> I started a fedora-29-dvm instance to test keepass
...
> When I was finished, I terminated the parent dvm expecting that the child and 
> grandchild would be removed along with it.  Instead I was left with two 
> windows (the keepass window and the Firefox window) that would not close.  
> The dvm instance was gone, but two dead windows were left behind.  
> 
> I was writing up the qubes-issues bug report when I found that repeating the 
> steps I just described worked as you would expect (all children of the parent 
> dvm were removed when the parent was terminated).
> 
> I ended up having to reboot the host to get rid of the dead windows.
> 
> Anyone else run into anything like this?

I ran into the same bug Monday, but...I think it was a fedora-26 DVM? 

I have a screenshot with the dead window and xltop showing that the particular 
VM in the window title was not running. I'm running R4 (installed from 4.0 
release image), fully updated through -testing repository on dom0 and all 
templates.

Did you open an issue in qubes-issues? If so, let me know the ID and I'll 
contribute to the thread there with a screen shot, at least.

Thanks,
Brendan

-- 
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 qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/d7a7cc9c-c851-40de-ba2e-a0cf0cde2a9e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to