[qubes-users] Re: new Qubes install shows dom0 kernel: ACPI Exception: AE_NOT_FOUND, Evaluating _PRS (20170728/pci_link-176)
A bit further, but no resolution. This seems to all be related to the Intel UHD 630 integrated graphics in the 9600K. Xorg.0.log shows that: [35.335] (==) No Layout section. Using the first Screen section. [35.335] (==) No screen section available. Using defaults. [35.335] (**) |-->Screen "Default Screen Section" (0) [35.335] (**) | |-->Monitor "" [35.335] (==) No monitor specified for screen "Default Screen Section". and it then loads the drivers and further down shows: [37.387] (WW) Falling back to old probe method for vesa [37.387] (EE) Screen 0 deleted because of no matching config section. [37.387] (II) UnloadModule: "modesetting" [37.388] (II) FBDEV(0): Creating default Display subsection in Screen section "Default Screen Section" for depth/fbbpp 24/32 [37.388] (==) FBDEV(0): Depth 24, (==) framebuffer bpp 32 [37.388] (==) FBDEV(0): RGB weight 888 [37.388] (==) FBDEV(0): Default visual is TrueColor [37.388] (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0) [37.388] (II) FBDEV(0): hardware: EFI VGA (video memory: 3072kB) [37.388] (II) FBDEV(0): checking modes against framebuffer device... [37.388] (II) FBDEV(0): checking modes against monitor... [37.388] (--) FBDEV(0): Virtual size is 1024x768 (pitch 1024) [37.388] (**) FBDEV(0): Built-in mode "current": 78.7 MHz, 59.9 kHz, 75.7 Hz [37.388] (II) FBDEV(0): Modeline "current"x0.0 78.65 1024 1056 1184 1312 768 772 776 792 -hsync -vsync -csync (59.9 kHz b) [37.388] (==) FBDEV(0): DPI set to (96, 96) [37.388] (II) Loading sub module "fb" [37.388] (II) LoadModule: "fb" [37.389] (II) Loading /usr/lib64/xorg/modules/libfb.so [37.391] (II) Module fb: vendor="X.Org Foundation" [37.391] compiled for 1.19.3, module version = 1.0.0 [37.391] ABI class: X.Org ANSI C Emulation, version 0.4 [37.391] (**) FBDEV(0): using shadow framebuffer [37.391] (II) Loading sub module "shadow" [37.391] (II) LoadModule: "shadow" [37.391] (II) Loading /usr/lib64/xorg/modules/libshadow.so [37.392] (II) Module shadow: vendor="X.Org Foundation" [37.393] compiled for 1.19.3, module version = 1.1.0 [37.393] ABI class: X.Org ANSI C Emulation, version 0.4 [37.393] (II) UnloadModule: "vesa" [37.393] (II) Unloading vesa [37.393] (==) Depth 24 pixmap format is 32 bpp [37.394] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by kernel - disabling) [37.398] (==) FBDEV(0): Backing store enabled [37.401] (==) FBDEV(0): DPMS enabled [37.402] (==) RandR enabled [37.412] (II) SELinux: Disabled on system [37.413] (II) AIGLX: Screen 0 is not DRI2 capable [37.413] (EE) AIGLX: reverting to software rendering [37.503] (II) IGLX: enabled GLX_MESA_copy_sub_buffer [37.504] (II) IGLX: Loaded and initialized swrast [37.504] (II) GLX: Initialized DRISWRAST GL provider for screen 0 so i tried to follow instructions in https://www.qubes-os.org/doc/nvidia-troubleshooting/ to create a xorg.conf.new but that fails with: Using config file "/root/xorg.conf.new" Using config directory "/etc/X11/xorg.conf.d" Using system config directory "/usr/share/X11/xorg.conf.d" modeprobe: FATAL Module fbcon not found in directory /lib/modules/4.14.119-2.pvops.qubes.x86_64 intel: waited 2020 ms for i915.ko driver to load Number of created screens does not match number of detected devices. (EE) Server terminated with error (2) Closing log file. My conclusion is that i need a newer kernel, but that is just an uneducated guess.. could anyone confirm this, and even suggest what the best way of going about it is. Should i start again with 4.0.2, or is there an easier way. Thanks again Al -- 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/71616f96-91fa-490e-b0f8-200e185b790f%40googlegroups.com.
Re: [qubes-users] Re: whonix tor browser customization
Matthew Finkel: > On Fri, Aug 23, 2019 at 7:59 PM wrote: >> panina: >>> On 7/31/19 5:35 PM, 'awokd' via qubes-users wrote: panina: > Hello. > > > I've been looking for how to fix some bad default settings in the whonix > tor browser. Namely, they removed NoScript from the toolbar, so that the > NoScript cannot be used as intended. > > Since it's not adviced (and not easily possible) to start the browser in > the template, I have to do this manually each time I start a whonix dvm. > Since this is cumbersome, I'm not using the NoScript plugin as intended. > > Does anyone know how to get this plugin into the toolbar for each dvm? I > realize that this is a Whonix issue, but all of the affected users are > on this list... You might be able to hack it like in 14- https://forums.whonix.org/t/how-do-i-customise-tor-browser-in-a-whonix-templatebased-dvm-in-whonix-14/5580/27. Note it may compromise anonymity by making your browser unique or at least less generic. >>> >>> Can't seem to get this working. I get confused by how the dvm's work, >>> and am not succeeding in starting any applications in the dvm template. >>> >>> >>> >>> On 8/9/19 9:05 AM, Patrick Schleizer wrote: > panina: > Namely, they removed NoScript from the toolbar, so that the > NoScript cannot be used as intended. We did not. Decision by upstream, The Tor Project. >>> https://forums.whonix.org/t/workstation-15-dropped-both-noscript-and-https/7733 >>> >>> Thanks, duly noted. Is there any chance to get them to add a setting for >>> this? Or re-think their decision? >>> >>> <3 >>> /panina >>> >> >>> Thanks, duly noted. Is there any chance to get them to add a setting for >>> this? Or re-think their decision? >> >> Please see: >> https://trac.torproject.org/projects/tor/ticket/30600 >> https://trac.torproject.org/projects/tor/ticket/30570 >> >> TL;DR The TBB developers pushed out some half-baked changes that >> compromise UX, are hostile to the idea of reverting those changes, and, >> three months later, apparently have zero interest in fully baking those >> changes. >> >> ¯\_(ツ)_/¯ > > That's a little harsh, isn't it? Saying there is no interest is > ignoring the fact that Tor Browser is maintained by a team of 10 > people for four different operating systems. Tor Browser is useless > (and actively harmful) if users are confused about which settings they > should change (due to careful design choices) and which settings they > shouldn't change. The Noscript and https-everywhere buttons on the > toolbar allowed people to tweak the settings easily, and this was not > something a normal user should do. If someone really needs to change > these settings, then they can go through a more complicated procedure > for accomplishing that. > > The team will finish implementing this, but (in particular) the > highest priority task right now is migrating the Tor Browser patches > and build system from Firefox 60esr to 68esr within the next few > weeks. > We're getting off-topic here, and I also don't wish to bring Tor Project politics into this list. That said: > That's a little harsh, isn't it? Saying there is no interest is > ignoring the fact that Tor Browser is maintained by a team of 10 > people for four different operating systems. No, it is frankly not harsh enough. Available developer time to finish implementing the half-baked changes is irrelevant. The correct way to do this would have been to wait until the changes were fully baked (i.e. until Proposal 101 was fully implemented, including per-site security settings), rather than half-assing them, pushing them out the door, then three months later thinking about maybe getting around to finishing up sometime in the future after higher priority tasks are done. > [...] this was not something a normal user should do. Well, I don't know how things *should* be, but an awful lot of TBB users have found these controls essential. I personally have had to explain to multiple non-technical TBB users in meatspace how to re-access the NoScript widget, which they all have found essential to using TBB. Regardless of available developer time and priorities, breaking a feature many users find essential without any warning, not giving any explanation of how to access that essential feature, and then forgetting about un-breaking that feature for months is simply piss-poor project management. -- 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/27bec4ce-662a-fa69-3902-7dc1f5016cc4%40riseup.net.
Re: [qubes-users] Re: whonix tor browser customization
panina: Well, personally the Tor browser is largely useless with default settings. I'm actively avoiding recommending Tor Browser to non-technical users right now since it breaks webpages. Almost a majority of them. Afraid I'm not following. The default settings are the most compatible. Making it easier for non-technical users to play around with them would only result in more broken websites. It's gone from being a superb way of hiding your traffic, usable by everyday surfers behind government firewalls. The privacy-aware crowd has been accused of being elitist, and this move is in line with that accusation. Making TB safer/easier for non-technical users seems the opposite of elitist to me? But the politics of TB isn't what this mailing list is for. True; I think security discussions are OK though. (?) Since I can't seem to hack the whole template/DVM scheme, I think I'll just have to go back to my own tweaked firefox setup. I guess I can put that behind a whonix gateway, should go some way towards being anonymized... Personally, I run the default Whonix templates and manually set the Security Level on Safest every time I start TB in a DVM. If a site needs a lower level, I'll open it in a separate DVM instance. It is a pain, but I didn't want to chance a customized prefs.js etc. making my browser unique so I hadn't investigated further since Whonix 14. -- 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/96545a72-5add-341e-17bd-777c5def50f7%40danwin1210.me.
Re: [qubes-users] Re:
canmasallah...@gmail.com: Different email same person. Now when I go to boot it up to do as you said it keep taking me to my other boot,linux mint, I try to repair it with boot qubes troubleshooting and still same result. What can I do now? Mount the Qubes LVM partition from within Mint and extract your data that way. If you need steps on how to go about it, search this mailing list- think I might have described or linked them here before. -- 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/5e7cfced-3c21-27db-4e8a-360a6fbdf786%40danwin1210.me.
Re: [qubes-users] Re: whonix tor browser customization
On 8/23/19 11:12 PM, Matthew Finkel wrote: > On Fri, Aug 23, 2019 at 7:59 PM wrote: >> panina: >>> On 7/31/19 5:35 PM, 'awokd' via qubes-users wrote: panina: > Hello. > > > I've been looking for how to fix some bad default settings in the whonix > tor browser. Namely, they removed NoScript from the toolbar, so that the > NoScript cannot be used as intended. > > Since it's not adviced (and not easily possible) to start the browser in > the template, I have to do this manually each time I start a whonix dvm. > Since this is cumbersome, I'm not using the NoScript plugin as intended. > > Does anyone know how to get this plugin into the toolbar for each dvm? I > realize that this is a Whonix issue, but all of the affected users are > on this list... You might be able to hack it like in 14- https://forums.whonix.org/t/how-do-i-customise-tor-browser-in-a-whonix-templatebased-dvm-in-whonix-14/5580/27. Note it may compromise anonymity by making your browser unique or at least less generic. >>> >>> Can't seem to get this working. I get confused by how the dvm's work, >>> and am not succeeding in starting any applications in the dvm template. >>> >>> >>> >>> On 8/9/19 9:05 AM, Patrick Schleizer wrote: > panina: > Namely, they removed NoScript from the toolbar, so that the > NoScript cannot be used as intended. We did not. Decision by upstream, The Tor Project. >>> https://forums.whonix.org/t/workstation-15-dropped-both-noscript-and-https/7733 >>> >>> Thanks, duly noted. Is there any chance to get them to add a setting for >>> this? Or re-think their decision? >>> >>> <3 >>> /panina >>> >> >>> Thanks, duly noted. Is there any chance to get them to add a setting for >>> this? Or re-think their decision? >> >> Please see: >> https://trac.torproject.org/projects/tor/ticket/30600 >> https://trac.torproject.org/projects/tor/ticket/30570 >> >> TL;DR The TBB developers pushed out some half-baked changes that >> compromise UX, are hostile to the idea of reverting those changes, and, >> three months later, apparently have zero interest in fully baking those >> changes. >> >> ¯\_(ツ)_/¯ > > That's a little harsh, isn't it? Saying there is no interest is > ignoring the fact that Tor Browser is maintained by a team of 10 > people for four different operating systems. Tor Browser is useless > (and actively harmful) if users are confused about which settings they > should change (due to careful design choices) and which settings they > shouldn't change. The Noscript and https-everywhere buttons on the > toolbar allowed people to tweak the settings easily, and this was not > something a normal user should do. If someone really needs to change > these settings, then they can go through a more complicated procedure > for accomplishing that. > > The team will finish implementing this, but (in particular) the > highest priority task right now is migrating the Tor Browser patches > and build system from Firefox 60esr to 68esr within the next few > weeks. > Well, personally the Tor browser is largely useless with default settings. I'm actively avoiding recommending Tor Browser to non-technical users right now since it breaks webpages. Almost a majority of them. It's gone from being a superb way of hiding your traffic, usable by everyday surfers behind government firewalls. The privacy-aware crowd has been accused of being elitist, and this move is in line with that accusation. But the politics of TB isn't what this mailing list is for. Since I can't seem to hack the whole template/DVM scheme, I think I'll just have to go back to my own tweaked firefox setup. I guess I can put that behind a whonix gateway, should go some way towards being anonymized... wish a better day for y'all /panina -- 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/fda5fa35-8090-ecf5-2c73-269ef63d79d1%40nonbinary.me. signature.asc Description: OpenPGP digital signature
Re: [qubes-users] Done with Qubes
O K: Thanks for all the help but I've been trying to figure out how to get Qubes running for months and I've decided it's just a giant waste of my time because every time I get one bug fixed, two more show up to take it's place. I think it's a brilliant idea but it needs a lot of work and streamlining before it's ready for public use. It's a shame because my privacy and anonymity online are a matter of my personal safety and it would be nice to have a secure OS. TAILS is not a fully usable system either. I will have to install Ubuntu. Good luck, everyone. Hi, Qubes definitely has a learning curve, but i think it's worth it (and i'm definitely no linux expert). But if you don't want to use qubes, one thing you can do for better security and privacy is install debian/ubuntu and use non-qubes whonix (you can use virtualbox, which is pretty easy to use). You can have multiple whonix workstations, and you can create other VMs like debian as well to compartmentalize your workflows. A solution like this is more insecure than qubes, but definitely less insecure than just using bare metal debian/ubuntu for everything. You still get the benefits of virtualization and compartmentalization, but without the extra security features of qubes (i'd recommend not using the host os for anything directly, and doing everything in VMs). -- 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/77318e98-5a5b-db3a-6b01-f3ff02187db3%40danwin1210.me.
[qubes-users] Re:
This is the link I use to troubleshoot https://deniszanin.com/bad-grub-fixing-qubes-boot-missing-on-uefi/ -- 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/5ebe359b-def6-4159-9c9c-59ad95b7195d%40googlegroups.com.
[qubes-users] Re:
Different email same person. Now when I go to boot it up to do as you said it keep taking me to my other boot,linux mint, I try to repair it with boot qubes troubleshooting and still same result. What can I do now? -- 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/5b45fc90-246a-4b69-b50d-58a27c9a93e2%40googlegroups.com.
Re: [qubes-users] Re: whonix tor browser customization
On Fri, Aug 23, 2019 at 7:59 PM wrote: > panina: > > On 7/31/19 5:35 PM, 'awokd' via qubes-users wrote: > >> panina: > >>> Hello. > >>> > >>> > >>> I've been looking for how to fix some bad default settings in the whonix > >>> tor browser. Namely, they removed NoScript from the toolbar, so that the > >>> NoScript cannot be used as intended. > >>> > >>> Since it's not adviced (and not easily possible) to start the browser in > >>> the template, I have to do this manually each time I start a whonix dvm. > >>> Since this is cumbersome, I'm not using the NoScript plugin as intended. > >>> > >>> Does anyone know how to get this plugin into the toolbar for each dvm? I > >>> realize that this is a Whonix issue, but all of the affected users are > >>> on this list... > >> > >> You might be able to hack it like in 14- > >> https://forums.whonix.org/t/how-do-i-customise-tor-browser-in-a-whonix-templatebased-dvm-in-whonix-14/5580/27. > >> Note it may compromise anonymity by making your browser unique or at > >> least less generic. > >> > > > > Can't seem to get this working. I get confused by how the dvm's work, > > and am not succeeding in starting any applications in the dvm template. > > > > > > > > On 8/9/19 9:05 AM, Patrick Schleizer wrote: > >>> panina: > >>> Namely, they removed NoScript from the toolbar, so that the > >>> NoScript cannot be used as intended. > >> > >> > >> We did not. Decision by upstream, The Tor Project. > >> > >> > > https://forums.whonix.org/t/workstation-15-dropped-both-noscript-and-https/7733 > > > > Thanks, duly noted. Is there any chance to get them to add a setting for > > this? Or re-think their decision? > > > > <3 > > /panina > > > > > Thanks, duly noted. Is there any chance to get them to add a setting for > > this? Or re-think their decision? > > Please see: > https://trac.torproject.org/projects/tor/ticket/30600 > https://trac.torproject.org/projects/tor/ticket/30570 > > TL;DR The TBB developers pushed out some half-baked changes that > compromise UX, are hostile to the idea of reverting those changes, and, > three months later, apparently have zero interest in fully baking those > changes. > > ¯\_(ツ)_/¯ That's a little harsh, isn't it? Saying there is no interest is ignoring the fact that Tor Browser is maintained by a team of 10 people for four different operating systems. Tor Browser is useless (and actively harmful) if users are confused about which settings they should change (due to careful design choices) and which settings they shouldn't change. The Noscript and https-everywhere buttons on the toolbar allowed people to tweak the settings easily, and this was not something a normal user should do. If someone really needs to change these settings, then they can go through a more complicated procedure for accomplishing that. The team will finish implementing this, but (in particular) the highest priority task right now is migrating the Tor Browser patches and build system from Firefox 60esr to 68esr within the next few weeks. -- 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/CAGF8hsss10Ugap-brrFWVjh0Gmvtv5%3D1%3Da1PWD%2BdagzBrOdwiQ%40mail.gmail.com.
Re: [qubes-users] Re: whonix tor browser customization
panina: > > > On 7/31/19 5:35 PM, 'awokd' via qubes-users wrote: >> panina: >>> Hello. >>> >>> >>> I've been looking for how to fix some bad default settings in the whonix >>> tor browser. Namely, they removed NoScript from the toolbar, so that the >>> NoScript cannot be used as intended. >>> >>> Since it's not adviced (and not easily possible) to start the browser in >>> the template, I have to do this manually each time I start a whonix dvm. >>> Since this is cumbersome, I'm not using the NoScript plugin as intended. >>> >>> Does anyone know how to get this plugin into the toolbar for each dvm? I >>> realize that this is a Whonix issue, but all of the affected users are >>> on this list... >> >> You might be able to hack it like in 14- >> https://forums.whonix.org/t/how-do-i-customise-tor-browser-in-a-whonix-templatebased-dvm-in-whonix-14/5580/27. >> Note it may compromise anonymity by making your browser unique or at >> least less generic. >> > > Can't seem to get this working. I get confused by how the dvm's work, > and am not succeeding in starting any applications in the dvm template. > > > > On 8/9/19 9:05 AM, Patrick Schleizer wrote: >>> panina: >>> Namely, they removed NoScript from the toolbar, so that the >>> NoScript cannot be used as intended. >> >> >> We did not. Decision by upstream, The Tor Project. >> >> > https://forums.whonix.org/t/workstation-15-dropped-both-noscript-and-https/7733 > > Thanks, duly noted. Is there any chance to get them to add a setting for > this? Or re-think their decision? > > <3 > /panina > > Thanks, duly noted. Is there any chance to get them to add a setting for > this? Or re-think their decision? Please see: https://trac.torproject.org/projects/tor/ticket/30600 https://trac.torproject.org/projects/tor/ticket/30570 TL;DR The TBB developers pushed out some half-baked changes that compromise UX, are hostile to the idea of reverting those changes, and, three months later, apparently have zero interest in fully baking those changes. ¯\_(ツ)_/¯ -- 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/ef7db2fe-f12d-ad36-7b54-5339deb4c902%40riseup.net.
Re: [qubes-users] Re: new Qubes install shows dom0 kernel: ACPI Exception: AE_NOT_FOUND, Evaluating _PRS (20170728/pci_link-176)
Bush Al: The system is not freezing on resume as i thought (because it did not respond to ctl-alt-delete) but was sitting at the login prompt. Once logging in blind i can power down the system via the keyboard. However the display does not get reset by the resume and stays at "no signal". This happens on the 9600K's Intel integrated graphics attached to a display via displayport or hdmi. There dont seem to be any relevant errors in the logs. For display issues, also check /var/log/Xorg.0.log. Don't have a precise fix (hopefully someone does!), but if your display goes to sleep mode from the screensaver versus a suspend, does it wake normally? Might help narrow it down. Could also try DVI if available. -- 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/34980f0b-e743-4dd8-bd7d-0f83d6653e5f%40danwin1210.me.
[qubes-users] Re: Done with Qubes
> > Thanks for all the help but I've been trying to figure out how to get > Qubes running for months and I've decided it's just a giant waste of my > time because every time I get one bug fixed, two more show up to take it's > place. I think it's a brilliant idea but it needs a lot of work and > streamlining before it's ready for public use. It's a shame because my > privacy and anonymity online are a matter of my personal safety and it > would be nice to have a secure OS. TAILS is not a fully usable system > either. I will have to install Ubuntu. Good luck, everyone. > I suggest you to keep trying. I am using Qubes since 3.2. I spent many months to know it. Today, if there is any bug, It does not bothers me. I have specialized templates, the -srv runs my docker services, the -data keeps all my data, the -app runs my personal, the -wks runs my work and -sec runs banking and crypto things. Bind-dirs keep my data servers isolated. All templates and windows - with sound but I do not like games - runs very fast using SSD with my old DDR3 AMD motherboard. It has auto initialization procedure. I keep my configuration files, installed programs list and data saved with timeshift. Easy and fast to reinstall. There is no chance I return to traditional linux anymore. -- 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/860a19bb-a84d-4e2b-813a-82d55ef6100f%40googlegroups.com.
[qubes-users] ~/.gnupg/gpg.conf not existing in debian 9 and 10 by default?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 hi, I tried to set up gpg in my Vault AppVM based on debian 9 and 10, and learned that the ~/.gnupg/gpg.conf is returning an empty file. It is the case for the debian 10 as well. In whonix-15 AppVMs I get the file ~/.gnupg/gpg.conf full of settings by default. I would like to follow the guide here https://riseup.net/en/gpg-best-practices , but the ~/.gnupg/gpg.conf is not existing by default, and so I cant pass the needed settings. I would like to ask where the gpg in debian is getting the settings from, and if I create the file ~/.gnupg/gpg.conf and put in my settings, if the gpg will behave based on the gpg.conf settings same as it does in whonix-15. Thank you. -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEExlmPb5HoPUTt+CQT44JZDAWK6UwFAl1fw+NfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEM2 NTk4RjZGOTFFODNENDRFREY4MjQxM0UzODI1OTBDMDU4QUU5NEMACgkQ44JZDAWK 6Uw9Ug/+PYiJ7arxzBG4MTZDM3DRn3rOmv94T5pxCp4Yzf87rtx43A5+ihlDXIp0 FBgFwbMHIZs01YI1U/gphAD1BKizFqAu0H0Y24uOcChGBizYt7zeDPt0srE21jZ1 eSNUp7rTHKFaw6NCq5OZEH8aKuNU7yOTDGmIYsLqmTlIzzL6P6L6O9XJX/cEyBV0 H7cSHaIDExPwQnJVsF4CKuSdsIqcx1udsxdX3cYVJ5FDl1obu02S8xhteadtVnDo NACCF4nZJGBJvOgPMASsYRTgWmYeZKGi3a+DEipq7K44I8nRQEt5vE7oUL5KPdg0 YMAPFzyB2Bw53Pivy9HOEePwkDzkPBnfH5tRt6UQRMJhsj1OYOmK9TqsZ0xbscd3 TrVzrzsBYjSelUZupUVh6s62TJSYkWlUn1fm2P+2tIZZ5rDtR0dLCZ1280wREA/H Bwbm9og5zOXBmCtgRiO78tV4JXzjEgjIkze4g/JE1H8ef1iU8cbpTz0jQCyCkAZI xf85XYwxpCAydEvnVJrNoipkL9TOAEL74sbnt/ot1fJLJ4pJiAgupwXVijyxjQM9 9L792MspFsdFdtgsNqV1FSAztc/jOsxjcVx//l6vQ5KwD3rc6ow2tVO2pcZ8uoCS 93lK3Xsflg82tZup+hDcm5Js1L2ormkEL3CQvrWF0wjhP1I98pw= =gjH/ -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/5aea2b51-6bb5-dfc4-197e-2d285b5cc0cc%40cock.li. 0xC1F4E83AF470A4ED.asc Description: application/pgp-keys
[qubes-users] Re: new Qubes install shows dom0 kernel: ACPI Exception: AE_NOT_FOUND, Evaluating _PRS (20170728/pci_link-176)
Thanks awokd for that. I now understand what is happening a bit more, but still dont have a resolution. I did make the dom0 kernel: ACPI Exception: AE_NOT_FOUND go away with a BIOS update. The system is not freezing on resume as i thought (because it did not respond to ctl-alt-delete) but was sitting at the login prompt. Once logging in blind i can power down the system via the keyboard. However the display does not get reset by the resume and stays at "no signal". This happens on the 9600K's Intel integrated graphics attached to a display via displayport or hdmi. There dont seem to be any relevant errors in the logs. Thanks again for your help, any tips gratefully accepted. Al -- 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/5e44b252-09f2-4ba9-9655-6bde9b3366e5%40googlegroups.com.
Re: [qubes-users] Re: On new installs, is exotic procedure still needed to cure debian apt bug or can we simply update/apt-upgrade from deb template?
American Qubist 001: > > > On Sunday, August 18, 2019 at 10:39:38 AM UTC-7, American Qubist 001 wrote: >> >> will make sure to use the lhe latest, but I thought 4.02 was still in >> beta. >> Also, the instructions in the QSB are much more complex than simply >> updating through the gui.Why do you think a regular update would work when >> the QSB or Qubes documentation advises a much more complex, completely >> different proceure? >> >> Somethhing is not right here. It is inconsisitent. If all you needto do is >> a regulsr simple update, the documentation should reflect thatand not send >> users through a much more elaboraate templace replacement process. >> > > ALSO the QSB says that the bug is actually inthe update process of apt > itself, so it stands to reason that if there has been a malicious code > injection, merely updating will not suffice. > > So, are we sure we are on the saame page here?? > Can't tell if you're replying to my message. Anyways, believe the documentation & QSB covers how to safely replace templates that may be compromised. Since you have known good templates in the 4.01 installer, additional steps aren't necessary. Also, the apt fix in Qubes Updater was added after those were written. Might not hurt to submit an update to the documentation. -- 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/97546dcb-d08e-8239-f254-d477e70ae7fa%40danwin1210.me.
Re: [qubes-users] SYS-USB errors during install, Any ideas what these results mean?
O K: > > > [image: IMG_6694.jpg] > Top part of image are the errors I got on installation. The last two are > what I get when I type the commands in the last line of the first image > into dom0 terminal. I think sys-usb wasn't created so the system is > basically unusable. First burnt iso onto dvd, got the error. Then used > Rufus to create bootable usb, got the error. I installed Qubes on this > same machine before and didn't get the error so it's not the hardware. > Sha-256, master key/release key/verify iso process was fine, no problems. > I have no idea what it could be. > See paragraph on strictreset https://www.qubes-os.org/faq/#i-created-a-usbvm-and-assigned-usb-controllers-to-it-now-the-usbvm-wont-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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/5b81e59c-f71d-fb86-73b7-2ffbc74c2f26%40danwin1210.me.
Re: [qubes-users] Wifi connection fails from AppVM am I supposed to connect via ysy-net?
American Qubist 001: > Never had this issue on open wifi but with my new wifi router Ubuntu > laptops and Android tablet connect, Qubes does not. I get the passsword > text box type in password and on Qubes only, no wifi connection. Does not > make sense to me. > An easy thing to try is to swap sys-net's template from Fedora to Debian. Also, make sure you have the appropriate wifi firmware package installed in the template (but if it worked on open wifi you probably do). -- 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/af343d7a-9978-9cf1-a999-737d73feda4f%40danwin1210.me.
Re: [qubes-users] new Qubes install shows dom0 kernel: ACPI Exception: AE_NOT_FOUND, Evaluating _PRS (20170728/pci_link-176)
Bush Al: dom0 kernel: ACPI Exception: AE_NOT_FOUND, Evaluating _PRS (20170728/pci_link-176) Possibly related to your suspend issue, but ignore for now. [FAILED] Failed to start Load Kernal Modules Cosmetic; ignore. Secondly (and possibly connected), if I suspend the machine it seems to do that happily, but on resume the power and fans etc come on but no display and i suspect it is frozen as ctl-alt-delete has no effect. I looked though journalctl, but saw nothing in red except How do i go about troubleshooting this? Try shutting down all VMs (sys-usb and sys-net in particular), then suspending and resuming. If that works, see https://www.qubes-os.org/doc/wireless-troubleshooting and/or search this mailing list for your type of PC + "suspend". Is there a description of which logs are important at which stage of the boot process under 4.0? /var/log/xen/console/hypervisor.log covers Xen itself. Journalctl in dom0 is also useful for troubleshooting system issues. -- 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/e7be32b6-f097-f488-1e19-4fde8a1eb73d%40danwin1210.me.
