[qubes-users] Re: Qubes OS screensharing
On Thursday, January 25, 2018 at 1:34:03 AM UTC-8, Vít Šesták wrote: > Dave, why you start a new VM and not just use a loopback? Is the reason > sharing apps from multiple VMs? If si, you are at least significantly > weakening isolation. Maybe you are not keeping any, not sure. X11 was not > designed for isolation at all. I run the vncserver in a new VM so that I can screenshare from... * multiple app VMs * VMs that can't access the conference site (i.e. bluejeans.com) or can't access the net at all * VMs that don't have vncserver installed, or don't have a plugin needed to screenshare My approach lowers security while screensharing. But the rest of the time, not screensharing, the VMs are running with normal firewall settings. I realize X11 is a weak link in what might be an otherwise secure desktop. One of the reasons I am a fan of 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/b9567fb7-af2f-4e12-8421-21a9ef6168c0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] ERROR: Device attach failed
ERROR: Device attach failed: /usr/lib/qubes/usb-import: 37: [: Illegal number: stash: printf: I/O error. How to solve 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/b0c6b3d2-f849-40d0-8bb9-1273a92ac55c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Qubes 4.0 Documentation
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2018-01-26 05:14, awokd wrote: > On Fri, January 26, 2018 3:36 am, Andrew David Wong wrote: >> On 2018-01-25 12:28, awokd wrote: >>> 1. Should I open an issue for tracking and move the discussion >>> over there? Move to qubes-devel? Keep here? >> >> Please open an issue in qubes-issues. > > https://github.com/QubesOS/qubes-issues/issues/3495 > > >> I agree that the tool man pages should not be shared between 3.2 >> and 4.0 (but they probably wouldn't be anyway, due to the nature >> of the system just described). > > What will be the naming convention for direct links? I can see > sometimes we'd want to link to the latest version of qvm-whatever, > and other times when we want to link to a specific major version. > We could either have different subdirectories for each version or include the version in the page name, as we do for some other version-specific pages. >> I think it makes sense to handle these cases specifically, by >> creating a page that collects all the versions of each one. I'll >> do this now. > > Thank you. > >> In general, it's worth thinking about whether we even want to >> keep severely outdated category 2 documentation around. Does it >> have any value anymore, or will it just produce misleading search >> results? (Note that it will all remain permanently archived in >> the git revision history, so it's mainly a question of visibility >> on the website.) > > My vote is to axe it. > - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlpsEAwACgkQ203TvDlQ MDAhCg//Xxt+qfhlLYXYoudWzpGX9WSwwBQHZpH/A6j0zZEhgIYl/sPtF66Mmxwx QOWA7DEElbojIRQ+DmVvt8FB4RWJkxRw9mqUY8aMbh5qVXHMbjiBDLfWDsnwjRnJ ZJREO450qYHDesg/g+8DasFbXE7D1qBxuUBM+uRvTaqzj9fhUUtCvI0NAUBZcv/u 6+0IFSTbm6fw4XyhfVYJEXpjuBI2WCfA++6mFlnAx0UY6AQenlnxRtOgEdK+N8wb 403fX7e0CaJhzCnXd+4g5i9Dm2ogewNAwHK/TLPXathJzmYmruZgzIJgiSrcUwVB vHrsPi3ZqPgR6vZkW/DwMBBjz0s+Y/WudBpDhFeXDJ/JbOU5mW1E/63LpCyB8p0+ V9Y+4pAkbdWuzX8JojNGSJ6K0ZrsGRgb3QIyhi8yRCwgNqUqjW6y/VitmeAi3HGT KPSaM8b8MjnEtfI6KQUNPOqS8lO9cX5D5tsPu64FGXx7ZTieVdCOl8oDjWduc4hU 1W2FxzH1p+hr6X17qYsUbwbyyr2lqV1so8g5ASitOflcMNqPHN4rfXRI9dKu5gfL 8PmpDk2hQUeaLy1RbpBrUzbHp1JnqmwMg1bfm9BJrqDbyOqXJapVLAuoAvg/bQmZ QfzRQPrZpjpS/6VW+qTojRj0zGadqE7NBiBvBIQF+0Z5bZ/Bck8= =U+U5 -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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/eb46324a-c834-3b0c-24e6-22a4fdeb1191%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Qubes 4.0 Documentation
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2018-01-26 05:38, 'awokd' via qubes-users wrote: > On Fri, January 26, 2018 9:22 am, Alex Dubois wrote: >> On Friday, 26 January 2018 03:36:33 UTC, Andrew David Wong >> wrote: > >> Happy to contribute. maybe we can have a direct conversation so >> that we can discuss what is needed and where I feel >> comfortable... > > Speaking only on my own behalf of course, thank you. Editing the > docs is pretty straight-forward > (https://www.qubes-os.org/doc/doc-guidelines/), so I'd suggest > jumping in and editing whatever you are comfortable with. I'm > coming across documents where someone else has already gone in and > called out or updated with R4.0 content, so thanks to those > contributors as well! > I agree. - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlpr1q4ACgkQ203TvDlQ MDAmmw//f5oa73EABlkL+6g78pOalsHZaX9jYbcwvfpZAycrdpYaxiXxxeIAjY/+ p5PZQe/0b5CQf1N3g7jcDcN7HzqztZgtpMmOPyWrZ1VMMBfJ2d8TmjAC9OU/d0Pv Jf7KujBhD+hJVRh2Zel8xIis89+5tdM2IKWJsetAuZgTssmvGVAXy+NzEXzchBbh jszjL5RixsxhSeBVkvNCuBSiD3XGGYBp3beOj8zvvnLu5mTVJA7p2hI3MAtADqlU yiWIpoTz1FBLfbo33ETl9O9NTP9v9pzs3175Llprf93XWABV9qZEY+QoAPZdEAac C/T0Fm9UZFJ/2xaNQiNBHqzO7CSOVUqOpwJQoiQBleeorIvCSpfeJdCEqUQ7PGKS rnAq9Sm8Fr7BiDfXQU99MJQbqmMeJVtq6BeUUx/JlcS7gW7KUzZ3W9LfirMdHRdQ KAuaG/pqio1LBtZatbXBUvCnQ8uWctaPJ4YknqPc99rvgCFl3if3dFxQRBcr56RH nXcPUifk+jbgFQzEjiyCzANYS9OdmXBsYa0QPWN/ZdIw4Dvl23J6qqcY5Vs7pEyJ EEm/sLiinPrQo9h5WjH7+55PQRcnPqm71rwC8fMlblde2Nx89fMgbksB0BQIyX+x pTxjh2feeWpDtf/bL1zfJ+zNAR2mEyxJML0Dbc6+Kj+EBTwGUtU= =czGG -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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/bc6054e7-98f3-b388-6bcc-f45109cc60b2%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: [qubes-project] Hosting for OpenQA instance
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2018-01-26 09:37, Marek Marczykowski-Górecki wrote: > Hi, > > Manual testing of installation is a time consuming job, so I was looking > for some tool to automate it. And found one: > > http://open.qa/ > > This works by launching the system under test in KVM and then interact > with it as user would do (mouse clicks, keyboard etc). Then compare > screenshots (or parts of it). > The nice thing is when using new new enough KVM, qemu and hardware with > VT-x + EPT, Qubes installation works there! In theory KVM supports even > nested virtualization, so HVM should works inside such setup, but in > practice Xen and/or qemu crashes badly... But PV works fine, which is > enough for installation testing. > > I've uploaded some basic tests here: > https://github.com/marmarek/openqa-tests-qubesos > > The problem is we don't have a place to host it in long run. While I can > launch it from time to time on one of my testing laptops, it doesn't > scale well. And access to it is restricted, which limit who can work on > this (and on issues found by tests). > > Does anyone have some place/recommendation where to look? Hardware we > need: > - CPU with VT-x + EPT, so KVM will work with reasonable performance ( >means a physical machine, not virtual one) > - 6-8 GB RAM (4GB for KVM + something for OpenQA itself) > - 50 GB of disk (preferably more) > > Does anyone have a spare machine running somewhere, and willing to > share? > > Alternatively, it looks like we can get one for ~70 EUR/month. Andrew, > Michael, could we use opencollective money for this? > The OpenCollective money is supposed to be used to pay developers to work on the open-source version of Qubes. While this would not be a direct payment to a developer, I can see how it would qualify, since it's directly saving you and other devs time and work that would otherwise have to be spent on testing. I think it would adhere to the spirit of the rule, which is that the money should be spent on improving the open-source version of Qubes. (Arguably, it would be even more efficient than paying a developer directly, since Qubes would probably benefit a lot more from the testing bought by that ~70 EUR/month than it would from the tiny amount of developer time ~70 EUR/month would pay for.) However, I'd be surprised if there were no one in the Qubes community willing to share a suitable machine for this purpose. My guess is that there aren't as many readers on qubes-project as there are on qubes-devel and qubes-users, so I'm CCing those other lists. - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlpr1ioACgkQ203TvDlQ MDBZaA/9HZWo8gZh5UsrKEAWIC4c4b4hnL2U0NZvqi508qbr65DmqW67y/QGXA0q EI3VNHpNrhL99jpWGlsGnN3K1Dss+NKKEk82AVsqw6in9P1LA+9CyMjf3TQB1yLn QkWyFc0E/+wN4ExpMgUuX7kqTv9TgjPrFki+KajpsIvQpXDOqMxM6vNdYitI8fer B1cpIn0gS17ANcvlXJU2OhLKEradX6msZJdAYWlrZPpy7XEIPtnJTugsN5fm6kr/ ChsQtGH7OTHIJkd0pEr9YODhyr/Tpp6OYDwsQL1uWW4W8K03Mhmh5q+MuKg/scvG nv8vINL0wo010GdiqsU/bvqB7pYkOFcdsghgM3gy1jBK8E7aR4KgNrafKn22D7eu fC0Y2LlJmGZ6s+l//sfI6YIMi/iCj+6zUHXLdcGrLI9v+iYu23/9Lz6oyKl1Vedv +6zh0PasElJXxAgdBGN7Se16ApC8/cTLeEcHhAQ1No/Tye3TaYE1U4ouj+9d6o1l f7LLiSs1wxmBZcRdK09yK7zqcqi92NsgwBzmKwoz6fQFljo+G3/giar0xZ+8HPXN HTnQ0von8o22yoK7x5H9jc+Fmq32zUvmYy2R3dAkY8PVmOgVEyf5z2OY3q0HEiEK 25kYJw9tdC7ZS6kI22l4tLGaAm6ntoM/ZbFUG0wrpESunWVrZOE= =EIwB -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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/55e4159c-7573-c6ca-b7f2-a859875dd5d0%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] I am unable to verify my image. Please help?
> > If you have the key files on disk, use --import: > $ gpg2 --import qubes-master-signing-key.asc > $ gpg2 --import qubes-release-3-signing-key.asc > > Then use --edit-key to set trust level to 4 on master key: > $ gpg2 --edit-key 36879494 > gpg> trust > gpg> save > > Then check that master<>release signatures are valid: > $ gpg2 --check-sigs > > You'll see the release key as "uid ... Qubes OS Release 3 Signing Key" > and directly underneath a line like: > "sig! DDFA1A3E36879494 2017-03-08 Qubes Master Signing Key" > > After all of this, the thing that validates the Signing key is "sig!". > It shows the Release key has been signed by the Master key and "!" means > the signature is valid. > > At this point, if you have taken care to verify the Master key by > retrieving it or viewing its fingerprint through other channels, then > your keys are all set. (Some people skip most of this and only import > the Singing key and verify its fingerprint, but I digress.) > > You can now do the --verify step. Thank you Chris (and sorry for the late response). I was able to verify my image. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/6f0588bf-00dd-4e2a-a081-e7254475a832%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Installation error: need at least 3mb more on /boot/efi
Thanks for the support! Altough right now I'm not planning on using a VPN so I might look at that in the future. I'm sorry I probably still can't understand how updates work in Qubes: I set the updateVM to sys-firewall as you said, I tried running sudo yum update in the fedora template and it still runs through TOR. I see a package updater utility in system tools, but it hasn't got internet since it's in dom0 so I can't do anything from that. If I try updating from sys-firewall directly, it only updates that specific VM. Also, I don't know how to update the whonix VM, since Tor can't run because it isn't up to date. Sorry for my noobyness. Have a great day -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/396e77b7-034f-40a2-a95e-98cec59a833c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Can I install Qubes 4.0 rc3 on external hard drive?
Thanks so much for your reply and your help. I installed using legacy boot and it worked fine -- in fact, I'm responding from "untrusted firefox" right now! I don't know if qubes comes up in the grub menu yet. I just got this installed, and ran it from the BIOS boot sequence Legacy-USB option, and I'm off for some errands myself. However, in lieu of killing myself with UEFI, since this works, I'll stick with it and am a happy camper. Maybe in the next week I'll play around more with UEFI, but I'm going to have to learn a bit more about it, I think. Anyway, you made my weekend! Thanks again for your reply. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/a81bb02b-94ed-4f22-90b7-9ec771b2d909%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: qubes 4 windows installation
On Fri, January 26, 2018 6:05 pm, Yuraeitha wrote: > On Friday, January 26, 2018 at 6:47:14 PM UTC+1, goo...@itrichter.de > wrote: > >> Am Samstag, 6. Januar 2018 20:28:21 UTC+1 schrieb goo...@itrichter.de: >> >> Addition: In order to get a stable Windows 7, I had to disable memory >> balancing AND set the min and max memory to the same value. Otherwise, >> the VM would crash each time the memory balancing occured. > > Yes, I can second this issue, I experience it too and had to turn off > dynamic memory. Although I did not confirm if it was the case the last > 1-2 months or so. I also had to be put on minimum Memory at 4GB, since > 3GB or 3.5GB RAM sometimes made Win7 crash. 4GB+ made it stable on my > system. Thirded, except I'm stable with 2GB min/max and have the Win7 swapfile fixed at 1GB. It didn't seem to like resizing the swap file. My Win7 gets very light use, however. > > For some > weird out reason I can't use my legal license key to download the medium > on the MS-website for a legal clean Win7 copy... seems like it isn't > uncommon either for others? Must be their way to encourage you to switch completely to Linux! > I can't see any windows-tools in the repository in Qubes 4, was it > integrated into Qubes from the beginning, done in a different way, or > maybe its not been done yet? There might be a GSoC suggestion to update them but like you found, I don't think they have an active maintainer. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/4be3443a79386c69cb5e8335a567d2c6.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: qubes 4 windows installation
On Tuesday, January 2, 2018 at 10:27:58 AM UTC+1, Roy Bernat wrote: > Hi All > > i am trying to understand if someone succeeded to install win7/10 on qubes 4. > R https://github.com/QubesOS/qubes-installer-qubes-os-windows-tools Seems like the Windows-Tools has been in-active for a long time. Except for power-settings adjustments in 2017, nothing else has happened since 2016. Is there a re-design made for Qubes 4 perhaps? Any ideas where to look or anyone got sources? -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/d8b82e1a-0a4d-480d-a8c3-26e17035238e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: qubes 4 windows installation
On Friday, January 26, 2018 at 6:47:14 PM UTC+1, goo...@itrichter.de wrote: > Am Samstag, 6. Januar 2018 20:28:21 UTC+1 schrieb goo...@itrichter.de: > > [...] > > Standalone Windows 7 VMs seem to work, though only without seamless GUI. > > But I have not been able to get template-based windows VMs, they always > > fail with "Cannot execute qrexec-daemon!". > > Addition: In order to get a stable Windows 7, I had to disable memory > balancing AND set the min and max memory to the same value. Otherwise, the VM > would crash each time the memory balancing occured. Yes, I can second this issue, I experience it too and had to turn off dynamic memory. Although I did not confirm if it was the case the last 1-2 months or so. I also had to be put on minimum Memory at 4GB, since 3GB or 3.5GB RAM sometimes made Win7 crash. 4GB+ made it stable on my system. I also brought over my Win7 install from Qubes 3.2. When I find a new clean install medium that I can be sure is 100% authentic, I'll re-install on Qubes 4 to test it out, but I'm hoping to get a clean verified install medium first. Maybe someone knows any reliable place to find trustworthy hash-sum values of the MS Win7 iso-files. I've seen some posted once, but it was on an unreliable website at the time. For some weird out reason I can't use my legal license key to download the medium on the MS-website for a legal clean Win7 copy... seems like it isn't uncommon either for others? Some reliable hash values would be wonderous for more trustworthy installs on Qubes. Also on my Qubes 3.2. Win7 on Qubes 4, I can easily transfer files in and out of Win7, and everything else Qubes related "seems" to work, except I have no internet connection. Just a heads up, and does anyone else experience this issue too from their Win7 that came from Qubes 3.2? I can't see any windows-tools in the repository in Qubes 4, was it integrated into Qubes from the beginning, done in a different way, or maybe its not been done yet? It seems very unfeasible to install Win7 without the qubes windows tools, or an Qubes 4 alternative that does the same. Does anyone know where we are at with these tools? I can't imagine installing Win7 is a good idea without it. Maybe find another computer, install Qubes 3.2. on it, install a new fresh Win7, backup, and then transfer it to Qubes 4? -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/ce377866-5357-4340-b6fc-58e4340d562e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: qubes 4 windows installation
Am Samstag, 6. Januar 2018 20:28:21 UTC+1 schrieb goo...@itrichter.de: > [...] > Standalone Windows 7 VMs seem to work, though only without seamless GUI. > But I have not been able to get template-based windows VMs, they always fail > with "Cannot execute qrexec-daemon!". Addition: In order to get a stable Windows 7, I had to disable memory balancing AND set the min and max memory to the same value. Otherwise, the VM would crash each time the memory balancing occured. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/92f0a09d-bed2-49d9-9923-75886c4af031%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Can I install Qubes 4.0 rc3 on external hard drive?
On Friday, January 26, 2018 at 4:59:00 PM UTC+1, bill...@gmail.com wrote: > I tried to send this question from the email address I used to subscribe to > the user group, but it's been about two hours and it hasn't shown up. I'm > assuming it's a Google thing, but I apologize if this question shows up twice. > > > So, here I go again. I'm a newbie with Qubes, but I love the idea. I tried > installing 3.2 some time ago, but had hardware difficulties, so I decided to > give 4.0 a try. > > I currently have a Dell Inspiron 5759 laptop, System BIOS 1.3.0, ePSA build > 4304.09 UEFI ROM, Intel i7-6500u cpu, secure boot disabled, Intel SGX > disasbled, fast boot set to "thorough" (though the same results occur with it > set ot "auto"). It is set up as dual boot with KDE Neon linux and Windows 10. > > I decided to give Qubes 4.0 rc3 a go. When I play with a new distro, I > usually start by installing it on an external hard drive, so I can make sure > it plays well with others without having to destroy my current working setup. > That's what I tried here. I attempted to install it on a Western Digital 2 > TB external portable drive. > > I downloaded the OS, created the installation flash drive, and chose the > external drive as the drive to install on. It seemed to go fine. No > warnings, no hangs. I installed using the default partitioning, with the > exception that I resized the / directory to make it a little smaller and > added a vfat /data partition. > > When I rebooted and hit F12 for the boot sequence options, sure enough > "Qubes" was one of them. Qubes *doesn't* show up in the boot options if it > gets to the grub boot list, that's still just neon and windows. But, if I use > the BIOS boot sequence, Qubes is an option. > > I chose "Qubes" as the option, and it dumped me into a BIOS screen that said > it was checking the safety of hardware, which it apparently passed, but then > came up and said it couldn't boot (though I did not write down the exact > error message, unfortunately). I rebooted again, did the boot sequence > thing, and it came up with a black screen with the options: > > "Press F1 to reboot" > "Press F2 to reboot into setup" > "Press F5 to run onboard diagnostics" > > And each button did exactly that. > > I then tried to boot on USB using legacy boot, but that came up with "no boot > device found." > > Booting into neon or windows still works fine. I can mount the external > drive and see all the normal linux stuff that a distro should have. I can > read and write to both the / and /data partitions on the drive with root > permissions. > > I tried changing usb ports, and that didn't do anything. I tried installing > with and without disk encryption, and that didn't change anything except that > I couldn't mount the encrypted / partition in neon. > > Is this some problem with having a /boot/efi on the external drive *and* a > /boot/efi on the internal drive? If so, why does it not work on an > installation but seems to work on the installation flash drive? > > Anybody have pointers to what I should try next? > > Thanks! > > billo aight, sorry I had to leave so abruptly on the previous post. To answer your question directly, yes it's very possible to install on an external drive. I've even installed Qubes on a thumb-drive. Fun times, albeit it was a bit slow :') It's really no different than normal install either, so whatever issue you have, is likely not involved in the settings of normal setup. It's probably more likely to be a bug, lack of hardware support, lack of kernel support, wrong UEFI/BIOS settings, wrong EFI/Grub settings, out-of-date UEFI/BIOS or buggy UEFI/BIOS which no update has been made available yet, and probably some other aspects I forgot to mention here, and I'm no expert either, so probably some things I don't know about too. I would check if you can update your UEFI/BIOS in your current situation. Just be careful, you can brick your motherboard if the update process goes badly. Especially if its interrupted before its done (power-outage, system-freezes, user-choice-to-restart-when-not-supposed-to, etc.), wrong update-version (although most motherboards should detect if its wrong version, some might not though). If you encounter questions regarding UEFI/BIOS updating process, then definitely don't forward without getting solid answers first. Think twice, or better yet, triple, before you do something here, as it's a sensitive update with bad consequences by any mistakes or accidents. Not trying to spread scaremongering here, just underlying to be careful and knowing the risk before deciding. Also EFI paths or SecureBoot keys might be lost in an UEFI update, in case you have other OS's on the machine. Also how far do you get with the LegacyBIOS/Grub install, do you encounter the initial Grub menu for the installer (and not the installed Qubes grub)? For example if you do, then it might
Re: [qubes-users] Installation error: need at least 3mb more on /boot/efi
On Thursday, January 25, 2018 at 8:21:37 PM UTC+1, dark...@gmail.com wrote: > Thanks for the lenghty response! Indeed the errors were python-code related, > but it turns out the problem was in the sys-net domain not starting correctly > because of the card reader, which was seemingly seen as a network adapter. > Now that I fixed that everything seems to work properly and I'm loving it. > One last thing: I set qubes to update packages over tor. I immediately > regretted > the decision. Is there a way to download update w/o Tor? > Regards Glad you love it already, you will likeliy only grow even happier with Qubes over time :-) It's an amazing project indeed! and there is still a lot of new things going on, expanding the idea of what Qubes is about further. Like the recent news here https://www.qubes-os.org/news/2018/01/22/qubes-air/ as far as I understood it it's not changing Qubes or the ideas and principles behind Qubes, but it is however expanding what you can opt-in and with choices you have with Qubes. Ad for changing updates over Tor, yes, and it's super easy too :-) Go to Qubes menu ---> System Tools ---> Global Qubes Settings. In there, change the UpdateVM away from sys-whonix, and put it to sys-firewall. There are many in the list, but on any default install, you can only use sys-whonix or sys-firewall, the former for Tor, and the latter for regular network. If you expand your default setup to include an VPN connection, multiple of VPN connections, or multiple of Tor connections, combine, or have multiple of firewalls, then here too is where you'll change where Qubes gets its updates from :-) Note in Qubes 4, Qubes will handle the default pre-installed template updates, so that templates has no internet themselves (unlike Qubes 3.2. where every template has internet on their own). You still update the same way, but Qubes will handle the distribution of template packages. As far as I know, this too will follow this setting, although I'm only almost sure, not entire, I did not yet check if my assumption here is true or not. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/908ef0f5-2dea-4787-b754-a8e15f2002ba%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Qubes Manager is coming back in Qubes 4.0-rc4!
On Saturday, 13 January 2018 03:58:03 UTC+1, Andrew David Wong wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > The Qubes VM Manager will be returning in Qubes 4.0-rc4, which is > scheduled for release next week. The returning Qubes Manager will be > slightly different from the 3.2 version. Specifically, it will not > duplicate functionality that is already provided by the new 4.0 > widgets. Specific examples include attaching and detaching block > devices, attaching and detaching the microphone, and VM CPU usage. > > - -- > Andrew David Wong (Axon) > Community Manager, Qubes OS > https://www.qubes-os.org > > -BEGIN PGP SIGNATURE- > > iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlpZdZwACgkQ203TvDlQ > MDB4GBAAqKQKgbUHWuTpzfW8o2HOjvM/fSxt9gSlDi+tS3x/dogNC0riO6VgFIJr > zNUm2/7nYF4iAiES0HamgVfNBHFpKY1QZgRYyokrLMK78HmCyIKJ3A0cF2LOvlsS > x88xpwBL0zwUX0y/eqsaxGGIqr9D1c25psYdi/IeE3KhR35gz/2j8HiB1/mEl0Z4 > JvepszI6HD7vJ41ullWsygHemTT2JAeFSCG0zWrfdxvkwYFQgXEn+AeEhgOL6BhM > RXFuMWnl2w0cbnPgDpnmT0IVHlz8gRsljkyWLkqT4k/pldhy9OCjtMKuHGIaaen6 > KLF2rGkpVObfgQQrQOdll03KrFqPona5ywtdeQUMDGVoNJXuhFidyCLWEKPBlAhS > LDCb/UxRbbPhwol4eEYeOnxWbCMgEwnEtnkEZiT4m9y3lQQLK+8zSZpW5uMLDzs0 > om9Xd9iba7hZomXE1rEcg2UaYok0lSQmzGS2YKh3OQbEmXtrZdILXVo0NLtDcTun > q47PzYjKc82ZeUZSLBjfkgf0mhocPuwk3FLsMb3rwW0kEbzuRZjHKgxgnRbOK67b > qH0roZ8GHrX7Xu4AvjYxUvlkTU+h2ObPMvxf2IR1/S37UUyrwNFEaC6czA/VmVV6 > 5SzFVGJkH/SFZsQ9qvzgjz/8OnLOMvBi3X/ee21G8s4ACmcrmrM= > =fcWR > -END PGP SIGNATURE- Thanks a lot :))) -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/5a6e79c3-7e77-495e-bb7b-dc2353752577%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Can I install Qubes 4.0 rc3 on external hard drive?
On Friday, January 26, 2018 at 4:59:00 PM UTC+1, bill...@gmail.com wrote: > I tried to send this question from the email address I used to subscribe to > the user group, but it's been about two hours and it hasn't shown up. I'm > assuming it's a Google thing, but I apologize if this question shows up twice. > > > So, here I go again. I'm a newbie with Qubes, but I love the idea. I tried > installing 3.2 some time ago, but had hardware difficulties, so I decided to > give 4.0 a try. > > I currently have a Dell Inspiron 5759 laptop, System BIOS 1.3.0, ePSA build > 4304.09 UEFI ROM, Intel i7-6500u cpu, secure boot disabled, Intel SGX > disasbled, fast boot set to "thorough" (though the same results occur with it > set ot "auto"). It is set up as dual boot with KDE Neon linux and Windows 10. > > I decided to give Qubes 4.0 rc3 a go. When I play with a new distro, I > usually start by installing it on an external hard drive, so I can make sure > it plays well with others without having to destroy my current working setup. > That's what I tried here. I attempted to install it on a Western Digital 2 > TB external portable drive. > > I downloaded the OS, created the installation flash drive, and chose the > external drive as the drive to install on. It seemed to go fine. No > warnings, no hangs. I installed using the default partitioning, with the > exception that I resized the / directory to make it a little smaller and > added a vfat /data partition. > > When I rebooted and hit F12 for the boot sequence options, sure enough > "Qubes" was one of them. Qubes *doesn't* show up in the boot options if it > gets to the grub boot list, that's still just neon and windows. But, if I use > the BIOS boot sequence, Qubes is an option. > > I chose "Qubes" as the option, and it dumped me into a BIOS screen that said > it was checking the safety of hardware, which it apparently passed, but then > came up and said it couldn't boot (though I did not write down the exact > error message, unfortunately). I rebooted again, did the boot sequence > thing, and it came up with a black screen with the options: > > "Press F1 to reboot" > "Press F2 to reboot into setup" > "Press F5 to run onboard diagnostics" > > And each button did exactly that. > > I then tried to boot on USB using legacy boot, but that came up with "no boot > device found." > > Booting into neon or windows still works fine. I can mount the external > drive and see all the normal linux stuff that a distro should have. I can > read and write to both the / and /data partitions on the drive with root > permissions. > > I tried changing usb ports, and that didn't do anything. I tried installing > with and without disk encryption, and that didn't change anything except that > I couldn't mount the encrypted / partition in neon. > > Is this some problem with having a /boot/efi on the external drive *and* a > /boot/efi on the internal drive? If so, why does it not work on an > installation but seems to work on the installation flash drive? > > Anybody have pointers to what I should try next? > > Thanks! > > billo You may want to opt to use LegacyBIOS/Grub instead of UEFI/EFI to install. One reason out of multiple, is that if you ever need to move the external drive to another machine, do an UEFI update, or similar, you might encounter issues with having to re-build the EFI path to UEFI. This is on some setups easier, and on others downright annoying or buggy. It can get more troublesome if you have secureboot, but luckily it's not part of the solution anyway without a Qubes SecureBoot key, which has not been made yet. Either way, having it with Grub, makes it easier, and also more intuitive if you need to use an older kernel/xen after having issues with a kernel/xen update. You can also install Qubes on another machine, update it, and then bring your drive back to the machine you intend to use it for. Just be careful not to use bad hardware, keep it to hardware you trust. Also don't install with UEFI/EFI on another computer, unless you know your way around re-building EFI paths to UEFI, which can harm both computers in terms of existing EFI paths, as well as making new EFI path each time you move the drive around. Unfortunately I'm out of time now, I gotta go. But for now I hope these thoughts can help you in some way. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/e846c2d8-a717-4404-ab35-7b48a630ef8e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Can I install Qubes 4.0 rc3 on external hard drive?
I tried to send this question from the email address I used to subscribe to the user group, but it's been about two hours and it hasn't shown up. I'm assuming it's a Google thing, but I apologize if this question shows up twice. So, here I go again. I'm a newbie with Qubes, but I love the idea. I tried installing 3.2 some time ago, but had hardware difficulties, so I decided to give 4.0 a try. I currently have a Dell Inspiron 5759 laptop, System BIOS 1.3.0, ePSA build 4304.09 UEFI ROM, Intel i7-6500u cpu, secure boot disabled, Intel SGX disasbled, fast boot set to "thorough" (though the same results occur with it set ot "auto"). It is set up as dual boot with KDE Neon linux and Windows 10. I decided to give Qubes 4.0 rc3 a go. When I play with a new distro, I usually start by installing it on an external hard drive, so I can make sure it plays well with others without having to destroy my current working setup. That's what I tried here. I attempted to install it on a Western Digital 2 TB external portable drive. I downloaded the OS, created the installation flash drive, and chose the external drive as the drive to install on. It seemed to go fine. No warnings, no hangs. I installed using the default partitioning, with the exception that I resized the / directory to make it a little smaller and added a vfat /data partition. When I rebooted and hit F12 for the boot sequence options, sure enough "Qubes" was one of them. Qubes *doesn't* show up in the boot options if it gets to the grub boot list, that's still just neon and windows. But, if I use the BIOS boot sequence, Qubes is an option. I chose "Qubes" as the option, and it dumped me into a BIOS screen that said it was checking the safety of hardware, which it apparently passed, but then came up and said it couldn't boot (though I did not write down the exact error message, unfortunately). I rebooted again, did the boot sequence thing, and it came up with a black screen with the options: "Press F1 to reboot" "Press F2 to reboot into setup" "Press F5 to run onboard diagnostics" And each button did exactly that. I then tried to boot on USB using legacy boot, but that came up with "no boot device found." Booting into neon or windows still works fine. I can mount the external drive and see all the normal linux stuff that a distro should have. I can read and write to both the / and /data partitions on the drive with root permissions. I tried changing usb ports, and that didn't do anything. I tried installing with and without disk encryption, and that didn't change anything except that I couldn't mount the encrypted / partition in neon. Is this some problem with having a /boot/efi on the external drive *and* a /boot/efi on the internal drive? If so, why does it not work on an installation but seems to work on the installation flash drive? Anybody have pointers to what I should try next? Thanks! billo -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/97e2671e-0c23-4574-8c9c-7a6537a590e9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Qubes 4.0 Documentation
On Fri, January 26, 2018 9:22 am, Alex Dubois wrote: > On Friday, 26 January 2018 03:36:33 UTC, Andrew David Wong wrote: > Happy to contribute. maybe we can have a direct conversation so that we > can discuss what is needed and where I feel comfortable... Speaking only on my own behalf of course, thank you. Editing the docs is pretty straight-forward (https://www.qubes-os.org/doc/doc-guidelines/), so I'd suggest jumping in and editing whatever you are comfortable with. I'm coming across documents where someone else has already gone in and called out or updated with R4.0 content, so thanks to those contributors as well! -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/012f06ff57be8fd2c1405d791ae01424.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Qubes 4.0 Documentation
On Fri, January 26, 2018 3:36 am, Andrew David Wong wrote: > On 2018-01-25 12:28, awokd wrote: >> 1. Should I open an issue for tracking and move the discussion >> over there? Move to qubes-devel? Keep here? > > Please open an issue in qubes-issues. https://github.com/QubesOS/qubes-issues/issues/3495 > I agree that the tool man pages should not be shared between 3.2 and > 4.0 (but they probably wouldn't be anyway, due to the nature of the > system just described). What will be the naming convention for direct links? I can see sometimes we'd want to link to the latest version of qvm-whatever, and other times when we want to link to a specific major version. > I > think it makes sense to handle these cases specifically, by creating a > page that collects all the versions of each one. I'll do this now. Thank you. > In general, it's worth thinking about whether we even want to keep > severely outdated category 2 documentation around. Does it have any value > anymore, or will it just produce misleading search results? (Note that it > will all remain permanently archived in the git revision history, so it's > mainly a question of visibility on the website.) My vote is to axe it. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/835aa4381a02b34be8f3162224d965f0.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Please help with 8th Generation Intel i5
On Thu, January 25, 2018 7:19 pm, Krišjānis Gross wrote: > > here it is (attached). Hope that helps! >From the journal: Jan 25 20:53:15 localhost.localdomain kernel: [drm] The driver support for your hardware in this kernel version is alpha quality See CONFIG_DRM_I915_ALPHA_SUPPORT or i915.alpha_support module parameter to enable support in this kernel version, or check for kernel updates. This is enabled by default on Qubes 4.0, but I'm not sure if that's the case for 3.2. That could be why video was so slow on 3.2. (On a side note, why is this Linux driver still alpha after it's been around for years?) Everything else looks fine. I see DMAR gets set up so hardware virtualization should work. Didn't notice any obvious problems in the Xorg logs. Look for the "i915.preliminary_hw_support=1" entries in https://pastebin.com/u8z6nWV5 for an example of where you should add them to 3.2 if they aren't there. I agree with the other suggestion made earlier, wait for rc4 then try 4.0 again too. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/effedb1fb5a5eca4867fac9287bf44ee.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Qubes 4.0 Documentation
On Friday, 26 January 2018 03:36:33 UTC, Andrew David Wong wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> On 2018-01-25 12:28, awokd wrote:
> > Resuming working my way through splitting up the documentation now
> > that the 3.2 vs. 3.3 question has been mostly settled. Some
> > general questions:
> >
> > 1. Should I open an issue for tracking and move the discussion
> > over there? Move to qubes-devel? Keep here?
>
> Please open an issue in qubes-issues.
>
> (Doing so does not preclude discussion here or on qubes-devel.)
>
> > 2. The command line tools in particular
> > (https://www.qubes-os.org/doc/vm-tools/ and
> > https://www.qubes-os.org/doc/dom0-tools/) seem Wrong to try to
> > share the same pages for 3.2 and 4.0. Not only is the selection of
> > commands slightly different between versions, but many have
> > slightly different options ("-a" vs. "a"). I'm thinking of copying
> > all the existing pages, appending "4" so they can be linked to
> > directly, and putting in their own section. Thoughts?
>
> Those pages are automatically generated from the man pages stored with
> the tools' source code in their own respective repos, so any changes
> to those pages in qubes-doc will be overwritten. Changes should be
> made to the original files instead. That way, the changes will persist
> when the qubes-doc versions are automatically generated.
>
> I agree that the tool man pages should not be shared between 3.2 and
> 4.0 (but they probably wouldn't be anyway, due to the nature of the
> system just described).
>
> > 3. Some of these documents are pretty outdated. Should we have an
> > Archive link and move stuff like
> > https://www.qubes-os.org/doc/template/fedora/upgrade-18-to-20/ to
> > it so it doesn't clutter up the main Docs page?
> >
> There are two categories of outdated documents:
>
> 1. Documents that we want updated (but that no one has updated yet).
> 2. Documents that are about old topics (but are otherwise good).
>
> I don't think it would make sense to move documents of category 1 into
> an archive section, since that would incorrectly suggest that we don't
> want or expect them to be updated.
>
> The old Fedora upgrade documents fall into category 2. However, it
> looks like they (and perhaps the release notes for unsupported Qubes
> versions) are the only major offenders visible in the main table of
> contents. This is understandable, since a new version of the document
> gets added each time there's a new version of the corresponding
> software. I think it makes sense to handle these cases specifically,
> by creating a page that collects all the versions of each one. I'll do
> this now.
>
> In general, it's worth thinking about whether we even want to keep
> severely outdated category 2 documentation around. Does it have any
> value anymore, or will it just produce misleading search results?
> (Note that it will all remain permanently archived in the git revision
> history, so it's mainly a question of visibility on the website.)
>
> - --
> Andrew David Wong (Axon)
> Community Manager, Qubes OS
> https://www.qubes-os.org
>
> -BEGIN PGP SIGNATURE-
>
> iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlpqojUACgkQ203TvDlQ
> MDDG4Q//Q6ND5fzToFv6KKQn4SzkcUSIIZQKtMPTlG9BkC7UCgjFZ+7sxrLA1N5X
> H+9Z88+QNRL6FBOa6DHpFZOOA6vomzw0HXkTF+g9VcplsJIFZh6iB7lpSta1XwKU
> 1DG+ayF0oDd8PxKtSjaslMWRsr9p9cApPM7G+z6sGLB34LLZfolx19FRhwcpfBBK
> 09wyaAzmr5sF9oO8rSxC1llz5u75GatXUu+tHIc3Jh9C4hBtX7MSwyoq7eTkXnKQ
> VpS35O8thmhm6cEuyNQsUD7ia853lWRcdTur1Am7GIx3jwl7VBQ6YCqanLRLueaI
> tm4LbBfNrZcxFexHp0mB+veDeIfkC4cJZm8/sbjrHEicK6Cuvp5E0E6iLOaMw9gI
> y3D1ypbEwMXyYQFPWW0h488pNow9RCrTHTcvBhgyIBw0xhCe0j89RZpbV3UB79k1
> n5YRoj36XXRmHho/KVIlFMrzsXE6q9sawU8P1/Q7mBjX3fQLDoOEwFMtHRZTiFLk
> NOkqv328xsqJy1smKgfFI4cpNMa1+Be0zGjqRWjBFNTqWEoNPkAbDbhbiwYPZYop
> CW0lDS6b6dc2KCMcxlP+3BwuFC+pS9Yw/Qw2B0yceVjrH0YnLoVkOaqC6ojGx6DH
> JAFtJLB6FbXssbK3JASOvGKpMxcktfQe3quJZmTaMY2yLkBaomA=
> =8MfO
> -END PGP SIGNATURE-
Happy to contribute. maybe we can have a direct conversation so that we can
discuss what is needed and where I feel comfortable...
--
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/134582e1-f89b-47d3-8176-68de4fd88851%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: i3 under Qubes 4 RC3
Den torsdag den 25. januar 2018 kl. 20.17.48 UTC+1 skrev Kevin Martinsen: > i3 has been working fine for me. > > Did you follow the installation instructions on > https://www.qubes-os.org/doc/i3/? Specifically: > $ sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing > i3-settings-qubes Yesh, I have followed those steps (but please also note that the documentation is related to 3.2, and as such it might be that i3 has actually been bumped to the stable repos, but I don't know :) > What do you mean you cannot start any programs from vms? How are you trying > to start programs? For me I have mod4+d to use dmenu. And do you mean to say > that qvm-run works correctly? My dmenu is broken, for starters. Dmenu only shows dom0 applications, so I cannot start anything that way. When I run qvm-run to start something, I can see that my VM is started (with qvm-ls) and I can hear my CPU responding (as in it starts fanning), but nothing visually happens. Nothing is ever started. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/4f15ee67-f291-41e4-b9bf-1b24df5fa915%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
