after update no VM 'starts' apps anymore.

[Tom Zander]

Is this a known issue?

I can start a VM using qvm-start, but when I use qvm-run nothing happens, it
hangs forever. Even commands that don't need a X server.
For any qube of the various OSs I run.

The Qubes icons also no longer show in my system-tray.
I can still update dom0 via yum, though. Thats a relief.
Is this a known issue? Can I expect a fix soon?


If not, are there any log files anywhere I can look at?
The only relevant part I found was in qrexec.Work.log some lines saying
"Unable to connect to X server".
Trial and error shows this is due to some timeout, as it only appears after
a substantial amount of seconds.


Would be really happy to get my system properly working again as this is my
work workstation :(


Some related questions;

what is 'anaconda' ? I thought it was the installer, but if it is then why
is it running on dom0?

Is there any way to connect to the VM and get a tty? Think serial-line
fallback.

is it known that grubs advanced menu doesn't get updated when new kernels
are installed?

--
Tom Zander
Blog: https://zander.github.io
Vlog: https://vimeo.com/channels/tomscryptochannel

[awokd]

On Tue, January 30, 2018 12:05 am, 'Tom Zander' via qubes-users wrote:
> Is this a known issue?
>
>
> I can start a VM using qvm-start, but when I use qvm-run nothing happens,
> it hangs forever. Even commands that don't need a X server. For any qube of
> the various OSs I run.

qvm-run works on both powered on and off VMs on my 4.0 on testing repo.
qvm-run works on powered on (only) VMs on my 3.2 stable.

I did notice some weirdness starting things on a recent update but a
reboot cleared it up.

> Is there any way to connect to the VM and get a tty? Think serial-line
> fallback.

Enable Debug mode? Sorry, don't know about your other questions.

[Connor Page]

sudo xl console -t serial Work

[Tom Zander]

On Tuesday, 30 January 2018 02:51:06 CET 'awokd' via qubes-users wrote:
> Enable Debug mode?

I always wondered what this was, anyone know what effect it has to set this
to true?

[Tom Zander]

On Tuesday, 30 January 2018 01:05:39 CET 'Tom Zander' via qubes-users
wrote:

> I can start a VM using qvm-start, but when I use qvm-run nothing happens,
> it hangs forever. Even commands that don't need a X server.
> For any qube of the various OSs I run.
>
> The Qubes icons also no longer show in my system-tray.
> I can still update dom0 via yum, though. Thats a relief.
> Is this a known issue? Can I expect a fix soon?

There were a bunch more updates in the repo 4.0 current-testing this morning
which I applied and I rebooted, but no change.
Still no icons in my systray, still not able to start any apps on any VMs.

does anyone know if its possible to tell qubes-dom0-update to go back to the
stable version (4.0 current instead of testing)?

----

I tried switching one of my VMs back to the previous kernel. No change.
guid log states;
```
Icon size: 128x128
libvchan_is_eof
Icon size: 128x128
domain dead
Failed to connect to gui-agent
```

pacat logs look ok, but nothing shows up in my dom0 mixer app

vchan log has repeated series of;
```
vchan closed
reconnecting
vchan closed
```

qrexec (after a while) has this log
```

Unable to connect to X server
Unable to connect to X server

eintr
```

I'll switch to my old ArchLinux OS, until Qubes gets more stable.

[Tom Zander]

On Tuesday, 30 January 2018 11:19:18 CET 'Tom Zander' via qubes-users wrote:
> There were a bunch more updates in the repo 4.0 current-testing this
> morning which I applied and I rebooted, but no change.
> Still no icons in my systray, still not able to start any apps on any VMs.

Oh, I focused into the issue.

I logged into xfce for 2 seconds and the Qubes app showed up.
Then logging out and logging back into KDE and stuff still works.

If you don't log into xfce you get the attached error from qubes-manager.

Maybe someone made a mistake and used an xfce specific thing?
I'm a bit worried that the system can become so broken.
That thing that logging into xfce started should likely be auto-triggered
and happen, not on login, but on need.


Still really looking forward to Qubes getting more stable...

[awokd]

On Tue, January 30, 2018 1:51 am, awokd wrote:
> On Tue, January 30, 2018 12:05 am, 'Tom Zander' via qubes-users wrote:
>
>> Is this a known issue?
>>
>>
>>
>> I can start a VM using qvm-start, but when I use qvm-run nothing
>> happens, it hangs forever. Even commands that don't need a X server. For
>> any qube of the various OSs I run.
>
> qvm-run works on both powered on and off VMs on my 4.0 on testing repo.
> qvm-run works on powered on (only) VMs on my 3.2 stable.

I ran into an odd issue trying to update today when dom0 was on testing
but whonix-gw was on current. $releasever wasn't getting replaced with the
version number so qubes-dom0-update was trying to pull from
"%36releasever" subdirectory. Switching whonix-gw to testing and updating
first resolved it. Were your templates and dom0 using the same repository
or mixed?

[Andrew David Wong]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 2018-01-29 19:51, 'awokd' via qubes-users wrote:
> On Tue, January 30, 2018 12:05 am, 'Tom Zander' via qubes-users
> wrote:
>> Is this a known issue?
>>
>>
>> I can start a VM using qvm-start, but when I use qvm-run nothing
>> happens, it hangs forever. Even commands that don't need a X
>> server. For any qube of the various OSs I run.
>
> qvm-run works on both powered on and off VMs on my 4.0 on testing
> repo. qvm-run works on powered on (only) VMs on my 3.2 stable.
>

Are you using the `-a` option?

qvm-run -a <vm_name> <command>

This starts the VM if it's powered off, then runs the command in it.
Working fine for me on 3.2.

- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlp6p/MACgkQ203TvDlQ
MDADKw//cWINAKpW/PM44bVJ+hm8iF++MzeH/kG8XNwvWRWWlOQbk0YkByvM5njN
SpWW08MLs8b5X9hQvRzAoJbE1eC4I4jrojXcx2f/FPvCShlIkhwkAoPetFuXl1Zq
HrYxhlbmB8u8efI6w4hTb6Re5iOoCXKGhlUtisvcapc6EGUcg5R9Yc1l6y2KrVES
RPHpNyDJx4ULs7Moqjk9NyjUSy5a0ehklxtzggBuNUg5i6RejyuJ+isHG4TefSn3
gh1rX0JIhhJZc8zgEO9swjQGwYYy45fSmAK6lSB20MHCtQvWwXsVyZ+JR1/p9Lad
Znscp6T5A6Iz3mIAlBRE3+4V8BR3iF8IxS9PfJEkDXnnNCbnKs24hkj/qg42HDMF
1Qx09TS4y3MZLYRZOuVc0TCtnahR3T92RVat1Ne5gtVbU+Hg2EToaZwmAHtLUXoD
nOQLTFCYlw4GuKiigDLjE+edo16G3IUtHjahuydgnl15HRqPjYa33NvdG1hxCIPL
/vUUW9C5Z5ooMYcTpnKEXzpHkaKeOtSxP8NLs0hG0VWyO93VTEbrYdeyzR/alaOm
txyufMGl9gSg21OaPXa4y86l2lN05FRrOsWxRUCRZ+61nE5ZGQxOKiLoEe5F61/u
qA/Nk+VaZSzWAvGbCwDqLDcAfw3KxMCpBZdlPeR2azU8VbY09EU=
=RaBw
-----END PGP SIGNATURE-----

[Tom Zander]

On Wednesday, 7 February 2018 08:17:11 CET Andrew David Wong wrote:
> Are you using the `-a` option?
>
> qvm-run -a <vm_name> <command>
>
> This starts the VM if it's powered off, then runs the command in it.
> Working fine for me on 3.2.

As I wrote, qvm-start works fine, the VM is active and working.

You just can t actually “run” anything on it. The reasons seems to be that
there is some magic thing that starts when you log into xfce4, and only
xfce4.
See the screenshot attached elsewhere in this thread of qubes manager dying
on startup due to the same issue.

Tested on Rc4.

[Andrew David Wong]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 2018-02-07 05:20, 'Tom Zander' via qubes-users wrote:
> On Wednesday, 7 February 2018 08:17:11 CET Andrew David Wong
> wrote:
>> Are you using the `-a` option?
>>
>> qvm-run -a <vm_name> <command>
>>
>> This starts the VM if it's powered off, then runs the command in
>> it. Working fine for me on 3.2.
>
> As I wrote, qvm-start works fine, the VM is active and working.
>
> You just can t actually “run” anything on it. The reasons seems to
> be that there is some magic thing that starts when you log into
> xfce4, and only xfce4. See the screenshot attached elsewhere in
> this thread of qubes manager dying on startup due to the same
> issue.
>
> Tested on Rc4.
>

I was mainly replying to awokd's last sentence in the quoted portion
you left out:

On 2018-01-29 19:51, 'awokd' via qubes-users wrote:
> On Tue, January 30, 2018 12:05 am, 'Tom Zander' via qubes-users
> wrote:
>> Is this a known issue?
>>
>>
>> I can start a VM using qvm-start, but when I use qvm-run nothing
>> happens, it hangs forever. Even commands that don't need a X
>> server. For any qube of the various OSs I run.
>
> qvm-run works on both powered on and off VMs on my 4.0 on testing
> repo. qvm-run works on powered on (only) VMs on my 3.2 stable.
>

Based on the fact that awokd wrote this in reply to you, and your
description (in the quoted portion) leaves open the possibility that
the same issue was affecting you, I included you as a "To:" recipient.

- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlp7uuQACgkQ203TvDlQ
MDAg5BAAw76und38XfkYaE/qp/PrGrMFn73rp5vI73/iOUkT6vi5O0NGBd9hkAky
IrG4Gaqe/fGj1rbX+Dp4J5hcJ+8HTggm8ftcv7/NgjmJ2ClkMKU/oitQinGn45Fo
6mh+X12qm3EjqtNGddg8xdBhKAuI9L428wv4MIjSgTXghkIhXWXRjFae0tHMl8Tl
SkQpGYtsaRAq3NZlJDol7NmRoCctNiCIvOah3VpFxFPgEHFbJ4OUG7BSDz9WwEbW
kakXDZAd1PTvY2BU8+c2rvKmUg9QoriNBEBJziliHtqXg4YPs+dwMIZBZwXAQ6F0
e3KsTr3yD79/iFdIKHAxEY6LfJrp6MgHHULJoGxHjDVc10/cMGVBTNaW+1v5bFbq
cq9fihipZgaTblWGVjlfahBOYzRPZRvzhO5SljR4B4kRpUSEEkA4f8FKCkHL/wYZ
5WowJ27bORtP+tRV4IBgHB52TEzvhLZ4+ECY3RsGZC5ReSj6oqCH6X5bSqkqbacA
z63o+ebaGUsNIMOgXiaOKInidv0VZ+V7vnrIdIX729g9L2gu3yEDsC9dcRgMO/sk
EA6wD/vWdfJX6cbH0QxJY9wQOoIWR0zRdZ4CVoJ9MojvuY/izN98JskeSYMkPe+x
zVlH24AGNh0Am5AWOClUS8LV88SpaP0rdXLOCmPC336o7pQqVrY=
=wUuc
-----END PGP SIGNATURE-----