Weird icon in Applications, behavior of the deleted VMs

22 views
Skip to first unread message

scurge1tl

unread,
May 30, 2019, 8:44:14 AM5/30/19
to qubes-users
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Yesterday I was experimenting with monero gui. I just unpacked the
monero-gui-linux-x64-v0.14.0.0.tar.bz2 (the hash and PGP verifications
were ok) in the AppVM named monero-on based on whonix-ws-14 and played
with it for some time. Than I deleted the AppVM and shut down the laptop
.

Today, when I click on the Q icon Applications, I see a weird icon in
the list between domain: and service: named "monero-on-vm", with a
weird icon which looks like a box with trash or what. Options
available are:

monero-on: Chat support
monero-on: Dolphin

None is working when clicked. I thought the Q button Applications is
under control of dom0 and there is no way how the
monero-gui-linux-x64-v0.14.0.0.tar.bz2 would influence dom0 this way.

I don't know if it is related, but when booting to Qubes, and watching
the boot process, I can still see Qubes is trying to boot AppVMs which
are for months deleted, with "Failed to start" the VM. How do I delete
it permanently?

Can you advice me how to work it out, and put a bit light into the matte
r?

Thank you!

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

iQKTBAEBCgB9FiEExlmPb5HoPUTt+CQT44JZDAWK6UwFAlzv0AFfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEM2
NTk4RjZGOTFFODNENDRFREY4MjQxM0UzODI1OTBDMDU4QUU5NEMACgkQ44JZDAWK
6Uz6nQ//T7N8S/u+mCX6hCwCI+e6GSW7WdOiFygmWV6IoPA+UnX5K3ypracVyiQM
DidkaqLYP4Nr5sH3h4WvYcD1Gpr4lv5PCIB5Gc/3g2pe0N+iv6FAfFDz/0T4shGM
xhbjux9mQPXFTcvRNSiyDsUYIl7QNf+iMXnDMwdsCCBLkm7tblxRxmSWy+/mkKML
ceTm7Wt/6TsOk/oMvMWtDIf1V7ud9GeGUyNmrZUuh+nBsHxvCndOdmWYkswuvSir
oGkBAgyg3iAYfBLSMeBPAzMyYnGoSqx1OP3qxozKNyGh9cIZuBvQfDMTyJQjK2f1
vaOTCh9Ia2IRK9nrynG5QnI+iWXKZnZAlWTFrZ6Rr5Ghg5SQgyGhr55ERb5e+QiE
HveE6jvAwoF2qmYk+YeeWjzc3Fe1doeNEmTyNGO103td5uxiuZ96c3kOfW6q0uCc
sRHpBgM4/gToeDEB93c1TVUU4h+b847yROBC0kfz7k2WyYqSnIyHO9NODrpDGY3P
On56xqYA6pwzuLLsDToSz001bNMfMKtTtMuL1jkhsGXpxj77P7pBUhK6zLSnZxys
BA5w7HFQEmICH/+A4QLsRYvra4CFeVXv392MXOdlXa3y8V+zQTaAzaYiAC1NqV99
rYE4QNh4X8GbAsY/IcqZYoJvVvgNVAWijRSYhxXL12YUA0Eeczs=
=GZCa
-----END PGP SIGNATURE-----
0xC1F4E83AF470A4ED.asc

Andrew David Wong

unread,
May 30, 2019, 10:20:59 PM5/30/19
to scurge1tl, qubes-users
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 30/05/2019 7.43 AM, scurge1tl wrote:
> Yesterday I was experimenting with monero gui. I just unpacked the
> monero-gui-linux-x64-v0.14.0.0.tar.bz2 (the hash and PGP verifications
> were ok) in the AppVM named monero-on based on whonix-ws-14 and played
> with it for some time. Than I deleted the AppVM and shut down the laptop
> .
>
> Today, when I click on the Q icon Applications, I see a weird icon in
> the list between domain: and service: named "monero-on-vm", with a
> weird icon which looks like a box with trash or what. Options
> available are:
>
> monero-on: Chat support
> monero-on: Dolphin
>
> None is working when clicked. I thought the Q button Applications is
> under control of dom0 and there is no way how the
> monero-gui-linux-x64-v0.14.0.0.tar.bz2 would influence dom0 this way.
>

