On Thursday, December 20, 2018 at 9:11:34 PM UTC-8, John Smiley wrote:
> I've been having head-banging issues with 4.0 and 4.0.1-rc1 ever since I
> became a fledgling Qubes user a few weeks ago. I never did get Qubes working
> well with Whonix 14 on the desktop.
>
> When 4.0.1-rc2 came out
I've been having head-banging issues with 4.0 and 4.0.1-rc1 ever since I became
a fledgling Qubes user a few weeks ago. I never did get Qubes working well
with Whonix 14 on the desktop.
When 4.0.1-rc2 came out the other day, I made a new bootable USB stick with it
and replaced Ubuntu on my
I should have been clearer in indicating how far the boot process got:
The text messages were displayed starting in the top left corner of the screen
until the screen cleared and the Qubes Q-logo was displayed with a progress bar
underneath.
The boot process continued until the progress
On Thursday, 20 December 2018 22:02:00 UTC-3:30, John Goold wrote:
> Attached is screenshot, taken under my current OS, showing OS and hardware
> info.
>
> After spending much too much time trying to track the problem down (using the
> 4.0, 4.0.1-RC1 and 4.0.1-RC2 ISOs) I discovered why
Attached is screenshot, taken under my current OS, showing OS and hardware info.
After spending much too much time trying to track the problem down (using the
4.0, 4.0.1-RC1 and 4.0.1-RC2 ISOs) I discovered why getting the installer to
run was failing...
I had to unplug my external monitor
On 20181220 at 14:53 -0500 Chris Laprise wrote:
> How stable is the CentOS 7 "testing" template? I'm so over Fedora,
> but need dnf for full compatibility with qubes-dom0-update.
It just self-destructed by upgrading x11-xorg*, see "[qubes-users]
updating CentOS-7 templa
On 12/20/2018 09:49 AM, Steve Coleman wrote:
On 12/19/18 6:39 PM, Andrew David Wong wrote:
It's an upstream Fedora issue. For more info, see:
https://github.com/QubesOS/qubes-issues/issues/4629
Yes, this is an upstream problem, which has been fixed in the
"updates-testing" repo. I got
On 12/20/2018 02:11 PM, menoldst...@gmail.com wrote:
Dec 20 20:49:08 VPN1 qubes-vpn-setup[2085]: Thu Dec 20 20:49:08 2018 RESOLVE:
Cannot resolve host address: fi.privateinternetaccess.com:1198 (Name or service
not known)
That's the problem.
Did you test the connection as suggested in Step
* qubes4-multi-update
Updates are now attempted for each specified VM even if some VMs
experience update errors. Any VMs with errors are reported at the end.
This allows an update process to be as complete as possible in less than
ideal conditions.
* findpref
Can now search on 'None' empty
Hello, I am trying to configure Qubes-vpn-support
https://github.com/tasket/Qubes-vpn-support/ , but I can not. Help. What do I
need to do to complete the VPN setup?
https://github.com/tasket/Qubes-vpn-support/
[user@VPN1 ~]$ systemctl status qubes-vpn-handler
● qubes-vpn-handler.service - VPN
> As I understood your setup for OnlyKey consists of two parts: first - make it
> work as a keyboard, second - make TOTP work. I think I stuck on the first
> one. I modified the file from Qubes docs and I able to attach a regular USB
> keyboard - it works in any qubes. But when I insert the
I thought this action was fix but it seem i still have to change all http to
htpps in qubes 4.0.1-rc2 by running the bottom comand .
Is that normal i still have to run these comand with this new fresh install ?
thank you
Qubes 4.0 Warning
In new installations of Qubes 4.0, the following steps
Just got the following Whonix 14 error. Seems like it downloaded the
whole file then reported an error code anyway...
_[0m _[1D_[0G 99% _[7m _[0m _[1D_[0G 100% _[7m
Failed to download: https://dist.torproject.org/torbrowser/8.0.4/tor-browser-linux64-8.0.4_en-US.tar.xz
I ran updates for dom0 this morning, I noticed that after the updates, the
default-mgmt-dvm is no longer hidden. It is still marked internal, but not
hidden. Is this the desired outcome of the latest dom0 updates?
Ed
--
You received this message because you are subscribed to the Google
On 12/20/2018 04:35 AM, menoldst...@gmail.com wrote:
Hello, you can help set up https://github.com/tasket/Qubes-vpn-support/
Qubes-vpn-support
#sorry my bad English
I seem to have done everything according to the instructions, but when I enter
systemctl status qubes-vpn-handler shows:
●
So does anyone reported this issue to qubes-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 post to this
On 12/19/18 6:39 PM, Andrew David Wong wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 12/19/18 4:34 AM, qubes-...@tutanota.com wrote:
Hi, I updated the dom0 and after I tried to update the Fed-28 template. I get
following error:
[user@fedora-28 ~]$ sudo dnf update
Last metadata
On 20181218 at 23:53 + unman wrote:
> On Tue, Dec 18, 2018 at 09:18:06PM +0100, Achim Patzner wrote:
> > [ap@dom0 bin]$ qvm-ls --disk BuilderNAME STATE DISKPRIV-
> > CURR PRIV-MAX PRIV-USED ROOT-CURR ROOT-MAX ROOT-
> > USEDBuilder Halted 124948 124948 2048 6100%
On Thu, Dec 20, 2018 at 10:29:31AM +, mossy wrote:
> unman:
> > On Wed, Dec 19, 2018 at 11:06:25PM +, mossy wrote:
> >> Hello all,
> >>
> >> I was looking to see if I could update an offline standalone VM, by
> >> appending a line to `etc/qubes-rpc/policy/qubes.UpdatesProxy` and I now
> >>
unman:
> On Wed, Dec 19, 2018 at 11:06:25PM +, mossy wrote:
>> Hello all,
>>
>> I was looking to see if I could update an offline standalone VM, by
>> appending a line to `etc/qubes-rpc/policy/qubes.UpdatesProxy` and I now
>> have some questions.
>>
>> First, I noticed the lines:
>>
>> ~~~
>>
So, you have found an ancient UNIX command to be useful for fuzzy testing: cat.
--
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
Hello, you can help set up https://github.com/tasket/Qubes-vpn-support/
Qubes-vpn-support
#sorry my bad English
I seem to have done everything according to the instructions, but when I enter
systemctl status qubes-vpn-handler shows:
● qubes-vpn-handler.service - VPN Client for Qubes proxyVM
22 matches
Mail list logo
