Some VMs Stopped Opening Terminal

[Matt Drez]

Hey guys,

Some of my VMs won't open "Terminal", and "Files". If I go to the dom0 terminal and try to run

`qvm-run <VM-name> terminal` then I get a `command failed with code: 127`

I can still run xterm though.

Any ideas as to why and how to fix it?

Matt

[Logan]

> --
> 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...@googlegroups.com
> <mailto:qubes-users...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/qubes-users/fJuKT_hptCBl25HvSijR1SVYAjEx8Y5wvObOFcR_3GfZ91ryXYN8sCqZx3MA2cNoW4B9bpGtb9F4ha66iQwtVCM1msX4CUExOhPn7Gxt55Q%3D%40pm.me
> <https://groups.google.com/d/msgid/qubes-users/fJuKT_hptCBl25HvSijR1SVYAjEx8Y5wvObOFcR_3GfZ91ryXYN8sCqZx3MA2cNoW4B9bpGtb9F4ha66iQwtVCM1msX4CUExOhPn7Gxt55Q%3D%40pm.me?utm_medium=email&utm_source=footer>.
Check your remaining disk space. 9/10 times when I have issues running
an application, it is caused by running out of space.

Also: iirc there's a bug that makes the Debian and Fedora-dvms unable to
run terminal in case that was the VM you tried it on. At least this is
true on my 4.0.3

Cheers,
Logan

[unman]

The crucial piece of informatio missing is which VM, and what
templates are they based on?
Do *all* qubes based on those templates act like this?
If so, most likely the template doesnt know what "Terminal" and "Files"
mean - This will be the case for Debian minimal templates for sure.

[Matt Drez]

> Check your remaining disk space. 9/10 times when I have issues running an application, it is caused by running out of space.

I have plenty of space.

> The crucial piece of informatio missing is which VM, and what
> templates are they based on?

> Do all qubes based on those templates act like this?

> If so, most likely the template doesnt know what "Terminal" and "Files"
> mean - This will be the case for Debian minimal templates for sure.

As of right now two are acting up. One is a standlone VM based on Fedora 31 and the other on is an app VM also Fedora 31. Both worked up until yesterday. There was no updates, no new installs on them. I have other HVMs and app VMs based on Fedora 31 that are still working to make it even more odd

[lik...@gmx.de]

try either:
`qvm-run <VM-name> xterm`

or
`qvm-run <VM-name> gnome-terminal`

[Matt Drez]

> try either:
> `qvm-run <VM-name> xterm`

As I mentioned earlier that is working


> or
> `qvm-run <VM-name> gnome-terminal`
that did not work, but this one had a different error code:
`Command failed with code: 1`

I really don't understand this. There is no rhyme or reason behind what kind of VMs don't work.

[dhorf-hfre...@hashmail.org]

On Wed, May 20, 2020 at 02:01:21PM +0000, 'Matt Drez' via qubes-users wrote:
> > `qvm-run <VM-name> gnome-terminal`
> that did not work, but this one had a different error code:
> `Command failed with code: 1`

check the output by adding a -p:
qvm-run -p <VM-name> gnome-terminal

it might actualy tell you why it does not want to start!
(or it may even work if the reason for not starting is it wanting
to say something...)

[Matt Drez]

> check the output by adding a -p:
> qvm-run -p <VM-name> gnome-terminal
>

> it might actualy tell you why it does not want to start!
> (or it may even work if the reason for not starting is it wanting
> to say something...)

I hope this means something to you :)
# posix_spawn avoided (fd close requested)

# Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Failed to execute child process ___dbus-launch___ (No such file or directory)

[Matt Drez]

I don't really understand why but installing `dbus-x11` fixed it.