On 10/02/2017 11:08 PM, Person wrote:
I followed the directions for enabling mac-spoofing on Qubes, and it didn’t
work. https://www.qubes-os.org/doc/anonymizing-your-mac-address/
I think I may have done something wrong. I could have not saved the gedit file
correctly, or I spelled wlpos1
On 10/02/2017 08:34 PM, joevio...@gmail.com wrote:
On Saturday, 5 August 2017 11:20:27 UTC-4, the2nd wrote:
Hi,
i switched to Qubes OS 3.2 on my notebook some weeks ago. Besides some issues i
had it works very well.
One problem was to get the installer to install qubes on LVM-on-LUKS. I
On Saturday, 5 August 2017 11:20:27 UTC-4, the2nd wrote:
> Hi,
>
> i switched to Qubes OS 3.2 on my notebook some weeks ago. Besides some issues
> i had it works very well.
>
> One problem was to get the installer to install qubes on LVM-on-LUKS. I
> preferred this over the default
Apparently the brackets were one of my mistakes. My bad (and thank you for
pointing that out).
I ran the copy-to-dom0 and attach-to-VM commands again, and dom0 didn’t
respond. So I opened the Standalone VM and it didn’t register anything to boot
from, even though I’m sure that I copied the ISO
On Sun, Oct 01, 2017 at 09:41:03PM -0600, Ron Hunter-Duvar wrote:
> On 10/01/2017 06:59 PM, Person wrote:
> > The file was in Home/User/Downloads, and I did make sure to include the
> > command. Also, the Ubuntu file did end in “.iso”.
> >
> > I did run qvm-start in dom0. I believe I typed
I looked at Arm again. It seems that Arm is working, but I don’t know the
commands to edit the Tor configuration.
Arm mentions a list of problems relating to Tor (http://imgur.com/XrJHKSK). It
seems that I have relaying disabled, torrc differs from what Tor is using,
there is insufficient
I have successfully changed the NetVM for the Whonix templates, luckily.
To explain what I said eariler, I changed the NetVM of whonix-gw to
anon-whonix, so that the “Whonix has no UpdateVM” (I think they mean that the
whonix-gw template does not use a NetVM with a whonix template) and the Tor
On 08/01/2017 09:49 PM, Tao Effect wrote:
Ran into all of the same issues that Mike Freemon experienced:
-
https://groups.google.com/forum/#!searchin/qubes-users/display$20resolution|sort:relevance/qubes-users/BUe4tFfERtA/buazJHIzCQAJ
On 08/20/2017 11:31 AM, cyrinux wrote:
It is a dock in thunderbolt*
Hi cyrinux,
If you'd like this computer to be listed on the HCL page, could you
attach a yml file from the qubes-hcl-report script?
--
Chris Laprise, tas...@posteo.net
https://twitter.com/ttaskett
PGP: BEE2 20C5 356E
On Mon, Oct 02, 2017 at 02:18:00PM +, Patrick Schleizer wrote:
> Yethal:
> > W dniu środa, 27 września 2017 14:08:56 UTC+2 użytkownik Patrick Schleizer
> > napisał:
> >> cooloutac:
> >>> On Sunday, September 24, 2017 at 12:23:39 PM UTC-4, cooloutac wrote:
> On Sunday, September 24, 2017
On Sun, Oct 01, 2017 at 06:35:03PM -0700, Person wrote:
> I changed the NetVM of whonix-gw from sys-net to anon-whonix (so whonix-gw
> finally has a NetVM that uses Whonix as its template) , and the Tor Control
> Port problem no longer appears. However, a Tor Bootstrap problem appears:
>
On Monday, October 2, 2017 at 11:35:37 AM UTC+2, Frédéric Pierret (fepitre)
wrote:
> Le lundi 2 octobre 2017 02:36:48 UTC+2, Reg Tiangha a écrit :
> > On 2017-10-01 10:21 AM, Frédéric Pierret (fepitre) wrote:
> >
> > >
> > > Hi, just a small update of current kernel branches status:
> > >
> >
Am 02.10.2017 um 20:17 schrieb Ron Hunter-Duvar:
> On October 2, 2017 10:30:49 AM MDT, evo wrote:
>>
>>
>> Am 01.10.2017 um 22:06 schrieb evo:
>>> Hello!
>>>
>>> i can not start one of the StandaloneVMs
>>> it just give me a timeout and "cannot execute qrexec-daemon"
>>>
On October 2, 2017 10:30:49 AM MDT, evo wrote:
>
>
>Am 01.10.2017 um 22:06 schrieb evo:
>> Hello!
>>
>> i can not start one of the StandaloneVMs
>> it just give me a timeout and "cannot execute qrexec-daemon"
>>
>> after reboot the same thing.
>>
>> logs show the
Am 01.10.2017 um 22:06 schrieb evo:
> Hello!
>
> i can not start one of the StandaloneVMs
> it just give me a timeout and "cannot execute qrexec-daemon"
>
> after reboot the same thing.
>
> logs show the following:
>
> guid.VM
> Icon size: 128x128
> XIO: fatal IO error 11 (Resource
Yethal:
> W dniu środa, 27 września 2017 14:08:56 UTC+2 użytkownik Patrick Schleizer
> napisał:
>> cooloutac:
>>> On Sunday, September 24, 2017 at 12:23:39 PM UTC-4, cooloutac wrote:
On Sunday, September 24, 2017 at 12:23:23 PM UTC-4, cooloutac wrote:
> On Sunday, September 24, 2017 at
Hi, i just installed qubes-4.0rc1 and updated everything with testing repo
enabled.
After that, the sys-firewall failed to start with the following error:
"Snapshot origin LV vm-sys-firewall-private not found in Volumegroup qubes_dom0"
I tried to add a symlink in qubes_dom0, but this doesn't
On Monday, October 2, 2017 at 12:01:41 AM UTC+3, One7two99 wrote:
> Hello Beso,
>
> > Mobile Broadband is enabled in
> > NetworkManager Applet.
> > I can create new Mobile Broadband
> > connection but it keeps connecting
> > and nothing else
>
> I am using mobile broadband within Qubes and
Le lundi 2 octobre 2017 02:36:48 UTC+2, Reg Tiangha a écrit :
> On 2017-10-01 10:21 AM, Frédéric Pierret (fepitre) wrote:
>
> >
> > Hi, just a small update of current kernel branches status:
> >
> > From our last commits with Reg, the last version of kernel 4.12.14 is
> > available and also I
After discussing this issue with some other Qubes users that reported
similar problems, I tried downgrading the dom0 kernel to 4.4.67-13 (and
keeping sys-net as 4.9.45-21, xen at 4.6.6)
That seems to resolve the issue between sleeps. Please let me know if
you need logs.
So it looks like it's a
On Thursday, September 28, 2017 at 5:59:09 PM UTC+2, steve.coleman wrote:
> On 09/26/2017 05:35 AM, pels wrote:
> > On Sunday, September 24, 2017 at 6:19:15 PM UTC+2, cooloutac wrote:
> >> On Sunday, September 24, 2017 at 12:17:33 PM UTC-4, cooloutac wrote:
> >>> On Sunday, September 24, 2017 at
21 matches
Mail list logo