Re: [qubes-users] How do I get Started?

2019-12-03 Thread Qubes User 
Thank you for your help. 

On Tuesday, December 3, 2019 at 12:10:11 PM UTC-8, Claudia wrote:
>
> Qubes User: 
> > I just installed Qubes on a new laptop. I'm trying to do some basic 
> things 
> > not listed on https://www.qubes-os.org/getting-started/ 
> > 
> > 1. How do I get connected to my wi-fi? 
>
> The networkmanager applet should appear in the task tray (next to the 
> clock). Just click on that and select a network. Make sure sys-net is 
> running. Can you manually launch networkmanager in sys-net? Do you see 
> your network card in iwconfig, ifconfig, lsusb, lspci, in sys-net? 
>
> When I click the applet, I see: 
Ethernet Network
device not managed
VPN Connections >
I don't see my WiFi networks. When I launch network manager in sys-net, I 
tried
to manually input the information for my WiFi (with the SSID and 
WPA2/Personal), 
but it doesn't connect after. 

When I run "lsusb" in the dom0 terminal, I get:
Realtek Semiconductor Corp
VIA Labs, Inc.
Linux Foundation 3.0 root hub
blank
Chicony Electronics Co., Ltd
VIA Lbs, Inc.
Logitech, Inc. Unifying Receiver (for my usb mouse)
Terminus Technology Inc.
VIA Labs, Inc.
Intel Corp.
Linux Foundation 2.0 root hub
None of these are my network cards, right? 
 

> > 2. How do I use an external display with HDMI? (just plugging it in 
> doesn't 
> > work for me) 
>
> What do you see when you plug it in? "No signal"? Blank screen? 
>
> You might have to do some configuration in XFCE. Look under system tools 
> for monitor/screen settings. Otherwise, you could try installing KDE. 
>
> https://www.qubes-os.org/doc/kde/ 
>
> Note that a lot of hardware features don't always work in Qubes. HDMI is 
> not tested very often by Qubes users, so I don't know if HDMI usually 
> works or not. 
>
> Does it work when running a Fedora 25 live CD? Did you have it working 
> on this machine on any other operating systems? 
>
When I plug in my HDMI, nothing happens. On Windows, the external display
works when I plug it in. I can try running Fedora on a live usb to see what 
happens. 

>
> > 3. How do I reduce the lag on my USB mouse? 
>
> I'm afraid I don't know much about this. Are you using dom0 or sys-usb? 
> Is anything else laggy? Does the touchpad (if any) work alright? 
>
> You can try temporarily disabling sys-usb so devices are attached to 
> dom0. See if it works any better that way. 
> https://www.qubes-os.org/doc/usb-qubes/#removing-a-usb-qube

I don't think I have usb-qubes enabled. I wasn't able to enable them after 
installation,
maybe because I have a USB keyboard. 
However, my touchpad/trackpad doesn't work. What can I do about that?

>
>
> - 
> This free account was provided by VFEmail.net - report spam to 
> ab...@vfemail.net  
>   
> ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of 
> the NSA's hands! 
> $24.95 ONETIME Lifetime accounts with Privacy Features!   
> 15GB disk! No bandwidth quotas! 
> Commercial and Bulk Mail Options!   
>

-- 
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/38321cc0-496a-4811-9cf7-46249e16ee4b%40googlegroups.com.

[qubes-users] Help sending multiple files using qrexec

2019-12-03 Thread prago 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

I am trying to send mutliple files using qrexec by catting the files using the
following scripts:

Script one on the client:

echo "$#"
while [ $1 ]; do
    echo $(wc -l $1)
    cat $1
    shift
done


Script two on the server:

read NUMFILES
READFILES=0
while [ $READFILES -lt $NUMFILES ]; do
    read CATFILESIZE CATFILENAME
    head -n $CATFILESIZE > "$CATFILENAME"
    ((READFILES++))
done


This successfully sends the first file, but not the second, can anyone help
with this or should I be using qvm-copy?

