Hit a bug in 4.0.1-rc2 I haven't been able to reproduce (yet)

[John Smiley]

Posting here in case anyone else has seen this:

I started a fedora-29-dvm instance to test keepass (as opposed to the outdated keepassx that comes installed with the fedora-29 template), installed it, launched it from xterm, and poked at it for a bit. Part of the poking included clicking the link to their site in the Help menu and then I opened some new tabs from there, so I had the parent dvm running xterm, a GUI keepass (v2) child, and a Firefox grandchild.

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?

[brenda...@gmail.com]

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

[John Smiley]

I have not created an issue in qubes-issues since I don't have a repro case. Without that, there's nothing much the devs can do to fix it. If I do find a repro case, I'll open an issue.