Re: [qubes-users] Installing qr-exec on HVM
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Fri, Oct 05, 2018 at 02:38:28PM -0700, Will Dizon wrote: > Unfortunately, it didn't work still when qubes-gui-agent was running. > > I tried recompiling everything again, and the results have changed quite a > bit. Now, instead of autohiding the HVM window in dom0, I can see a very > clear failure which points me in the direction of Xorg instead. > > Sadly, this feels like a regression, but alas... I'm sure I'll get there > eventually. > > As far as "xl console lfs", dom0 reports "unable to attach console". And in > terms of dom0, it is still giving no sense of failure: > > $ qvm-run --pass-io personal whoami > user > $ qvm-run --pass-io lfs whoami > $ qvm-run lfs "touch /tmp/dummy" > Running 'touch /tmp/dummy' on lfs > > Needless to say, /tmp/dummy doesn't ever emerge. > > The new error is > > systemctl status qubes-gui-agent.service > ... > Process: 660 ExecStart=/usr/bin/qubes-gui $GUI_OPTS (code=exited, > status=1/FAILURE) > ... > lfs qubes-gui[660]: XIO fatal IO error 11 (Resource temporarily unavailable > on X server ":0" > lfs qubes-gui[660]: after 37 requests (36 known processed) with 0 events > remaining) > > X works (startx shows me a desktop and consoles), but nothing yet from > getting Qubes GUI agent and qrexec. qubes-gui-agent starts its own X server, on :0. So, it conflicts with the one started manually with startx. - -- Best Regards, Marek Marczykowski-Górecki Invisible Things Lab A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlvBRPgACgkQ24/THMrX 1yzOfAf/WdwNBlfHtR7Oin5+j3SV48z27ajfarE+UBOXrwZkrsl+mPDrvllou9Kq uVUVOBBswJhAVT9hWhKJbOZvDPW9r4jyKpiidg3FvdRWX7i/Dci5UYK1qqrPuDtw vZs3raKofxmprH7wKNcwcBVslr1SeTOOvbkNkv1WYbS46sGd1X//CWvXghYCQzqL HTX3v732aYO9LADgNwHRV5AQKsBtYLM/Ej8QR2Amd3frHIx905hErix8ForYGzUp JxRIR0ZuAmoK3aQglb1Jon2YmJ0MeOszMP9aqh1BTpTZ+JrM5/hWj2g0NN+rwRIo GOYt7eTlrfmGfAeCgQitOOszc/oSzQ== =g83e -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/20181013010601.GD5083%40mail-itl. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Default keyring
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Fri, Oct 12, 2018 at 07:12:35AM -0700, Patrick wrote: > When creating a new template, then launching a browser in it (in order to > install software), a dialog box asks: > > An application wants access to the keyring "Default keyring". > > Never seen this, my passwords don't work. Is that browser chrome/chromium by a chance? I think it's this issue: https://askubuntu.com/questions/31786/chrome-asks-for-password-to-unlock-keyring-on-startup#191490 Either try setting empty password, or try solution with - --password-store=basic. - -- Best Regards, Marek Marczykowski-Górecki Invisible Things Lab A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlvBQkwACgkQ24/THMrX 1yxOAAgAgkTv3NhST1QmRCrAjueYMFRv0bQV9gl+JaPuc99QBI1plqnm5uuQqaEb MbHJ033R0LQhCKneGOUeXu1jEmbeCRlQ3GnDQAuJQRVOl/sszBCuNYL+0cl8oHfg +hUcKADdOGe1fs0ZG8wpm0ty6uJ6HfZ0MCudQz3r97BmBl3fAsNSEs4Y/xxqAJIj 5/7py1tx9R+R026llEfQmDpQq+UllOODoFywMc/RpSkCnDYKyP02SBXvj/2GGD2/ kAGfbncFWSzAztPmMrBKMjejAhAJJ6ztV+m2cdjxd5m1WVqKsPzqGv5SKw5pqBZV T4eTPKICj6bL3b8NK/vQrQ2+2M3LIQ== =XMHS -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/20181013005437.GC5083%40mail-itl. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Fujitsu Lifebook U757
On 10/12/2018 04:42 PM, Gep Petto wrote: Why can't Qubes OS be installed on the Fujitsu Lifebook U757? http://www.fujitsu.com/global/products/computing/pc/notebooks/lifebook-u757/ Did you try? Keep in mind that selecting a computer for Qubes comes with some general constraints, so here is my 'compatibility lecture': 1. Computer must be compatible with open source OS/drivers. If open source developers had to guess in order to make compatible drivers, then the level of compatibility and stability may be poor. 2. Computer must have advanced virtualization and memory management features which must be correctly configured and programmed by the hardware vendor. But some of these features end up in models that aren't marketed to advanced users, so the features are left unsupported or mis-configured by the BIOS/motherboard to save on engineering costs. Usually when Qubes doesn't work on a particular model its because of some combination of 1 and 2. This is not surprising with models like the U757 because the Fujitsu data sheet only lists MS Windows as a compatible operating system. - My advice is to start looking for a Qubes laptop on the HCL page below and/or look at business models from the 'big 3' manufacturers Dell, Lenovo and HP in addition to Linux-focused System 76 and Purism which the manufacturer describes as "Linux compatible" and does _not_ rely on Nvidia graphics. Although that doesn't specifically address the Xen aspect of Qubes, this is a pretty good starting point in general for finding compatible hardware. https://www.qubes-os.org/hcl/ Users should note that "Compatible with MS Windows" is not the Good Housekeeping Seal Of Approval For Linux Users... It means a partnership exists between the hardware vendor and Microsoft without regard as to whether or not design specs required to write good drivers have been made available to open source/Linux developers or anyone else. It can also mean that Microsoft intended that partnership (and hardware info) to be exclusive meaning the info _won't_ be distributed to anyone else. -- Chris Laprise, tas...@posteo.net https://github.com/tasket https://twitter.com/ttaskett PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 -- 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/56425a3b-6a2a-5e67-7986-5ddba3692c93%40posteo.net. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Fujitsu Lifebook U757
Why can't Qubes OS be installed on the Fujitsu Lifebook U757? http://www.fujitsu.com/global/products/computing/pc/notebooks/lifebook-u757/ -- 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/2b128c89-09fe-4a7f-9007-212d555c37f1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Default keyring
When creating a new template, then launching a browser in it (in order to install software), a dialog box asks: An application wants access to the keyring "Default keyring". Never seen this, my passwords don't work. -- 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/cdfe0295-90f1-4fe1-9401-7d4fef98d283%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] whonix upgrade, qubes4
I went thru the steps to remove any existing whonix. No errors were reported. Then I issued the command to re-install whonix-14. Whonix does not work. Whenever I boot up one of the VMs based on the new whonix, I find that qrexec-agent is crashing. [ 15.903799] qrexec-agent[789]: segfault at 70d5257f6ff8 ip 70d5255f3355 sp 70d5257f7000 error 6 in ld-2.24.so[70d5255dd000+23000] This is similar to whonix-9 template issues some have seen. qubesdb-daemon also segfaults in the same manner earlier in the boot. -- 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/a23b3d8b-aaec-45c6-a1aa-ce8334b54cf4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