Thanks for reading
-BEGIN PGP SIGNATURE-

iIgEARMKADAWIQRFNnsoPo7HH0XEMXc88cBGMbAIWAUCXecNwhIccHJhZ29AdHV0
YW5vdGEuZGUACgkQPPHARjGwCFiw0gD/TPKyOcTLN94aJYJd8oaf+4ciHy1jKZ9W
XBlIif0fJHMA/jy3LS32Ed21PcbACGz0RZIIGYGFoSptsyLQM5SH9fNd
=F4IQ
-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/LvDZBfL--3-1%40tutanota.de.

Re: [qubes-users] Fedora 29 has reached EOL

2019-12-03 Thread Claudia 

Frédéric Pierret (fepitre):

Before end of the month we hope to have a testing ISO for dev purpose.
Currently we are on upgrading Fedora installer which have drastically
changed the way of creating ISO.


Awesome. I'll keep my eye out for it. Thanks.


-
This free account was provided by VFEmail.net - report spam to ab...@vfemail.net

ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the 
NSA's hands!
$24.95 ONETIME Lifetime accounts with Privacy Features!  
15GB disk! No bandwidth quotas!
Commercial and Bulk Mail Options!  


--
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/81961b20-3119-8449-f5cc-19ba7eba4ecc%40vfemail.net.

Re: [qubes-users] How do I get Started?

2019-12-03 Thread Claudia 

Qubes User:

I just installed Qubes on a new laptop. I'm trying to do some basic things
not listed on https://www.qubes-os.org/getting-started/

1. How do I get connected to my wi-fi?


The networkmanager applet should appear in the task tray (next to the 
clock). Just click on that and select a network. Make sure sys-net is 
running. Can you manually launch networkmanager in sys-net? Do you see 
your network card in iwconfig, ifconfig, lsusb, lspci, in sys-net?



2. How do I use an external display with HDMI? (just plugging it in doesn't
work for me)


What do you see when you plug it in? "No signal"? Blank screen?

You might have to do some configuration in XFCE. Look under system tools 
for monitor/screen settings. Otherwise, you could try installing KDE.


https://www.qubes-os.org/doc/kde/

Note that a lot of hardware features don't always work in Qubes. HDMI is 
not tested very often by Qubes users, so I don't know if HDMI usually 
works or not.


Does it work when running a Fedora 25 live CD? Did you have it working 
on this machine on any other operating systems?



3. How do I reduce the lag on my USB mouse?


I'm afraid I don't know much about this. Are you using dom0 or sys-usb? 
Is anything else laggy? Does the touchpad (if any) work alright?


You can try temporarily disabling sys-usb so devices are attached to 
dom0. See if it works any better that way. 
https://www.qubes-os.org/doc/usb-qubes/#removing-a-usb-qube


-
This free account was provided by VFEmail.net - report spam to ab...@vfemail.net

ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the 
NSA's hands!
$24.95 ONETIME Lifetime accounts with Privacy Features!  
15GB disk! No bandwidth quotas!
Commercial and Bulk Mail Options!  


--
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/dec7d491-1378-5b0b-98c8-a3630daeba86%40vfemail.net.

Re: [qubes-users] [Qubes OS 4.0.1 / Debian 10] 403 Forbidden IP sudo apt update

2019-12-03 Thread Charles Peters 
On Tue, Dec 3, 2019 at 5:07 AM  wrote:

> Hello,
> I've been trying to install QGIS via their repositories for a few days
> now, but I have a problem when I do sudo apt update:
>
> user@debian-10:~$ sudo apt update
> ...
> Achieved: 4 https://cdn-aws.deb.debian.org/debian-security buster/updates
> InRelease
> Reading package lists Fact
> E: Unable to retrieve https://qgis.org/debian/dists/buster/InRelease 403
> Forbidden[IP : 127.0.0.0.1 8082]
> E: The deposit https://qgis.org/debian buster InRelease is not signed.
> N: Updates from such a repository cannot be done securely, and are
> therefore disabled by default.
> N: See the apt-secure(8) manual pages for repository creation and user
> configuration details.
> user@debian-10:~$
>
> It seems that my IP address is blacklisted from the QGIS repository.
>

