[qubes-users] xkb compose confusion
I use the "US international with dead keys" keyboard layout as a convenient way of getting accented characters. The keyboard is defined in: /usr/share/X11/xkb/symbols/us and the dead key combinations themselve are in: /usr/share/X11/locale/en_US.UTF-8/Compose I am currently customising the dead key combinations. This can be done by copying /usr/share/X11/locale/en_US.UTF-8/Compose to ~/.XCompose and making modifications there. But I have noticed a discrepancy between Fedora and Debian VMs. The default settings in Debian and Fedora are identical. In particular they both contain the line: : "ć" This implies that if I type a single quote followed by the "c" key I should get the character "ć" (unicode character U0107 or hex c487). In Debian VMs, this is indeed what happens. But in Fedora VMs, I get "ç" (unicode character U00E7 or hex c387). [If by way of experiment (in Fedora), I modify another line, setting, for example: : "ć" then I can get the "ć" character by typing a single quote followed by the "v" key. I can also modify the line to obtain something completely different. For example: : "Y" does indeed give me the character "Y" when I type a single quote followed by "c".] It seems as though in Fedora (but not in Debian) there is some other mechanism which is overriding some, but not all, of the xkb compose settings. Does anybody know what is going on? Thanks in advance. -- 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/1574401811.1865.3.camel%40gmail.com.
[qubes-users] How to navigate the Qubes OS versions and forum posts.
Greetings I am new to the OS and forum, I read thought some of the documentation and I was interested in knowing how to navigate the versions and bug fixes. Currently, I see we are 4.0.1; however, I’ve seen other mentions of stable versions in the forum. Is it correct to assume all the fixes suggested in the forum are about this (4.0.1) version and not the EOL versions? https://www.qubes-os.org/doc/supported-versions/ And, can I assume the fixes suggested in the forum will be tested and released in future? Kindly asking for some clarity, -- 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/b16ac3dc-cb25-4f96-b2ec-56232c372036%40googlegroups.com.
Re: [qubes-users] Days since last backup
On Thu, Nov 21, 2019 at 10:04:59AM -0500, Steve Coleman wrote: However, I am stuck on how to determine how many days it has actually been since the last backup. What you are looking for is this command: qvm-prefs --get $vm backup_timestamp Perfect, thank you! -- 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/20191122014408.GA10869%40danwin1210.me.
[qubes-users] Turning a NetVM into an AppVM
Hello there, I realized that everytime I made a new Qubes VM, I have been checking the "provides network" option turning it into a NetVM. I mistakenly believed that the option of "provides network" meant that the VM would need connectivity (yeah, I didn't RTFM), so now they are all NetVMs... hehe It would be cumbersome to delete them all and start over, so I was wondering which commands I could use to block such functionality turning it effectively into an AppVM. Thanks in advance! n -- 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/LuFblsh--3-1%40tuta.io.
[qubes-users] Re: Issue with activating ALFA usb drivers
On 2019-11-21 20:58, Cyber Secure Labs Limited wrote: Hi, I am experiencing issues with attaching WLAN card. I have attached / imported it into the Debian9 vm and have issued the command lsusb - this shows that the VM detected. However, issuing the command: sudo iwconfig I am getting wireless device not connected. Am I doing something to activate the wireless card. The type of wireless card is Realtek RTL8812AU The specs can be located here: https://www.alfa.com.tw/service_1_detail/13.htm Can you please advise on what course of actions that needs to be taken to shift this thing into gear. This might help: https://www.reddit.com/r/Qubes/comments/aljbjo/howto_qubes_4_alfa_awus036ac_80211ac_usb_30_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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/46d49569-948a-5c64-5ce1-c2ffbff9088e%40gmx.de.
[qubes-users] Issue with activating ALFA usb drivers
Hi, I am experiencing issues with attaching WLAN card. I have attached / imported it into the Debian9 vm and have issued the command lsusb - this shows that the VM detected. However, issuing the command: sudo iwconfig I am getting wireless device not connected. Am I doing something to activate the wireless card. The type of wireless card is Realtek RTL8812AU The specs can be located here: https://www.alfa.com.tw/service_1_detail/13.htm Can you please advise on what course of actions that needs to be taken to shift this thing into gear. Thanks in advance. 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/CAEPeKkfAdcfvZiKPBRC3FUxLrcm%3Dm%3D%3DmOw-6R4ZitipJopPoFQ%40mail.gmail.com.
Re: [qubes-users] Looking to change value of dom0_mem=max, tried finding xen-cmdline but no luck
Sphere: > However, a ram stick just died on me this week and I badly need all the RAM > that I could get. Even right now, my dom0 is actively using just about 940 > MB worth of RAM... which is why I think it would be best if I could > permanently allocate 2048M to dom0 instead of 4096M for my case. /boot/efi/EFI/qubes/xen.cfg -- - 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/b52f773c-08f5-886b-160b-c42b96b8fd89%40danwin1210.me.
[qubes-users] Re: How to get Ledger Nano S connected to VM
You probably did an installation without sys-usb. The installer defaults to not create sys-usb if during installation you have a USB keyboard attached. If that is the case, I find that following https://www.qubes-os.org/doc/usb-qubes/ and Auto Enabling Keyboard and Mouse input is a good solution. I ran into the exact same situation, and did that myself a couple of days ago. After this change, all your USB devices will show at the Qubes Devices applet the same way block devices does, and you'll be able to pass them through to any vm. Rafael Em sábado, 29 de junho de 2019 12:12:16 UTC-3, li...@tutanota.com escreveu: > > Qubes 4.0 default installation with USB keyboard and USB mouse > The device-manager-icon works with normal flash drives perfectly > ___ > > Tried to follow > https://www.whonix.org/wiki/Ledger_Hardware_Wallet#Qubes_R4 < > https://www.whonix.org/wiki/Ledger_Hardware_Wallet#Qubes_R4> > https://www.qubes-os.org/doc/usb-devices/ < > https://www.qubes-os.org/doc/usb-devices/> > > Ledger Nano S connected and unlocked > directly connected (without hub); tested on all USB ports) > > Generated a new VM: > VM 'ledger-nano-s' > type: Standalone qube based on a template > based on Debian 9 > ___ > > # checking VM 'ledger-nano-s' > > $ sudo apt-get install qubes-usb-proxy > Reading package lists... Done > Building dependency tree > Reading state information... Done > qubes-usb-proxy is already the newest version (1.0.21+deb9u1). > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > > # checking dom0: > > $ qvm-usb > BACKEND: DVID DESCRIPTIONUSED BY > > # So, I do not see any USB; more precisely missing the line# > sys-usb:2-1.4 Ledger_Nano_S_0001 > > $ lsusb > > # show several connected USB devices like my keyboard, mouse and USB hub > etc. but no Nano. > > ___ > > How do I uncover the Nano S in Qubes? > > > -- 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/d34ba004-e645-4aa3-a20d-6a54b12d65b6%40googlegroups.com.
Re: [qubes-users] Help, I broke my Qubes...
'Zeko' via qubes-users: > [ OK ] Stopped target Local File Systems > Unmounting /boot... (if it matters, boot is on a USB device) Probably. > [ 172.272900 ] usb 1-12: USB disconnect, device number 3 > [ OK ] Unmounted /boot. > [ OK ] Stopped File System Check on /dev/disk/by-uuid/... (haven't yet > figured out which partition this is) > [ 172.287911 ] usb 1-13: USB disconnect, device number 4 > > Then a wall of text scrolls by too fast and ends with "Kernel Panic!" and a > dump of CPU registers, and the machine reboots. > > The cause of this all is me installing sys-usb following Qubes website > instructions, because the instructions said not to do that if you have both > USB mouse and kbd and I do and/or because one step of the install failed but > I still rebooted my PC without trying to revert changes in dom0. Boot in rescue mode. Edit your xen.cfg and remove the option named something like qubes.hideallusb. Edit /var/lib/qubes/qubes.xml and locate sys-usb's autostart property, and set to False. Reboot. -- - 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/fc6c6822-9a15-d219-a234-0999f93c9675%40danwin1210.me.
[qubes-users] Qubes UEFI Boot inner working information
Hey everyone! I'd like to know where I can find doc / information on how the UEFI boot process of Qubes is configured / structured. Since the files repeat themselves on different folders at /boot, I'm unsure how / what to change in order to use a freshly generated ramdisk image. I've looked into instructions online, but every doc only references GRUB and Legacy boot, never anything on UEFI. UEFI troubleshooting on Qubes Doc is limited to specific situations, it does not provide an overview of the boot system. I have added a module to dracut, then I run dracut -fv and it generates /boot/initramfs-***.img just fine. After that, should I move the file somewhere? Should I change xen.cfg? What exactly is the process here? Hope somebody could help. Thanks in advance Rafael -- 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/037a8905-393c-4442-933c-db5d7af25765%40googlegroups.com.
Re: [qubes-users] USB Attachment "Backend Side" Logs?
Thanks, that approach helped. While I never did find any "backend" logs, I solved this problem by also installing the package `qubes-usb-proxy` in the template for the new disposable sys-usb. Matthew On Fri, 15 Nov 2019 at 12:48, 'awokd' via qubes-users < qubes-users@googlegroups.com> wrote: > Matthew Roy: > > When attaching a USB device from a new, disposable & > > minimal-template-based, sys-usb, I get the following error: > > > > user@dom0 ~]$ qvm-usb attach disp6xx5 sys-usb-dvm:2-2 > >> Device attach failed: No device info received, connection failed, check > >> backend side for details > > Try making a regular AppVM sys-usb from that same template and see if > you have the same issue. You might not have the required usb proxy > packages installed in the template. > > -- > - 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/07c04284-2aac-c96e-7d2a-1dd64aa791eb%40danwin1210.me > . > -- 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/CAGG2-sA36UttPGgx480JHc4BmDRgub2KGc2d80EjfF3vPK-tVQ%40mail.gmail.com.
Re: [qubes-users] Days since last backup
On 2019-11-20 22:12, tetrahedra via qubes-users wrote: > The built-in Qubes backup functionality is great but it's very easy to > forget to run a backup and end up going days (or weeks, or months...) > without it. > > However, I am stuck on how to determine how many days it has actually > been since the last backup. What you are looking for is this command: qvm-prefs --get $vm backup_timestamp I have a script that when it runs, it queries all VM's that have not been backed up since the last time they were run, and if they are not currently running, it kicks off backup to sys-usb to back it up, each to its own file. If I were to put this script in cron all I would have to do is shut down a VM and it would automatically be backed up, though that would likley cause problems if I restarted one that was gettign backed up, so I don't generally leave it running in the background. So, at the end of my work day I just shutdown what VM's I can and kick off my script and my work for that day is always archived on a local LUKS volume. This works pretty well for me on a the local drive, but then I still need to deal with issues with getting the "corporate backup software" to spool those huge files off to the server farm at night in order to fulfill my required retention policy. > Potential options: > 1) Assume all backups are done by a shell script, and that shell script > somehow saves the date to disk. How do we do this in an easy-to-parse > way? > > 2) Assume backups may happen by command line or GUI (assume we don't > know). Where can we find the date of the last backup on disk, and parse > it into an integer value that can be checked by a notification script? > -- 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/488a70ad-c676-0873-b1b9-0890c2cf36ea%40jhuapl.edu.
Re: [qubes-users] Help, I broke my Qubes...
Sorry about the delay, I had a week of ddrescuing a failing drive to distract me. I've managed to boot the Qubes DVD (EFI settings were originally preventing me) but didn't get the rescue process to work, it keeps asking me for passwords to non-Qubes luks partitions. I can open the partition with the password tho. Booted it without "rhgb quiet" and it gets to "Starting Start Qubes VM sys-usb", prints some messages about seizing and disconnecting a bunch of USB devices, then: [ OK ] Stopped target Local File Systems Unmounting /boot... (if it matters, boot is on a USB device) [ 172.272900 ] usb 1-12: USB disconnect, device number 3 [ OK ] Unmounted /boot. [ OK ] Stopped File System Check on /dev/disk/by-uuid/... (haven't yet figured out which partition this is) [ 172.287911 ] usb 1-13: USB disconnect, device number 4 Then a wall of text scrolls by too fast and ends with "Kernel Panic!" and a dump of CPU registers, and the machine reboots. The cause of this all is me installing sys-usb following Qubes website instructions, because the instructions said not to do that if you have both USB mouse and kbd and I do and/or because one step of the install failed but I still rebooted my PC without trying to revert changes in dom0. Zeko -- 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/obE7E03QIjiyOCktqHc-EPBe7e1JeiFnuaUCG_0Z3jexYk-Kb01HyAAu1YBu4nVyeNQJF2oLC-pyFpYfVLdEU_44LfdvqBqZZplXvBtR-GQ%3D%40protonmail.com.
