On Wednesday, October 18, 2017 at 8:01:50 PM UTC, Roy Bernat wrote:
> I am getting error download whonix regarding
>
> could not read file curl error (37) NOKEY .
>
> any suggestions ?
>
> R
Alternatively, wait for the Qubes 4-RC2 release the 23th, on next monday. It
might be faster to
On Saturday, October 7, 2017 at 9:12:47 PM UTC, Stumpy wrote:
> For some reason the audio in all my Debian VMs has stopped working?
> AFAIK I haven't done anything other than regular updates. I didn't
> notice until recently so I am not sure about exactly when it started.
>
> In the audio mixer
On Wednesday, October 18, 2017 at 8:11:53 PM UTC, Sven Semmler wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Hi,
>
> I regularly trim my templates after updating them. I don't recall this
> process ever being interrupted, but it appears that something got
> corrupted once when
On 18.10.2017 20:16, qubenix wrote:
Foppe de Haan:
On Wednesday, October 18, 2017 at 12:38:05 AM UTC+2, Stumpy wrote:
hm...
Is there something else I can post that would make this easier to
diag?
I really really would like to resolve this.
On 16.10.2017 02:28, Stumpy wrote:
No one?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear Qubes Community,
Simon Gaiser (aka HW42) has just published an article titled "MSI support for
PCI device pass-through with stub domains" on the Qubes OS website:
https://www.qubes-os.org/news/2017/10/18/msi-support/
The source text of the
On Wednesday, October 18, 2017 at 8:01:50 PM UTC, Roy Bernat wrote:
> I am getting error download whonix regarding
>
> could not read file curl error (37) NOKEY .
>
> any suggestions ?
>
> R
Please check:
https://forums.whonix.org/t/qubes-4-0-rc1-cant-find-the-whonix-template-package/4221
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
I regularly trim my templates after updating them. I don't recall this
process ever being interrupted, but it appears that something got
corrupted once when trimming whonix-ws. What I have already done:
* deleted
On Wednesday, 18 October 2017 04:16:00 UTC-4, Roy Bernat wrote:
> Hi
>
> After update the system get an error cannot excute grexec daemon (libxenlight
> failed to create qubes) for existing vm .new vm seems to work fine .
>
> any ideas ?
>
> Roy
fixed it by update the default vm as well
Foppe de Haan:
> On Wednesday, October 18, 2017 at 12:38:05 AM UTC+2, Stumpy wrote:
>> hm...
>>
>> Is there something else I can post that would make this easier to diag?
>> I really really would like to resolve this.
>>
>> On 16.10.2017 02:28, Stumpy wrote:
>>> No one?
>>> I still haven't
El dimarts, 17 setembre de 2013 22:58:41 UTC+2, Brian J Smith-Sweeney va
escriure:
> Hey folks,
>
> Finally got around to a longstanding todo of checking out the current
> state of Qubes OS, and I'm quite pleased so far. I've installed it on
> the new XPS 13 and it works nicely.
>
> Wireless
On Wed, Oct 18, 2017 at 10:59:52AM +, Holger Levsen wrote:
> apt gets: cannot connect to 10.137.255.254…
still not sure why this happened (and why now), but running systemctl on sys-net
made it obvious what the fix was:
sudo service qubes-updates-proxy restart
--
cheers,
Holger
On Sunday, October 15, 2017 at 10:11:16 AM UTC+2, Foppe de Haan wrote:
> I've just tried 4.13 again, still getting the same behavior, with the mouse
> cursor becoming progressively less responsive, and mouse and kb both becoming
> unresponsive, then X crashing/dying some time after that. Looking
Hi,
I'm running 3.2 and this week for the first time template VMs lost connectivity,
as in they couldnt connect to their software repos anymore. A reboot "fixed"
this and I could update them again. Then, yesterday, they lost connectivity
again…
apt gets: cannot connect to 10.137.255.254…
and
On Wednesday, 18 October 2017 04:41:55 UTC-4, Roy Bernat wrote:
> Hi
>
> i cretaed a vm called mfa like this article
>
> https://www.qubes-os.org/doc/multifactor-authentication/
>
> everything work fine . i thought to my self the key are open is there a
> workaround to encrypt this scripts
On Tuesday, 17 October 2017 14:50:33 UTC-4, Roy Bernat wrote:
> pressing the appVm for example on firefox seems that the vm is started but
> after couple of minutes its disappear.when i check qvm-ls it halted .
>
> only when i start the machine with qvm start vmname it started ok .
>
>
On 10/17/2017 08:08 PM, Roy Bernat wrote:
On Tuesday, 17 October 2017 11:01:04 UTC-4, David Hobach wrote:
i have dell xps 9360 ( kaby lake i7 intel 620 )
when i installed qubes after installation the qubes didnt succeeded to start .
work around that worked was to remove from grub the
Hi
i cretaed a vm called mfa like this article
https://www.qubes-os.org/doc/multifactor-authentication/
everything work fine . i thought to my self the key are open is there a
workaround to encrypt this scripts ?
Roy
--
You received this message because you are subscribed to the Google
On Sun, Oct 15, 2017 at 10:44:02PM -0700, Dave C wrote:
> On Friday, July 28, 2017 at 7:16:36 AM UTC-7, little help wrote:
> [snip...]
> >
> > This also might also work:
> > 1.Go here: https://user.riseup.net/
> >
> > 2.Make a "help ticket", and write "I need an invitation code because
Hi
After update the system get an error cannot excute grexec daemon (libxenlight
failed to create qubes) for existing vm .new vm seems to work fine .
any ideas ?
Roy
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from
> On Saturday, 12 November 2016 18:31:05 UTC-5, tai...@gmx.com wrote:
>> I have tried all the options in the power control menu but my screen
>> still doesn't turn off it just disconnects the output so the screen will
>> say "NO VGA/DVI DETECTED" when power save mode turns on.
>>
>> Ideas?
>
>
20 matches
Mail list logo