It looks like you haven't added the repository key.
 https://qgis.org/en/site/forusers/alldownloads.html#debian-ubuntu

Did you add the repository gpg key?
Note: If you follow the commands listed on the web page in a Template VM,
the wget command will fail.
curl -x 127.0.0.1:8082 https://qgis.org/downloads/qgis-2019.gpg.key >
qgis-2019.gpg.key

-- 
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/CAMet1z499%3D_0efHsAqG7ggb2zagvwZWsjZTtQd-u16O8Qi4mhw%40mail.gmail.com.

[qubes-users] Re: Help regarding IOMMU and HVM

2019-12-03 Thread Ana Z 
Dana utorak, 3. prosinca 2019. u 18:15:02 UTC, korisnik qubes123 napisao je:
>
> Maybe if you post the content of /var/log/libvirt/libxl/libxl-driver.log file 
> also, we can see what the problem is. Otherwise the logs seem OK for me.
> If you installed a std R4.0.1 and let the setup configure the base qubes, 
> then sys-net should already be a HVM with all your Net cards passed through 
> to this HVM.
> For USB devices, when passed to a HVM, it could require, that you set 
> "strict reset" in "Devices" tab for the USB devices of that qubes, 
> otherwise it will not boot. Because of this, I recommend to try to start a 
> hvm with only Net devices passed through to it, or even without any passed 
> devices to narrow down the problem to HVMs in general or passthrough issues.
> One tip: if the HVMs problem still persists, change the Virt mode to PV 
> temporarily for the sys-net (make sure, that a Net card is passed to it), 
> and if networking is OK, then update dom0 to the latest version.
> Then switch it back to HVM and try to boot.  PV mode is not recommended 
> (larger attack surface) on long term, but R4.0.1 is and old version...
>
>
Hi.

I sure can! I uploaded the libxl-driver.log as well. 

