The domain (VmNmae) attempted to perform an invalid or suspicious GUI request error?

86 views
Skip to first unread message

xyzo

unread,
Jan 30, 2020, 12:50:03 PM1/30/20
to qubes-users
Qubes version:R4.0

The issue:

when I start any archlinux based appvm. I get the error in the title with two options, to 'terminate' which will shutdown the appvm or 'ignore' which will leave the appvm running but won't execute any commands such as Firefox, xfce4-terminal..etc. Please see pics attached of the error.

Backstory:

I have had archlinux running with no issues for a while now until just last night. I was running a few archlinux based appvms when my laptop battery died and laptop shut off. When I rebooted to start the archlinux appvm again. I got the error in the pics. Now if I start ANY archlinux based appvm. I will get the same error. All other appvms for example fedora, Debian work fine.

In guid log
/var/log/qubes/guid.archlinux

"Verify failed: untrusted_hdr.type > MSG_MIN && untrusted_hdr.type < MSG_MAX"

Has anyone seen this error before?

IMG_20200130_122420.jpg
IMG_20200130_122703.jpg

xyzo

unread,
Jan 30, 2020, 1:36:00 PM1/30/20
to qubes-users
Apologies. I didn't realize the attached pics are flipped on my phone.

Aleksander Okonski

unread,
Jan 30, 2020, 3:01:26 PM1/30/20
to xyzo, qubes-users
Hey, I am having the same issue as you are. I think this is due to an upgrade of qubes-gui-agent-linux (https://github.com/QubesOS/qubes-gui-agent-linux).
I currently am trying to debug this issue. If you click 'ignore' and then try and launch any app from that vm does it load?


‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> -------------------------------------
>
> 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.
> To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/b5a49a43-ebd4-47b7-9043-2b29d560adfc%40googlegroups.com.


xyzo

unread,
Jan 30, 2020, 3:59:06 PM1/30/20
to qubes-users
On Thursday, January 30, 2020 at 3:01:26 PM UTC-5, Aleksander Okonski wrote:
> Hey, I am having the same issue as you are. I think this is due to an upgrade of qubes-gui-agent-linux (https://github.com/QubesOS/qubes-gui-agent-linux).
> I currently am trying to debug this issue. If you click 'ignore' and then try and launch any app from that vm does it load?
>
> > --------------------
No, it doesn't. I tried to launch several apps through the app icon launcher and through the "run a command", neither one worked. The vm will stay running but it won't launch any app. This problem is with only archlinux based appvms. I can however connect as root with "sudo xl console archlinuxappvm"

I see the last commit was in November. But I can't tell what the error really means. This thread has the same error but I don't think its Relevant.
https://www.mail-archive.com/qubes...@googlegroups.com/msg03879.html

How did you get this error? Was it random or maybe after a reboot?

Aleksander Okonski

unread,
Jan 30, 2020, 4:59:30 PM1/30/20
to qubes-users
> > Hey, I am having the same issue as you are. I think this is due to an upgrade of qubes-gui-agent-linux (https://github.com/QubesOS/qubes-gui-agent-linux).
> > I currently am trying to debug this issue. If you click 'ignore' and then try and launch any app from that vm does it load?
> >
> > >
>
> No, it doesn't. I tried to launch several apps through the app icon launcher and through the "run a command", neither one worked. The vm will stay running but it won't launch any app. This problem is with only archlinux based appvms. I can however connect as root with "sudo xl console archlinuxappvm"
>
> I see the last commit was in November. But I can't tell what the error really means. This thread has the same error but I don't think its Relevant.
> https://www.mail-archive.com/qubes...@googlegroups.com/msg03879.html
>
> How did you get this error? Was it random or maybe after a reboot?

Ok, it seems like we have the same issue as I also am having the same problems that you described.

I got this error after I updated my whole arch system yesterday evening and then rebooted.
I use 'yay' as my package manager and saw that it pulled in new packages from aur that are related to qubes (https://aur.archlinux.org/packages/?O=0&SeB=nd&K=qubes&outdated=&SB=n&SO=a&PP=50&do_Search=Go). Digging deeper I was able to isolate the 'qubes-vm-gui' package as the one that causes the problem.

I rebuilt the arch template today and was able to boot into it with no problem. But once I updated 'qubes-vm-gui' (from 4.0.27-9) via the aur pkg to 4.1.5-1 I am getting the same issue as before.

Have you updated arch using any of the aur packages? Can you check using 'xl' what version of 'qubes-vm-gui' you have running on your arch vm?
I think that the link you posted is useful, the version that I update to (4.1.5-1) I believe is for Qubes4.1.



‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Thursday, January 30, 2020 8:59 PM, xyzo <eduz...@gmail.com> wrote:

> On Thursday, January 30, 2020 at 3:01:26 PM UTC-5, Aleksander Okonski wrote:
>
> > Hey, I am having the same issue as you are. I think this is due to an upgrade of qubes-gui-agent-linux (https://github.com/QubesOS/qubes-gui-agent-linux).
> > I currently am trying to debug this issue. If you click 'ignore' and then try and launch any app from that vm does it load?
> >
> > >
>
> No, it doesn't. I tried to launch several apps through the app icon launcher and through the "run a command", neither one worked. The vm will stay running but it won't launch any app. This problem is with only archlinux based appvms. I can however connect as root with "sudo xl console archlinuxappvm"
>
> I see the last commit was in November. But I can't tell what the error really means. This thread has the same error but I don't think its Relevant.
> https://www.mail-archive.com/qubes...@googlegroups.com/msg03879.html
>
> How did you get this error? Was it random or maybe after a reboot?
>
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> 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.
> To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/b8bf0999-7423-4e54-bd31-fc681870aea6%40googlegroups.com.


dhorf-hfre...@hashmail.org

unread,
Jan 30, 2020, 5:10:43 PM1/30/20
to Aleksander Okonski, qubes-users
On Thu, Jan 30, 2020 at 09:59:17PM +0000, 'Aleksander Okonski' via qubes-users wrote:
> I rebuilt the arch template today and was able to boot into it with no
> problem. But once I updated 'qubes-vm-gui' (from 4.0.27-9) via the aur
> pkg to 4.1.5-1 I am getting the same issue as before.

yes, installing a qubes 4.1 pkg on a qubes 4.0 system might not work.


xyzo

unread,
Jan 31, 2020, 12:44:59 AM1/31/20
to qubes-users
Yeah, I just checked "qubes-vm-gui" it's 4.1.5-1. I think I remember now. I updated arch a few days ago without rebooting.

So we should be able to roll back the qubes pkgs shown in the pic. Or download qubes-core 4.0 pkgs and install them manually with "pacman -U" I just gotta find them first. The link to Olivier medoc seems to be dead
http://olivier.medoc.free.fr/archlinux/pkgs/
But it seems to be

IMG_20200131_002755.jpg

Aleksander Okonski

unread,
Feb 1, 2020, 8:01:37 AM2/1/20
to qubes-users
Hey, yes downgrading to 4.0.27 is recommended as the current work around (See comments [0]). I believe that you can get the current 4.0.27 version at [1].
I think that Oliver Medoc is no longer working with Qubes. It seems like the github account has been deleted/removed (see username for commit [2]) and the pkg server you linked is dead as well.

[0] https://aur.archlinux.org/pkgbase/qubes-gui-agent-linux/
[1] https://github.com/QubesOS/qubes-gui-agent-linux/releases/tag/v4.0.27
[2] https://github.com/QubesOS/qubes-core-agent-linux/commit/7ee8c9c672fed744c0b62a9f316fce91e5eddba5


‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> 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.
> To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/e25e8f3f-5d59-4527-b600-31ba872d4f88%40googlegroups.com.


xyzo

unread,
Feb 4, 2020, 3:41:09 AM2/4/20
to qubes-users
Thanks Aleksander for the links. They were very helpful.  I was able to successfully downgrade qubes-vm-gui to v4.0.27 and recover archlinux without having to rebuild the template. But I had to modify 4.0.27 PKGBUILD since it was so outdated. Thanks to seberm for maintaining this package.
I have attached the modfied pkgbuild for v4.0.27 qubes-vm-gui in case anyone is stuck with the same problem. Download v4.0.27 from QubesOS repo (in the post above) > extract it > drop the modified pkgbuild into  qubes-v4.0.27/archlinux/ folder.  Edit pkgbuild-z-qubes-session.sh file, there's a whitespace char after the word "session" delete it, otherwise the makepkg pkgbuild won't work.   tar.gz everything and  do CopytoAppvm to your archlinux template. Run the archlinux  appvm and access it through debug console "sudo xl console archlinux", login is root.  makepkg doesn't work as root. so "su -l user"  find the tar.gz in Qubesincoming, untar it and go into archlinux folder,  do "chmod +x ./* ; chmod 777 ./*" then "makepkg -si". It will download v4.0.27 for qubes-vm-gui and pulseaudio. It will complete pulseaudio installation but, for qubes-vm-gui it will say something abou  it couldn't find correct "xorg-server version blah blah right dependency, choose to continue 'y/n' ?" either choice, it won't install it but you will have qubes-vm-gui-4.0.27.tar.xz pkg (attached) downloaded in your current directory. So just do "pacman -Udd qubes-vm-gui-4.0.27.tar.xz" to install it and skip the dependencies check. Verify that it installed qubes-vm-gui 4.0.27 "pacman -Q | grep qubes"  that's it. shutdown console "sudo shutdown now" and reboot archlinux template. You should be able to run any apps now. You can update archlinux via normal way "pacman -Syu" or with 'yay', but becareful with yay when updating  just make sure you exclude qubes-vm-gui-4.1.5 package before you update. thanks gents and  I hope this helps



PKGBUILD
qubes-vm-gui-4.0.27-9-x86_64.pkg.tar.xz
qubes-vm-pulseaudio-4.0.27-9-x86_64.pkg.tar.xz
Reply all
Reply to author
Forward
0 new messages