This usually indicates that the VM has been deleted, and the leftover
Application Menu shortcut was not cleaned up correctly. It's a box of
trash because the original, correct icon is no longer available.

You can clean up the shortcuts manually using the information documented
here:

https://www.qubes-os.org/doc/managing-appvm-shortcuts/#behind-the-scenes

> I don't know if it is related, but when booting to Qubes, and
> watching the boot process, I can still see Qubes is trying to boot
> AppVMs which are for months deleted, with "Failed to start" the VM.
> How do I delete it permanently?
>

I haven't heard of this problem before. Please consider reporting this
bug if it hasn't been reported yet:

https://www.qubes-os.org/doc/reporting-bugs/

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

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

iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlzwj2kACgkQ203TvDlQ
MDCcLA/+PDuzqqpl816BBd+pEjIAwKQiJbkSMd/snscb7D+EiITUymP4X/f7ZeRV
Njh45jQRS9nJkQAwkOFvaV1Kp+tVHIsch6e8zDx80V3ycBOZdrm+0eICFAPDIHS7
GJ47gZsJMdTpLA592IAKqyONoFV8qr0IykADIqulAMoZu0We4Ro+jrx3JNsMF6XO
Sp93sdMGu/wb+oIp3V9XKAPz/apSitUvryFi9cE/ZX72FHymHSbVMCj+HNaGlKFk
GiBOeNUpz27mrf3O8bQ0LI6fVwMetCAmW9YfyoPCcC4EeguqMU8utvX2qxjSufnR
5RaF/COWhpR7dOn8QcFOFpM8TW3Qha88y5iOF8J7fg3Xxa73pc35O0lHBcd2Hhug
JmvMeKa0uW63Eo9p749v18r1XfDaiSIsTtErHd/KwSAjXDAWkfiWbDKBwnzmi9I/
70Rp1t7R7tVis9952d+sintROFOCSQ9/3H4IaiEr0odmWqIHHgt6qZpQdL/BLlAP
UXYP9TLS9zkplLoV6d1csCa0RjVHxr+xBpvsOAG3iItx43hIu7m1UwJKS5SIg25y
yNLbTL+SBAhXhQKX7ON9PdwI6Zu/T9AaBfPQX7v7OImRlwHz6CYCIR6C7Jk4CgHr
taQaZD15B9q+DNOAPnBsHgQdv1W3xPC5LVJvc7rmuD1it69GLow=
=rq7P
-----END PGP SIGNATURE-----

scurge1tl

unread,
May 31, 2019, 3:58:53 AM5/31/19
to qubes...@googlegroups.com
If
>
I understand it properly, I should go in dom0 to
/etc/qubes-rpc/qubes.GetAppMenus and delete the entry manually. The
issue is that in my /etc/qubes-rpc/ there is no qubes.GetAppMenus file.

Also in dom0 the /usr/libexec I dont see any qubes-appmenus to get to
qubes-receive-appmenus. Maybe I am doing something wrong. Could you be
more specific with precise commands to follow?

>
>> I don't know if it is related, but when booting to Qubes, and
>> watching the boot process, I can still see Qubes is trying to
>> boot AppVMs which are for months deleted, with "Failed to start"
>> the VM. How do I delete it permanently?
>
>
> I haven't heard of this problem before. Please consider reporting
> this bug if it hasn't been reported yet:
>
> https://www.qubes-os.org/doc/reporting-bugs/

I will report it.

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