As of your second part of the message, I didn't mention that after doing 
all the steps suggested in linked "Bug in libxenlight" topic I encountered 
that all assigned HVMs (bullet 8) wouldn't load (such as sys-usb and 
sys-net) and dom0 was updated before that change (bullet 7), and yes, now 
that I think of it, it gave me a different error and suggestion that I read 
the /var/log/libvirt/libxl/libxl-driver.log you asked for! So I hope you 
could tell me from it what's the matter. I then, changed back all the VMs 
to PV mode and I was setting up new templates, even got my USB WIFI dongle 
to work, but as you mentioned it's not as secure as HVM is so I really want 
to make it 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/a3c4e8c6-c46d-4715-b231-bf091b212cdf%40googlegroups.com.
2019-12-02 12:34:30.798+: libxl: libxl.c:1853:libxl_console_get_tty: unable 
to read console tty path `/local/domain/1/console/tty': Resource temporarily 
unavailable
2019-12-02 12:36:10.284+: libxl: libxl.c:1853:libxl_console_get_tty: unable 
to read console tty path `/local/domain/2/console/tty': Resource temporarily 
unavailable
2019-12-02 12:39:29.948+: libxl: libxl.c:1853:libxl_console_get_tty: unable 
to read console tty path `/local/domain/4/console/tty': Resource temporarily 
unavailable
2019-12-02 12:47:27.881+: libxl: libxl_pci.c:1176:libxl__device_pci_reset: 
The kernel doesn't support reset from sysfs for PCI device :00:13.0
2019-12-02 12:47:27.911+: libxl: libxl_pci.c:1176:libxl__device_pci_reset: 
The kernel doesn't support reset from sysfs for PCI device :00:12.0
2019-12-02 12:47:27.938+: libxl: libxl_pci.c:1176:libxl__device_pci_reset: 
The kernel doesn't support reset from sysfs for PCI device :00:10.0
2019-12-02 12:47:27.940+: libxl: libxl_pci.c:1176:libxl__device_pci_reset: 
The kernel doesn't support reset from sysfs for PCI device :00:10.1
2019-12-02 13:09:07.331+: libxl: libxl_linux.c:155:libxl__loopdev_cleanup: 
unable to release device /dev/loop1: No such device or address
2019-12-02 13:10:30.867+: libxl: libxl_pci.c:1199:libxl__device_pci_reset: 
The kernel doesn't support reset from sysfs for PCI device :00:13.0
2019-12-02 13:10:30.922+: libxl: libxl_pci.c:1517:do_pci_remove: 
xc_physdev_unmap_pirq irq=18: Invalid argument
2019-12-02 13:10:30.922+: libxl: libxl_pci.c:1199:libxl__device_pci_reset: 
The kernel doesn't support reset from sysfs for PCI device :00:12.0
2019-12-02 13:10:30.934+: libxl: libxl_pci.c:1517:do_pci_remove: 
xc_physdev_unmap_pirq irq=17: Invalid argument
2019-12-02 13:10:30.971+: libxl: libxl_pci.c:1517:do_pci_remove: 
xc_physdev_unmap_pirq irq=18: Invalid argument
2019-12-02 13:10:30.971+: libxl: libxl_pci.c:1199:libxl__device_pci_reset: 
The kernel doesn't support reset from sysfs for PCI device :00:10.0
2019-12-02 13:10:30.979+: libxl: libxl_pci.c:1517:do_pci_remove: 
xc_physdev_unmap_pirq irq=17: Invalid argument
2019-12-02 13:10:30.979+: libxl: libxl_pci.c:1199:libxl__device_pci_reset: 
The kernel doesn't support reset from sysfs for PCI device :00:10.1
2019-12-02 13:10:38.678+: libxl: libxl_pci.c:1517:do_pci_remove: 
xc_physdev_unmap_pirq irq=83: Invalid argument
2019-12-02 13:10:38.678+: libxl: libxl_pci.c:1521:do_pci_remove: 
xc_domain_irq_permission irq=83: Operation not permitted
2019-12-02 13:11:24.859+: libxl: libxl_pci.c:1199:libxl__device_pci_reset: 
The kernel doesn't support reset from sysfs for PCI

[qubes-users] Re: Help regarding IOMMU and HVM

2019-12-03 Thread Ana Z 
Hi.

I sure can! I uploaded the libxl-driver.log as well. 

As of your second part of the message, I didn't mention that after doing 
all the steps suggested in linked "Bug in libxenlight" topic I encountered 
that all assigned HVMs (bullet 8) wouldn't load (such as sys-usb and 
sys-net) and dom0 was updated before that change (bullet 7), and yes, now 
that I think of it, it gave me a different error and suggestion that I read 
the /var/log/libvirt/libxl/libxl-driver.log you asked for! So I hope you 
could tell me from it what's the matter. I then, changed back all the VMs 
to PV mode and I was setting up new templates, even got my WIFI card to 
work, but as you mentioned it's not as secure as HVM is so I really want to 
make it work.

Dana utorak, 3. prosinca 2019. u 18:15:02 UTC, korisnik qubes123 napisao je:
>
> Maybe if you post the content of /var/log/libvirt/libxl/libxl-driver.log file 
> also, we can see what the problem is. Otherwise the logs seem OK for me.
> If you installed a std R4.0.1 and let the setup configure the base qubes, 
> then sys-net should already be a HVM with all your Net cards passed through 
> to this HVM.
> For USB devices, when passed to a HVM, it could require, that you set 
> "strict reset" in "Devices" tab for the USB devices of that qubes, 
> otherwise it will not boot. Because of this, I recommend to try to start a 
> hvm with only Net devices passed through to it, or even without any passed 
> devices to narrow down the problem to HVMs in general or passthrough issues.
> One tip: if the HVMs problem still persists, change the Virt mode to PV 
> temporarily for the sys-net (make sure, that a Net card is passed to it), 
> and if networking is OK, then update dom0 to the latest version.
> Then switch it back to HVM and try to boot.  PV mode is not recommended 
> (larger attack surface) on long term, but R4.0.1 is and old version...
>
>

-- 
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/2b705f67-ecf0-465d-9fa2-201ebac60854%40googlegroups.com.
2019-12-02 12:34:30.798+: libxl: libxl.c:1853:libxl_console_get_tty: unable 
to read console tty path `/local/domain/1/console/tty': Resource temporarily 
unavailable
2019-12-02 12:36:10.284+: libxl: libxl.c:1853:libxl_console_get_tty: unable 
to read console tty path `/local/domain/2/console/tty': Resource temporarily 
unavailable
2019-12-02 12:39:29.948+: libxl: libxl.c:1853:libxl_console_get_tty: unable 
to read console tty path `/local/domain/4/console/tty': Resource temporarily 
unavailable
2019-12-02 12:47:27.881+: libxl: libxl_pci.c:1176:libxl__device_pci_reset: 
The kernel doesn't support reset from sysfs for PCI device :00:13.0
2019-12-02 12:47:27.911+: libxl: libxl_pci.c:1176:libxl__device_pci_reset: 
The kernel doesn't support reset from sysfs for PCI device :00:12.0
2019-12-02 12:47:27.938+: libxl: libxl_pci.c:1176:libxl__device_pci_reset: 
The kernel doesn't support reset from sysfs for PCI device :00:10.0
2019-12-02 12:47:27.940+: libxl: libxl_pci.c:1176:libxl__device_pci_reset: 
The kernel doesn't support reset from sysfs for PCI device :00:10.1
2019-12-02 13:09:07.331+: libxl: libxl_linux.c:155:libxl__loopdev_cleanup: 
unable to release device /dev/loop1: No such device or address
2019-12-02 13:10:30.867+: libxl: libxl_pci.c:1199:libxl__device_pci_reset: 
The kernel doesn't support reset from sysfs for PCI device :00:13.0
2019-12-02 13:10:30.922+: libxl: libxl_pci.c:1517:do_pci_remove: 
xc_physdev_unmap_pirq irq=18: Invalid argument
2019-12-02 13:10:30.922+: libxl: libxl_pci.c:1199:libxl__device_pci_reset: 
The kernel doesn't support reset from sysfs for PCI device :00:12.0
2019-12-02 13:10:30.934+: libxl: libxl_pci.c:1517:do_pci_remove: 
xc_physdev_unmap_pirq irq=17: Invalid argument
2019-12-02 13:10:30.971+: libxl: libxl_pci.c:1517:do_pci_remove: 
xc_physdev_unmap_pirq irq=18: Invalid argument
2019-12-02 13:10:30.971+: libxl: libxl_pci.c:1199:libxl__device_pci_reset: 
The kernel doesn't support reset from sysfs for PCI device :00:10.0
2019-12-02 13:10:30.979+: libxl: libxl_pci.c:1517:do_pci_remove: 
xc_physdev_unmap_pirq irq=17: Invalid argument
2019-12-02 13:10:30.979+: libxl: libxl_pci.c:1199:libxl__device_pci_reset: 
The kernel doesn't support reset from sysfs for PCI device :00:10.1
2019-12-02 13:10:38.678+: libxl: libxl_pci.c:1517:do_pci_remove: 
xc_physdev_unmap_pirq irq=83: Invalid argument
2019-12-02 13:10:38.678+: libxl: libxl_pci.c:1521:do_pci_remove: 
xc_domain_irq_permission irq=83: Operation not permitted
2019-12-02 13:11:24.859+: libxl: libxl_pci.c:1199:libxl__device_pci_reset: 
The kernel doesn't support reset from sysfs for PCI device

