[qubes-users] Re: HCL - Thinkpad x220, Qubes 4.1 + Heads firmware
Hi Jolly, could you please give a complete manual on this setup? How to make the heads firmware, how to flash it (ME will stop you from using flashrom -p internal). Some SPI programming experiments with raspi-pi were not successfull at least for me. It seems that the unpowered chipset of the computer pulls the data to ground and eats 3.3V so the programmer has no power to live. A complete tutorial to set this up would be cool. And if you make a video, better than nothing. Thanks in advance Ludwig On Friday, August 20, 2021 at 5:13:40 PM UTC+2 jolly@tuta.io wrote: > > Thanks for the work you've done! > P.S. x220 will never die :) > -- 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/fc2fb12b-3161-4a42-8750-8429bf431ca8n%40googlegroups.com.
Re: [qubes-users] i915 driver problems
The current Intel driver, which does not work for me, is xorg-x11-drv-intel-2.99.917-48.20200205.fc33.x86_64.rpm Just use dnf to uninstall it. actually Q4.0.4 ships with xorg-x11-drv-intel-2.99.917-49.20210126.fc25.x86_64.rpm which does not work for me either. The one I installed using dnf is xorg-x11-drv-intel-2.99.917-32.20171025.fc33.x86_64.rpm and this does work OK. this one is from Q4.0.1, qhereas Q4.0.0 ships xorg-x11-drv-intel-2.99.917-26.20160929.fc25.x86_64.rpm So you confirm that you install it in dom0 via sudo dnf install xorg..whatever.rpm (that requires deleting kernel-latest-qubes-vm, if present). Then you need to do an update-grub or something similar to build the downgraded version in the respective initramfs ??? Bernhard -- 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/6d0e8fda-3077-3a24-0b81-490d33a7fa39%40web.de.
[qubes-users] building cubes how to include custom patches
Hi all, I would like to patch some sources of xen and would like to know how to introduce the patches into the build system. Regards, Ludwig -- 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/8f585861-a8cd-4bf1-b1eb-9f42d24f6e78n%40googlegroups.com.
[qubes-users] qubes build system is fragile
Hi all,
has someone a VM of a 100% working qubes-build system?
I am trying to get qubes-build running on
-qubes machine, here I have dedicated 8 cores of my workstation
-stand alone machine with fc33, 48 cores of Xeon(R) CPU E5-2697 v2 @
2.70GHz
with 128GB RAM in both cases I dont have success.
Also there is a "mount problem" that make remount does not solve as
advertised
in the error message.
One needs to disable selinux completely then this works, which I found
after some
web search...
And now on both machines it stops with a problem in libvirt.
"
Now it spits an error:
[sudo] password for build:
-> Building core-libvirt (libvirt.spec) for fc33 dom0 (logfile:
build-logs/core-libvirt-dom0-fc33.log)
--> build failed!
make[2]: Entering directory '/home/build/src/qubes-builder'
/home/build/src/qubes-builder/qubes-src/builder-rpm//update-local-repo.sh
fc33
sudo BACKEND_VMM=xen dnf
--installroot=/home/build/src/qubes-builder/chroot-dom0-fc33
--installroot=/home/build/src/qubes-builder/chroot-dom0-fc33 --refresh -y
update
Qubes OS Builder Repository 2.9 MB/s | 3.0 kB
00:00
Qubes OS Builder Repository 456 kB/s | 22 kB
00:00
Fedora 33 - x86_64 235 kB/s | 26 kB
00:00
Fedora 33 openh264 (From Cisco) - x86_64 12 kB/s | 989 B
00:00
Fedora 33 - x86_64 - Updates109 kB/s | 10 kB
00:00
Fedora 33 - x86_64 - Updates1.8 MB/s | 2.9 MB
00:01
Dependencies resolved.
Nothing to do.
Complete!
sudo BACKEND_VMM=xen chroot /home/build/src/qubes-builder/chroot-dom0-fc33
su -c 'rpmspec -P --define "debug_package %{nil}" --define "fedora 33"
--define "dist .fc33" --define "fedora 33" --define "dist .fc33"
/home/user/qubes-src/core-libvirt/libvirt.spec >
/home/user/qubes-src/core-libvirt/libvirt.spec.parsed' - user
cat: version: No such file or directory
error: line 275: Empty tag: Version:
make[2]: ***
[/home/build/src/qubes-builder/qubes-src/builder-rpm/Makefile-legacy.rpmbuilder:51:
dist-build-dep.spec] Error 1
make[2]: Leaving directory '/home/build/src/qubes-builder'
make[1]: *** [Makefile.generic:191: packages] Error 1
make[1]: Leaving directory '/home/build/src/qubes-builder'
make: *** [Makefile:267: core-libvirt-dom0] Error 1
"
As the core developers are having a working build system, it would be nice,
if
they could just share the complete VM so it easy to just use it. No more
brushing
of big animals with dirty furs.
Anyone who just has a working qubes builder and who is willing to share it,
so I can run it with qemu, virtualbox or something else?
I just want to change 10 lines of Xen code and I find my self brusing fury
animals for more than a week (not the main work, but it is a waste of time,
the fragile qubes build system)
Thanks and best Regards,
Ludwig
--
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/2fbe89f0-ec04-4c20-930b-812d302344e4n%40googlegroups.com.
# vim: ft=make ts=4 sw=4
# Ready to use config for full build of the latest development version Qubes OS
(aka "master").
GIT_BASEURL ?= https://github.com
GIT_PREFIX ?= QubesOS/qubes-
NO_SIGN ?= 1
BACKEND_VMM=xen
DIST_DOM0 ?= fc33
DISTS_VM ?= fc33 buster
MGMT_COMPONENTS = \
mgmt-salt \
mgmt-salt-base \
mgmt-salt-base-topd \
mgmt-salt-base-config \
mgmt-salt-dom0-qvm \
mgmt-salt-dom0-virtual-machines \
mgmt-salt-dom0-update
COMPONENTS ?= \
vmm-xen \
core-libvirt \
core-vchan-xen \
core-qubesdb \
core-qrexec \
linux-utils \
python-cffi \
python-xcffib \
python-objgraph \
python-hid \
python-u2flib-host \
python-qasync \
python-panflute \
rpm-oxide \
core-admin \
core-admin-client \
core-admin-addon-whonix \
core-admin-linux \
core-agent-linux \
intel-microcode \
linux-firmware \
linux-kernel \
artwork \
grub2 \
grub2-theme \
gui-common \
gui-daemon \
gui-agent-linux \
gui-agent-xen-hvm-stubdom \
seabios \
vmm-xen-stubdom-legacy \
vmm-xen-stubdom-linux \
app-linux-split-gpg \
app-thunderbird \
app-linux-pdf-converter \
app-linux-img-converter \
app-linux-input-proxy \
app-linux-usb-proxy \
app-linux-snapd-helper \
app-shutdown-idle \
app-yubikey \
app-u2f \
screenshot-helper \
$(MGMT_COMPONENTS) \
infrastructure \
repo-templates \
meta-packages \
manager \
desktop-linux-common \
desktop-linux-kde \
desktop-linux-xfce4 \
desktop-linux-xfce4-xfwm4 \
desktop-linux-i3 \
desktop-linux-i3-settings-qubes \
desktop-linux-awesome \
[qubes-users] Re: qubes build system is fragile
Now I tried again: make clean make install-deps make get-sources make qubes after a short while: " gcc -m64 -DBUILD_ID -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes -Wdeclaration-after-statement -Wno-unused-but-set-variable -Wno-unused-local-typedefs -O2 -fomit-frame-pointer -D__XEN_INTERFACE_VERSION__=__XEN_LATEST_INTERFACE_VERSION__ -MMD -MP -MF .afl-harness.d -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -ffile-prefix-map=/home/user/rpmbuild/BUILD/xen-4.14.2/tools/fuzz/x86_instruction_emulator/../../..=. -O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -Wno-error=declaration-after-statement -I/home/user/rpmbuild/BUILD/xen-4.14.2/tools/fuzz/x86_instruction_emulator/../../../tools/include -D__XEN_TOOLS__ -I. afl-harness.o fuzz-emul.o x86-emulate.o cpuid.o wrappers.o -o afl-harness /usr/bin/ld: /tmp/afl-harness.R8wVcg.ltrans0.ltrans.o: in function `data_read': /usr/include/bits/string_fortified.h:29: undefined reference to `emul_memcpy' /usr/bin/ld: /tmp/afl-harness.R8wVcg.ltrans0.ltrans.o: in function `data_read': /usr/include/bits/stdio2.h:110: undefined reference to `emul_putchar' /usr/bin/ld: /tmp/afl-harness.R8wVcg.ltrans0.ltrans.o: in function `fuzz_read_msr': /usr/include/bits/stdio2.h:110: undefined reference to `emul_puts' /usr/bin/ld: /tmp/afl-harness.R8wVcg.ltrans0.ltrans.o: in function `dump_state': /usr/include/bits/stdio2.h:110: undefined reference to `emul_puts' /usr/bin/ld: /tmp/afl-harness.R8wVcg.ltrans0.ltrans.o: in function `check_state': /usr/include/bits/stdio2.h:110: undefined reference to `emul_puts' /usr/bin/ld: /tmp/afl-harness.R8wVcg.ltrans0.ltrans.o: in function `LLVMFuzzerTestOneInput.constprop.0.isra.0': /usr/include/bits/stdio2.h:110: undefined reference to `emul_puts' /usr/bin/ld: /usr/include/bits/stdio2.h:110: undefined reference to `emul_puts' /usr/bin/ld: /tmp/afl-harness.R8wVcg.ltrans0.ltrans.o:/usr/include/bits/stdio2.h:110: more undefined references to `emul_puts' follow /usr/bin/ld: /tmp/afl-harness.R8wVcg.ltrans0.ltrans.o: in function `LLVMFuzzerTestOneInput.constprop.0.isra.0': /usr/include/bits/string_fortified.h:29: undefined reference to `emul_memcpy' /usr/bin/ld: /tmp/afl-harness.R8wVcg.ltrans0.ltrans.o: in function `LLVMFuzzerTestOneInput.constprop.0.isra.0': /home/user/rpmbuild/BUILD/xen-4.14.2/tools/fuzz/x86_instruction_emulator/x86_emulate/x86_emulate.c:8782: undefined reference to `emul_memcmp' /usr/bin/ld: /tmp/afl-harness.R8wVcg.ltrans0.ltrans.o: in function `LLVMFuzzerTestOneInput.constprop.0.isra.0': /usr/include/bits/string_fortified.h:56: undefined reference to `emul_memset' /usr/bin/ld: /usr/include/bits/string_fortified.h:29: undefined reference to `emul_memcpy' /usr/bin/ld: /usr/include/bits/string_fortified.h:56: undefined reference to `emul_memset' /usr/bin/ld: /usr/include/bits/string_fortified.h:56: undefined reference to `emul_memset' /usr/bin/ld: /usr/include/bits/string_fortified.h:29: undefined reference to `emul_memcpy' /usr/bin/ld: /tmp/afl-harness.R8wVcg.ltrans0.ltrans.o: in function `main': /usr/include/bits/stdio2.h:110: undefined reference to `emul_puts' collect2: error: ld returned 1 exit status make[6]: *** [Makefile:43: afl-harness] Error 1 make[6]: Leaving directory '/home/user/rpmbuild/BUILD/xen-4.14.2/tools/fuzz/x86_instruction_emulator' make[5]: *** [/home/user/rpmbuild/BUILD/xen-4.14.2/tools/fuzz/../../tools/Rules.mk:242: subdir-install-x86_instruction_emulator] Error 2 make[5]: Leaving directory '/home/user/rpmbuild/BUILD/xen-4.14.2/tools/fuzz' make[4]: *** [/home/user/rpmbuild/BUILD/xen-4.14.2/tools/fuzz/../../tools/Rules.mk:237: subdirs-install] Error 2 make[4]: Leaving directory '/home/user/rpmbuild/BUILD/xen-4.14.2/tools/fuzz' make[3]: *** [/home/user/rpmbuild/BUILD/xen-4.14.2/tools/../tools/Rules.mk:242: subdir-install-fuzz] Error 2 make[3]: Leaving directory '/home/user/rpmbuild/BUILD/xen-4.14.2/tools' make[2]: *** [/home/user/rpmbuild/BUILD/xen-4.14.2/tools/../tools/Rules.mk:237: subdirs-install] Error 2 make[2]: Leaving directory '/home/user/rpmbuild/BUILD/xen-4.14.2/tools' make[1]: *** [Makefile:72: install] Error 2 make[1]: Leaving directory '/home/user/rpmbuild/BUILD/xen-4.14.2/tools' make: *** [Makefile:134: install-tools] Error 2 error: Bad exit status from /var/tmp/rpm-tmp.96o9LJ (%build) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.96o9LJ (%build) make[2]: *** [/home/build/src/qubes-builder/qubes-src/builder-rpm/Makefile-legacy.rpmbuilder:66: dist-package-build] Error 1 make[2]: Leaving directory '/home/build/src/qubes-builder' make[1]: *** [Makefile.generic:191: packages] Error 1 make[1]: Leaving directory '/home/build/s
[qubes-users] Re: HCL - Dell XPS 13 (9360)
Hey, wanted to say thanks for the tips. The settings you provided gave me a smooth install. I wanted to come by and say my webcam, USB-C and MIC worked. The USB-C was a WD19S dock and at first it wasn't working except to charge my laptop. After running updates through Qubes it worked after a few reboots and has been working since. I didn't mess with it too much, it just kind of happened. My 9360 already had an Intel network card, only has 8gb of RAM but is an i5-7300u. Again, appreciate the post. On Thursday, May 24, 2018 at 5:27:07 PM UTC-4 Satnam Ram wrote: > I just installed the latest Qubes R4.0 on my XPS 13 FHD-Model (9360). It > required some minor tweaking. > > 1. Preparation > > - update your BIOS > Version: 2.6.2 Release Date: 22 Mar 2018 > - replace killer wifi with an Intel 8265 card > - apply Thunderbolt 3 Firmware Update (don't know if this was required) > - apply adaptive brightness display firmware update (only if you want/need > it) > > 2. BIOS Settings > > - change SATA Operation from "RAID On" to "AHCI" > - disable secure boot > - disable EFI (the first time the Installer froze while installing the > Whonix template) > - disable Intel SpeedStep (!!!) > If you don't the OS will run a lot slower if you start the device > unplugged no matter if you > plug it in later. I can confirm the "happy" and "unhappy" states > described here: > https://groups.google.com/forum/#!topic/qubes-users/9Hqyepkp8XM > Booting on battery was about 1min25s for me while booting with AC gave > me 55s. After turning > it off I get about 55s in both situations which is fine. > > 3. Qubes > - enable trackpad features > add the Option entries to your > /usr/share/X11/xorg.conf.d/60-libinput.conf touchpad section > > Section "InputClass" > Identifier "libinput touchpad catchall" > MatchIsTouchpad "on" > MatchDevicePath "/dev/input/event*" > Driver "libinput" > ->Option "Tapping" "True" > ->Option "PalmDetection" "True" > ->Option "TappingDragLock" "True" > EndSection > > --- > > Update: > > I use Qubes for about a week now - primarily for go development with > Goland, browsing and watching videos. Everything I used worked very well. > The battery life is good. Video playback and similar things (using software > rendering) heat up the CPU and drain considerably more power (my estimated > remaining time is usually halfed). Booting takes about 1 minute (starting > net, firewall and whonix qubes). Suspend to RAM works most of the time - > once in a while the screen stays black after resume - this is the only bug > I encountered so far but its negligible. I managed to install Kali 2018.1 > after I set the system volume size to 30GB (default setting caused the kali > installer to fail). I was able to expose my Intel 8265 directly to the kali > hvm and put it into monitoring mode. Rising initial memory to 1GB lowers > boot time for most VMs, setting a high VCPU count for VMs where you cannot > afford lag helped transitioning from bare metal. I installed Steam and > Factorio in a another VM and I was able to play with minor glitches > (v-sync) and major cpu heat. > > not tested: > - USB-C > - Webcam > - Mic (but its recognized) > > > -- 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/84264ff6-4cb9-4ffb-9ba0-87368f6f0c12n%40googlegroups.com.
Re: [qubes-users] i915 driver problems
On 9/2/21 1:44 PM, haaber wrote: The current Intel driver, which does not work for me, is xorg-x11-drv-intel-2.99.917-48.20200205.fc33.x86_64.rpm Just use dnf to uninstall it. actually Q4.0.4 ships with xorg-x11-drv-intel-2.99.917-49.20210126.fc25.x86_64.rpm which does not work for me either. The one I installed using dnf is xorg-x11-drv-intel-2.99.917-32.20171025.fc33.x86_64.rpm and this does work OK. this one is from Q4.0.1, qhereas Q4.0.0 ships xorg-x11-drv-intel-2.99.917-26.20160929.fc25.x86_64.rpm So you confirm that you install it in dom0 via sudo dnf install xorg..whatever.rpm (that requires deleting kernel-latest-qubes-vm, if present). Then you need to do an update-grub or something similar to build the downgraded version in the respective initramfs ??? Bernhard Hi Bernard, I just looked at my history in bash, and what I did was :- dnf downgrade xorg-x11-drv-intel-2.99.917-32.20171025 vi /etc/dnf/dnf.conf Appended "exclude=xorg-x11-drv-intel" as the last line in the file. Mike. -- 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/10e6607c-34c0-a52b-37e4-f4340805daca%40keehan.net.
Re: [qubes-users] i915 driver problems
On 9/2/21 7:24 PM, Mike Keehan wrote: On 9/2/21 1:44 PM, haaber wrote: The current Intel driver, which does not work for me, is xorg-x11-drv-intel-2.99.917-48.20200205.fc33.x86_64.rpm Just use dnf to uninstall it. actually Q4.0.4 ships with xorg-x11-drv-intel-2.99.917-49.20210126.fc25.x86_64.rpm which does not work for me either. The one I installed using dnf is xorg-x11-drv-intel-2.99.917-32.20171025.fc33.x86_64.rpm and this does work OK. this one is from Q4.0.1, qhereas Q4.0.0 ships xorg-x11-drv-intel-2.99.917-26.20160929.fc25.x86_64.rpm So you confirm that you install it in dom0 via sudo dnf install xorg..whatever.rpm (that requires deleting kernel-latest-qubes-vm, if present). Then you need to do an update-grub or something similar to build the downgraded version in the respective initramfs ??? Bernhard Hi Bernard, I just looked at my history in bash, and what I did was :- dnf downgrade xorg-x11-drv-intel-2.99.917-32.20171025 vi /etc/dnf/dnf.conf Appended "exclude=xorg-x11-drv-intel" as the last line in the file. Mike. Hmm, looking through the history list, there was a "yum downgrade" line after the dnf one. Might be that the "dnf downgrade" did not work. yum downgrade xorg-x11-drv-intel-2.99.917-32.20171025.fc25.x86_64.rpm that is the full filename of the rpm file. Mike. -- 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/a0369483-8c20-ffdd-2db6-fe5b73be62b7%40keehan.net.
Re: [qubes-users] qubes-builder fails rpmlock permission denied
ludwig...@gmail.com: Hi all, I try to roll my own variant of an qubes install cd and it does not work to build with system. It is stable and should work somehow, others did also build qubes. The machine runs FC33 on bare metal with newest updates -> Preparing fc33 build environment -> Initializing RPM database... error: can't create transaction lock on /home/build/src/qubes-builder/chroot-dom0-fc33/var/lib/rpm/.rpm.lock (Permission denied) make[1]: *** [/home/build/src/qubes-builder/qubes-src/builder-rpm/Makefile-legacy.rpmbuilder:37: /home/build/src/qubes-builder/chroot-dom0-fc33/home/user/.prepared_base] Error 1 FC33 is somewhat new, have you seen others build successfully with that version? Otherwise, double-check you aren't running make as a su/root. -- - don't top post Mailing list etiquette: - trim quoted reply to only relevant portions - when possible, copy and paste text instead of screenshots -- 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/e51a1ced-655d-a199-d6be-0ebb6d774051%40danwin1210.me.
Re: [qubes-users] usb keyboard not working on debian 11 template
'qtpie' via qubes-users: When I switch the sys-usb to a debian 11 template: (same) 4. I can use the keyboard inside the sys-usb qube, not in other qubes. The mousepointer does not respond at all. How can I troubleshoot this? thanks for your suggestions. Double-check you have the same Qubes packages installed in your deb11 template. I'd look for qubes-usb-proxy and qubes-input-proxy-sender first. -- - don't top post Mailing list etiquette: - trim quoted reply to only relevant portions - when possible, copy and paste text instead of screenshots -- 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/ac78ce88-b0a4-c409-9ce0-2e44744a5cd7%40danwin1210.me.
Re: [qubes-users] building cubes how to include custom patches
ludwig...@gmail.com: Hi all, I would like to patch some sources of xen and would like to know how to introduce the patches into the build system. There is a patch directory somewhere in the build environment where custom Qubes patches get applied to the Xen kernel. It may be inside the chroot filesystem, but I don't have a build VM handy to confirm. Run something like "sudo find -name *patch*" at the top level of your build machine and I think you can find it, then check the make file that applies the patches to add your own. -- - don't top post Mailing list etiquette: - trim quoted reply to only relevant portions - when possible, copy and paste text instead of screenshots -- 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/4c87814c-baa7-3180-9549-c43f5299b375%40danwin1210.me.
Re: [qubes-users] Re: qubes build system is fragile
ludwig...@gmail.com: /usr/bin/ld: /tmp/afl-harness.R8wVcg.ltrans0.ltrans.o: in function `data_read': These and subsequent errors suggest a (probably newer) package isn't supplying expected functions. Maybe try to build in an FC32 VM instead? -- - don't top post Mailing list etiquette: - trim quoted reply to only relevant portions - when possible, copy and paste text instead of screenshots -- 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/2dbe8ab2-7e9e-bfcd-ea9b-c5d2459e255e%40danwin1210.me.