iQKTBAEBCgB9FiEExlmPb5HoPUTt+CQT44JZDAWK6UwFAlzw3oVfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEM2
NTk4RjZGOTFFODNENDRFREY4MjQxM0UzODI1OTBDMDU4QUU5NEMACgkQ44JZDAWK
6UxRRRAAuDNdemKY7HtKUmInJv7hkSDlLND6qaK/ULF47iJ/SCkH+Se9kVSw3bjF
/VH6AZzIS6JQM9CRV9o8Jbl2++5ekDjVQ70vfTinK3zhwTJAsy4q6avY9Kau0UTr
WiGXdM7IEBihYlVL6V32ySl14FOgTTUzOtrCklUz+5aKssZHXN7LWE9p4bY4Kerr
yzAspUJkbVRKcLzDfjNE7jjx+xLgranTVR62rW6TSZfxAbFBYG2R1RxRRlzOOic3
qU2/ldSh90WBdylFnAQrYauU40uW2rSfVpHMj0sbnd9zfZeH0S5W1cFH2vTYPPJj
MApjjx1TL5zbkIYMCpSzsTvvyHtfCwDMJlNT4MiytfPI4UJ0Ww1qQsAmDdFFLOrv
37PiPMdTMXnBCA0QRPntEurkhOCTRQTFcV0V8x77TqD63oD5dqFOaTSR2gWWZB6o
RcVGQ525VvSqYhIm1LvqDb02PzJM2XCjyAnTLP6EyZBSYKxBzmwcPA8xSYN2gPXF
upnDfxfG7A6GED5nFkON3GkvPmdxFV0UNPuDGe8GaHY2Z0yJmvtQ2rX9ZNeE/NeD
LMlfic3m3g6iuUPl+91/ptBPmvm/QvDzBhns2B+t8hQIKcDdp0ijeFYAUUdmM12o
x5BOJqMdWsMZKgKvhRVW3lAki0X7glsEU5qyOEes3CImSpvRZFQ=
=5dzo
-----END PGP SIGNATURE-----
0xC1F4E83AF470A4ED.asc

Andrew David Wong

unread,
May 31, 2019, 9:32:30 PM5/31/19
to scurge1tl, qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

No, that's the RPC policy directory. Don't delete anything in that
directory unless you know what you're doing. Modifying the contents of
that directory can have significant security implications. You can
read more about RPC policies here:

https://www.qubes-os.org/doc/rpc-policy/

> Also in dom0 the /usr/libexec I dont see any qubes-appmenus to get
> to qubes-receive-appmenus. Maybe I am doing something wrong. Could
> you be more specific with precise commands to follow?
>

I just submitted a PR to add this section in an attempt to answer your
question:

https://github.com/QubesOS/qubes-doc/pull/825/files

Does it help?

For reference, this came from my discussion with Marek on:

https://github.com/QubesOS/qubes-issues/issues/4711

>>> I don't know if it is related, but when booting to Qubes, and
>>> watching the boot process, I can still see Qubes is trying to
>>> boot AppVMs which are for months deleted, with "Failed to
>>> start" the VM. How do I delete it permanently?
>
>
>> I haven't heard of this problem before. Please consider
>> reporting this bug if it hasn't been reported yet:
>
>> https://www.qubes-os.org/doc/reporting-bugs/
>
> I will report it.
>

Thanks!

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

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

iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlzx1ZUACgkQ203TvDlQ
MDCx5BAAxNIpJsdr7eHVyt58xhZ1r6X4jTCAfcNQFHm1H7WlOAjTe4Z1ZdgyMIbT
I/moyTGgooPxaXvah8IWyqXrtYtKYqfuSkH4TcxUjHyy0dQ6gW3x7xlAnPqtbE81
lzixUAPsT6fy+xbzCWrWOvt55Tt/jQeCFTJ4IgQc6xvIPGMlM5OmaUBHKlHlF5Jv
OEb3WmuDUlKnsj41Zw5fkzDNqSqtKiPzhmSoPRQ9NaFqslHrJEFanM+dSpVxVoz5
0SpMeSnsCJZQ5bLNRIR51BY3rfWkV6uVrf2Ifk6B/taklYmFWgVAKxJOSOGOOue5
+zoTbGwme1+16l2/i3nnIL/TkLfrVJ2fjHA6aSCo7jab0T1luCxqC2QRjzElbznt
JeR+/6o57nj0qTbvmAVFikmuIGpfLSE/mh06TRVclYGhIiIjj4vfnUk2SrEYhvxB
mkeBjjdPmJt+gr0WcfvFLZhtfTtbHil3/FGah6ekcE2sdDRpEkGBuLt6tEB9Cwa+
jjol5dG3QyIXLUxOXNX1FmfMUNV9tLSRY4hVC3N/Xfu10yrJYZPYL25SIVMgVRmY
684bAaXdu+rTlWtM5fC84SN+N2V5oRjEnZsJo9ayTWDVQTLj+el4snBIMqFsCMjL
EoxJbRdxSmw3clkz0F5OsGbOiVkb58C4RrqMiI78bkpj10GnLSY=
=gjDf
-----END PGP SIGNATURE-----