[qubes-users] Re: Help regarding IOMMU and HVM

2019-12-03 Thread qubes123 
...correction: R4.0.1 is not old (this is the current released version), 
but the iso build is from January...

-- 
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/9dcbdf09-0e11-4065-ae58-af26b4086da0%40googlegroups.com.

[qubes-users] Re: Help regarding IOMMU and HVM

2019-12-03 Thread qubes123 
Maybe if you post the content of /var/log/libvirt/libxl/libxl-driver.log file 
also, we can see what the problem is. Otherwise the logs seem OK for me.
If you installed a std R4.0.1 and let the setup configure the base qubes, 
then sys-net should already be a HVM with all your Net cards passed through 
to this HVM.
For USB devices, when passed to a HVM, it could require, that you set 
"strict reset" in "Devices" tab for the USB devices of that qubes, 
otherwise it will not boot. Because of this, I recommend to try to start a 
hvm with only Net devices passed through to it, or even without any passed 
devices to narrow down the problem to HVMs in general or passthrough issues.
One tip: if the HVMs problem still persists, change the Virt mode to PV 
temporarily for the sys-net (make sure, that a Net card is passed to it), 
and if networking is OK, then update dom0 to the latest version.
Then switch it back to HVM and try to boot.  PV mode is not recommended 
(larger attack surface) on long term, but R4.0.1 is and old version...

