Can't start my StandaloneVM anymore

[faber]

I have a Debian-9 StandaloneVM that I recently am unable to start it.
The only thing I've done, before getting stuck there, was removing
libreoffice (all packages), jack, mutt and icedove, nothing special.

logs from /var/log/xen/console/guest-dev.log:

https://share.riseup.net/#jt9PHXk7pbpDkz0ZKmwy7g


If you need anything else, please let me know!

[Unman]

If you start it using qvm-start what error do you see?
Once you have started it can you attah to the console from dom0 using
(as root) xl console <name> ?

[cooloutac]

ya and if you can do that check apt log. I kill my debian system all the time removing or installing packages. I blindly click yes and don't realize its asking me if it can kill my system by removing desktop haha.

after reading about how when updating a template you could accidentally click yes to a not verified key I had to tell my family to make sure they read for that specific thing especially before hitting y. (this has nothing to do with your issue sorry)

[cooloutac]

and when that happens you just keep trying till it gets a valid key.

[faber]

unman:

> If you start it using qvm-start what error do you see?
> Once you have started it can you attah to the console from dom0 using
> (as root) xl console <name> ?

When it gets at

"starting the qrexec daemon..."

and

"Waiting for VM's qrexec agent......"

it goes timeout and says

"Cannot connect to 'standaloneVM' qrexec agent for 60 seconds, giving up
ERROR: Cannot execute qrexec-daemon!"


If I try to do sudo xl console 'standaloneVM' I get what I think is the
same output of the log that I posted before, but then it asks for login
credential of the VM (which I have no idea what they are)

[Unman]

I hope this was a joke.
I have no sense of humour - do NOT do this.
It's a common situation and you will find many answers with a simple
search.

[Unman]

log in as root, no password.
Then follow the advice an look at your apt logs - almost certainly you
have chosen to delete essential Qubes packages. Look in the apt logs and
see exactly what you did. As you have root access you can run any apt
tool to reinstall the missing packages.

unman

[faber]

Ok I've been able to log in, these are the last logs (I removed some
other programs that I didn't remember before, like imagemagick, but I
still don't think there is something wrong with it):
https://share.riseup.net/#TaSVuYAJQCblXyFZc0z2aQ

unman:

[Unman]

Plesae don't top post.

I think that you will find that your decision to remove qubes-gui-agent
and qubes-core-agent may have something to do with your problems.

As you have root access to the qube you can reinstall these packages and
packages on which they depend (e.g imagemagick).

Two points:
First, the qube was starting, as you discovered from attaching to the
console. Almost everything about your initial post was misleading.

Second, exactly this problem has been covered before on the list. A
simple search would have enabled you to understand your problem and fix
it yourself. Just saying.

unman

[cooloutac]

I'm starting to think you're the joke.

[cooloutac]

Instead of arrogantly telling someone to do a simple search if you are too lazy to give a solution. Do everyone a favor and keep your fucking mouth shut!

[Holger Levsen]

instead of attacking people on the list, please read https://www.qubes-os.org/code-of-conduct/

thanks.


--
cheers,
Holger

[cooloutac]

Well if this is gonna turn into the typical linux help channel with arrogant assholes insulting people askikng questions. Good Luck to Qubes...

[cooloutac]

Linux isn't unpopular cause its hard to use...

[Andrew David Wong]

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

I'm unclear about the disagreement here. I understood cooloutac as saying:

Sometimes, apt-get may download a package with an invalid signature.
In that case, you should not install the invalidly signed package.
Instead, you should re-download the package (and let apt-get re-check
the signature), e.g., after a period of time, from a different server,
or via a different connection, until you get a validly signed package,
and only then proceed with installing that package.

If that's what cooloutac meant, then I'm not sure I see the problem
with that approach. Isn't that what we *should* do in that situation?

P.S. - Let's keep the discussion civil and productive, please.

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

iQIcBAEBCgAGBQJYzcRHAAoJENtN07w5UDAwv38P/idMKPQlh+1hqJmlPwQJJHVq
TjXSUJnS3AL2kX9WGmAbID1cPl3SxHG8ElDWbU5CxnJ7CdgffIV4CRqBcxo/z75H
6ggMHBKQuZXTUzKTU8IObHwy2A2wTo6RYNYsVO93GFiPsRGQnrXOYxcQ2jFhvZsM
Hsih4Eg60Rbv/pbagWcooVfKDhMrqMHR+tnBBJzcXEwwgqVl2vhCcvzeL/ZeYfAN
Z1nCenv42AQ601hKIDkD8+CgbXzCxAPtQQ7vXHAYq9W8UL/nWRzSbT3L5ih2Z7JW
NUoNJ3NmMXPj11uf7EnZb+NY1mA70njdCQ0HdxiXB6iAZVQ8fJ0Fz6juyFie6RyP
murVctv1Btgz6FR5clKfS9tIFxZJ2bTtPtFNTeiOZInDqIyJLr662Ji/i8Qql6b2
aTfk0PxSWiDhXeyyBy6NuCckDRvUWyb0FNXJBLNUTzNR8zAuAuR+/jnwTdT+Q/YY
v9Ja6LoqH3s7nfluxi4Zm4TInd/I7XkehYdikm+O4D9re4haoPJkYGfiMzc+g6qH
vDMbGWttj7Tc0wQbmItbb31Nr1/R13wAfST9XMXQS0pav9zOS6J3yOy0Lu8aiQyU
vcB2lP2cQon5capDrP8fatb4mEpRORdBwJ5tv+N2Tqq3tshzxaxJ6AhgzPDHUJmu
punfqhmLEuvp2TodREZT
=xrUX
-----END PGP SIGNATURE-----

[cooloutac]

I'm sorry Andrew.