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] (**) |-->S
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
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.
Maki
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 ex
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, th
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
stream
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-us
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
"
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 th
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.
>>>
>>>
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
h
>
> 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
-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
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
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
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 o
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 sw
17 matches
Mail list logo
