[qubes-users] Re: Fedora-29 update does not work
On 4/24/19 12:58 PM, Claudio Chinicz wrote: On 18/03/2019 12:10, Claudio Chinicz wrote: Hi All, I'm getting notification that I need to update Fedora-29 (Qubes 4.0.1), I do it but it keeps asking to update. On Qubes manager all VMs based on Fedora-29 template show they need to restart because I've updated Fedora-29, although it keeps asking to update. I've even updated it manaully (opened terminal and issued sudo dnf update/upgrade) and it seems updated, but still Qubes thinks it needs to update. Any insights? Thanks, Claudio Chinicz Hi again, After a long time, the issue returned and for almost I see the update icon on the upper right corner indicating I need to update Fedora 29 template. When I try to update, I get an error saying "Failed to synchronize cache for repo \ 'fedora-modular\'\n . Comment: System is already up-to-date\n". When I try to update using command line I get this error message: sudo dnf update Error: Failed to synchronize cache for repo 'fedora-modular' Anyone else has been having this same problem? any ideas how to clear it? Thanks in advance, Claudio what does dom0 $qubes-prefs say for updateVM ? did you happen to recently change anything? I suppose you are aware that the Qubes Manager sometimes won't get rid of the little green arrow even though your up to date ?If your saying that you closed your Fedora-29 template and then closed all your AppVM Qubes and restarted them and still see the recycle green circle on them, I've never heard of that problem before . have you ever done $sudo dnf upgradevs update -- 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/c8ec5b15-e2bf-c11a-2394-bc3bbf93933e%40riseup.net. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: E' DAVVERO DA ARRESTARE IL PEDOFILO ED OMICIDA DANIELE MINOTTI
E' DAVVERO DA ARRESTARE IL PEDOFILO ED OMICIDA DANIELE MINOTTI (CRIMINALISSIMO AVV DI RAPALLO E GENOVA.. RAPALLO..OVE ORGANIZZA TRAME ASSASSINE ED OMICIDI NAZISTI E MAFIOSI, INSIEME "AL RAPALLESE" DI RESIDENZA, PEZZO DI MERDA, HITLERIANO, RAZZISTA, KU KLUK KLANISTA, RICICLA SOLDI MAFIOSI, SEMPRE PIU' PEDERASTA ANCHE LUI: PIERSILVIO BERLUSCONI)! E' DA FERMARE STRA SUBITO: L ' AVVOCATO SATANISTA, NAZISTA, ^SATA-N-AZISTA^, PEDOFILO ED OMICIDA DANIELE MINOTTI DI GENOVA, RAPALLO! CRIMINALE OMICIDA, TERRRORISTA DI ESTREMISSIMA DESTRA, AGENTE SEGRETO IN COPERTO DI TIPO SWASTIKATO E KILLER! https://grokbase.com/t/python/python-list/148jckyh1w/avvocato-pedofilomosessuale-ed-assassino-daniele-minotti-facebook-oltre-che-nazi-megalava-euro-mafiosi-e-come-detto-mandante-di-omicidi-o-suicidate-stalker-di-eroe-civile-michele-nista-su-ordine-di-tiranno-fasciocamorrista-silvio-berlusconi -- 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/f7fdcacd-50be-4114-966c-576c97378f60%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] E' DAVVERO DA ARRESTARE IL PEDOFILO ED OMICIDA DANIELE MINOTTI
E' DAVVERO DA ARRESTARE IL PEDOFILO ED OMICIDA DANIELE MINOTTI -- 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/dda562c6-94e6-4586-a310-811b6787c2f6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Android-x86 7.1-r2 with GAPPS installation guide
I am stuck on this process already twice. When I put the command Download sources: repo sync --no-tags --no-clone-bundle --force-sync -j$( nproc --all ) and when it show this: >From git://git.osdn.net/gitroot/android-x86/platform/frameworks/av * [new branch] nougat-x86 -> x86/nougat-x86 Fetching project platform/external/android-clat remote: Counting objects: 1, done remote: Finding sources: 100% (793/793) remote: Total 793 (delta 244), reused 793 (delta 244) Receiving objects: 100% (793/793), 517.38 KiB | 0 bytes/s, done. Resolving deltas: 100% (244/244), done. >From https://android.googlesource.com/platform/external/android-clat * [new tag] android-7.1.2_r36 -> android-7.1.2_r36 I got nothing, I mean it's look like freeze. -- 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/10960761-1f4f-4542-b2bf-1916c149e4e1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Qubes OS screensharing
On Thursday, April 25, 2019 at 1:54:38 PM UTC-4, Fernando wrote: > The fix from Marmarek worked for me as soon as it was released, but then > after a few updates (I don't remember exactly when) it stopped working for me. > > Do you have any suggestions on where I can start looking to debug this issue? > From what I see, no one else has reported problems. Is release repo up to date with the related changes from testing? I'm using testing and it worked on and off recently, but worked ok the last two attempts. Hard to pin down, though, as I'm updating dom0 daily-ish. Just tried a few device attach/detach/attach/VM restart/VM start/attach of an ISOstick with -testing updates and it seems to be working today... Brendan -- 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/fafde20d-d111-4ab2-bea6-ce605d3078f5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Qubes OS screensharing
On Tuesday, December 11, 2018 at 2:00:56 PM UTC-3, Dave C wrote: > On Thursday, October 18, 2018 at 5:52:31 AM UTC-7, Vít Šesták wrote: > > Marmarek has identified the issue and fixed it: > > https://github.com/QubesOS/qubes-issues/issues/4351 > > > > I haven't been vocal on this thread in a while... but I appreciate the > comments from v6ak and the bugfix from Marmarek. > > I had a moment to update my blog post about screensharing in Qubes: > https://www.dave-cohen.com/blog/qubes-vnc-screenshare/, please check it out > if interested. I welcome any constructive feedback. > > Cheers, -Dave The fix from Marmarek worked for me as soon as it was released, but then after a few updates (I don't remember exactly when) it stopped working for me. Do you have any suggestions on where I can start looking to debug this issue? From what I see, no one else has reported problems. Thanks, Nando. -- 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/9542060b-6ba1-4b4c-9f25-bea9916bc70e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Very confused setting up a vpn
On 4/25/19 5:01 AM, Mishima wrote: Ok thank you, so I managed to set it up this time, however upon restarting the ProxyVM I don't get a pop up saying LINK IS UP but a pop us saying "Ready to start link". And I have no internet access on the vm. What went wrong this time? How can I link this right? I already did in earlier step sudo ln -s example.ovpn vpn-client.conf The config you downloaded from your VPN provider is "example.ovpn"? That sounds a little odd. You should view the log with 'sudo journalctl -u qubes-vpn-handler' to see what failed. When it says Ready but there is no connection, its usually because of a mis-typed username or password. You can check this in the /rw/config/vpn/userpassword.txt file. -- 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/789098d0-61aa-a7f2-02a5-c39c233584c1%40posteo.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Qubes update of debian-9 templates is failing
On Thu, Apr 25, 2019 at 04:59:22PM +0300, Claudio Chinicz wrote:
> On 25/04/2019 15:18, unman wrote:
> > On Thu, Apr 25, 2019 at 01:06:26PM +0300, Claudio Chinicz wrote:
> > > Hi All,
> > >
> > > I'm getting the following error message:
> > >
> > > root@debian-9:/home/user# apt-get update
> > > Ign:1 http://dl.google.com/linux/chrome/deb stable InRelease
> > > Ign:2 https://deb.qubes-os.org/r4.0/vm stretch InRelease
> > > Ign:3 https://deb.debian.org/debian stretch InRelease
> > > Err:4 http://dl.google.com/linux/chrome/deb stable Release
> > >500 Unable to connect
> > > Err:5 https://deb.qubes-os.org/r4.0/vm stretch Release
> > >Received HTTP code 500 from proxy after CONNECT
> > > Ign:6 https://deb.debian.org/debian-security stretch/updates InRelease
> > > Err:7 https://deb.debian.org/debian stretch Release
> > >Received HTTP code 500 from proxy after CONNECT
> > > Err:8 https://deb.debian.org/debian-security stretch/updates Release
> > >Received HTTP code 500 from proxy after CONNECT
> > > Reading package lists... Done
> > > E: The repository 'http://dl.google.com/linux/chrome/deb stable Release'
> > > does no longer have a Release file.
> > > N: Updating from such a repository can't be done securely, and is
> > > therefore
> > > disabled by default.
> > > N: See apt-secure(8) manpage for repository creation and user
> > > configuration
> > > details.
> > > E: The repository 'https://deb.qubes-os.org/r4.0/vm stretch Release' does
> > > no
> > > longer have a Release file.
> > > N: Updating from such a repository can't be done securely, and is
> > > therefore
> > > disabled by default.
> > > N: See apt-secure(8) manpage for repository creation and user
> > > configuration
> > > details.
> > > E: The repository 'https://deb.debian.org/debian stretch Release' does no
> > > longer have a Release file.
> > > N: Updating from such a repository can't be done securely, and is
> > > therefore
> > > disabled by default.
> > > N: See apt-secure(8) manpage for repository creation and user
> > > configuration
> > > details.
> > > E: The repository 'https://deb.debian.org/debian-security stretch/updates
> > > Release' does no longer have a Release file.
> > > N: Updating from such a repository can't be done securely, and is
> > > therefore
> > > disabled by default.
> > > N: See apt-secure(8) manpage for repository creation and user
> > > configuration
> > > details.
> > >
> > > Have anyone faced the same issue? Any ideas how to solve it?
> > >
> > > Thanks,
> > >
> > > Claudio
> > >
> >
> > Hi Claudio
> >
> > The important is the error messages - everything else is consequential.
> > 500 is an internal server error.
> > Combined with connect error suggest there's something wrong with your
> > proxy or your connection.
> >
> > If you are using sys-whonix could be intermittent fault on Tor network.
> > Try again later.
> > If not, look closely at proxy configuration, and check qube where proxy
> > is running. (Look in /etc/qubes-rpc/policy/qubes.UpdatesProxy if you're
> > not sure.)
> >
>
> Hi unman,
>
> Thanks for your prompt answer. I've reviewed my connection and made sure I'm
> using standard sys-net and sys-firewall. Also, I'm using my home connection
> (no proxy) and not updating through whonix, although internet is connecting
> ok and tor is connected through sys-whonix, as usual.
>
> So, I could not find any issue on my side. I'll try it again Sunday or
> Monday using a different internet connection.
>
> One thing to note is that after trying to update (this time using qubes
> updater and not command line), qubes manager shows the two arrows ("this
> qube must be restarted for its filesystem to reflect the recent committed
> changes") on all Fedora-based VMs (sys-net, sys-usb and sys-firewall) BUT
> NOT on my Personal VM, which is Debian 9 based (??).
>
> Best Regards,
>
> Claudio
>
That's very strange: if you're using clearnet then I'd be looking
carefully at the update proxy - what's showing in that policy file? If it's
sys-net then look at sys-net logs to see if there's an issue there.
I think the Fedora problem is a known issue, not relevant here. Fix on
its way.
--
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/20190425151147.m2tkwnqmiervhps5%40thirdeyesecurity.org.
For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Qubes update of debian-9 templates is failing
On 25/04/2019 15:18, unman wrote:
On Thu, Apr 25, 2019 at 01:06:26PM +0300, Claudio Chinicz wrote:
Hi All,
I'm getting the following error message:
root@debian-9:/home/user# apt-get update
Ign:1 http://dl.google.com/linux/chrome/deb stable InRelease
Ign:2 https://deb.qubes-os.org/r4.0/vm stretch InRelease
Ign:3 https://deb.debian.org/debian stretch InRelease
Err:4 http://dl.google.com/linux/chrome/deb stable Release
500 Unable to connect
Err:5 https://deb.qubes-os.org/r4.0/vm stretch Release
Received HTTP code 500 from proxy after CONNECT
Ign:6 https://deb.debian.org/debian-security stretch/updates InRelease
Err:7 https://deb.debian.org/debian stretch Release
Received HTTP code 500 from proxy after CONNECT
Err:8 https://deb.debian.org/debian-security stretch/updates Release
Received HTTP code 500 from proxy after CONNECT
Reading package lists... Done
E: The repository 'http://dl.google.com/linux/chrome/deb stable Release'
does no longer have a Release file.
N: Updating from such a repository can't be done securely, and is therefore
disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration
details.
E: The repository 'https://deb.qubes-os.org/r4.0/vm stretch Release' does no
longer have a Release file.
N: Updating from such a repository can't be done securely, and is therefore
disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration
details.
E: The repository 'https://deb.debian.org/debian stretch Release' does no
longer have a Release file.
N: Updating from such a repository can't be done securely, and is therefore
disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration
details.
E: The repository 'https://deb.debian.org/debian-security stretch/updates
Release' does no longer have a Release file.
N: Updating from such a repository can't be done securely, and is therefore
disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration
details.
Have anyone faced the same issue? Any ideas how to solve it?
Thanks,
Claudio
Hi Claudio
The important is the error messages - everything else is consequential.
500 is an internal server error.
Combined with connect error suggest there's something wrong with your
proxy or your connection.
If you are using sys-whonix could be intermittent fault on Tor network.
Try again later.
If not, look closely at proxy configuration, and check qube where proxy
is running. (Look in /etc/qubes-rpc/policy/qubes.UpdatesProxy if you're
not sure.)
Hi unman,
Thanks for your prompt answer. I've reviewed my connection and made sure
I'm using standard sys-net and sys-firewall. Also, I'm using my home
connection (no proxy) and not updating through whonix, although internet
is connecting ok and tor is connected through sys-whonix, as usual.
So, I could not find any issue on my side. I'll try it again Sunday or
Monday using a different internet connection.
One thing to note is that after trying to update (this time using qubes
updater and not command line), qubes manager shows the two arrows ("this
qube must be restarted for its filesystem to reflect the recent
committed changes") on all Fedora-based VMs (sys-net, sys-usb and
sys-firewall) BUT NOT on my Personal VM, which is Debian 9 based (??).
Best Regards,
Claudio
--
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/q9sefq%2411j3%241%40blaine.gmane.org.
For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes menu failing. Come on guys
On Friday, November 9, 2018 at 9:56:22 AM UTC-5, steve.coleman wrote: > There is one consistently reproducible way to destroy the Qubes menu, by > simply using the built in xfce/other menu editor to reorganize your menu > entries, if you happen to be the impatient type in trying to get it > done. I have tried every menu editor I could find, and they all seem to > do pretty much the same damage. > > Example: > 1) Right click on the xfce/Qubes menu button. > 2) Select properties from the popup menu > 3) Select the edit menu button. > 4) Select a sub-menu for any VM to edit > 5) Select an entry on the right to move an application up/down in the list > 6) Press the up or down button quickly in succession, say to move an > entry from the bottom of the list, up to the top of the list. > 7) Save the menu. > > Congratulations, you now have no Qubes menu at all, so lets hope you > still have a dom0 command window open. > > To recover the menu, start a template vm via qvm-run, and run dnf to > update or make any change that in turn forces a dom0 resync of the Qubes > menu items. Or perhaps you can just force a resync from the dom0 command > line (qvm-sync-appmenus), but I have not tested that. ... > Bottom line, don't be too quick with changes to the menu, or you will be > spending even more time repairing your system. The first time this > happened I had no clue how to recover. Hi Steve, I know this was posted long ago, but would an alternate fix be to right click on the desktop, open terminal here, and then execute the following: qvm-appmenus dom0 ? B -- 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/de77700c-8c60-4f1b-92d2-fd4b7d7713ee%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Failing to increase Screen Resolution in HVM Ubuntu -Limited 800x600..
On Tue, Apr 23, 2019 at 08:28:10PM -0700, gandalf boomerang wrote: > -tried xrandr but ALWAYS get the error: > > 'failed to get size of gamma for output' > > Ubuntu HVM, full installation, 4000mb ram, 20GB disk > > > can not find any solution online... Try searching this list for HVM resolution > > how can I increase my screensize on my ubuntu HVM to a minimum of 1200x ? > > > > > the qubes linux tips also do not work with error > 'a xorg server is already running' > when trying to close the xorg ,my Ubuntu HVM crashes... > After changing the Xorg configuration you need to restart the X server. My HVM doesnt crash when I do this - if yours does, just restart the qube. -- 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/20190425122503.sads6ewlayuneobm%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes update of debian-9 templates is failing
On Thu, Apr 25, 2019 at 01:06:26PM +0300, Claudio Chinicz wrote: > Hi All, > > I'm getting the following error message: > > root@debian-9:/home/user# apt-get update > Ign:1 http://dl.google.com/linux/chrome/deb stable InRelease > Ign:2 https://deb.qubes-os.org/r4.0/vm stretch InRelease > Ign:3 https://deb.debian.org/debian stretch InRelease > Err:4 http://dl.google.com/linux/chrome/deb stable Release > 500 Unable to connect > Err:5 https://deb.qubes-os.org/r4.0/vm stretch Release > Received HTTP code 500 from proxy after CONNECT > Ign:6 https://deb.debian.org/debian-security stretch/updates InRelease > Err:7 https://deb.debian.org/debian stretch Release > Received HTTP code 500 from proxy after CONNECT > Err:8 https://deb.debian.org/debian-security stretch/updates Release > Received HTTP code 500 from proxy after CONNECT > Reading package lists... Done > E: The repository 'http://dl.google.com/linux/chrome/deb stable Release' > does no longer have a Release file. > N: Updating from such a repository can't be done securely, and is therefore > disabled by default. > N: See apt-secure(8) manpage for repository creation and user configuration > details. > E: The repository 'https://deb.qubes-os.org/r4.0/vm stretch Release' does no > longer have a Release file. > N: Updating from such a repository can't be done securely, and is therefore > disabled by default. > N: See apt-secure(8) manpage for repository creation and user configuration > details. > E: The repository 'https://deb.debian.org/debian stretch Release' does no > longer have a Release file. > N: Updating from such a repository can't be done securely, and is therefore > disabled by default. > N: See apt-secure(8) manpage for repository creation and user configuration > details. > E: The repository 'https://deb.debian.org/debian-security stretch/updates > Release' does no longer have a Release file. > N: Updating from such a repository can't be done securely, and is therefore > disabled by default. > N: See apt-secure(8) manpage for repository creation and user configuration > details. > > Have anyone faced the same issue? Any ideas how to solve it? > > Thanks, > > Claudio > Hi Claudio The important is the error messages - everything else is consequential. 500 is an internal server error. Combined with connect error suggest there's something wrong with your proxy or your connection. If you are using sys-whonix could be intermittent fault on Tor network. Try again later. If not, look closely at proxy configuration, and check qube where proxy is running. (Look in /etc/qubes-rpc/policy/qubes.UpdatesProxy if you're not sure.) -- 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/20190425121806.eottc52zine4a27a%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Qubes update of debian-9 templates is failing
Hi All, I'm getting the following error message: root@debian-9:/home/user# apt-get update Ign:1 http://dl.google.com/linux/chrome/deb stable InRelease Ign:2 https://deb.qubes-os.org/r4.0/vm stretch InRelease Ign:3 https://deb.debian.org/debian stretch InRelease Err:4 http://dl.google.com/linux/chrome/deb stable Release 500 Unable to connect Err:5 https://deb.qubes-os.org/r4.0/vm stretch Release Received HTTP code 500 from proxy after CONNECT Ign:6 https://deb.debian.org/debian-security stretch/updates InRelease Err:7 https://deb.debian.org/debian stretch Release Received HTTP code 500 from proxy after CONNECT Err:8 https://deb.debian.org/debian-security stretch/updates Release Received HTTP code 500 from proxy after CONNECT Reading package lists... Done E: The repository 'http://dl.google.com/linux/chrome/deb stable Release' does no longer have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. E: The repository 'https://deb.qubes-os.org/r4.0/vm stretch Release' does no longer have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. E: The repository 'https://deb.debian.org/debian stretch Release' does no longer have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. E: The repository 'https://deb.debian.org/debian-security stretch/updates Release' does no longer have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. Have anyone faced the same issue? Any ideas how to solve it? Thanks, Claudio -- 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/q9s0r3%24shk%241%40blaine.gmane.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Very confused setting up a vpn
Ok thank you, so I managed to set it up this time, however upon restarting the ProxyVM I don't get a pop up saying LINK IS UP but a pop us saying "Ready to start link". And I have no internet access on the vm. What went wrong this time? How can I link this right? I already did in earlier step sudo ln -s example.ovpn vpn-client.conf -- 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/3d67f6fb-d20c-4603-a5c4-69c9604f6857%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