-- 
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/f17635d6-dcc2-41be-be0f-218ecbe29881%40googlegroups.com.

[qubes-users] Help regarding IOMMU and HVM

2019-12-03 Thread Ana Z 
Hi. 

First of all, I want to mention that I'm not really experienced with Linux 
or Xen but I tried my best for the past 3 days to make my Qubes 
installation work. I need help with enabling hardware-assisted virtual 
machines. 

I was trying to install Qubes 4.0.1 but I ran into some issues. While 
installing, I was first greeted with "Missing features: IOMMU/VT-d/AMD-Vi, 
Interrupt Remapping. Without these feature, Qubes OS will not function 
normally.". I checked my BIOS and IOMMU was enabled (motherboard is ASUS 
A88XM-A), but my BIOS version was old. I updated the BIOS to the latest 
version and the error from the installation disappeared, but then, after 
the install, on setup I got another message saying:

[“/usr/bin/qvm-start’,’sys-firewall’] failed:
stdout: ""
stderr: “Start failed: internal error: libxenlight failed to create new 
domain ‘sys-
firewall’, see /var/log/libvirt/libxl/libxl-driver.log for details
""

I searched qubes-users for help and I came across this post: Bug in 
libxenlight 


This indeed helped me finish the setup without errors, but all of my qubes 
are paravirtualized and when I try to change, for example, my sys-usb to 
HVM I get a timeout error and that I should check 
/var/log/xen/console/quest-sys-usb.log. I have searched for some 
explanation online but to no avail. I've put all the important logs (I 
hope) in attachments and I'd appreciate if someone could help me.

Ana.




