Re: [qubes-users] Whonix 14 to whonix 15 upgrade: Protonmail Bridge (gnome-keyring or pass nneded?) issues
V C: Was this removed from Whonix-15? Is it possible to add "pass" or "gnome-keyring" into Whonix-15? Don't know if it was removed, but it's possible to add. Go to a terminal on whonix-gw-15 and "sudo apt install gnome-keyring". Be careful what you install in here, though, since it is responsible for keeping your whonix-ws-15 qubes anonymous. -- 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/b33f78dd-b146-87ec-a21f-8a4514b5faec%40danwin1210.me.
Re: [qubes-users] Re: Popup When Starting or Shutting down Whonix VMs
pudding: /etc/qubes-rpc/policy/whonix.NewStatus, and it had only one line: @anyvm @anyvm ask I then added a line "$tag:anon-vm $tag:anon-gateway allow" at the top of the file. It seems that this fixed the popup problem. Also, I noticed anon-whonix now appears in the right-click menu of sys-whonix sdwdate-gui icon. I am not sure if this is OK security wise, though. If not, I will try your suggestion and update my Whonix templates from testing repo. Anyway, thank you for the idea which helped me find the solution. Many thanks! Mine has these three lines in it, not sure why ours are different since both our dom0's have been updated: $tag:anon-vm $tag:anon-gateway allow $tag:anon-vm sys-whonix allow $anyvm $anyvm deny -- 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/6a86c171-2882-aa78-f9e1-bd534bf1cb2f%40danwin1210.me.
Re: [qubes-users] Re: Popup When Starting or Shutting down Whonix VMs
Hello awokd, Thanks for the answer, I remember seeing that post too. I checked the dom0 log and found that hitting "Cancel" generated the following log: dom0 qrexec[23456]: whonix.NewStatus+anon-whonix: anon-whonix -> sys-whonix: denied: denied by the user /etc/qubes-rpc/policy/whonix.NewStatus:7 My guess was that the popup was triggered by anon-whonix registering to the sdwdate-gui of sys-whonix. I checked /etc/qubes-rpc/policy/whonix.NewStatus, and it had only one line: @anyvm @anyvm ask I then added a line "$tag:anon-vm $tag:anon-gateway allow" at the top of the file. It seems that this fixed the popup problem. Also, I noticed anon-whonix now appears in the right-click menu of sys-whonix sdwdate-gui icon. I am not sure if this is OK security wise, though. If not, I will try your suggestion and update my Whonix templates from testing repo. Anyway, thank you for the idea which helped me find the solution. Many thanks! P.S. Sorry for replying to your mailbox, I made a mistake. :( On 9/11/19 5:49 PM, 'awokd' via qubes-users wrote: pudding: For your reference, I just found that the popup also randomly appears during the time a Whonix-base VM is on. :( There appears to be a new dom0 widget in current-testing that tells if Whonix workstations have synced to a time source. I remember reading a development thread about it somewhere. I bet those popups are because something's not matching between versions. Suggest setting your whonix-gw-15 and whonix-ws-15 templates to also update from Qubes current-testing repo, to match dom0, and rebooting. Not getting those popups on a PC where I've updated everything Qubes related to current-testing. -- 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/5dc97ea2-a6e5-aa5e-a1ea-60b99ea81b2b%40cock.li.
[qubes-users] Re: DisplayLink
It's worth noting this problem is for the USB type A running USB x3 connection port to the host (the DisplayLink runs over this). And is not a USB-C port type. The other USB-A x3 ports are all functionally normally. On Thursday, 12 September 2019 09:05:44 UTC+10, Martin Thygesen wrote: > > +1 same problem, same Dell D3100 dock issue > > On Thursday, 12 September 2019 07:22:09 UTC+10, Alex wrote: >> >> Hi everyone >> >> I can see that Qubes recognises my DisplayLink Dell D3100 USB3 dock; it's >> listed in the "Qubes Devices" widget in the panel. But, xfce's window >> manager seems to only recognise one screen (my laptop's built in LCD). No >> mention of my external monitors. >> >> How can I fix this? >> >> Thanks, >> >> Alex >> > -- 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/1e5b1722-dd6b-4460-ba21-e31a2244008f%40googlegroups.com.
[qubes-users] Re: DisplayLink
+1 same problem, same Dell D3100 dock issue On Thursday, 12 September 2019 07:22:09 UTC+10, Alex wrote: > > Hi everyone > > I can see that Qubes recognises my DisplayLink Dell D3100 USB3 dock; it's > listed in the "Qubes Devices" widget in the panel. But, xfce's window > manager seems to only recognise one screen (my laptop's built in LCD). No > mention of my external monitors. > > How can I fix this? > > Thanks, > > Alex > -- 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/bb5457e9-4f8d-4197-a0bd-afb67d198d01%40googlegroups.com.
[qubes-users] DisplayLink
Hi everyone I can see that Qubes recognises my DisplayLink Dell D3100 USB3 dock; it's listed in the "Qubes Devices" widget in the panel. But, xfce's window manager seems to only recognise one screen (my laptop's built in LCD). No mention of my external monitors. How can I fix this? Thanks, Alex -- 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/7CF4621E-E02D-4A21-A631-4424C6B99CA4%40gmail.com.
[qubes-users] Whonix 14 to whonix 15 upgrade: Protonmail Bridge (gnome-keyring or pass nneded?) issues
Hey all...thank you again for making and supporting an awesome OS! Thank you Qubes... Just upgraded to Whonix 15, using these instructions: https://www.whonix.org/wiki/Qubes/Install ...seemed to go smooth. A couple of notes and a question: 1) Adjust Whonix Version Number In dom0. Open file whonix.jinja with root rights. [3] sudo nano /srv/formulas/base/virtual-machines-formula/qvm/whonix.jinja Change 14 to 15. Save. *Please report if this step was necessary or unnecessary for you! * **I didn't have to do this step! It appeared already set to "15" 2) I had changed the name of sys-firewall and sys-net, however when I upgraded to Whonix 15, it seemed to add these Appvms during the upgrade? I kept my old sys-firewall and sys-net. Not sure this was expected but didn't seem to be an issue. Question: I suspect this is something new with Whonix-15 or maybe something else. I am trying to set up Protonmail bridge in my new Whonix-15 set up(used in conjunction with Thunderbird) but it appears as if a "key-ring" is missing? I had this working in Whonix-14 by downloading and installing the bridge into a dedicated template, however when I try to do this in Whonix-15 I notice during the Appvm set up that I am NOT asked to create a "Key-ring", I also get an error in the "Protonmail bridge" that states: "ProtonMail Bridge is not able to detect s supported password manager (pass, gnome-keyring). Please install and setup supported password manager and restart the application". Was this removed from Whonix-15? Is it possible to add "pass" or "gnome-keyring" into Whonix-15? I consider myself still very basic in terms of a Qubes user so any specific instructions and commands to enter would be greatly appreciated. Thank you again... VC -- 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/31506297-a3e1-4625-929f-134a6bb3c065%40googlegroups.com.
Re: [qubes-users] Trouble building RTL8821CE WiFi drivers
muhammad19238...@gmail.com: > Thank you, this worked fine(For future duckduckgoers, I did this on fedora > in the end, I now feel it makes more sense because the disk usage of the > template is not avoidable, by having extra templates its just weighing your > disk down). However I have one last parting question, once I reboot > sys-net, I lose my driver and have to install it again. I have a feeling > that I should install the driver in the template to keep persistence, is > this correct? What is the qubes way to do this? > I should have thought of that! Probably the easiest thing to do in your case is to create a new qube, choosing the Standalone copied from template and check the "provides network" box. This behaves as a regular VM, so you can make any changes you need and they will stay. Once you have it set up, uncheck auto-start on sys-net, add auto-start to your new qube, and set sys-firewall Qube Settings to use it. Also change anything pointing to sys-net in Qubes Global Settings. Qubes Update will see it in the list for updates. -- 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/89c3040d-5aad-7018-5318-c53edd1845bf%40danwin1210.me.
Re: [qubes-users] Re: Popup When Starting or Shutting down Whonix VMs
pudding: > For your reference, I just found that the popup also randomly appears > during the time a Whonix-base VM is on. :( > There appears to be a new dom0 widget in current-testing that tells if Whonix workstations have synced to a time source. I remember reading a development thread about it somewhere. I bet those popups are because something's not matching between versions. Suggest setting your whonix-gw-15 and whonix-ws-15 templates to also update from Qubes current-testing repo, to match dom0, and rebooting. Not getting those popups on a PC where I've updated everything Qubes related to current-testing. -- 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/b4400701-0d06-3876-7a9b-bcee27d05c1c%40danwin1210.me.
Re: [qubes-users] Trouble building RTL8821CE WiFi drivers
Thank you, this worked fine(For future duckduckgoers, I did this on fedora in the end, I now feel it makes more sense because the disk usage of the template is not avoidable, by having extra templates its just weighing your disk down). However I have one last parting question, once I reboot sys-net, I lose my driver and have to install it again. I have a feeling that I should install the driver in the template to keep persistence, is this correct? What is the qubes way to do this? -- 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/7e419f88-c4db-4da4-af9b-aab3196a8601%40googlegroups.com.
[qubes-users] F2 stoped working after last kernel update
We used to be able to switch to console when typing password or after to see messages, now just black screen. Pressing F2 again shows GUI. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/cf72bf7e-6c65-4447-be49-1b2b208a34c0%40googlegroups.com.
Re: [qubes-users] SWAPGS Side Channel Attack
Thank you Simon for the informative reply. Good to hear there is some progress on Spectre variant 1. I hope something similar to Respectre will be available in the future. -- 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/a3a216a4-3b3a-432a-9427-7c00912d0d63%40googlegroups.com.
[qubes-users] Re: Suspend to RAM not working
Note that Anti Evil Maid is also a variable that affects Suspend. For me, when I boot with AEM and suspend the machine, it immediatly shuts down instead. Booting without AEM, then Suspend works normally. -- 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/bf4ea8bd-11d2-4e29-a974-89226498241d%40googlegroups.com.
[qubes-users] Re: Popup When Starting or Shutting down Whonix VMs
For your reference, I just found that the popup also randomly appears during the time a Whonix-base VM is on. :( -- 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/877e037a-78c7-90ac-25ca-8a7621577009%40cock.li.
[qubes-users] Re: Popup When Starting or Shutting down Whonix VMs
Hello awokd, No. I updated my Whonix templates from stable repo. Here's exactly what I did: 1. I updated whonix-gw-15 and whonix-ws-15 from stable repo (plenty of packages to update), and the popup appeared when shutting down these two templateVMs; 2. I restarted sys-whonix after templateVMs were shut down, and updated dom0 using sys-whonix from stable repo; two packages related to kernel were updated, but the popup still appeared when trying to start Whonix-based VMs; 3. I updated dom0 from the current-testing repo; the popup problem persisted; 4. I rebooted my PC, and the problem is still there. Pressing "Cancel" in the popup makes the popup go away and the VM start or shutdown procedure resume as usual. The popup appears about 3-4 times on VM start, random , and 1 time on VM shutdown. I have encountered this popup problem before, and was able to fix it by updating dom0 to current-testing repo, but this time it doesn't work. So if there is a way to solve it, I would like to know. Thanks! -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/0f6360f7-eae6-6c3d-2f53-6462bc2fda6c%40cock.li.
Re: [qubes-users] R4.0.1 UEFI black screen after boot
'awokd' via qubes-users: duc...@disroot.org: This is an issue that's been reported before, and some solutions appear to be out there, including re-installing with Legacy boot. However, they all seem to involve modifying the installer prior to installation or making changes via a GRUB menu. I'm never presented with a GRUB menu with either (I suspect that's a UEFI issue), so I'm not quite sure how to proceed with troubleshooting. I want to stick with UEFI-only boot as far as possible. The last messages echoed before the black screen are: [VT-D]Passed iommu=no-igfx option. Disabling IGD VT-d engine. Scrubbing Free RAM on 1 nodes using 2 CPUs .done. Initial low memory virq threshold set at 0x4000 pages. Std. Loglevel: All Guest Loglevel: Nothing (Rate-limited: Errors and warnings) Xen is relinquishing VGA console. The screen goes black indefinitely at this point. This is a device with only integrated GPU so I suspected this might be a problem. How should I proceed? Intel integrated GPU usually works well as is. Are you getting the black screen when you boot the installer, or after it completes and reboots? For what it's worth, yesterday I updated dom0 on a previously working Qubes 4.0.1 installation, rebooted, and ran into this exact problem. I have absolutely no idea if it's related. Also, re: grub, from my experience it appears to me that it only uses grub.efi if you have more than one OS installed, such as R4.0.1 and R4.1, otherwise xen.efi is used which does not have any boot menu or command line capabilities. I imagine you could change this from rescue media using some kind of UEFI boot config utility, or perhaps by running grub-install? With rescue media, you also can modify boot parameters in /boot/xen.cfg directly. In my case, changing xen.cfg back to 4.14 kernel seems to solve the issue, but I know I had a 4.19 kernel working on this same machine before. I haven't tried legacy boot at all. Anyway, point is that it may not be strictly due to UEFI, per se. For me, 4.14 worked fine under UEFI, and then the 4.19 update caused the same symptoms you're seeing, which is just like any other update-gone-wrong, UEFI or not. Also, I don't even know if it was the kernel update that caused it. It could have been caused by a dracut update, Xen, or anything else, I assume. It's on a currently non-production system so I'm probably not going to troubleshoot it. Most likely I'll wait around for the next kernel update and see if that fixes it, or wait around for 4.0.2 and reinstall and see if that fixes it. - This free account was provided by VFEmail.net - report spam to ab...@vfemail.net ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands! $24.95 ONETIME Lifetime accounts with Privacy Features! 15GB disk! No bandwidth quotas! Commercial and Bulk Mail Options! -- 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/591e6cc2-8728-4d34-96d1-03fa80869d6e%40vfemail.net.
Re: [qubes-users] Re: Suspend to RAM not working
drogo: On Tuesday, September 10, 2019 at 5:22:32 PM UTC-4, Claudia wrote: drogo: On Sunday, June 24, 2018 at 10:12:17 PM UTC-4, cooloutac wrote: On Friday, June 15, 2018 at 5:59:46 PM UTC-4, drogo wrote: My newly built system is unable to suspend. The process starts, but fails and ends up with just a locked screen. This is a desktop, so there shouldn't be any wifi drivers causing issues. But I'm not sure if there's a module that might be making it resume right away. Any ideas where to start troubleshooting this? HCL report is attached. Thank You can try to see if it suspends on the same baremetal feodora version as dom0 to narrow it down to a qubes or xen issue, or try newer fedora and see if its a kernel issue. I had similar issue with suspend ot ram, but upon resume sys-net has no network. restarting module or network connection doesnt' work. the suggested fix of blacklisting network driver module for my desktop in the qubes file, in my case ethernet, didn't work either. I know it's been a while, and I'm hesitant to resurrect an old thread, but I put this on hold for a bit. Also, this system is my daily driver, so re-installing would be a big interruption. (Just chiming in here so sorry if I missed anything important) You don't have to reinstall, just try suspending in a Fedora 25 and/or Fedora 30 live CD. In my experience, if suspend is going to work at all, it should work in a live CD just the same. Worth a try, considering it's trivial to do. - This free account was provided by VFEmail.net - report spam to ab...@vfemail.net ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands! $24.95 ONETIME Lifetime accounts with Privacy Features! 15GB disk! No bandwidth quotas! Commercial and Bulk Mail Options! I must be tired or something (for a year?? :) ) but I completely forgot about a live-USB. Just grabbed a copy of Fedora 30, and it suspends successfully. Both by hitting the power button, and by choosing the "pause" icon from the user menu. Thanks for the reminder! Not sure of your situation, since for some reason I'm not seeing the whole thread. (For some reason, sometimes mid-thread replies show up as the root of a thread for me, earlier replies sometimes don't show up at all, and/or replies will show up as individual, out-of-thread messages.) ... but that probably means that the relevant drivers aren't in F25 (whether originally or by updates). I ran into the same issue recently; bought-new a relatively recent laptop, which fails to resume on F25 and Qubes but resumes flawlessly on F30 and Ubuntu 19.04. i.e. The hardware is too new for the software. You could try upgrading to the testing or unstable dom0 kernels (up to 5.9 available, I think) and Xen versions. In my case, interestingly, this didn't work. F30 with an older kernel worked, but not Qubes (F25) with a newer kernel. So apparently userland plays a role as well. Beyond that, there's no remedy that I know of. I remember reading somewhere that upgrading dom0 to F30 is more or less impossible, and I don't think minor releases (R4.0) ever ship newer Fedoras. You might be able to narrow down what userland components are responsible, and upgrade them specifically, but I have no idea how to go about this (if you do, let me know!). And finally, while there are pre-release R4.1 (w/ F30) builds available, I'm guessing it'll probably be at least another year or so until we get an R4.1 beta. And of course, Xen doesn't support hibernate, and Qubes doesn't support Xen's "save VM state" feature. - This free account was provided by VFEmail.net - report spam to ab...@vfemail.net ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands! $24.95 ONETIME Lifetime accounts with Privacy Features! 15GB disk! No bandwidth quotas! Commercial and Bulk Mail Options! -- 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/fd60972f-d99b-252f-399f-2022e18b22d7%40vfemail.net.
Re: [qubes-users] Popup When Starting or Shutting down Whonix VMs
pudding: > Hello, > today after updating my whonix-ws-15 and whonix-gw-15 template, every > time I start or shut down any of my whonix AppVMs or templateVMs, I get > the "Operation execution" popup like the attached pic 3 or 4 times. It's > pretty annoying. I tried updating dom0 from current-testing repo, but > the problem persists. Is there any way to make the popup disappear? > Thank you! > You said you updated dom0, but did you also update your templates from current-testing, and reboot afterwards? -- 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/0088910f-5bc1-04d0-15e3-3cc26e1f5ab9%40danwin1210.me.
[qubes-users] Is it safe to reinstall templates automatically again?
The docs on template reinstallation indicate that QSB 050 means it is not safe to automatically reinstall templates: https://www.qubes-os.org/doc/reinstall-template/ However QSB 050 suggests that patches were pushed out some time ago: https://www.qubes-os.org/news/2019/07/24/qsb-050/ Indeed `sudo qubes-dom0-update --enablerepo=qubes-dom0-security-testing` says no new patches are available. Does this mean that (contrary to the template reinstall docs) it is safe to use automatic reinstallation now? -- 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/20190911074607.GA2011%40danwin1210.me.
