Domain '[whichever appVM]': qrexec not connected.

[gameld]

Qubes OS version (e.g., R3.2):

Affected TemplateVMs (e.g., fedora-23, if applicable):

fedora-23

---

Expected behavior:

No issues on startup of appVMs

Actual behavior:

Often when starting appVMs, the dom0 manager will show the yellow warning triangle. When hovering over it, it says "Domain '[whichever appVM]: qrexec not connected"

Steps to reproduce the behavior:

Inconsistent, but only happens when starting the appVMs

General notes:

Usually goes away when restarting the appVM; sometimes takes 2 restarts.

Sometimes dom0 returns an error like:

Line: assert not vm.is_running()
func: start_vm
line.:1171
file: /usr/lib64/python2.7/site-packages/qubesmanager/main.py
----
line: self.caller.start_vm(vm)
func: check_if_vm_has_shutdown
line no.:289
file: /usr/lib64/python2.7/site-packages/qubesmanager/main.py"

This error seems to occur when qrexec doesn't connect multiple times in a row.

[andrewdavidwong]

Please check whether this is a duplicate of #2001.

[andrewdavidwong]

Please check whether this is a duplicate of #2001.

[gameld]

Hello, It appears that this is related to that. I apologize. My searching the bug reports didn't turn this up so I submitted a new one. The only changes I have: I was using the Fedora-23 templates. I am using Qubes 3.2 I was not attempting to open multiple applications in a single appVM. Doing this while opening Firefox in both the Personal and Work VMs at the same time (e.g. after updating the template). Thank you.

…

On 03/05/2017 04:18 AM, Andrew David Wong wrote: Please check whether this is a duplicate of #2001 <#2001>. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#2667 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AIhX4gz6KPBxTpl2U0ONkHwXhYOqanl3ks5rin3RgaJpZM4MTHaa>.

[gameld]

Hello, It appears that this is related to that. I apologize. My searching the bug reports didn't turn this up so I submitted a new one. The only changes I have: I was using the Fedora-23 templates. I am using Qubes 3.2 I was not attempting to open multiple applications in a single appVM. Doing this while opening Firefox in both the Personal and Work VMs at the same time (e.g. after updating the template). Thank you.

…

On 03/05/2017 04:18 AM, Andrew David Wong wrote: Please check whether this is a duplicate of #2001 <#2001>. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#2667 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AIhX4gz6KPBxTpl2U0ONkHwXhYOqanl3ks5rin3RgaJpZM4MTHaa>.

[andrewdavidwong]

I was not attempting to open multiple applications in a single appVM.
Doing this while opening Firefox in both the Personal and Work VMs at
the same time (e.g. after updating the template).

This sounds like it's not a duplicate of #2001, then.

[andrewdavidwong]

I was not attempting to open multiple applications in a single appVM.
Doing this while opening Firefox in both the Personal and Work VMs at
the same time (e.g. after updating the template).

This sounds like it's not a duplicate of #2001, then.

[jpouellet]

I can reproduce the error in case of opening two applications in the same AppVM with 100% reliability (this is a well-known behavior), and have never even once been able to reproduce the error in case of opening two applications in different AppVMs.

@gameld Can you please double-check this is indeed what you experienced, and whether or not it is reliable?

[jpouellet]

I can reproduce the error in case of opening two applications in the same AppVM with 100% reliability (this is a well-known behavior), and have never even once been able to reproduce the error in case of opening two applications in different AppVMs.

@gameld Can you please double-check this is indeed what you experienced, and whether or not it is reliable?