[qubes-users] Failed to attach dom0 microphone: pulseaudio not running in target vm error
Hey, I would like to attach dom0:mic to a target vm that has pulseaudio-qubes package installed on it. The problem is that It says pulseaudio agent is not running in the target vm when It is. Any ideas on what could be the problem? Also it's worth noting that this target vm doesn't show up under the dom0 pulseaduio audio mixer list. I don't know why, even though it has pulseaudio-qubes installed. So alternatively, I have a cheap audio usb that I use on this target vm to get some sound. I also connect my headphones to the audio usb to record soundnin this vm. But the sound quality is bad, hissing/static noise when I'm recording. So I wanted to try using the build in dom0:mic sound card instead and see if it will make a difference. Any ideas on how I can attach dom0:mic block. -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/87878f63-fa05-495d-9f97-bbfab90040ebn%40googlegroups.com.
[qubes-users] Re: X11 only works by manually typing startx in tty
The solution was to symlink default.target to graphical.target. So it was to do "systemctl set-default graphical.target" or deleting the existing default.target in /etc/systemd/system/default.target and reboot. It was symlinked to the wrong target. https://wiki.archlinux.org/index.php/Systemd#Change_default_target_to_boot_into On Tuesday, September 29, 2020 at 12:06:31 AM UTC-4 xyzo wrote: > I have a Kali HVM that was working fine until I installed a few of qubes > core packages on it. I installed qubes-usb-proxy, qubes-core-qrexec, > qube-core-agent. It required a few more qubes packages as dependencies like > qubesdb.etc.. The installation was successful and I double checked that > qrexec, core-agent daemons were successfully running. So everything was > good so far. And I was able to attach usb devices to HVM, copy to other Vm > from HVM..etc.. But something got messed up in Xorg-server. I'm not sure > what exactly happened. Now every time I boot into the HVM, I have to login > through tty first then type "startx" for xinit to pull up the desktop > environment. I already tested with a few different DE, gdm, lightdm. They > all worked when I typed startx. So it's not the DE. it's something in > xorg. This is my Xorg.0.log. I noticed it says glamor failed. but I > failed to fix that. Any help is really appreciated . > -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/c703f8ef-2690-4e1e-a1fc-f4ea3540336cn%40googlegroups.com.
[qubes-users] X11 only works by manually typing startx in tty
I have a Kali HVM that was working fine until I installed a few of qubes core packages on it. I installed qubes-usb-proxy, qubes-core-qrexec, qube-core-agent. It required a few more qubes packages as dependencies like qubesdb.etc.. The installation was successful and I double checked that qrexec, core-agent daemons were successfully running. So everything was good so far. And I was able to attach usb devices to HVM, copy to other Vm from HVM..etc.. But something got messed up in Xorg-server. I'm not sure what exactly happened. Now every time I boot into the HVM, I have to login through tty first then type "startx" for xinit to pull up the desktop environment. I already tested with a few different DE, gdm, lightdm. They all worked when I typed startx. So it's not the DE. it's something in xorg. This is my Xorg.0.log. I noticed it says glamor failed. but I failed to fix that. Any help is really appreciated . -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/98028b14-e6c1-417c-9ddb-0c036b607250n%40googlegroups.com. [ 9463.486] X.Org X Server 1.20.8 X Protocol Version 11, Revision 0 [ 9463.486] Build Operating System: Linux 4.19.0-8-amd64 x86_64 Debian [ 9463.486] Current Operating System: Linux Kali-bad-clone-test-with-qubes 5.8.0-kali1-amd64 #1 SMP Debian 5.8.7-1kali1 (2020-09-14) x86_64 [ 9463.486] Kernel command line: BOOT_IMAGE=/vmlinuz-5.8.0-kali1-amd64 root=/dev/mapper/blackB0x--vg-root ro initrd=/install/initrd.gz quiet splash [ 9463.486] Build Date: 31 March 2020 10:14:40AM [ 9463.486] xorg-server 2:1.20.8-2 (https://www.debian.org/support) [ 9463.486] Current version of pixman: 0.36.0 [ 9463.486] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 9463.486] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 9463.486] (==) Log file: "/home/ka3dcl/.local/share/xorg/Xorg.0.log", Time: Mon Sep 28 21:11:49 2020 [ 9463.486] (==) Using config file: "/etc/X11/xorg.conf" [ 9463.486] (==) Using config directory: "/etc/X11/xorg.conf.d" [ 9463.486] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 9463.487] (==) ServerLayout "X.org Configured" [ 9463.487] (**) |-->Screen "Screen0" (0) [ 9463.487] (**) | |-->Monitor "Monitor0" [ 9463.487] (**) | |-->Device "Card0" [ 9463.487] (**) |-->Input Device "Mouse0" [ 9463.487] (**) |-->Input Device "Keyboard0" [ 9463.487] (==) Automatically adding devices [ 9463.487] (==) Automatically enabling devices [ 9463.487] (==) Automatically adding GPU devices [ 9463.487] (==) Max clients allowed: 256, resource mask: 0x1f [ 9463.487] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 9463.487] Entry deleted from font path. [ 9463.487] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 9463.487] Entry deleted from font path. [ 9463.487] (**) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins, /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [ 9463.487] (**) ModulePath set to "/usr/lib/xorg/modules" [ 9463.487] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled. [ 9463.487] (WW) Disabling Mouse0 [ 9463.487] (WW) Disabling Keyboard0 [ 9463.487] (II) Loader magic: 0x5592d69c0e20 [ 9463.487] (II) Module ABI versions: [ 9463.487] X.Org ANSI C Emulation: 0.4 [ 9463.487] X.Org Video Driver: 24.1 [ 9463.487] X.Org XInput driver : 24.1 [ 9463.487] X.Org Server Extension : 10.0 [ 9463.488] (++) using VT number 2 [ 9463.489] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_33 [ 9463.490] (II) xfree86: Adding drm device (/dev/dri/card0) [ 9463.491] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 13 paused 0 [ 9463.498] (--) PCI:*(0@0:3:0) 1234::1af4:1100 rev 2, Mem @ 0xf100/16777216, 0xf2024000/4096, BIOS @ 0x/131072 [ 9463.498] (II) "glx" will be loaded. This was enabled by default and also specified in the config file. [ 9463.498] (II) LoadModule: "glx" [ 9463.498] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [ 9463.499] (II) Module glx: vendor="X.Org Foundation" [ 9463.499] compiled for 1.20.8, module version = 1.0.0 [ 9463.499] ABI class: X.Org Server Extension, version 10.0 [
Re: [qubes-users] Can someone pls help me troubleshoot why qvm-run --pass-io doesn't work with win7-template
On Friday, June 12, 2020 at 7:38:42 PM UTC-4, unman wrote: > On Fri, Jun 12, 2020 at 03:57:35PM -0700, xyzo wrote: > > qubes version 4.0. > > I need to copy files from win7-template to a Linux appvm. I was suggested > > to use (qvm-run --pass-io win7-template "type C:\n.pdf" > ./n.pdf) > > To copy files from win7-template to dom0 then move it from dom0 to any > > destination appvm. Invoking this command in dom0 terminal, the curosr just > > hangs and nothing happens and I exit by ^C in terminal. Running it with > > --verbose parameter shows "Running win7-template C:\n.pdf" and it hangs. > > It's like it's not seeing that win7-template is already running. > > > > I discovered that the command only works when win7-template is powered off. > > Then invoking above command will power on win7-template and successfully > > execute. > > > > PS: I can copy files from any Linux appvm to the win7-template > > QubesIncoming folder by right-clicking the file I want to copy to > > win7-template and selecting "copy to another Vm" this works fine to copy > > any file from Linux appvm over to win7-template. But not the other way > > around. > > > > So I'm not sure why the qvm-run --pass-io hangs when win7-template is > > already running. Any help is appreciated. Thanks > > > > Why are you doing this? > In Windows, right click on the file, Select "Send to", and there are the > options to copy or move to another qube. > > As to your "problem", on my windows templates with QWT installed, I do > not see the behaviour you report. Simply, it does not hang, but it does > not provide the output that you want. Man thank you so much.. I was totally not aware of the send-to option. Somehow I missed that info in the windows doc. The Send-to option worked perfectly.. for a long time I thought there was no way we can copy files through the windows gui. But now I know thanks. Out of curiosity what was the command you entered in dom0 and what was its output? It would be nice to learn if there's a way we could copy files from windows via terminal without having to interact directly with Windows gui. -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/c2e8b118-3161-4a5b-a924-9d1cdba6a18ao%40googlegroups.com.
[qubes-users] Can someone pls help me troubleshoot why qvm-run --pass-io doesn't work with win7-template
qubes version 4.0. I need to copy files from win7-template to a Linux appvm. I was suggested to use (qvm-run --pass-io win7-template "type C:\n.pdf" > ./n.pdf) To copy files from win7-template to dom0 then move it from dom0 to any destination appvm. Invoking this command in dom0 terminal, the curosr just hangs and nothing happens and I exit by ^C in terminal. Running it with --verbose parameter shows "Running win7-template C:\n.pdf" and it hangs. It's like it's not seeing that win7-template is already running. I discovered that the command only works when win7-template is powered off. Then invoking above command will power on win7-template and successfully execute. PS: I can copy files from any Linux appvm to the win7-template QubesIncoming folder by right-clicking the file I want to copy to win7-template and selecting "copy to another Vm" this works fine to copy any file from Linux appvm over to win7-template. But not the other way around. So I'm not sure why the qvm-run --pass-io hangs when win7-template is already running. Any help is appreciated. Thanks -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/18e41e96-3a97-4850-9939-bdbd8b510dc8o%40googlegroups.com.
[qubes-users] How to qvm-copy FROM a win 7 appvm?
I can use qvm-copy-to-vm to copy files to win7vm. But how do copy FROM win 7 to another appvm? Thanks -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/090b621c-57c3-406e-b0ec-08af588d8259o%40googlegroups.com.
[qubes-users] Qubes new Archlinux commits revoke old maintainer keys from keyring and update problems for existing/old archlinuxappvm
Sorry guys about the typos I am typing from my phone.. -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/e7c06b84-c5fa-47d3-9849-e5dcd485b77a%40googlegroups.com.
[qubes-users] Qubes new Archlinux commits revoke old maintainer keys from keyring and update problems for existing/old archlinuxappvm
Updating Archlinux with "pacman -Syu" I got "pgp signature failed. Gpgme error no data. Multilib.db, core, extra.db failed to update" So I just tried the reintializing keys and repopulating it with "pacman-key --init; pacman-key --populate Archlinux" it repoulated the keys but I was still getting the same error. Removing /var/lib/Pacman/sync and retryng with "Pacman -Syu" gave me the same error. I looked online and found out there's been some changes done to Archlinux template with revoking old maintainer from trusted keyring. https://github.com/QubesOS/qubes-core-agent-linux/tree/master/archlinux https://github.com/QubesOS/qubes-core-agent-linux/commits/master/archlinux I couldn't find qubesos-vm.gpg to place in /usr/share/Pacman/keyring . And the new keyring-trusted commit is a 0 byte file.. hmm does anyone with an Archlinux have problems updating theirs. Any feedback is appreciated thankyou -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/c03688fe-1a91-474b-a889-6a3bf1f73e54%40googlegroups.com.
[qubes-users] Unable to open mtp device. Android shows up in sys-usb only
I need to transfer files from my Android smartphone (Opo7). I can successfully attach my Android phone to a Debian appvm. Inside the appvm, It will list my phone when I open a file manager but it won't mount it. It says "unable to mount device USB:0xx" I installed most of the mtp pkgs. (Mtp-tools libmtp9 libmtp-common libmtp-dev libmtp-dev libmtp-runtime) but still gives the same error.. However, I can access my phone through sys-usb vm. So now I have to transfer my stuff from appvm to sys-usb and copy it over to my phone Which defeats the purpose of having sys-usb. Any help is appreciated -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/c3cc1180-b116-4ab5-81de-b14a667501dc%40googlegroups.com.
Re: [qubes-users] Re: Win7 Qubes windows-tools v3.2. attaching any device failsf
>I always do this while the hvm is shutdown in which case you need to add >the --persistent parameter. Also some (including my) USB controller >don't support PCI resets so you need an additional parameter dealing >with that... >qvm-pci attach win --persistent --option no-strict-reset=True >dom0:xx_xx.x Thanks >Don't hold your breath. It won't work for more complex devices. I honestly only care about connecting only the webcam for proctorU for schools exams sigh. Unfortunately ProctorU can only run on win or Mac and I only run Qubes on my daily driver. I can install win7 on another SSD but I would really hate to reboot back & forth between win7 and Qubes. It's much more practical to have the win appvm running along with the rest of my other appvms. But at least USB works when attaching the USB controller. I think there's a special USBIP driver for windows that must be installed first with USBIP https://github.com/QubesOS/qubes-issues/issues/2335 >Well I've seen it happen by accident ;-) My normal setup is to enable >the hotspot function on my iPhone and have sys-net connect to it via >WiFi. Big thumbs up for the hotspot suggestion. I just tested it and it works. I am always anti-wifi without a VPN unless it's my home wifi. I always tether into any machine when I am outside.. >Basically I agree if you only thether then assigning the USB controller >to Windows will have the rest of Qubes offline (since now obviously >sys-usb doesn't have it anymore). But Windows should be able to use the >conntection if the right drivers are installed. It should and I have an Android. I installed the Android drivers. The tether network adapter just stays as "identifying network" and never actually connects through. But I definitely didn't think of using the hotspot. >Side note: my old MacBookPro which I used with Qubes R3.2 had two USB >controllers. So I could keep one connected to sys-usb while the other >one was connected to Windows. Just had to figure out which port connects >to which controller. You might be lucky and also have two controllers. Wow just the right hardware setup for any Qubes hvm. My daily driver is a Lenovo E5 model. No 2usb controllers for me unfortunately.. I appreciate your feedback and your great help. -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/2d2e8c48-c7d9-4737-ba20-4e1f22b5b0ab%40googlegroups.com.
Re: [qubes-users] Re: Win7 Qubes windows-tools v3.2. attaching any device failsf
>I use a little USB audio in/out adapter [1] for $9.99 Thank you so much. +1 for the USB audio adapter suggestion. >I get this error if there is any storage media connected on USB when I >boot the Windows VM. Maybe try again and make sure nothing is connected >when you boot. that was it. Now it's boots up once I unplugged the storage media >It's my understanding that this functionality is simply not implemented >in the Qubes Windows drivers. The way this is implemented in Qubes is >using USBIP but instead of a network IP connection it uses the XEN >qrexec mechanism: https://github.com/QubesOS/qubes-app-linux-usb-proxy >So I tried to run USBIP in Windows and run an unchanged USPIP host in >sys-usb a couple years back and that worked for simple devices / >protocols (e.g. USB-to-serial interface but not more complex USB devices >like RealICE debuggger). So I gave up on that and instead have dom0 >scripts to easily switch the controller between sys-usb, app-dev and >app-win. So the script would basically be something like "qvm-pci attach app-win dom0:bdf_usb_controller_address"? I will look into the usbip thanks.. There's something else with windows hvm, not sure if you have experienced it yet. But have you ever tethered into Win7 while USB controller attached to win7. Usually the way I tether into any appvm. The sys-usb will have networkmanager service enabled. And then I will just change sys-firewall netvm to sys-usb instead of sys-net. so any appvm with sys-firewall as netvm I can tether into it and access the internet.. however now detaching USB controller from sys-usb to attach it to win7 you can't tether in windows. I tried changing win7 netvm to none as sys-usb and add networkmanager service in Qubes manager as sys-usb but that didn't work..the only way to access internet while having usb pci attached to win7 is to have sys-net connected to Internet with sys-firwall as the win7 netvm and sys-firewall netvm as sys-net.. sometimes I don't have access to an internet to connect to sys-net. So I usually tether through sys-usb. Are you aware of a way to have USB pci attached to win7 and still be able to tether in win7. I think it's possible it's just a matter of configuring your win7 net adapter correctly.. -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/3e298064-42d8-46ae-8b7f-e8c81ec46123%40googlegroups.com.
[qubes-users] Re: Win7 Qubes windows-tools v3.2. attaching any device failsf
Quick update I updated the pv drivers to 8.2.2 and now win 7 is running a lot smoother. If I attach the audio pci controller under devices in Qubes device manager. The audio will work and is recognized in win 7. That's great but Is there anyway I can get the audio to work with out attaching audio controller to only win 7? I'd like to have audio running in other appvms in parallel to hvm. Also, attaching the USB controller pci to win7 will stop win 7 from booting. It will say "no bootable device was found" when I run it. And if I try attaching any USB device through dom0 "qvm-usb attach Win7 sys-usb:2-7" I get "exception failed. Device failed to attach" I'm lost with this one. any help is appreciated thanks -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/f4d0b7eb-f0da-49a3-81f5-ff55af9d35b9%40googlegroups.com.
[qubes-users] Win7 Qubes windows-tools v3.2. attaching any device failsf
Qubes R4.0 Windows-tools v3.2.2-3 I recently installed a Win7 hvm with Window-tools v4.x. I initially had problems getting qrexec service to work on Win7. So I tried version 3.2.2-3 and It successefully installed all of the qubes-tools, qubes_core-agents, qubes-gui.etc. and now Win7 has a green dot state when it's powered on. I can copy files from other appvms to the windows Qubesincoming. The pv drivers installed are the same version bundled with windows-tools v3.2.2-3. I've been scratching my head with attaching USB devices like the internal webcam, audio, thumb drive on win7. I get an error msg "Qubes exception.failed. attach device failed".. with audio I know I have to have pulseaudio running on Windows? qvm-usb a Win7 sys-usb:xx: gives the same error. I am not sure what to do next at this point. thanks -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/66f9d3aa-4e37-4a1b-823a-f126d0af5be7%40googlegroups.com.
[qubes-users] Re: The domain (VmNmae) attempted to perform an invalid or suspicious GUI request error?
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 -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/6eed1c3a-75d0-448f-a0a8-6c16b9856848%40googlegroups.com. PKGBUILD Description: Binary data qubes-vm-gui-4.0.27-9-x86_64.pkg.tar.xz Description: Binary data qubes-vm-pulseaudio-4.0.27-9-x86_64.pkg.tar.xz Description: Binary data
Re: [qubes-users] The domain (VmNmae) attempted to perform an invalid or suspicious GUI request error?
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-devel@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+unsubscr...@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.
[qubes-users] Re: The domain (VmNmae) attempted to perform an invalid or suspicious GUI request error?
Apologies. I didn't realize the attached pics are flipped on my phone. -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/ff1d22d5-54aa-4c4c-b334-0899395ddd98%40googlegroups.com.
