Re: [qubes-users] xsel via qrexec fails to set clipboard, "conversion refused"
On Sunday, December 30, 2018 at 5:32:58 AM UTC-8, unman wrote: > On Fri, Dec 28, 2018 at 10:28:12AM -0800, Dave C wrote: > > I've written a qrexec script which, among other things, attempts to place > > something into the clipboard, using `xsel`. > > > > xsel fails, with error: "xsel: Conversion refused" > > > > Attempting to troubleshoot, I've learned that `xsel -o` can show the > > contents of the clipboard, but `xsel` fails to set the clipboard. Both > > `xsel -v` and `xsel -b -v` fail with the "conversion refused" messages. > > `xsel` works fine when I run it from a terminal. The error occurs only > > when running via qrexec. > > > > For some context, if you're interested... I recently became aware of a > > password manager with some interesting features: > > https://github.com/renatoathaydes/go-hash. I'd like to modify it, so that > > it both opens a URL in a VM, and places a password in that VM's clipboard. > > I've got most of that working, except that I can't get the password into > > the clipboard, because xsel fails with "conversion refused". > > > > It would help if you provided a copy of your script and some detail on > where you are calling xsel, how you are handling it on the receiving > side, and what templates you are using. > Are you using the normal Qubes clipboard paste mechanism or are you > rolling your own? I'll attach a file, which is a version of the script I'm working on. It's based on /etc/qubes-rpc/qubes.OpenURL. In addition to opening URLs, it takes the first line of stdin and uses `xsel` to put that line into the clipboard. It doesn't work. If you change `xsel -v`, you'll see it gets the error I've described in the first post. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/01fcad0f-c818-448f-91cc-2a28310ae332%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. qpass.ClipOpenURL Description: Binary data
[qubes-users] Re: screen brightness
On Friday, December 21, 2018 at 2:44:36 PM UTC-8, haaber wrote: > I run Q4 on a dell notebook.The "screen brightness" key-combination > leans qubes to show a screen brightness icon, but I cannot change > brightness at all.Is this maybe a setting somewhere? Especially in > evening hours this is really a pain in the eye ... Bernhard The key combination fn-f5 lowers brightness on my laptop. (fn-f5 raises it) But the lowest brightness available through the keyboard shortcut is still too bright at night. I find that brightness can be further lowered with the following, in dom0: xrandr --output eDP1 --brightness .75 Use `xrandr-q` to figure out what to replace "eDP1" with. And try .5 or lower to fine tune your brightness. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/33af20b4-b665-4f7e-ba08-66bab0190dce%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Install errors on Thinkpad P1 (aka X1 Extreme) with R4.0 and R4.0.1-rc2
For the record, I am now using 4.0.1 since it released (same problems). On Monday, January 7, 2019 at 12:49:52 AM UTC-5, awokd wrote: > > Try temporarily disabling your wifi card for the install. > Good idea! I disabled it, along with just about every device I could find. It generated a different GUI error during the Post installation qubes configuration screen, with everything disabled and disconnected: ['/usr/bin/qvm-start', 'sys-firewall'] failed: stdout: "" stderr: "PCI device dom0:00_14.3 does not exist" Once logged in, I see that Fedora in dom0 isn't detecting the 4K resolution like it has on my Thinkpad Yoga 3rd gen and Thinkpad Tablet 3rd gen devices - everything is tiny text. Running lspci shows me that 00_14.3 is described as the network controller (it has an onboard network card, along with the wifi card). Given, the PCIe device IDs could change since I have been disabling/enabling various devices at this point. But the error would seem to point to the onboard network card, even though it is Disabled in the bios. Now, I've noticed that none of the VMs startup (sys-firewall, sys-net, sys-usb). $ sudo systemctl status qubes-vm@sys-net.service This shows the exact same error message as above. Going into the bios and re-enabling everything, generates the original error in the first message in this thread. 00:1f.6 points to "Ethernet controller" 00:14.3 points to "Network controller" Going back into the bios and disabling "Wireless" and "Ethernet" devices (under Security), sys-usb is now able to start. However, sys-net and sys-firewall gives the exact same "00:14.3 does not exist" error on starting any VM. However, now it does not show under lspci with everything disable. Nor does 14.3 show up under any Qubes settings as attached to either sys-net or sys-firewall. I did another full install with everything disabled, and the same error of 14.3 does not exist keeps showing up, preventing sys-net and sys-firewall from starting. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/bd18842b-bf03-4133-ab62-b6ee6e149a71%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Install errors on Thinkpad P1 (aka X1 Extreme) with R4.0 and R4.0.1-rc2
See inlines. On Friday, January 4, 2019 at 5:16:16 PM UTC-5, Achim Patzner wrote: > > The good old I219-LM problem... Before assigning (or after 8-) it to > sys-net (I do not really see any reason it should be assigned to sys- > firewall... are you sure?) it needs to get set to no-strict-reset=true > and permissive=true; take a look at qubes-os.org. I think you mis-understand. I am not assigning/attaching anything. This is doing installation only that generates the error. > Use the dGPU or take care of turning off the nouveau driver completely > (nouveau.modesetting=0). > > Why don't you use the nVidia GPU instead? It is definitely faster than > the iGPU anyway, booting faster, using (at least on my machine) less > energy and you do not meed to modify the kernel command line. And on > kernel-latest my system is working with all cores. > That is not ideal. The main reasons to disable the dGPU is for battery life. Under Arch, I can do this (not efficiently have you) with bbswitch. However, I am not making it that far with Qubes as I cannot boot into the system after installation. > > WARNING (to anyone else installing on a P1/X1 Extreme/P52, etc): To > > install, you must switch to discrete graphics in BIOS (no hybrid). But, DO > > NOT DO THIS unless you have BIOS 1.17 or later or you will BRICK YOUR > > THINKPAD! > > That didn't break mine. Turning on Thunderbolt BIOS support and turning > off secure boot did that for me. Switching to dGPU is only causing > problems if you do not wait on the next reboot for the system to > reinitialize the device tree in ME (and thus starting with empty ACPI > tables) by resetting it at just the right time during the 30 seconds > this would take. > First of all, what laptop do you have? "That didn't break mine" indicates you also have a P1? Please share your experience installing Qubes to a fully functional state (including suspend - not even us Arch guys have figured out suspend yet with the ACPI tables on the P1). It is an extremely well known bricking problem with all modern (early to late 2018) Lenovo Thinkpad models: https://www.reddit.com/r/thinkpad/comments/a2g0k4/warning_do_not_change_from_hybrid_graphics_to/ (and dozens of threads on the Lenovo forums) If you have an early 2018 Thinkpad, you're pretty much ok. My warning applies to all current models. It got so bad Lenovo actually pulled the last 2 or 3 BIOS from just about every Thinkpad and Yoga series from the downloads site. The 1.15 my P1 came with is long gone, as well as the 1.13 version that was there. Only 1.10 and 1.17 are available now - and 1.17 I can confirm does not brick it. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/6dfd1f09-1434-4639-9afc-15959fc8eeb5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Device Widget doesn't show USB devices
Patrick wrote on 1/12/19 7:22 PM: Hi, on my laptop qubes this doesn't show any usb devices, and an external keyboard using USB doesn't work. What can I check and do? I compare my settings to my other machine running 4.0 and they look the same, and do see USB. One difference - I do not see a sys-USB on my machine that DOES work with USB, and I DO see the sys-USB on the laptop that doesn't show USB. Thoughts? Test a different USB device other than a mouse or keyboard on your laptop with sys-usb. If that works, you need to edit a file to allow your external keyboard. It's something like rpc input proxy permissions file, try searching this list for it. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/5a805e43-6549-8ce8-b26a-4def5307365c%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Kernel panic due to Ctrl+C interrupted dom0 update and reboot
simone.f...@gmail.com wrote on 1/12/19 10:31 PM: Le samedi 12 janvier 2019 21:43:21 UTC+1, simon...@gmail.com a écrit : Hi, Error message : [3.680649] Call Trace: [3.680707] dump_stack+0x5c/0x85 [3.680764] panic+0xe4/0x252 [3.681184] mount_block_root+0x35b/0x52c [3.681601] ? do_early_param+0x16e/0x16e [3.682018] prepare_namespace+0x278/0x2d5 [3.682434] ? do_early_param+0x16e/0x16e [3.682851] kernel_init_freeable+0x2e8/0x32d [3.683270] ? rest_init+0xb0/0xb0 [3.683685] kernel_init+0xa/0x101 [3.684101] ret_from_fork+0x35/0x40 [3.684536] Kernel Offset: disabled. So, I booted into recovery mode prompt from a USB key (Troubleshooting and Rescue a Qubes system (read-write choice). It seems that I can’t boot an older kernel version. # ls /boot initramfs-vmlinuz-4.14.74-1.pvops.qubes.x86_64 # I don't really know what to do to fix it. Your help will be greatly appreciated! Thank you a lot for your valued assistance Thanks awokd. The system is mounted under /mnt/sysimage directory. In /mnt/sysimage/boot/grub2/grub.cfg, I changed : module /vmlinuz-4.14.74-1.pvops.qubes.x86_64 by module /vmlinuz-4.14.57-2.pvops.qubes.x86_64 but no change, same error when booting :-( That looks better. Double check /mnt/sysimage/boot/efi/EFI/qubes/xen.cfg too in case you are booting UEFI maybe. Not sure what else it could be... -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/1ff015a2-24fe-9c4f-f91c-12f8145e7d51%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Kernel panic due to Ctrl+C interrupted dom0 update and reboot
Le samedi 12 janvier 2019 21:43:21 UTC+1, simon...@gmail.com a écrit : > Hi, > > Error message : > > [3.680649] Call Trace: > [3.680707] dump_stack+0x5c/0x85 > [3.680764] panic+0xe4/0x252 > [3.681184] mount_block_root+0x35b/0x52c > [3.681601] ? do_early_param+0x16e/0x16e > [3.682018] prepare_namespace+0x278/0x2d5 > [3.682434] ? do_early_param+0x16e/0x16e > [3.682851] kernel_init_freeable+0x2e8/0x32d > [3.683270] ? rest_init+0xb0/0xb0 > [3.683685] kernel_init+0xa/0x101 > [3.684101] ret_from_fork+0x35/0x40 > [3.684536] Kernel Offset: disabled. > > So, I booted into recovery mode prompt from a USB key (Troubleshooting and > Rescue a Qubes system (read-write choice). > > It seems that I can’t boot an older kernel version. > > # ls /boot > initramfs-vmlinuz-4.14.74-1.pvops.qubes.x86_64 > # > > I don't really know what to do to fix it. > > Your help will be greatly appreciated! > > Thank you a lot for your valued assistance Thanks awokd. The system is mounted under /mnt/sysimage directory. In /mnt/sysimage/boot/grub2/grub.cfg, I changed : module /vmlinuz-4.14.74-1.pvops.qubes.x86_64 by module /vmlinuz-4.14.57-2.pvops.qubes.x86_64 but no change, same error when booting :-( -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/9c7f45b7-d779-4a15-9fb0-617270a97c91%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] USB 3.0 to Ethernet adapter with QubesOS possible?
On 1/12/19 10:07 PM, 'awokd' via qubes-users wrote: Possibly the firmware and/or device driver isn't installed in dom0? Thought you actually needed sys-usb for usb redirection to work, but then I don't know how your camera is showing up in the widget. Sorry awokd, I was wrong. It's the Microphone shown in the Device Manager, not the Camera.> See https://www.qubes-os.org/doc/assigning-devices/. qvm-pci or lspci will list devices you can assign. Read further in there how to determine to which one your keyboard's connected. I'll do that. Thanks to you and have a nice weekend. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/fe255958-7eba-5d64-14b5-ecd92c092181%40posteo.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Kernel panic due to Ctrl+C interrupted dom0 update and reboot
simone.f...@gmail.com wrote on 1/12/19 8:43 PM: Hi, Error message : [3.680649] Call Trace: [3.680707] dump_stack+0x5c/0x85 [3.680764] panic+0xe4/0x252 [3.681184] mount_block_root+0x35b/0x52c [3.681601] ? do_early_param+0x16e/0x16e [3.682018] prepare_namespace+0x278/0x2d5 [3.682434] ? do_early_param+0x16e/0x16e [3.682851] kernel_init_freeable+0x2e8/0x32d [3.683270] ? rest_init+0xb0/0xb0 [3.683685] kernel_init+0xa/0x101 [3.684101] ret_from_fork+0x35/0x40 [3.684536] Kernel Offset: disabled. So, I booted into recovery mode prompt from a USB key (Troubleshooting and Rescue a Qubes system (read-write choice). It seems that I can’t boot an older kernel version. # ls /boot initramfs-vmlinuz-4.14.74-1.pvops.qubes.x86_64 # I think you might be looking at the USB key's /boot there. Your fixed disk should be somewhere under /mnt- it tells you where it's mounting it but I don't remember exactly. Then look for grub.cfg or xen.cfg under that and edit it so it boots an older kernel. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/e3870e13-ce77-05e5-8a2d-7868402f4782%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] USB 3.0 to Ethernet adapter with QubesOS possible?
gone wrote on 1/12/19 9:00 PM: Thanks @awokd. I understand, that dom0 has no networking on purpose. That's a good point. But even if it can't do it's networking job in dom0, I still wonder why the adapter isn't visible in the Device Widget. Shouldn't the USB part of it still be assignable to an appVM? Possibly the firmware and/or device driver isn't installed in dom0? Thought you actually needed sys-usb for usb redirection to work, but then I don't know how your camera is showing up in the widget. As I don't even know exactly the meaning of things like "usb 2-6", how could I find out how many USB controllers the machine has and which one the keyboard is assigned to? Is such an assignment static or somehow dynamic? I'd really like to use LAN by cable but don't want to risk to lock myself out. See https://www.qubes-os.org/doc/assigning-devices/. qvm-pci or lspci will list devices you can assign. Read further in there how to determine to which one your keyboard's connected. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/09e028b0-520a-26d2-2d13-c682ab1a%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] USB 3.0 to Ethernet adapter with QubesOS possible?
On 1/12/19 6:03 PM, gone wrote: On 1/12/19 1:44 AM, 'awokd' via qubes-users wrote: gone wrote on 1/11/19 9:01 PM: Hello, I've tried to use different USB to Ethernet adapters with QubesOS but without success. Is there a chance to make them usable? I've seen some have been successful. Where is it not working? Have you checked sys-usb's "ip addr" and journalctl after plugging one in? Sorry for my unprecise way of asking. It's not working on a Dell XPS Laptop with QubesOS booted from USB. So far I have only used external USB memory media as removable devices in QubesOS, which can be listed with qvm-block and can be perfectly used and assigned to appVMs with the Devices Widget. After plugging in the USB to ethernet adapter the following is shown: $ journalctl | grep usb | tail -8 Jan 12 16:18:33 dom0 kernel: usb 2-1: USB disconnect, device number 7 Jan 12 16:19:49 dom0 kernel: usb 2-6: new SuperSpeed USB device number 8 using xhci_hcd Jan 12 16:19:49 dom0 kernel: usb 2-6: New USB device found, idVendor=0bda, idProduct=8153 Jan 12 16:19:49 dom0 kernel: usb 2-6: New USB device strings: Mfr=1, Product=2, SerialNumber=6 Jan 12 16:19:49 dom0 kernel: usb 2-6: Product: USB 10/100/1000 LAN Jan 12 16:19:49 dom0 kernel: usb 2-6: Manufacturer: Realtek Jan 12 16:19:49 dom0 kernel: usb 2-6: SerialNumber: 0100 Jan 12 16:19:50 dom0 kernel: usb 2-6: reset SuperSpeed USB device number 8 using xhci_hcd $ qvm-usb BACKEND:DEVID DESCRIPTION USED BY So the adapter is recognized on usb 2-6. This also works with a second adapter of a different brand. And it works on different USB slots. I haven't tried that with external USB hubs so far. I plugged them directly into the Laptop. The Devices Widget only shows local harddisk's partitions and the camera owned by dom0. There is no VM called "sys-usb". I read at https://www.qubes-os.org/doc/usb/ that creating and using a USB cube could kill functionality of the USB keyboard in a LUKS install. As this combination is the case here (internal keyboard is USB) I don't think creating one would be a good idea. Thanks @awokd. I understand, that dom0 has no networking on purpose. That's a good point. But even if it can't do it's networking job in dom0, I still wonder why the adapter isn't visible in the Device Widget. Shouldn't the USB part of it still be assignable to an appVM? As I don't even know exactly the meaning of things like "usb 2-6", how could I find out how many USB controllers the machine has and which one the keyboard is assigned to? Is such an assignment static or somehow dynamic? I'd really like to use LAN by cable but don't want to risk to lock myself out. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/8dd5a41a-991d-b63a-33db-493363f73008%40posteo.net. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Kernel panic due to Ctrl+C interrupted dom0 update and reboot
Hi, Error message : [3.680649] Call Trace: [3.680707] dump_stack+0x5c/0x85 [3.680764] panic+0xe4/0x252 [3.681184] mount_block_root+0x35b/0x52c [3.681601] ? do_early_param+0x16e/0x16e [3.682018] prepare_namespace+0x278/0x2d5 [3.682434] ? do_early_param+0x16e/0x16e [3.682851] kernel_init_freeable+0x2e8/0x32d [3.683270] ? rest_init+0xb0/0xb0 [3.683685] kernel_init+0xa/0x101 [3.684101] ret_from_fork+0x35/0x40 [3.684536] Kernel Offset: disabled. So, I booted into recovery mode prompt from a USB key (Troubleshooting and Rescue a Qubes system (read-write choice). It seems that I can’t boot an older kernel version. # ls /boot initramfs-vmlinuz-4.14.74-1.pvops.qubes.x86_64 # I don't really know what to do to fix it. Your help will be greatly appreciated! Thank you a lot for your valued assistance -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/396a1866-6004-4320-a48f-3921967356fd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Smart cards, split GPG, and timing attacks
That makes sense. How should one best handle GitHub accounts? One per project? GitHub does not seem to allow per-project SSH keys, sadly. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/bc07144f-672b-47b3-9e08-7d8f7ce56671%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] USB 3.0 to Ethernet adapter with QubesOS possible?
gone wrote on 1/12/19 5:03 PM: On 1/12/19 1:44 AM, 'awokd' via qubes-users wrote: gone wrote on 1/11/19 9:01 PM: Hello, I've tried to use different USB to Ethernet adapters with QubesOS but without success. Is there a chance to make them usable? I've seen some have been successful. Where is it not working? Have you checked sys-usb's "ip addr" and journalctl after plugging one in? Sorry for my unprecise way of asking. It's not working on a Dell XPS Laptop with QubesOS booted from USB. So far I have only used external USB memory media as removable devices in QubesOS, which can be listed with qvm-block and can be perfectly used and assigned to appVMs with the Devices Widget. After plugging in the USB to ethernet adapter the following is shown: $ journalctl | grep usb | tail -8 Jan 12 16:18:33 dom0 kernel: usb 2-1: USB disconnect, device number 7 Jan 12 16:19:49 dom0 kernel: usb 2-6: new SuperSpeed USB device number 8 using xhci_hcd Jan 12 16:19:49 dom0 kernel: usb 2-6: New USB device found, idVendor=0bda, idProduct=8153 Jan 12 16:19:49 dom0 kernel: usb 2-6: New USB device strings: Mfr=1, Product=2, SerialNumber=6 Jan 12 16:19:49 dom0 kernel: usb 2-6: Product: USB 10/100/1000 LAN Jan 12 16:19:49 dom0 kernel: usb 2-6: Manufacturer: Realtek Jan 12 16:19:49 dom0 kernel: usb 2-6: SerialNumber: 0100 Jan 12 16:19:50 dom0 kernel: usb 2-6: reset SuperSpeed USB device number 8 using xhci_hcd $ qvm-usb BACKEND:DEVID DESCRIPTION USED BY So the adapter is recognized on usb 2-6. This also works with a second adapter of a different brand. And it works on different USB slots. I haven't tried that with external USB hubs so far. I plugged them directly into the Laptop. The Devices Widget only shows local harddisk's partitions and the camera owned by dom0. There is no VM called "sys-usb". I read at https://www.qubes-os.org/doc/usb/ that creating and using a USB cube could kill functionality of the USB keyboard in a LUKS install. As this combination is the case here (internal keyboard is USB) I don't think creating one would be a good idea. Thanks for the added detail! Not running a sys-usb is probably why you are having trouble with the adapter. Dom0 has no networking by design, so if your USB devices are getting connected to it networking won't work. Does that laptop have another USB controller not used by the keyboard? If it does, you could make a sys-usb with just that controller and try again. If not, I think you might be stuck with the internal wifi. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/156cb87b-8ade-f84f-79e9-b43db1c2c4df%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Keyboard backlight color based on active qube
On Saturday, January 12, 2019 at 2:48:24 PM UTC-5, Brendan Hoar wrote: > ...I took Marmarek's keyboard-color script, modified it a bit, and voila, I > now have a little night-light indicator as an extra reminder on which VM has > focus. In action: https://www.youtube.com/watch?v=qIbFJvUgMa4 Brendan -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/ec0dddfb-7069-4bd6-858a-dcf2dfd349f8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Problem installing 4.0.1 on an HP laptop model 15t-da000
Folk, I am trying to install 4.0.1 on a new HP laptop model 15t-da000. It has one 250G SSD and one 1 TB SATA drives, i7 cpu, intel graphics. I have overwritten the Windows 10 default installation with KDE neon (ubuntu based), using about 100G of the 250G SSD. I am trying to make a dual boot with 4.0.1 on the remaining 130-ish Gig of the SSD. The installation seemed to start fine, though the default file system format of "LVM thin client" would not work, so I chose LVM. Installation chugged along until the end when I got the error "failed to install boot loader. To you want to continue? It will not be bootable..." or something to that effect. I indicated "yes" just to see what would happen, and it completed. On reboot, neither Qubes nor KDE neon would come up, no grub menu came up, and no explicit EFI locations came up in the BIOS boot menu -- though the two disk drives were mentioned (and would not boot). So, I reinstalled KDE neon, at which point the grub menu came up and gave me both Qubes and KDE options. Just for giggles, I chose Qubes, and the initial config screen came up. I chose the default config, and it gave me the error that the kernel file was not found and hung. KDE neon comes up fine. I tried to do an installation again, only I chose "standard partition" instead of "LVM." It didn't seem to make a difference -- it still hung at "failed to install boot loader." I stopped it at that point because I had some work to do and didn't want to have to reinstall the ubuntu partition. Any pointers would be appreciated. Thanks! billo -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/b75b3ab6-e359-4284-b534-ae9ae90512a1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Keyboard backlight color based on active qube
> > On Thursday, October 11, 2018 at 1:01:12 PM UTC-4, Marek
> > Marczykowski-Górecki wrote:
> > > I've published the first post on my blog:
> > > https://blog.marmarek.net/blog/2018/10/11/keyboard-backlight-color-qubes.html
In the spirit of fun, after I ran across a $13 USB device that is, essentially,
a serial-port connected RGB LED...
https://fit-iot.com/web/product/fit-statusb/
http://www.fit-pc.com/wiki/index.php/Fit-statUSB
...I took Marmarek's keyboard-color script, modified it a bit, and voila, I now
have a little night-light indicator as an extra reminder on which VM has focus.
My wife was amused...ish at this < 2hr project.
Right now, I don't have any custom scripts or executables on the sys-usb side,
the script just printf's to a cat >> redirect. There probably should be
something sys-usb side to identify the correct /dev/ttyACM{0,1,2} device, set
the tty speed and reset the permissions, esp. after a suspend or
removal/insertion.
Enjoy
https://pastebin.com/H6bj5tSS
Brendan
--
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/1021fb81-123d-4f2b-88f9-0abb081c49c2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[qubes-users] Device Widget doesn't show USB devices
Hi, on my laptop qubes this doesn't show any usb devices, and an external keyboard using USB doesn't work. What can I check and do? I compare my settings to my other machine running 4.0 and they look the same, and do see USB. One difference - I do not see a sys-USB on my machine that DOES work with USB, and I DO see the sys-USB on the laptop that doesn't show USB. Thoughts? Thanks, Patrick -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/3cd3a86d-58ef-4deb-9d20-b220a47b7d4c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Set up a ProxyVM as a Wireguard instead of a OpenVPN gateway
On 01/12/2019 10:47 AM, Ivan Mitev wrote: On 1/12/19 5:16 PM, Daniil Travnikov wrote: Does anyone know how could be configured the Wireguard (https://www.wireguard.com/) in Proxy VM? Maybe do you know some doc like https://www.qubes-os.org/doc/vpn/ where it is already described step by step? I understand that this is new technology, but maybe someone knows which OS is more preferable and what is the first step in the settings? The following thread might be helpful, although it's a bit old: https://groups.google.com/d/msg/qubes-users/MQaePIslfY8/k0s65DfaCQAJ Yeah, that's old and not really useful now. Currently you can get a full Qubes wireguard setup using Qubes-vpn-support, which has been tested with Mullvad's wireguard service: https://github.com/tasket/Qubes-vpn-support/ To change it from openvpn to wireguard after installation in a "proxy" provides-network appVM, look in the /rw/config/qubes-vpn-handler.service.d directory and rename '10_wg.conf.example' to '10_wg.conf'. You may also have to create your proxy VM as a standalone and run "qvm-prefs vmname kernel ''" to blank out the kernel setting. Then boot and install the 'wireguard' package. -- Chris Laprise, tas...@posteo.net https://github.com/tasket https://twitter.com/ttaskett PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/e0cc892c-f41b-0bc4-7fc1-ac6815401347%40posteo.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] USB 3.0 to Ethernet adapter with QubesOS possible?
On 1/12/19 1:44 AM, 'awokd' via qubes-users wrote: gone wrote on 1/11/19 9:01 PM: Hello, I've tried to use different USB to Ethernet adapters with QubesOS but without success. Is there a chance to make them usable? I've seen some have been successful. Where is it not working? Have you checked sys-usb's "ip addr" and journalctl after plugging one in? Sorry for my unprecise way of asking. It's not working on a Dell XPS Laptop with QubesOS booted from USB. So far I have only used external USB memory media as removable devices in QubesOS, which can be listed with qvm-block and can be perfectly used and assigned to appVMs with the Devices Widget. After plugging in the USB to ethernet adapter the following is shown: $ journalctl | grep usb | tail -8 Jan 12 16:18:33 dom0 kernel: usb 2-1: USB disconnect, device number 7 Jan 12 16:19:49 dom0 kernel: usb 2-6: new SuperSpeed USB device number 8 using xhci_hcd Jan 12 16:19:49 dom0 kernel: usb 2-6: New USB device found, idVendor=0bda, idProduct=8153 Jan 12 16:19:49 dom0 kernel: usb 2-6: New USB device strings: Mfr=1, Product=2, SerialNumber=6 Jan 12 16:19:49 dom0 kernel: usb 2-6: Product: USB 10/100/1000 LAN Jan 12 16:19:49 dom0 kernel: usb 2-6: Manufacturer: Realtek Jan 12 16:19:49 dom0 kernel: usb 2-6: SerialNumber: 0100 Jan 12 16:19:50 dom0 kernel: usb 2-6: reset SuperSpeed USB device number 8 using xhci_hcd $ qvm-usb BACKEND:DEVID DESCRIPTION USED BY So the adapter is recognized on usb 2-6. This also works with a second adapter of a different brand. And it works on different USB slots. I haven't tried that with external USB hubs so far. I plugged them directly into the Laptop. The Devices Widget only shows local harddisk's partitions and the camera owned by dom0. There is no VM called "sys-usb". I read at https://www.qubes-os.org/doc/usb/ that creating and using a USB cube could kill functionality of the USB keyboard in a LUKS install. As this combination is the case here (internal keyboard is USB) I don't think creating one would be a good idea. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/3192d93d-3956-0c82-9338-93cf947c29e8%40posteo.net. For more options, visit https://groups.google.com/d/optout.
[qubes-users] OpenSC smartcards + LVM
Dear all, This is my first post, so I would like to thank the community for the hard work around Qubes. Here are some questions before I consider replacing my system with Cubes. 1) OpenSC smartcards I would like to use OpenSC smartcard with pinpad reader to secure my SSH key. The pinpad reader is a USB device. Is Qubes suitable for that? Shall I create a minimal debian template, install OpenSC and libccid, allow USB device. Then shall I run a disposable VM each time I want to access a remote server using SSH? 2) Disc access + LVM What is the technology used for disc access? The question is that I am considering running a PostgreSQL database and it might be running slowly on a disc image. I read in documentation that dom0 had its own LVM logical volume (LV). I also read that VMs were stored in a disc image. Can VMs have their own logical volume ? Kind regards, -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/1106738391.57850.154731205%40office.mailbox.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Questions about Qubes : OpenSC, LVM, etc ...
Dear all, This is my first post, so I would like to thank the community for the hard work around Qubes. Here are some questions before I consider replacing my system with Cubes. 1) OpenSC smartcards I would like to use OpenSC smartcard with pinpad reader to secure my SSH key. The pinpad reader is a USB device. Is Qubes suitable for that? Shall I create a minimal debian template, install OpenSC and libccid, allow USB device. Then shall I run a disposable VM each time I want to access a remote server using SSH? 2) Disc access + LVM What is the technology used for disc access? The question is that I am considering running a PostgreSQL database and it might be running slowly on a disc image. I read in documentation that dom0 had its own LVM logical volume (LV). I also read that VMs were stored in a disc image. Can VMs have their own logical volume ? Kind regards, Alexandre Belgrand -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/729006416.57825.1547311727500%40office.mailbox.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] "Qubes Update" icon (Sun Looking icon on top right)
Just used this feature again...Debian-9, Fedora-29 and Dom0 updates(or lack of) went fine i.e. My Fedora templates seemed to update and no updates were needed for Dom0 or my Debian templates. My Whonix-14-GW and -WS however did deliver an error that might be related to what you refer to Marek. The sun icon gives me the following error(abbreviated): File "/var/tmp/.root_62a99a_saltimport salt.modules.cmdmod File "/var/tmp/.root_62a99a_saltimport salt.util.http File "/var/tmp/.root_62a99a_saltimport salt.util.events ... ImportError: No module named concurrent...CancelledError stdout: I manually updated the whonix-gw and -ws using the Qubes Manager OK. Any chance some one can share the commands to allow me to update using the "sun icon"? Its nice to check all templates for updates and have them run in the back ground one-by-one. I thought this would crash my system but worked pretty slick appart from the whonix-gw and -ws error I got... Again thanks to all for the help! Marek you do good work!! awokd/799 thanks for your engagement... -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/cc02c036-7b82-4f9d-aea5-47fb7f3a9aa8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] fedora-28 upgrade to fedora-29 messes up the wireless network icon
I have never "upgraded" my templates...new template installs only, however over time I too have seen distorted icons including: * Looks like 2 icons on top of themselves * Very "Red" icon for sys-net that also is a little difficult to see signal strength... Just thought I would add my insight... -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/e0548e34-4323-4442-bafd-be938c74e7e6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Set up a ProxyVM as a Wireguard instead of a OpenVPN gateway
On 1/12/19 5:16 PM, Daniil Travnikov wrote: > Does anyone know how could be configured the Wireguard > (https://www.wireguard.com/) in Proxy VM? > > Maybe do you know some doc like https://www.qubes-os.org/doc/vpn/ where it is > already described step by step? > > I understand that this is new technology, but maybe someone knows which OS is > more preferable and what is the first step in the settings? The following thread might be helpful, although it's a bit old: https://groups.google.com/d/msg/qubes-users/MQaePIslfY8/k0s65DfaCQAJ -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/3a9c7b8a-8267-e603-bcc8-ba5581a06d7b%40maa.bz. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Set up a ProxyVM as a Wireguard instead of a OpenVPN gateway
Does anyone know how could be configured the Wireguard (https://www.wireguard.com/) in Proxy VM? Maybe do you know some doc like https://www.qubes-os.org/doc/vpn/ where it is already described step by step? I understand that this is new technology, but maybe someone knows which OS is more preferable and what is the first step in the settings? -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/e842dd0d-627a-480a-a39a-045321b5fca8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Fedora 29 update metadata does not expire
After switching to the Fedora 29 template, I noticed I have to clean old metadata in order to update it, or I will get this: Last metadata expiration check: 5 days, 18:23:45 ago. Dependencies resolved. Nothing to do. Complete! With the older Fedora versions it usually expired after a day or so, but I have even seen another templatevm with last check 13 days ago, that's crazy long. Is there some setting to let it refresh after X time so I don't have to manually clean metadata and launch the update again? -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/993be68d-7169-4abd-8c79-1260ac68214e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: USB Keyboard no longer reachable following recent update
On Saturday, 12 January 2019 12:52:29 UTC, Alex Dubois wrote: > Hi, > > Did a qubes-dom0-update + fedora template update last night. Reboot this > morning and I can't reach the USB keyboard anymore. > > I can't remember if I had removed my sys-usb VM after I got bitten recently > and fixed the situation following this > https://github.com/QubesOS/qubes-issues/issues/2270. > > Following the explanation there I could boot and use the USB keyboard from my > fedora on USB-key: > I did not have any entry with rd.qubes.hide_all_usb in xen-4.x.x.config > And I did not have a file > /etc/systemd/system/multi-user.target.wants/qubes-vm@sys-usb.service. > > Any hint appreciated. > > I am using Qubes as my home firewall and the entire house is disconnected > (can't reconnect easily as I have VLans all over the place, dns server on > QubesOS, etc...). Had to edit out from grub.cfg rd.qubes.hide_all_usb entries to be able to enter the LUKS password -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/e0ea7822-6b25-4956-b508-154a1e70b038%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] USB Keyboard no longer reachable following recent update
Hi, Did a qubes-dom0-update + fedora template update last night. Reboot this morning and I can't reach the USB keyboard anymore. I can't remember if I had removed my sys-usb VM after I got bitten recently and fixed the situation following this https://github.com/QubesOS/qubes-issues/issues/2270. Following the explanation there I could boot and use the USB keyboard from my fedora on USB-key: I did not have any entry with rd.qubes.hide_all_usb in xen-4.x.x.config And I did not have a file /etc/systemd/system/multi-user.target.wants/qubes-vm@sys-usb.service. Any hint appreciated. I am using Qubes as my home firewall and the entire house is disconnected (can't reconnect easily as I have VLans all over the place, dns server on QubesOS, etc...). -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/aa317785-af08-4a3c-ac52-fdf3f11cd066%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Issues installing QubesOS on Samsung Gateway from bootable external hard drive
Hello everybody! Set up qubes on external hard drive to boot upon launch. Downloaded latest version from [https://www.qubes-os.org](https://www.qubes-os.org/) Installer loads fine, proceeds with install, but then I get these errors: [ 215.94. ] dracut-initqueue[649]: Warning: dracut-initqueue timeout - starting timeout scripts [ 215.94. ] dracut-initqueue[649]: Warning: Could not boot [ 215.94. ] dracut-initqueue[649]: Warning: /dev/root does not exist Starting Dracut Emergency Shell Warning: /dev/root does not exist Generating "/run/initramfs/rdsosreport.txt" Entering emergencym ode. Exit the shell to continue. Type "journalctl" to view system logs. You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot after mounting them and attach it to the bug report. And when I enter journalctl I get a thousand line report. Laptop: Samsung Gateway 700Z series. Let me know which more data should I submit to help troubleshoot and find solution to this problem. Looking forward to hearing any tips, NewbieLinuxUser -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/bHU50cw4MmYLSw2E15vUWCfnVQUe1bwmSQz9UwrjtWnNzY431vprCA3mrI-1cssTwUXZUZNw19YDfUZ4qUKcs_uoZ_ICLJjG6hs_mLCEB9g%3D%40protonmail.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] ANN: blib - a bash library
Dear all,
I recently released blib [1], a bash library which also aims to be
useful for Qubes OS bash developers.
The documentation can be found at [2], the Qubes specific part at [3].
A short example of what it can do:
---
#!/bin/bash
source blib
b_import "os/qubes4/dom0"
function getTheAnswer {
echo "There's none?!"
return 42
}
vm="d-testing"
b_dom0_ensureRunning "$vm" || { B_ERR="Failed to start the VM ${vm}.
Maybe it doesn't exist?" ; B_E }
b_silence b_dom0_execFuncIn "$vm" "" "getTheAnswer"
echo "The answer to everything, computed by the VM ${vm}: $?"
---
Please let me know if there's any issues with it.
Best Regards
David
[1] https://github.com/3hhh/blib
[2] https://3hhh.github.io/blib-doc/blib.html
[3] https://3hhh.github.io/blib-doc/blib.html#osqubes4dom0
--
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/55f125e3-2948-3c68-1956-c325e19e3be2%40hackingthe.net.
For more options, visit https://groups.google.com/d/optout.
smime.p7s
Description: S/MIME Cryptographic Signature
Re: [qubes-users] fedora-29-minimal sys-net/firewall problem
On Saturday, January 12, 2019 at 6:59:38 AM UTC+1, rumsey@gmail.com wrote: > Thanks to Ivan, I figured it out (with a bit of luck). > > After comparing packages in his working template to my own, I first tried to > install: > > dbus-glib > ipcalc > iproute > iproute-tc > iputils > > That fixed it as far as I can tell. I now have a working sys-net and > sys-firewall with the fedora-29-minimal template. I'm assuming the ip* > packages were the key, but I don't really have any idea. Thanks for taking the time to compare the installed package lists. :) -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/558e0ef1-a4bb-4f4e-9df2-9d078008c9f7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
