I have a standard trackpad. It works perfectly fine under debian/ubuntu. However, during installation, it completely stops working. Any ideas? \-- Sent using MsgSafe.io's Free Plan Private, encrypted, online communication For everyone. https://www.msgsafe.io -- 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/20200908051821.39BE06CFB4%40exit1-us.msgsafe.io.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2020-09-05 12:35 PM, 'awokd' via qubes-users wrote: > If you're concerned about Fedora's lack of signing, switch to > Debian templates, or some other that has signing. This is a misconception. Fedora packages are absolutely cryptographically signed by PGP keys. The signature verification must succeed, or else the package will not be updated or installed. You can prove this for yourself by temporarily moving/renaming the signing keys, then trying to install a package. The real issue is about signing repo metadata. See these threads: https://groups.google.com/g/qubes-users/c/HHedtfDFdj4/m/dap-D0nwEwAJ https://groups.google.com/g/qubes-users/c/cNwCH3rcIGk/m/grr1yJktDAAJ https://groups.google.com/g/qubes-users/c/X0GvIdpQtcM/m/Tey9k_geWGUJ - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAl9Wt2YACgkQ203TvDlQ MDAcSQ//Z4gXnuTfz2GyFTycvJ2wsoLdI24SbM8f6+jron8tlFEo9hcjWF4leM/d DlvT7sVGX94XBbe8gdsYIFQbNXCknq5d4F89jDnxHLpe/vQtZ23VSBzE81yGZjTq WU1fCclQD3pMhASYna8u4o+TcYe3RfbLqSaq3HfVhtFMsYXaZLp6MKbVAWtLcXXz VeBAnOft/E7HJeBtZQQj66zgsbdzjKvcm8ot+dE/VrTZ8ohX+P6uXca04G2Z4G90 oyRgpIFr4u+3EORNap7R2Cr44U7WZBI4Wv9bcXkZZcC4yxSetD1hYkl9bhC8a8GV iJhFu/Y5Utowfj3IeXb17Bt724YeNhTJUO9hGrN4W16+XmIPmF7Vy2yNS196NipQ NkW6dXw7CDDLjBFMr+Uv5S1sjCGT1TVGLolfkZt4MlAeGlNYw8gjnVQx7fzE7Vnf RRE4ckPmtJRf1FU3/ONaowhQ/RCxakJqF3CSoaf7+Wg++mqu02/jm5d/0AMrB7Ib /iVm1Ztc1DAqe7GGMQGl2uWAGFg6RuEmgxWInwFnuCzOm/LId2bRI2PI52PQAEJl A+F4MbhuiHeG4WRMZOKCwRZgHaNGE8Zk3wj9q9BE5dAPm/+OWpc6GmKnRfckBxwo 8ZEzgOkBgkmd0WMGjMQGXlvosj4irRtycUpUi+ByWSHzRNqF/MU= =eHe6 -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/d0c4aa78-dc42-dbb9-88d3-664eb64e602a%40qubes-os.org.
This exact problem happened to me recently in Qubes 4. The steps outlined here worked. The commands for me were along the lines of: sudo xl console, pkill -u 1000, umount, e2fsck, resize2fs. A HUGE THANK YOU FOR DOCUMENTING ALL OF THIS HERE! Excuse the yelling, this is my excitement about having this resolved :) Additional note: Since I had snapd installed in the TemplateVM I needed to remove this too to get rid of its mounted file systems in the AppVM. On Saturday, July 7, 2018 at 12:10:22 PM UTC+2 RSS wrote: > > > > resize2fs /dev/xvdb > > > then prompted to first run fsck on /dev/xvdb. After this > > > > Usually Qubes handles that resize2fs automatically; I suspect whatever > > caused the need for fsck was preventing that. > > I wish I could remember if anything odd happened at the time, that is > already several days ago and there has been a lot of water under the > bridge since then. > > > > If someone believes there is a natural and desirable home for this > > > tidbit somewhere in the Qubes Docs, I would be happy to put in > > > there. > > > > There is https://www.qubes-os.org/doc/resize-disk-image/, but I don't > > think the process you described is intended. Does it happen every > > time you resize a Linux AppVM's volumes (i.e. can you recreate it)? > > If so, might be better to file an Issue instead. Anyways, glad it > > finally worked for you! > > No, actually this is I believe the first time on either Qubes 3 or 4 > that this has happened to me, and I tend to be resizing private storage > quite regularly. So it's basically a one-off that I have no way of > reproducing, and I don't recall many (any?) other people talking about > this on the list, so perhaps we can just let the mail archive take care > of it. > > It might be worth noting here that after using Qubes 4 for several > months, I have had two significant glitches, this and another, and they > both were storage issues. Everything else has worked perfectly so far. > > Thanks for the help! > -- 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/fd05e798-7275-4e27-9a3c-6deec546b29fn%40googlegroups.com.
Xe probably won't work quite yet, AMD GPUs have mainline kernel support by now, so that they're usually supported within a few months. (Though buying one 6mo or older is probably helpful.) On Sunday, September 6, 2020 at 8:57:35 AM UTC sandyi...@gmail.com wrote: > I'm contemplating a new computer, either laptop or all-in-one desktop, > on which I'll run Qubes. Looking at > https://www.qubes-os.org/doc/system-requirements/ I find: > > : Intel IGP (strongly preferred) > :: Nvidia GPUs may require significant troubleshooting. > :: AMD GPUs have not been formally tested, but Radeons (RX580 and > earlier) generally work well > > Is that still accurate? > Intel have a new graphics chip called Iris Xe; does Qubes work on that? > -- 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/2712a840-234b-4ae3-8e70-450f4bc1d0dfn%40googlegroups.com.
On 2020-09-05 13:35, 'awokd' via qubes-users wrote: Stumpy: I was reminded about qubes hardening that Chris L has been working on and also noticed that Patrick/Whonix is now basing whonix on thier kicksecure distro and was trying (not so successfully) to absorb all of this. I got the impression that Chris's work wouldnt jive so well with kicksecure (fair enough, can just use it on non-whoinx setups) but wasnt sure. Also there is the idea of DVM sys-* (net/usb/firewall/etc) vms sounded like they would add an extra layer of security, maybe based on centos (I have seen conversations about how fedora doesnt sign or something apps in their repos? please dont troll me, i am not trying to pretend like i understand that) and some other things that i am sure i have missed (maybe a iptable/firewall gui [apart from whats built into qubes settings... i just dont find that intuitive). Just running Qubes by itself is already more hardened than 99% of people out there, so if your main concern is standard/driveby attacks against mainstream OSes, you shouldn't be very much so. My threat model is not super strict at home (when traveling totally different scenario [lots of diff scenarios actually, will save for another post]) You cover multiple points: - There is something in the works to allow custom kernels inside AppVMs. Whonix and others can use them for additional hardening and/or additional drivers. Don't think it's released yet. Nice! I wasnt aware of that, will hurry up and wait :) - Chris's VM hardening works on regular qubes. Not sure if it will on Whonix ones. I got the impression it wouldnt but that might be moot as kicksecure seems to be quite hardened. - DVM sys-* is pretty straight-forward, just follow the docs. True enough i guess - Centos is unrelated. Well I had mentioned CentOS since I thought thier packages, like RH, were signed? If you're concerned about Fedora's lack of signing, switch to Debian templates, or some other that has signing. So centOS doesn't sign their packages? - Mirage can be used as a sys-firewall replacement. I thought about that, i ended up just going with a minimal centOS template for my sys-* appvms. I know there have been back and forths about Qubes "Ease of use" especially for non-techies; I consider myself somewhere in the middle, but I was wondering about configs during start up? I totally understand the Qubes Team has more important (sec) things to work on but I think a UX person was hired to address some of the UX things in Qubes which could be polished? (not 100% sure about that, maybe i was reading about another distro). It would just be nice if a thorough howto could bring much of the hardening documentation together rather than skiping around from one doc to another - or better yet make some of these things options during the install like which "distro would you like to use for your minimal templates", "Would you like to add X community templates", click here to input your VPN provider info if you want a VPN proxy, "click here if you want your sys-* to be a DVM", "select your win iso if you want a MS win appvm, and click here if you want it to be standalone or a template", while I am completely aware that its easier to suggest such things than to actually do them it seems like a worthy goal for making a more versitle and perhaps noobish friendly Qubes while also addressing FAQ (granted not everything i listed is a requalr mailing/forum list question) which might make those FAQs a bit less... frequent? :) Anyway, just my ? cents. Cheers -- 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/2132b9ec-7906-d988-ee4c-76d44a05554d%40posteo.net.