-- 
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/4b63dfb3-a3d1-4f49-9c00-b2ef5200acab%40googlegroups.com.
[0.00] Linux version 4.19.86-1.pvops.qubes.x86_64 (user@build-fedora4) 
(gcc version 6.4.1 20170727 (Red Hat 6.4.1-1) (GCC)) #1 SMP Sun Dec 1 07:16:00 
UTC 2019
[0.00] Command line: placeholder root=/dev/mapper/qubes_dom0-root ro 
rd.luks.uuid=luks-5e749bff-cae3-42f8-ac78-83cabe591c1d 
rd.lvm.lv=qubes_dom0/root rd.lvm.lv=qubes_dom0/swap i915.alpha_support=1 rhgb 
quiet plymouth.ignore-serial-consoles
[0.00] random: get_random_u32 called from bsp_init_amd+0x23f/0x2f0 with 
crng_init=0
[0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point 
registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[0.00] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, 
using 'standard' format.
[0.00] Released 0 page(s)
[0.00] BIOS-provided physical RAM map:
[0.00] Xen: [mem 0x-0x0009dfff] usable
[0.00] Xen: [mem 0x0009e800-0x000f] reserved
[0.00] Xen: [mem 0x0010-0xad1c] usable
[0.00] Xen: [mem 0xad1d-0xad1f] reserved
[0.00] Xen: [mem 0xad20-0xad21bfff] ACPI data
[0.00] Xen: [mem 0xad21c000-0xad755fff] ACPI NVS
[0.00] Xen: [mem 0xad756000-0xae3aefff] reserved
[0.00] Xen: [mem 0xae3af000-0xae3a] usable
[0.00] Xen: [mem 0xae3b-0xae5b5fff] ACPI NVS
[0.00] Xen: [mem 0xae5b6000-0xae9f2fff] usable
[0.00] Xen: [mem 0xae9f3000-0xaeff3fff] reserved
[0.00] Xen: [mem 0xaeff4000-0xaeff] usable
[0.00] Xen: [mem 0xf800-0xfbff] reserved
[0.00] Xen: [mem 0xfeb8-0xfec00fff] reserved
[0.00] Xen: [mem 0xfec1-0xfec10fff] reserved
[0.00] Xen: [mem 0xfed0-0xfed00fff] reserved
[0.00] Xen: [mem 0xfed8-0xfed8] reserved
[0.00] Xen: [mem 0xfee0-0xfeef] reserved
[0.00] Xen: [mem 0xff00-0x] reserved
[0.00] Xen: [mem 0x0001-0x000152a47fff] usable
[0.00] Xen: [mem 0x00fd-0x00ff] reserved
[0.00] NX (Execute Disable) protection: active
[0.00] SMBIOS 2.7 present.
[0.00] DMI: System manufacturer System Product Name/A88XM-A, BIOS 3001 
03/09/2016
[0.00] Hypervisor detected: Xen PV
[0.024260] tsc: Fast TSC calibration using PIT
[0.024262] tsc: Detected 4499.980 MHz processor
[0.024262] tsc: Detected 4500.036 MHz TSC
[0.030855] e820: update [mem 0x-0x0fff] usable ==> reserved
[0.030857] e820: remove [mem 0x000a-0x000f] usable
[0.030864] last_pfn = 0x152a48 max_arch_pfn = 0x4
[0.030865]

[qubes-users] [Qubes OS 4.0.1 / Debian 10] 403 Forbidden IP sudo apt update

2019-12-03 Thread schwoereraxel 
Hello,
I've been trying to install QGIS via their repositories for a few days now, 
but I have a problem when I do sudo apt update:

user@debian-10:~$ sudo apt update
Err: 1 https://qgis.org/debian buster 
InRelease
  403 Forbidden[IP : 127.0.0.0.1 8082]
Achieved: 2 https://deb.qubes-os.org/r4.0/vm buster 
InRelease   
Achieved: 3 https://cdn-aws.deb.debian.org/debian buster InRelease 
Achieved: 4 https://cdn-aws.deb.debian.org/debian-security buster/updates 
InRelease
Reading package lists Fact
E: Unable to retrieve https://qgis.org/debian/dists/buster/InRelease 403 
Forbidden[IP : 127.0.0.0.1 8082]
E: The deposit https://qgis.org/debian buster InRelease is not signed.
N: Updates from such a repository cannot be done securely, and are 
therefore disabled by default.
N: See the apt-secure(8) manual pages for repository creation and user 
configuration details.
user@debian-10:~$ 

It seems that my IP address is blacklisted from the QGIS repository.
So I tried to pass my template through sys-net and sys-firewall but it 
doesn't change anything. I also tried to go through my VPN, but nothing 
either...

Any solution?

PS : I've installed Ubuntu and I also have the same problem when I do a 
sudo apt update.

Thanks in advance!

-- 
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/965bf414-a33d-4edb-b6b3-d1c4b30e2541%40googlegroups.com.