scurge1tl

unread,
Jun 1, 2019, 5:08:11 AM6/1/19
to qubes...@googlegroups.com
$ qvm-appmenus --update --force monero-on
Traceback (most recent call last):
File "/usr/bin/qvm-appmenus", line 9, in <module>
load_entry_point('qubesdesktop==4.0.17', 'console_scripts',
'qvm-appmenus')()
File "/usr/lib/python3.5/site-packages/qubesappmenus/__init__.py",
line 612, in main
vm = args.app.domains[vm]
File "/usr/lib/python3.5/site-packages/qubesadmin/app.py", line 87,
in __getitem__
raise KeyError(item)
KeyError: 'monero-on'

Now I didn't try yet to execute $ rm -i
~/.local/share/applications/my-old-vm-* just in case you would like me
to try some other tests when issue is alive, to see thats going on.

Also if you tell me how to log the boot sequence, where my long time
deleted VMs are appearing and trying to boot, I will send it to you.

>
> Does it help?
>
> For reference, this came from my discussion with Marek on:
>
> https://github.com/QubesOS/qubes-issues/issues/4711
>
>>>> I don't know if it is related, but when booting to Qubes, and
>>>> watching the boot process, I can still see Qubes is trying
>>>> to boot AppVMs which are for months deleted, with "Failed to
>>>> start" the VM. How do I delete it permanently?
>
>
>>> I haven't heard of this problem before. Please consider
>>> reporting this bug if it hasn't been reported yet:
>
>>> https://www.qubes-os.org/doc/reporting-bugs/
>
>> I will report it.
>
>
> Thanks!
>
>
-----BEGIN PGP SIGNATURE-----

iQKTBAEBCgB9FiEExlmPb5HoPUTt+CQT44JZDAWK6UwFAlzyQF1fFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEM2
NTk4RjZGOTFFODNENDRFREY4MjQxM0UzODI1OTBDMDU4QUU5NEMACgkQ44JZDAWK
6UzEtg//fgtYzKJZpCYPXXCzrCPrGUMPi4c4OdfFx5th+wQvkQPwWu82ya9hXGPe
uBFLZ5eCKqwSjxvcBiLqJgJ75Ye+r4FWVm8MoOh4ZQRbTf89/CixpGKrzzspUh5M
9hlNnG60kKuGMqV84TWcRZy8Lcc+uAgJTyZBlhonyP/SQ94/unSMwgfqfwDUe5C3
Ag/EdiLhOIogiA0fTCbf/KZCf3LuHU/uR46jVcqylHJMrwUDHbir55X2XzwU8aY/
9/0KiUfhAlMYH9tI27NEdHqOGPSlhieGiZzIXfeZYshQrNiCRNVGnupoWJztdUFo
U7ZzJzX+jg7kI3Z10jLjmaW84m8mYSgJSgZL0mfXNMhVIsJKnv1W7bAKpp07QL7q
M2wQUGEqFiYCdzDKkycsTUGlOqNCdXYDSI00G72eAjIObZUPXgT9h38WOkmhNWX9
DmHWwxlACTA4245XIbGLr9MDSdo3e3Uxb6wprH0Iw6dJEcSJAm+lLDs5PrwvuJDY
TxLIpN2KhZi8WmjDx9zBroj3AiJ/7Xt9q20k91GKsvo7CVIVqQEw+3F9uTV2ClOH
js7dkGSvR0d/Fe81A0qjwhStbo/LAo/AbrqmoTL3AIOIo/ZuOVpbMb3pZBUufMo/
y/vza+yOwu68s/vqRVHLLzbBMfPNRvkOPZEGptoy2Nt1hYezOvw=
=9bda
-----END PGP SIGNATURE-----
0xC1F4E83AF470A4ED.asc

