[qubes-users] Is it safe to reinstall templates automatically again?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2019-09-11 2:47 AM, tetrahedra via qubes-users wrote: > 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? > Yes, it is safe as long as you have core-admin-client v4.0.26, which migrated to stable on 2019-08-31 (or newer). For details, please see: https://github.com/QubesOS/updates-status/issues/1241#issuecomment-526871872 The documentation has been updated. (Thank you, awokd.) - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAl16+ooACgkQ203TvDlQ MDADkQ//e1TyE2ZNMCoFALN6Rtu4oBi36TuovhkYfLNsafaCkCkyry1y0BefKyR8 Oq2l72bSitzTM41Q+kXK3pCopKoSSaUI6N7LzBb3O1L6dvBwUPCT01/2dSQh68dW HfQgdTUsnEDAU9isdQ7SLfSk1KupApJJx+gZUGUkaHvdvk9a4VngM7E4kAi1auh0 AuAfWv3hSCqJFkTERfiCiScc09Y9O1VdSetAVA6aPWLUYyGwNUs9b6FHigMvXcUp OrLjnxQANwGLn5Tu8AeDs/I0nWmzqx2PF4jXRc5wKjN5vrStbZxIQxWBGcSNVvrq xzYwoifX2z+kzFJt3FP0inKletBcfZTC7Sb97wz19nx/fRNXtOhD9R8HtdUj/9ig yl9WdtDoazwnpbrmD3w0rKxtv93vQ0A/EAl1kCwn87zJZ/VL2Ky7z6bWhJwPD46X oT6aI66+xmELw5clavyY4NsrSZ25QRFSGILzC20baUIkuK6BSMXh2GwoRYk82Is9 RIPs7W3m1uMvXXDluRBO8h2LG03mW4zZgrpSq3v7kUrN8hla/SCLtUcdvbl0/CGQ Hk04I4yvSvMHQwfUE71utr7o0naWVuVvaogFKRwDhpVAGxqN7AQso7RhvwCIShUm 6sQDdKuMkn8HhYaKdozUOaEN071d/lB9FWJPGS4an5jLanmZ3tI= =3hGq -END PGP SIGNATURE- -- 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/af22fa0f-d84b-0378-89c2-ddf370eb23dc%40qubes-os.org.
[qubes-users] Kernel Panic at Boot (Account Services) & Changing the Grub Boot Menu Order
Hello, I kindly was referred to this user group, from github for help with a kernel issue (ISSUE#5272). Computer boots Linux 4.14.74-1 normally. No issues. Linux 4.19.67-1 or 5.2.11-1 kernel upgrades cause the CPU to freeze and forces a reboot once the Boot reaches "Account Services" just before the xfce login page appears. If it does manage to boot, the CPU freezes completely at the shutdown command. I have tried: -Updating with all Repo enabled -Adjusting memory and VM options at boot -Updating to kernel-latest for newer hardware -Reinstalling Qubes 4.0.1 I believe at this point, it's just hardware and I can't do anything. I'm not sure how to pull logs for this issue. I was hoping someone knew if the GRUB Boot Menu (Legacy BIOS) order could be changed. How may I boot Xen 4.8.5-7.fc25 and Linux 4.14.74-1.pvops.qubesx86_64 automatically instead of having to select it in advanced options every time? Thanks for taking time to read. -- 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/9WOsTRc_7B9AZ3GcGc8_a2-zGGpAqlDuTYsvGYVWM9R2DqJVnP12J2XfbxOqHcN6awD8uhhlRISUG95TO1ITKOJIhG0w7b2gsj6KowygZFA%3D%40protonmail.com.
[qubes-users] Whonix Tor Browser Starter safest setting fails
Setting tb_security_slider_safest=true (either by selecting Yes in the Tor Browser Starter screen or by creating a line in /etc/torbrowser.d/50_user.conf) does not result in the expected behavior. Expected Behavior: - Shield icon is fully colored - Security Level is set to Safest in about:preferences#privacy - JavaScript is disabled by default on ALL sites Actual Behavior: - Shield icon is fully colored - Security Level is set to Safest in about:preferences#privacy - JavaScript is ALLOWED on selected sites. To view these sites click on the NoScript Preferences button in the about:addons page and then select the Per-Site Permissions tab. -- 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/YhL10GmrV7yk0L2xjHpqblDZ8yRK2dMGORVtHSpv4GdicmT9kfLoUtMvy8eXlPMRNRUrtCIm8ckxrJMuNrLcCamWqdOHHoyLf9yDL8F7WAg%3D%40protonmail.ch.
Re: [qubes-users] Whonix 14 to whonix 15 upgrade: Protonmail Bridge (gnome-keyring or pass nneded?) issues
Most excellent...worked like a charm. If anybody is doing something similar, here were my steps: 1. Download the latest Protonmail Debian bridge (1.2.2-1 at the time of this post) in a DispVM 2. Move to dedicated template 3. Install Protonmail bridge in template (Commands: sudo apt-get install "then drag and drop the downloaded file into the terminal") 4. Install Gnome-keyring in template (Commands: sudo apt install gnome-keyring) 5. Close dedicated template 6. Create new AppVM with dedicated template containing Gnome-keyring and Protonmail Bridge 7. Launch new Appvm (provide password for keyring and configure Thunderbird) Thanks Awokd...good stuff! 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/8bb29669-4968-4655-89f5-3e739770dd6d%40googlegroups.com.
Re: [qubes-users] Wifi Antenna Boosters
On Thu, Sep 12, 2019 at 11:53 AM wrote: > Hi, I need a Wifi Antenna Boosters (attached to the usb). Can a Wifi > Antenna Boosters be used with qubes? > > I guess question is whether or not the software will work. > > Not only that, it should be linux compatible, it is also a matter of sharing the connection with others VMs. There is an option during Qubes installation to have sys-net and sys-usb in the same VM. That may simplify the matter of sharing. But to simplify your life I would buy a small router with antennas, such as this one, which uses open wrt: https://www.amazon.com/GL-iNet-GL-AR300M-Pre-installed-Performance-Compatible/dp/B01K6MHRJI/ref=pd_sbs_147_4/145-4592551-8089030?_encoding=UTF8&pd_rd_i=B01K6MHRJI&pd_rd_r=388bcea2-90ba-4dba-8fbe-ea1e08a2ddb7&pd_rd_w=Ao4jy&pd_rd_wg=3bMus&pf_rd_p=d66372fe-68a6-48a3-90ec-41d7f64212be&pf_rd_r=80SCACTM536CX08Y5K1D&psc=1&refRID=80SCACTM536CX08Y5K1D With a router you do not need to touch your Qubes settings and security and the signal will be available for your phone and your close friends as well. Also you have the option to buy a couple of stronger antennas if you want. -- 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/CAPzH-qA3WGSXi4Wo6nMOaw61RspdPzxtz_xCf61Ls2uLYrx9gQ%40mail.gmail.com.
[qubes-users] Re: Wifi Antenna Boosters
Den torsdag 12 september 2019 kl. 16:53:27 UTC+2 skrev alterat...@gmail.com: > > Hi, I need a Wifi Antenna Boosters (attached to the usb). Can a Wifi > Antenna Boosters be used with qubes? > > I guess question is whether or not the software will work. > > I had something like this in mind; > > https://expertvagabond.com/wifi-antenna-booster/ > -- 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/36d0e168-aa4e-4277-9d65-63328307e68a%40googlegroups.com.
[qubes-users] Re: Wifi Antenna Boosters
Den torsdag 12 september 2019 kl. 16:53:27 UTC+2 skrev alterat...@gmail.com: > > Hi, I need a Wifi Antenna Boosters (attached to the usb). Can a Wifi > Antenna Boosters be used with qubes? > > I guess question is whether or not the software will work. > > I had something like this in mind; > > https://expertvagabond.com/wifi-antenna-booster/ > -- 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/24b510e9-e8d9-4e53-9d85-4733848dde67%40googlegroups.com.
[qubes-users] Wifi Antenna Boosters
Hi, I need a Wifi Antenna Boosters (attached to the usb). Can a Wifi Antenna Boosters be used with qubes? I guess question is whether or not the software will work. I had something like this in mind; https://expertvagabond.com/wifi-antenna-booster/ -- 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/ca622833-e282-42d8-8bce-0c82bb5fd727%40googlegroups.com.
Re: [qubes-users] Re: Suspend to RAM not working
On Wednesday, September 11, 2019 at 9:24:08 AM UTC-4, Claudia wrote: > > 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! > That makes some sense. I'll try poking around w/F25 and see if I can get it working. If not, I've waited a year on this, so another one waiting on R4.1 isn't that big a deal. If I make any progress, I'll let you know. Thanks again! -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiv
Re: [qubes-users] Is it safe to reinstall templates automatically again?
tetrahedra via qubes-users: > 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/ Submitted a doc update. Believe it's safe now too. https://github.com/QubesOS/qubes-doc/pull/865 -- - 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/447a45b7-7830-79a0-5ac9-dec831df121b%40danwin1210.me.
Re: [qubes-users] R4.0.1 UEFI black screen after boot
duc...@disroot.org: > 'awokd' via qubes-users: >> 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? >> > The installer boots just fine, no issues at all. It's only after it > completes and I try to boot Qubes OS proper that I've just installed > that I get this problem. > OK, you should be pretty close then. If you still have Qubes installed on your HDD, try this: - https://www.qubes-os.org/doc/uefi-troubleshooting/#accessing-installer-rescue-mode-on-uefi - it will tell you where it mounted your HDD, think it's /mnt/sysimage - cd /mnt/sysimage/boot/efi/EFI/qubes - ls should list xen.cfg, nano it - do steps 11 & 12 in https://www.qubes-os.org/doc/uefi-troubleshooting/#cannot-start-installation-installation-completes-successfully-but-then-bios-loops-at-boot-device-selection-hangs-at-four-penguins-after-choosing-test-media-and-install-qubes-os-in-grub-menu If that doesn't help, reboot into Rescue mode and nano xen.cfg again. Remove those mapbs and noexitboot lines, then add efi=attr=uc to the end of each options line (step 5 for "3.2" in https://www.qubes-os.org/doc/uefi-troubleshooting/#system-crashrestart-when-booting-installer). -- 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/53c5e7a7-6680-5889-1e20-3871673a13f5%40danwin1210.me.
Re: [qubes-users] R4.0.1 UEFI black screen after boot
Claudia: > '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! Think I'll put 4.0.1 out to pasture and wait for 4.0.2 then. Glad to get your input. -- 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/764aea2a-a1e1-45ff-8db6-4d39cdc183e5%40disroot.org.
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? > The installer boots just fine, no issues at all. It's only after it completes and I try to boot Qubes OS proper that I've just installed that I get this problem. -- 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/999a21f7-3cbb-1db8-d6fb-65ee50a55ff4%40disroot.org.
