[qubes-users] pool "Manual repari required"
Hello All, What is the general procedure in Qubes 4, if we can open the Luks, but then pool00 seems inaccessible with rdsosreport message: Check of pool qubes_dom0/pool00 failed (status:1). Manual repair required! Thank you for your time. Crypto Carabao Group --- #Plow_with_Carabao! #Plow_like_Carabao! PGP: `3f7d5efddfe0cfa588c134065d72fe83efbb7649` Sent with ProtonMail Secure Email. -- 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/YL94dzEv24F1_G45avhJNyAszDnofxVjgtp8Z3c6NtWhtX-ZL3frwWRplbYpI_kMdC9NGdBMaCSHYx53k-CbuGoKha0A9PiZphgVOBS-RqA%3D%40protonmail.ch. publickey - cryptocarabao@protonmail.ch - 0x3F7D5EFD.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
[qubes-users] Trezor 1 not working with web wallet
We have this same problem as here: https://github.com/trezor/trezord-go/issues/163#issuecomment-552288220 The trezor devs reopened the issue, but looks like they have more important problems to work. Is anyone using Trezor 1 with Qubes 4 successfully? What's the setup or at least troubleshooting steps please? Crypto Carabao Group --- #Plow_with_Carabao! #Plow_like_Carabao! PGP: `3f7d5efddfe0cfa588c134065d72fe83efbb7649` Sent with ProtonMail Secure Email. -- 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/aRl3ulugyXDxipRu0Z1s1YnCEWd0cUBDSB_n2rZD_SaIr-YAXaEM7WU_lnL-TCYCmsuf6R5nGM870NxiuW958vIUsRF07yZGD4ikZxMnvY8%3D%40protonmail.ch. publickey - cryptocarabao@protonmail.ch - 0x3F7D5EFD.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
[qubes-users] qvm-block doesn't see a thin volume
Created a thin volume on a second hdd. Can use mount to attach it to dom0 and make a backup on it for example. mounted or unmounted, qvm-block can't see it. So, can't attach it to any other cube. Is that how it's supposed to be? -- 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/6sfv9dW7SH_SOg0yhUpdpNY9vhBXQ_Pa5-psyO_ZXizPPbTqPWxpNz8jNGn3eLUPYb20gzPFx6Y42TGjtp9n9P7BVU0bfDvR__xzD8yOzbs%3D%40protonmail.ch. For more options, visit https://groups.google.com/d/optout. publickey - cryptocarabao@protonmail.ch - 0x3F7D5EFD.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
[qubes-users] An app's dialogs are not displayed properly
Has anyone experienced this kind of problem with any of your apps: https://github.com/bisq-network/bisq/issues/2855 -- 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/gaJBgvOop_QXSucD0f3KcO7PFn82Q_7npOJjm7amPP_JO38H_HlogVpoNMDrauHDEXzYbPuLCPDaue9aAU3AboUyKP4k4K0vo7qvSPYzJ8E%3D%40protonmail.ch. For more options, visit https://groups.google.com/d/optout. publickey - cryptocarabao@protonmail.ch - 0x3F7D5EFD.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
[qubes-users] Qubes: Unable to connect to VPN
We've also been trying for days to get a VPN to resolve on a brand new R4.0 install, to either one of 2 different VPN providers, using the iptables and cli scripts: https://www.qubes-os.org/doc/vpn/#set-up-a-proxyvm-as-a-vpn-gateway-using-iptables-and-cli-scripts I've also set it up before on a 3.x cubes and it worked using the above. So far, what's pretty certain is that these instructions were carried over automatically, but actually don't work for the R4.0 version. BTW, there is no "/usr/lib/qubes/qubes-vpn-setup" in the Fedora 29 or Debian 9 templates. So, wherever that came from, it's not in the new installer version we got. Neither is there a path: /etc/openvpn/update-resolv-conf in the VMs based on Fedora 29. (Haven't tried Debian 9 for that yet.) That probably came from a particular VPN provider, and would have to be installed in the template anyway to persist, right? It seems that the update-resolve-conf is a default script that ships with some distros, such as Mint (attached), and works on our other machine, and does the function that the "`qubes-vpn-handler.sh`" does in the Qubes VPN instructions, but it doesn't work on Qubes in our case for the same VPN provider either. Seems to require a lot of modification and merge the two maybe, which will take us another several days to figure out, if ever. Openvpn actually does connect, but there's no DNS resolution, because the resolv.conf doesn't get updated. One thing we noticed is that in the resolvctl the 8.8.8.8 and 8.8.4.4 and a couple of IPv6 servers are listed as "Fallback DNS Servers". We can even resolve manually using them with dig. However, the systemd-resolved or whatever is doing the resolution in this systemd mess, actually doesn't use them as a "Fallback" to resolve. Don't know what to do next to fix this, except just more trial and error, and messy hack arounds... On Tuesday, November 20, 2018 at 7:38:17 PM UTC, Otto Kratik wrote: > Further update: I decided to try a completely different VPN provider's config > file, and to my surprise that one worked fine using the old simple method of > calling openvpn from the AppVM. > > Examining both files and looking for the difference between the two, it > appears the broken one did not ever invoke resolvconf include the following > lines: > > script-security 2 > up /etc/openvpn/update-resolv-conf > down /etc/openvpn/update-resolv-conf > > > Adding those lines to the non-functioning file and running it resulted in > success. -- 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/J1cmNix8ygkshY3RKFWTEOuBvaV8rx7JRFEnnrurBo5JaFl-mRz9r9Osn1o3oh2vah8J4G7YPFcQ2ThmDp2U0TGQx7kV192unHv9mKU9H_M%3D%40protonmail.ch. For more options, visit https://groups.google.com/d/optout. update-resolv-conf Description: Binary data publickey - cryptocarabao@protonmail.ch - 0x3F7D5EFD.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
Re: [qubes-users] Re: Qubes: Unable to connect to VPN
> > Install per the instructions for Mr.Laprise's excellent > qubes-vpn-setup in an Template-based AppVM , don't miss any steps. > ELSE > > delete the AppVM and startover make sure openvpn is installed in > the Template chosen , make sure to enable proxy in the created AppVM > , and for services add the openvpn in the qubes manager tab > > Which VPN provider are you using ? > > Thanks. Turned out that we probably got it to work earlier, but didn't know how to test it properly. So, we spent days trying to figure out a problem that didn't exist. We were confused from Step 1 by fact that to create ProxyVM, one now has to know to create an AppVM, and check "provides network". Setting "vpn-handler-openvpn" in the the Services for that qubes, as some thread suggested, is still something we are not sure about. We've decided to move to a hardware device from the VPN provider. With so many manual steps and several different ways to set it up, on top of VPN provider script variations, a device seems the safest option to avoid making some mistake or misunderstanding, because we are not security experts or developers in the field. - > > 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/ac3b7cc3-eede-c2f3-d368-7de333dd3c2a%40riseup.net. > For more options, visit https://groups.google.com/d/optout. -- 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/ZMCpY0k63FxEEoDdmVtdC14qqJlZYEZTH-m9p7B5mUiIIKxzjT1TjRuQ8jSC0ONyt2DKRFHf0OC7XeDfTXd9J6TFdkjlamj967-cr97J1wM%3D%40protonmail.ch. For more options, visit https://groups.google.com/d/optout.