Andrew David Wong

unread,
Jun 1, 2019, 4:36:30 PM6/1/19
to scurge1tl, qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 01/06/2019 4.07 AM, scurge1tl wrote:
>> On 31/05/2019 2.58 AM, scurge1tl wrote:
>>
>> [...]
>>
>> I just submitted a PR to add this section in an attempt to
>> answer your question:
>
>> https://github.com/QubesOS/qubes-doc/pull/825/files

For reference, this has been merged as is now live here:

https://www.qubes-os.org/doc/managing-appvm-shortcuts/#fixing-shortcuts

>
> $ qvm-appmenus --update --force monero-on Traceback (most recent
> call last): File "/usr/bin/qvm-appmenus", line 9, in <module>
> load_entry_point('qubesdesktop==4.0.17', 'console_scripts',
> 'qvm-appmenus')() File
> "/usr/lib/python3.5/site-packages/qubesappmenus/__init__.py", line
> 612, in main vm = args.app.domains[vm] File
> "/usr/lib/python3.5/site-packages/qubesadmin/app.py", line 87, in
> __getitem__ raise KeyError(item) KeyError: 'monero-on'
>
> Now I didn't try yet to execute $ rm -i
> ~/.local/share/applications/my-old-vm-* just in case you would like
> me to try some other tests when issue is alive, to see thats going
> on.
>

Please file a bug report for this. There should be no traceback.

Thank you!

> Also if you tell me how to log the boot sequence, where my long
> time deleted VMs are appearing and trying to boot, I will send it
> to you.
>

I'm afraid I don't know how to do that. Perhaps one of the more
knowledgeable folks around here will be able to help with this part.

>
>> Does it help?
>
>> For reference, this came from my discussion with Marek on:
>
>> https://github.com/QubesOS/qubes-issues/issues/4711
>
>>>>> I don't know if it is related, but when booting to Qubes,
>>>>> and watching the boot process, I can still see Qubes is
>>>>> trying to boot AppVMs which are for months deleted, with
>>>>> "Failed to start" the VM. How do I delete it permanently?
>
>>>> I haven't heard of this problem before. Please consider
>>>> reporting this bug if it hasn't been reported yet:
>
>>>> https://www.qubes-os.org/doc/reporting-bugs/
>
>>> I will report it.
>
>> Thanks!

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

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

iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlzy4boACgkQ203TvDlQ
MDC4GxAArnzZBCCzkMAZ6A8Mn0cj6/KaQqpOD8pnTDOPM0zpMgXbN/hueXtDgVnT
akUgKsv29Pf2guKd1TE0567XQF2SfOfvEneMjR32ZSlD6CcIRlwilV1+DI6Vn8cj
9XNUyjyqgfQrkHKwTrPmeOazYOQsZPhDcyFqfvFpOhAYKObOWwJxBB9nC1dXQ15F
vYzH7lD33mmCTI6M85KEw83Ca3k1YijumdiSCg4s57JKVM0qE5+Ix8tUlm7RYLna
fCKAKFrsqiEyc6f7qkKwVjvWdzdGIp33WZDKUWtVLkRWBz9eIxWSUjafXGHaoDbY
zKUOPsT/GOutUEg1OtbIQPMR6ZOlfbOQpUpipszulFgYYOxOo2WtzQGsGILrD9fg
c70xiEDk674WHnjakhblL4s2tFaskEIu64q/tamCVG923F8uv1Qx9Qv4j8r0rgL+
PmLnp2XOF+YDHIWnle+5k7CUt5WWmStinwsUNRjtWOOZknn4HkKym+NtRcI29dIX
Eg74Kiup0UOi4zCeDdi2px642m+0+1nUX+sHy4yZIjM+LEfSD7Sx4nsx2a5hIVnN
5GoosuMcS74ChJDCGvDXwtn4MUpp7SK7KxdFqy8MMDuY6TTvCJaNUnRgddF3X06z
svsntT6SBQcN/h732f4t5f6DeVPstTa/6M5YLOcsnb1X1aLHhD0=
=t4Tr
-----END PGP SIGNATURE-----

Reply all
Reply to author
Forward
0 new messages