[qubes-users] Re: vpnleak or my vpn

2016-07-31 Thread eliwu
> 
> Newer VPN instructions at https://www.qubes-os.org/doc/vpn/


Maybe silly, but in my .ovpn file, I should comment out..

#down /etc/openvpn/update-resolv-conf
#up /etc/openvpn/update-resolv-conf

right? (it is in the .ovpn file given to me by my vpn)

dnsleak.com is saying that I am leaking, but not from my ip or the dns server 
that I am using..  Why would that be?

-- 
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/dd455cd3-0003-41dd-8bb7-8f60d4d4a293%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: vpnleak or my vpn

2016-07-31 Thread eliwu
Maybe silly, but in my .ovpn file, I should comment out..

#down /etc/openvpn/update-resolv-conf
#up /etc/openvpn/update-resolv-conf

right? (it is in the .ovpn file given to me by my vpn)


> Newer VPN instructions at https://www.qubes-os.org/doc/vpn/

-- 
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/76c73c75-749c-41df-873e-de2f466201ae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: vpnleak or my vpn

2016-07-31 Thread eliwu
On Sunday, July 31, 2016 at 7:44:14 AM UTC, bur...@gmail.com wrote:
> On Sunday, July 31, 2016 at 1:09:03 AM UTC-4, el...@tutanota.com wrote:
> > I set up a vpn in accordance to cprise's advice.. 
> > https://groups.google.com/d/topic/qubes-users/UbY4-apKScE/discussion.  
> > 
> > dnsleaktest.com comes back all good.  (shows my vpn's ip address)
> > dnsleak.com, however, is showing multiple dns leaks.   
> > They are, however, from random places all over the world, none of which 
> > have any connection to my IP.  
> > Does this have something to do with my vpn or am I setting it up wrong?  
> > 
> > Connecting through dhcp to the vpn..
> > 
> > One thing I am not sure about is where to put are the up/dwn commands. 
> > Working now, I have in my *.ovpn file, is..
> > 
> > #down /etc/openvpn/update-resolv-conf
> > #up /etc/openvpn/update-resolv-conf
> > script-security 2
> > up vpn-setup2.sh
> > down vpn-setup2.sh
> > 
> > Is that right?  
> > 
> > Here is the dnsleak result.
> > Looks like your DNS might be leaking...
> > Your IP: 185.57.87.27
> > DNS IP: 37.48.74.75
> > Hostname: hosted-by.leaseweb.com
> > Country: Netherlands
> > City: Amsterdam
> > Looks like your DNS might be leaking...
> > Your IP: 185.57.82.27
> > DNS IP: 185.57.82.25
> > Hostname: 185.57.82.25
> 
> Newer VPN instructions at https://www.qubes-os.org/doc/vpn/

Maybe silly, but in my .ovpn file, I should comment out..

#down /etc/openvpn/update-resolv-conf
#up /etc/openvpn/update-resolv-conf

right? (it is in the .ovpn file given to me by my vpn)

-- 
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/ba054c38-c6f7-4245-8c38-e63f5d915d6f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: vpnleak or my vpn

2016-07-31 Thread eliwu
Maybe silly, but in my .ovpn file, I should comment out..

#down /etc/openvpn/update-resolv-conf
#up /etc/openvpn/update-resolv-conf

right? (it is in the .ovpn file given to me by my vpn)

-- 
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/c00874ef-bac1-4bb0-9329-24df29f0de4d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Yellow dot / guid crash in appvms

2016-07-31 Thread Chris Laprise

On 07/31/2016 04:32 PM, Marek Marczykowski-Górecki wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Sun, Jul 31, 2016 at 04:19:50PM -0400, Chris Laprise wrote:

ErrorHandler: BadWindow (invalid Window parameter)
  Major opcode: 10 (X_UnmapWindow)
  ResourceID:   0xe7
  Failed serial number:  179
  Current serial number: 179

The above error sometimes results when I start a debian 8 appvm (I'm not
currently using fedora appvms so I don't know if the problem exists there
too). My app window will not appear until I run some other command in the vm
(at which point the vm status dot turns green).


I'll determine whether this error can be reproduced.

Looks like this issue:
https://github.com/QubesOS/qubes-issues/issues/2085

You're using KDE, aren't you? ;)

- -- 


In dom0, yes. I do also happen to have kde installed in the template 
(completely forgot about that), but I do get this error when starting 
gtk apps.


Chris

--
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/bff2411e-df41-4579-669e-e8e4c468c755%40openmailbox.org.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Qubes Bluetooth (mouse)

2016-07-31 Thread Iestyn Best
Hi,

I am using a bluetooth mouse (Mad Catz M.O.U.S 9) via the sys-usb VM where it 
is passing through the functionality via some form of Qubes input passthrough 
to the rest of the system.

This seems to be working fine for me. The general functions of the mouse all 
seem to work fine; ie. movement, left/right/middle clicks, back/forward buttons 
and scrolling.

The one thing I haven't figured out, and haven't really looked into at the 
moment, is that it doesn't auto connect at start up. Each time I boot the 
computer I have to open a console for sys-usb and power on the bluetooth and 
then connect the mouse.

Just thought I would share my experience even though I thought it would be 
something that would cause more trouble.

Something I would like to look into in the future is the possibility of 
bluetooth headset. Could we get this connected to the sys-usb and have the 
audio, and possibly mic, passed through via some form of qubes audio mixer.

Regards,
Iestyn Best

-- 
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/8580a47e-190b-4f2c-9683-f5c1e9b98d93%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Install kde/plasma desktop in qubes 3.2rc2

2016-07-31 Thread Adrian Rocha
El domingo, 31 de julio de 2016, 17:53:01 (UTC-6), Marek Marczykowski-Górecki 
escribió:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> On Sun, Jul 31, 2016 at 04:40:16PM -0700, Andrew David Wong wrote:
> > On 2016-07-31 15:38, Adrian Rocha wrote:
> > > Hello all,
> > > 
> > > I installed 3.2rc2 from scratch and I can't choose the kde/plasma desktop
> > > not even as an optional software.
> > 
> > This was announced with the release of R3.2-rc2:
> > 
> > "Beginning with this release, we’ve officially switched from KDE to Xfce4,
> > which is now the new default desktop environment in dom0."

I remember this announcement, but, why don't maintain it in the ISO as 
alternative?

> > 
> > https://www.qubes-os.org/news/2016/07/28/qubes-OS-3-2-rc2-has-been-released/
> > 
> > > How can I install this desktop in this new release?
> > > 
> > 
> > Even though KDE was removed from the ISO, you should still be able to 
> > install
> > it from the repos. We don't have documentation for this yet, but if the
> > command matches Xfce, it should be:
> > 
> > $ sudo qubes-dom0-update @kde-desktop-qubes

Perfect, I'm installing.

Many thanks

> 
> Yes, exactly.
> 
> - -- 
> Best Regards,
> Marek Marczykowski-Górecki
> Invisible Things Lab
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2
> 
> iQEcBAEBCAAGBQJXno9WAAoJENuP0xzK19csi8UH/A6i8oGtJdTBd7C4f5QiHuER
> qwUCnXWbrPduaTL9SM7PLvzcyVx4HmD+pHbH3f4dy/w/ftJEf0bFRo/x1PIevzlZ
> zUTcwmFy7v8ToLiXwoeePRnNKOBV3GUuf+qRSVgNGn/dUv1ETmczGNvfODHG08wr
> AzPszYKxxLMEuGwxe65o6k++xkeGk4X3h6iiuLBHAJ7Rwxb0X9DkNSfsDPGj6Rb/
> 9K1hMgD77QwptpLbApW9l1Kkuk4UAQbll0q7khiO9xaeT1KF73tb6Okv6gXueR8j
> 3LDb02KN979KRtbb9EgQcEcLutoedOunXP2mgkDG2Xvq+TuRpE5YEsxmdLvwSIc=
> =18xI
> -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 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/65956c3c-bd7c-4fde-bd7b-a12355b2e1e9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Qubes server?

2016-07-31 Thread Iestyn Best
Hi,

I have been interested in an idea like that as I could see it beneficial for 
many organisations but currently I have had no actual driving need for it at 
this time.

I would be interested in hearing of something like this is happening or even 
possible.

Appreciate all the work the Qubes team has been doing.

Regards,
Iestyn Best

-- 
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/4e69dbb5-7f8a-4bea-b4d5-96329348ff42%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Qubes 3.2-RC2 - Sys-Firewall Not Found?

2016-07-31 Thread Ben Wika
On Monday, 1 August 2016 10:21:59 UTC+10, Iestyn Best  wrote:
> Hi Ben,
> 
> Do the rest of your default VMs install?
> 
> If not, you can retry configuration by calling 'sudo qubesctl 
> state.highstate' in a console in dom0.
> 
> This seems to be coming up as a common problem at the moment with the R3.2 
> releases.
> 
> Regards,
> Iestyn Best

I couldn't get past that screen at all (do get to Dom0 konsole) but I forget if 
I tried proceeding using the option to set up all templates myself.

I'll try again later and maybe try your suggestion.

Are we thinking this is something to do with rufus? maybe if I create another 
bootable USB from linux dd instead?

-- 
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/edf9c768-07d4-476a-8f94-95410e97b799%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Different version usr/src and kernel - Installink module aziokdb

2016-07-31 Thread Facundo Curti
Hi there. I'm trying to install a kernel module for my keyboard. But I'm having 
troubles when I have to install it...

I have a diferent version on /usr/src that the kernel.

ls /usr/src/kernels:
4.4.14-11.pvops.qubes.x86_64

ls /boot:
xen-4.6.1.gz
symvers-4.4.12-9.pvops.qubes.x86_64.gz
initramfs-4.4.12-9.pvops.qubes.x86_64.img
vmlinuz-4.4.14-9.pvops.qubes.x86_64

ls -l /lib/modules/4.4.12-9.pvops.qubes.x86_64/
build -> /usr/src/kernels/4.4.12-9.pvops.qubes.x86_64

When I try to compile aziokdb module:

make:
error /lib/modules/4.4.12-9.pvops.qubes.x86_64/build does not exist


I didn't put the entire output because it is from dom0 and I cant copy-paste as 
easy than with another vm. I made it manually.

Some idea how can I fix this? :/ I'ts possible to reinstall kernel without 
compiling it manually? It would solve it? :P

Thx

-- 
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/76a07c1d-6b60-43e6-9f0c-8eae18469688%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Battery Life Qubes 3.2 rc2

2016-07-31 Thread Peter M
Is anyone else noticing very significant increases in battery life with 3.2 as 
opposed to 3.1?

On 3.1 I was lucky to get 1h 30 min while with 3.2 I am easily getting 3 hours. 
I have an Nvidia Quadro graphics card so I am guessing some improvement in the 
nouveau driver is helping.

Anyone else want to share their battery life experiences?

-- 
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/6cb79850-62a9-462a-be7f-7266e58877d6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] [code] Testers wanted: Bluetooth dead man's switch

2016-07-31 Thread Andrew
Manuel Amador (Rudd-O):
> On 07/24/2016 02:29 AM, Andrew wrote:
>> Hello,
>>
>> I have made proper RPMs out of the dead man's switch code posted to the
>> list a few years back.  The code can be found here:
>> https://github.com/kbrn/qubes-app-dms.  Pre-built RPMs are attached.
>> These packages have already been tested on my machine and Work for Me™.
> 
> You need to document what the dead man's switch does on the readme.  I
> had to go read the source to understand what it does.
> 
> Also, frankly, trying to shut down the VMs gracefully is a life-dooming
> mistake.  Kill them using low-level xl commands or qvm-kill, then
> proceed to memory wipe.
> 

Thanks for looking.  I'll improve the documentation.

I disagree about the prudence of qvm-kill'ing everything.  One must
strike a balance between the consequences of killing everything on a
false alarm and the consequences of delaying a bit when really needed.

I'll make this configurable in the next version so each user can make
the decision for his or herself.

Thanks,
Andrew

-- 
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/a99863d8-d010-d869-4758-2fc4c4d83878%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Qubes 3.2-RC2 - Sys-Firewall Not Found?

2016-07-31 Thread Iestyn Best
Hi Ben,

Do the rest of your default VMs install?

If not, you can retry configuration by calling 'sudo qubesctl state.highstate' 
in a console in dom0.

This seems to be coming up as a common problem at the moment with the R3.2 
releases.

Regards,
Iestyn Best

-- 
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/44eaffd1-2b32-40ce-88d2-c1385e1ebfaf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: [3.2rc2] Default VMs failed to get created after installation

2016-07-31 Thread Iestyn Best
Hi,

This problem has happened even with RC1.

You can retry configuration by calling 'sudo qubesctl state.highstate' in a 
console in dom0.

I had this problem and it resolved it for me with RC1. I have not installed RC2 
from scratch.

Regards,
Iestyn Best

-- 
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/af083888-0603-4d17-af97-d149dde8078c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] [code] Testers wanted: Bluetooth dead man's switch

2016-07-31 Thread Manuel Amador (Rudd-O)
On 07/24/2016 02:29 AM, Andrew wrote:
> Hello,
>
> I have made proper RPMs out of the dead man's switch code posted to the
> list a few years back.  The code can be found here:
> https://github.com/kbrn/qubes-app-dms.  Pre-built RPMs are attached.
> These packages have already been tested on my machine and Work for Me™.

You need to document what the dead man's switch does on the readme.  I
had to go read the source to understand what it does.

Also, frankly, trying to shut down the VMs gracefully is a life-dooming
mistake.  Kill them using low-level xl commands or qvm-kill, then
proceed to memory wipe.

-- 
Rudd-O
http://rudd-o.com/

-- 
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/cea89dc9-166a-4245-5ba4-d287a976db9b%40rudd-o.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Install kde/plasma desktop in qubes 3.2rc2

2016-07-31 Thread Marek Marczykowski-Górecki
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Sun, Jul 31, 2016 at 04:40:16PM -0700, Andrew David Wong wrote:
> On 2016-07-31 15:38, Adrian Rocha wrote:
> > Hello all,
> > 
> > I installed 3.2rc2 from scratch and I can't choose the kde/plasma desktop
> > not even as an optional software.
> 
> This was announced with the release of R3.2-rc2:
> 
> "Beginning with this release, we’ve officially switched from KDE to Xfce4,
> which is now the new default desktop environment in dom0."
> 
> https://www.qubes-os.org/news/2016/07/28/qubes-OS-3-2-rc2-has-been-released/
> 
> > How can I install this desktop in this new release?
> > 
> 
> Even though KDE was removed from the ISO, you should still be able to install
> it from the repos. We don't have documentation for this yet, but if the
> command matches Xfce, it should be:
> 
> $ sudo qubes-dom0-update @kde-desktop-qubes

Yes, exactly.

- -- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJXno9WAAoJENuP0xzK19csi8UH/A6i8oGtJdTBd7C4f5QiHuER
qwUCnXWbrPduaTL9SM7PLvzcyVx4HmD+pHbH3f4dy/w/ftJEf0bFRo/x1PIevzlZ
zUTcwmFy7v8ToLiXwoeePRnNKOBV3GUuf+qRSVgNGn/dUv1ETmczGNvfODHG08wr
AzPszYKxxLMEuGwxe65o6k++xkeGk4X3h6iiuLBHAJ7Rwxb0X9DkNSfsDPGj6Rb/
9K1hMgD77QwptpLbApW9l1Kkuk4UAQbll0q7khiO9xaeT1KF73tb6Okv6gXueR8j
3LDb02KN979KRtbb9EgQcEcLutoedOunXP2mgkDG2Xvq+TuRpE5YEsxmdLvwSIc=
=18xI
-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 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/20160731235253.GN32095%40mail-itl.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: Qubes 3.2 rc2 has been released!

2016-07-31 Thread Marek Marczykowski-Górecki
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Sun, Jul 31, 2016 at 02:32:38PM -0700, Andrew David Wong wrote:
> On 2016-07-31 14:10, arthur.summ...@gmail.com wrote:
> > Two questions: 1) Do you have a list of specific things that you would
> > like users to check based on changes/fixes you made from RC1 to RC2? I've
> > got RC2 installed and would gladly provide feedback.
> 
> Thank you for offering to test it! It would be great if you could specifically
> test the new changes from the previous release candidate. (Marek, do we have a
> fine-grained way to view those changes? It looks like our lowest level of
> granularity is point releases, e.g., R3.1 to R3.2, but not R3.2-rc1 to
> R3.2-rc2.)

Indeed, we don't have such high level list. In fact the only real change
was switching away from KDE. Besides that, only a lot of bug fixes.

> Here are the release notes for R3.2:
> 
> https://www.qubes-os.org/doc/releases/3.2/release-notes/
> 
> As that page points out, you can find more detailed descriptions and
> discussions in completed GitHub issues with the "Release 3.2" milestone:
> 
> https://github.com/QubesOS/qubes-issues/issues?q=is%3Aissue+sort%3Aupdated-desc+
> milestone%3A%22Release+3.2%22+label%3Arelease-notes+is%3Aclosed
> 
> (But as I mentioned above, this doesn't really distinguish between changes
> that occurred in R3.2-rc1 and R3.2-rc2. I think it would still be helpful to
> test both, though.)
> 
> > 2) As a new user to the community, where is the preferred place to post 
> > bugs? So far, I've just been dumping them in the qubes-users section (I 
> > reported my snd_hda_intel issue), but I'm not sure if that's where you
> > want them to go.
> 
> Thanks for asking! All bugs have to go into qubes-issues on GitHub eventually
> so that we can track what gets fixed, so if you're certain that something is a
> bug and you don't mind using GitHub to report it, please feel free to open an
> issue on GitHub. However, if you're not sure that something is a bug or if you
> don't want to use GitHub for any reason, then it's perfectly fine to write to
> the mailing list instead. (Not a big deal either way.)

Yes, exactly.

- -- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJXnoz7AAoJENuP0xzK19csIpAH/0xS5qPXuDnpGZwnYCf6Mx9a
tBPupuJxg99ls6eUvh34lf3wQQxQQlq7usH62DIheCdtd4fUKrjRFoRQt4GipgBo
unTSGbtH1ctg2zn+LLmNpKRxWP9A25bvjXBH2DPWXVxvbKpQv8LBhB5m1V2epBqV
lxxoOoIb3N/OBJgD0+R7wdY0+WnlFiDBxfpIAXWdV+Ste0ZfNKZuKSyT/zPXWr83
VKGXXgXn0tiitGwTP5iNXHxf0bvE/Rz/XJGsAuTNx0HHR5fZriaocwt2uuqLpuf9
t27sEdX1aJ85AulqAMi6zEpDYZHReWW7GJOJymUpVRWuhdurNZVHxZkTXLsMapI=
=4Ajf
-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 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/20160731234250.GM32095%40mail-itl.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Install kde/plasma desktop in qubes 3.2rc2

2016-07-31 Thread Andrew David Wong
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-07-31 15:38, Adrian Rocha wrote:
> Hello all,
> 
> I installed 3.2rc2 from scratch and I can't choose the kde/plasma desktop
> not even as an optional software.

This was announced with the release of R3.2-rc2:

"Beginning with this release, we’ve officially switched from KDE to Xfce4,
which is now the new default desktop environment in dom0."

https://www.qubes-os.org/news/2016/07/28/qubes-OS-3-2-rc2-has-been-released/

> How can I install this desktop in this new release?
> 

Even though KDE was removed from the ISO, you should still be able to install
it from the repos. We don't have documentation for this yet, but if the
command matches Xfce, it should be:

$ sudo qubes-dom0-update @kde-desktop-qubes

- -- 
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJXnoxgAAoJENtN07w5UDAwTC8P/0p/JpdQP3szMX3wbL4rTwp8
EKm7XG35xw8roI6GujcWmjIxcYWf8DzUdI13e2Bn6B7vqGBocFpGtE3v0/8ynOA0
0nZ8hCRgGlGeotejt8NYjEXxuTUHfY9AB8lcbqgjnA5MQzTU3TRzwLe2Wg8Jco2E
blb5VxI+HSt5MfNXwXSxFmch88UNijrKYwnvECtPwrRGJxFi39/f/8ffWAUWbeAn
fTzGk/Df7P1aqJyc52cZNYTRpY2g3879BvyQQBSugp3rHBOpNvPUPFUcwaBJslhT
HgJplSENxMPqzPk4Kn0X7U9MZYlPdTRVixnLoSyFdzsZJrvX7wfYmNTrUQbd9+Kj
ajeeObjYZ0gSOsmHrauE0hzlKMDcYnd39TLHnMmk2ITykxEqLbN1hE5rAjV18rf3
Rf2QTuXpUATm7J2cfFbxBdLcfeSdsQSR2X9+hshA9vzu++3nTZhv2i3ATSIu98pX
0z5EeRdeboKjCr56nsQ0ylja8I+29ycH1lxqjAemZJoDd6I5odlQ7kSVlfk19w7j
Q1ZMMu4owucEdBJb+8dmldYlNZCPO3/aWEmqqMxv9/BW5eYEZ7CyYItwKn1DdcPx
mWMS0OMlAl+QY1fqqt7K27pwnT8w9H4sR0phMPmtS8iR2JW0OvjiBBOI8G37rINA
/qzl6LkBshz3/aN9aIXD
=NKX2
-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 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/c6a78dc0-2db9-b662-ac30-74ee06b57f60%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] AEM with Linux 4.4 causes hard reboot (cont... Trying to resolve issue)

2016-07-31 Thread Marek Marczykowski-Górecki
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Sun, Jul 31, 2016 at 02:45:42PM -0700, Andrew David Wong wrote:
> On 2016-07-31 13:45, Andrew David Wong wrote:
> > On 2016-07-31 13:42, Andrew David Wong wrote:
> >> On 2016-07-31 13:38, Marek Marczykowski-Górecki wrote:
> >>> On Sun, Jul 31, 2016 at 01:30:42PM -0700, Andrew David Wong wrote:
>  On 2016-07-31 10:41, donoban wrote:
> > On 07/30/2016 11:52 PM, Marek Marczykowski-Górecki wrote:
> >> On Sat, Jul 30, 2016 at 02:44:24PM -0700, tel wrote:
> >>> Sorry for the delay, Chris. I was waiting for 3.2-rc2, which I
> >>>  just installed. It seems to come with the latest AEM package,
> >>> so I didn't have to install that package myself.
> > 
> >>> I added the parameter to the tboot line. It didn't reboot, but 
> >>> it hung before asking for the password with "Waiting for 
> >>> /dev/disk/by-label/aem* to be connected..."
> > 
> >>> Not sure where to go from here.
> > 
> >> Do you use also USB VM? In that case, dom0 has no access to USB 
> >> controllers...
> > 
> >> But you can re-enable it just for boot time by editing 
> >> /etc/default/grub and removing the line with "hide_all_usb" (or 
> >> just comment it out). Then rerun `grub2-mkconfig -o 
> >> /boot/grub2/grub.cfg`. It will expose dom0 for all connected USB 
> >> devices for a short time during system startup.
> > 
> > 
> > 
> > Nice, this should be added to: 
> > https://www.qubes-os.org/doc/usb/#tocAnchor-1-1-4
> > 
> > With some warning: "Caution! Enabling usb-vm with LUKS encryption
> > and a USB keyboard could stop you from booting your system"
> > 
> > :)
> > 
> > 
>  If a USB keyboard is detected, the installer does not allow the
>  option of creating a USB qube, so it should not be possible for a
>  user to accidentally get him- or herself into this predicament.
> > 
> >>> But using USB qube will not stop you from creating AEM usb stick (or
> >>> the other way around).
> > 
> > 
> >> So, the problem is that if rd.qubes.hide_all_usb is added to grub.cfg
> >> when the USB qube is created, but the user later decides to create an AEM
> >> USB stick, then the user must be told to remove rd.qubes.hide_all_usb, or
> >> else it will not work. Is that correct?
> > 
> > 
> > (And, as you said, the converse: If a user creates an AEM USB stick, then 
> > later decides to create a USB qube, they should be warned not to add 
> > rd.qubes.hide_all_usb to grub.cfg.)
> > 
> 
> Ok, added a new section to the USB documentation explaining hiding USB devices
> from dom0:
> 
> https://github.com/QubesOS/qubes-doc/commit/15d418b778a8879323091c79fdc1084d
> ecb890cb
> 
> And a pull request to the AEM README with a warning about using an AEM USB
> device with a USB qube:
> 
> https://github.com/QubesOS/qubes-antievilmaid/pull/15

Thanks!

- -- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJXnoZVAAoJENuP0xzK19csQYQH/jU8vL8JPtg0cBe2fXxtfLr9
mZPclxrW1qctpsHDcgxWz5guWMEcwhTC2YwOHgI5RYnzc5Q68QWGIIu/G/JjYybt
oyBVi6WXvL1ZFKjMXASn7u9Xx4/FdFi4OHw9Kob7DMiFiH2QAn9shfTzyEPoffLu
dYDi2QiMsyQVsotH54/W28qUqdZ8ibnKJiksoCqLMCoueRQCOV4IxF8aYblQ16wz
PpXFd9F59OKnTiV+Q1qiIWV502kOqbUMbE1dGRNgx4JTH/pMB8tUXOWxz7y+tHwX
YfhRaxBAkcoveqmwnc/idlENwR6Lb+egLvvQzkflTGJ4TW/n2epX/qNDJ4xOzic=
=iolQ
-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 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/20160731231428.GJ32095%40mail-itl.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Qubes 3.2-RC2 - Sys-Firewall Not Found?

2016-07-31 Thread Ben Wika
On Monday, 1 August 2016 08:56:42 UTC+10, Ben Wika  wrote:
> Hi,
> 
> Whilst I ignored RC1, I thought I'd give 3.2-RC2 a try, but when it gets to 
> the installation stage of setting up all the default templates, I can't get 
> passed this screen.
> 
> No matter what combination of pre-installed templates I select, so long as 
> the box to install sys-net and sys-firewall is checked, whilst setting them 
> up, it just keeps giving the error message that sys-firewall is not found.
> 
> Also, with the changes in USB handling, is it now safe for me to set up a 
> USB-qube given I have USB mouse?   (PS2 keyboard, on-board cabled network)
> 
> Ben

https://github.com/QubesOS/qubes-issues/issues/2213

-- 
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/b322a7fe-3b9b-4981-bcd7-bf6d97863114%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: [3.2rc2] Default VMs failed to get created after installation

2016-07-31 Thread Ben Wika
On Monday, 1 August 2016 08:58:31 UTC+10, Ben Wika  wrote:
> On Monday, 1 August 2016 07:21:59 UTC+10, koto...@gmail.com  wrote:
> > Hi,
> > 
> > I gave up on installing on a USB stick and managed to get my hands on a 
> > second disk and installed Qubes on it. Everything went fine but after the 
> > first boot when configuring the VMs the following error appeared "A VM with 
> > the name 'sys-firewall' does not exist in the system".
> > 
> > Can I somehow restart this configuration process without reinstalling 
> > everything? Or how can I create the default VMs (personal, work, vault 
> > etc)? Has someone experience the same error?
> > 
> > Thanks for your help & thanks for your work!
> 
> Just posted the same error.

https://github.com/QubesOS/qubes-issues/issues/2213 

-- 
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/8c838a72-3efb-4ff5-81c4-744501f4f040%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: What do you think about the idea of a FileVM?

2016-07-31 Thread Ben Wika
On Sunday, 31 July 2016 10:11:18 UTC+10, Manuel Amador (Rudd-O)  wrote:
> On 07/30/2016 12:12 AM, arthur.summers wrote:
> > I agree with the idea of having an option for a storage VM, but my 
> > agreement goes a little deeper (and forks a bit). I know that the primary 
> > goal of Qubes is security, but there are a lot of different use cases for 
> > it. I use it because I like the compartmentalization provided by VMs. 
> > Security is almost a secondary for me - I wanted a bare-metal client 
> > hypervisor. Since XenClient no longer exists and no other offerings are 
> > well maintained, I landed on Qubes. For my purposes, sharing storage would 
> > be great, but baking it in DOES defeat the primary goals of the project.
> 
> I'm not necessarily sure that conclusion is foregone.  Perhaps it's a
> good idea to provide a vchan-backed FUSE file system that allows a VM to
> "mount" the subdirectory of another VM.  This would require a few things
> UX-wise, but it's totally doable otherwise.  Of course, the mounting VM
> would need to trust the mounted VM, but it'd be quite good otherwise.
> 
> Failing that, a mechanism to provide networking between VMs, such that a
> VM can serve another VM via SSH or CIFS, would be okay.  Sometimes I
> think that the networking model in Qubes is far too restrictive.
> 
> -- 
> Rudd-O
> http://rudd-o.com/

I too am a little unsure of the best practice for accessing my cryfs encrypted 
google drive (insync) folders.

Currently I sync to a secondary drive that I can just mount in whatever VM I 
need. But there always seems to be that risk of sharing one drive across 
multiple VMs at different times.

Is there a clear advantage (security or convenience) in just setting up a 
CloudVM and using network sharing to access it from the other VMs, vs just 
mounting the drive on one VM at a time?

Ben

-- 
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/12df9ee4-50ff-4ba7-b4a4-c2d629c06038%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Install kde/plasma desktop in qubes 3.2rc2

2016-07-31 Thread Ben Wika
On Monday, 1 August 2016 08:38:32 UTC+10, Adrian Rocha  wrote:
> Hello all,
> 
> I installed 3.2rc2 from scratch and I can't choose the kde/plasma desktop not 
> even as an optional software.
> How can I install this desktop in this new release?
> 
> Best Regards

+1

-- 
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/ac4602b6-17c9-4f43-ab52-b1bcfa229871%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: [3.2rc2] Default VMs failed to get created after installation

2016-07-31 Thread Ben Wika
On Monday, 1 August 2016 07:21:59 UTC+10, koto...@gmail.com  wrote:
> Hi,
> 
> I gave up on installing on a USB stick and managed to get my hands on a 
> second disk and installed Qubes on it. Everything went fine but after the 
> first boot when configuring the VMs the following error appeared "A VM with 
> the name 'sys-firewall' does not exist in the system".
> 
> Can I somehow restart this configuration process without reinstalling 
> everything? Or how can I create the default VMs (personal, work, vault etc)? 
> Has someone experience the same error?
> 
> Thanks for your help & thanks for your work!

Just posted the same error.

-- 
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/59e4fa4f-d8d1-4425-a4d6-9df1ef1a4d00%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Qubes 3.2-RC2 - Sys-Firewall Not Found?

2016-07-31 Thread Ben Wika
Hi,

Whilst I ignored RC1, I thought I'd give 3.2-RC2 a try, but when it gets to the 
installation stage of setting up all the default templates, I can't get passed 
this screen.

No matter what combination of pre-installed templates I select, so long as the 
box to install sys-net and sys-firewall is checked, whilst setting them up, it 
just keeps giving the error message that sys-firewall is not found.

Also, with the changes in USB handling, is it now safe for me to set up a 
USB-qube given I have USB mouse?   (PS2 keyboard, on-board cabled network)

Ben

-- 
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/d62ed862-72dc-4933-9c9b-ced541a8eb3b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Is a legacy BIOS preferable to UEFI for a secure system?

2016-07-31 Thread Stephen Moreno
Hi,

I'm looking to build a new desktop system for Qubes. In an ideal world I would use a motherboard with a Libreboot open source BIOS, however this is currently not practical.

I am therefore intending to use a motherboard with an AMD AM3 chipset, to at least avoid the AMD PSP and Intel ME technologies. This would either contain a proprietary legacy BIOS or a newer UEFI BIOS. My question is, what would be most preferable for a secure Qubes system?

It is my current understanding that once a legacy BIOS has finished initializing the hardware, it hands off to the OS and no longer executes. In contrast, a UEFI BIOS has runtime services that continue to execute while the OS is running.

I was therefore coming to the conclusion that if the BIOS was compromised (and it could potentially be compromised before I received it), then a system that could only run a legacy BIOS would be preferable, as it could theoretically do less damage.

The Wikipedia page on UEFI also states, “UEFI can support remote diagnostics and repair of computers, even with no operating system installed”. (https://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface)
This has me further concerned about UEFI in a proprietary form.

Are there any benefits of a UEFI BIOS that would outweigh my concerns?

Any input on this topic would be much appreciated.



-- 
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/trinity-f83af5b0-0cdc-432f-840a-ed28630a4556-147000484%403capp-mailcom-lxa08.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Install kde/plasma desktop in qubes 3.2rc2

2016-07-31 Thread Adrian Rocha
Hello all,

I installed 3.2rc2 from scratch and I can't choose the kde/plasma desktop not 
even as an optional software.
How can I install this desktop in this new release?

Best Regards

-- 
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/52669c85-3697-4132-ba94-19f4c58ace08%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] [3.2-rc2] issue with detaching usb flashes fat32

2016-07-31 Thread Andrew David Wong
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-07-31 15:20, Eva Star wrote:
> 
>> 
>> By "ALL ICONs from ALL domains," do you mean all shortcuts to start
>> programs in AppVMs?
> 
> Yes, sure. But without sub-folders. See screenshot (only header of the
> list):
> 
> https://i.imgur.com/3qk2Cl7.png
> 

Thanks. Tracking:

https://github.com/QubesOS/qubes-issues/issues/2217

- -- 
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJXnnyAAAoJENtN07w5UDAwZawP/1Tz3X7FObrZJRASs7s3Rq4y
ov96T0qkqm881KRVmJowhPE6H4XhPzAhRA4EcsU8+B4PQKH/9rTMXxpnd7tJyiG7
v3ZBkd/VclD+Y5tPfkIQ/eGRZb31r4h4DSKPhACih+xGnSf0Uxlon5qtJ5tatVh2
3luKZAN6kqbq62AQvd2ldRiYkTbecAK7XKktz0CJawmCFvUO1xIeczOFkwhymmxT
Rg234aym+bRNphoMEowTV+ldBDXY/ZFIlMjS8EUgJ1tUCJgnNjJJUKYAszDzoQk6
ZRcDybqOOi+mb9rnPDdmqifn2JdgFSNcyHrlLZ0vZqP6AmKhuU0j+TjV1X8NEmMi
CjStl7FtgQBrwTIfcTxW5WCA27pW8B6LgFk3dupo1OCwidThQAJx+ymD/7O8b/D0
gfs/rU3ftnwQ6NzYBGz0BVpAWsmVtYK3+KOaRH6Vc+zGAil+BrhpcACWAxr7mY45
b0JYCynCPDcaYpwFQ7ENonVnjXbDZIaSJxg55BR72QkiX3eLKnjTUE5LxPVam1CW
uY2oqazgwxZ0rXxkrQtauHZ2FJimFyT2Vw5Y7QecNlJA2Imhik3uyYDs7/VM1AX1
RyuKF6PYnMSQwR/6cEkUnX1wgViAPXUPp63B1Q+17t6MDqHCxGHIgLzV5CEok+sM
cYJg4hrzXNaqQLH5UUEj
=E9ms
-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 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/68b0e14d-8735-44f7-ea0c-13aeb0f9533e%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] [3.2-rc2] issue with detaching usb flashes fat32

2016-07-31 Thread Eva Star




By "ALL ICONs from ALL domains," do you mean all shortcuts to start programs
in AppVMs?


Yes, sure. But without sub-folders. See screenshot (only header of the 
list):


https://i.imgur.com/3qk2Cl7.png

--
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/e29b002c-13d1-b57e-b432-af6a70493d4b%40openmailbox.org.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] 3.2 RC2 - laptop screen lock bug

2016-07-31 Thread Andrew "Arthur" Summers
I attached the output of dmesg after I removed the "fix" I made. I also
included the output of lspci. Marek would probably know in better detail,
but it seems like the sound card's misconfiguration is causing the system
to wait for it to respond. Since it never responds, the system doesn't
sleep, there is a bit of a delay during startup/shutdown, and I obviously
have no sound.

On Sun, Jul 31, 2016 at 5:02 PM Andrew David Wong  wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> On 2016-07-30 16:11, arthur.summ...@gmail.com wrote:
> > Ah, right you are - it DOES have to do with the sound card. My system was
> > failing to go to sleep when I closed my laptop lid (I actually hate that
> > setting). This was because my sound card wasn't configured properly. I
> > couldn't launch any of the audio mixer programs, and dmesg was giving the
> > error: snd_hda_intel :03:00.1: Cannot lock devices!
> >
> > I "fixed" it with the hack of adding the following to a modprobe.d conf
> > file: options snd-hda-intel enable=0,1,0
> >
> > Now, the system goes to sleep properly when I close the lid. However,
> > since my sound card worked in 3.1, this means that there is an issue with
> > the snd_hda_intel module in 3.2 RC2. Do you need more info about my
> > system?
> >
>
> I've been trying to think about how we would file a useful bug report for
> this, but it seems like there's not much to go on (yet).
>
> Can we say anything more concrete than just "the sound card worked in 3.1,
> but
> it doesn't work in 3.2-rc2"?
>
> Is this an accurate summary?
>
> "Standby works by itself. The sound card works by itself. But standby only
> works when the sound card is disabled, and enabling the sound card causes
> standby not to work."
>
> Also, did you already give the exact model of the sound card?
>
> - --
> Andrew David Wong (Axon)
> Community Manager, Qubes OS
> https://www.qubes-os.org
> -BEGIN PGP SIGNATURE-
>
> iQIcBAEBCgAGBQJXnnV4AAoJENtN07w5UDAwMCoQAIAwDkrWt5POuB+osrEuqoT7
> CIoofWTqNEJHGSX5TiKR3fWwnI8ZEGnZ6SyRxVe2OK8+crloJXSOTWdBGhVS5cAh
> NH0XflsIMYNmIusiZXYWRX/CVWdblgYSqNUz1RLVPX3xNIDUiKyMcI4XsXJU0v1C
> b8QhkR1ZlWiG3eOpkYHeAefL6ft9YvfbkZ88OD3NmLGfqcvXrkNt0FY/wXbJkSNf
> 8AJxtuxdzLXiKAUpqh051CHYgS8AWPm/w2XbiLlNkQ/PBvrJfIUCbxyN4VVaA3+R
> zkDekvJg/f27Og9Z9a8RyZeAC85T/ma3175dd9r7KBY7ARXGXFnBj2gtBYPDzNRw
> tXX7JNTy5OSRUNDzBkqmX+UGeehpM5ysaHminpjKT6FFrpOc7d9gTLQsPa+2VP0S
> odtM99nKao2YUolqy4H4NiVxkBAmWiXP2g4fpZ5Znu2q9vlcVVg4VbnGt1PgS8Um
> dhnTt6dRQH0Ncj6e8rqhdR248LfB6qZ0cM2ZLiBLDLHqJpaCCcGKIsIWlTnF2LbH
> b9XLrkRMsEu7jPjlhwAvW5oulavRcJUUhfqo/j1n+VPnbr8r+WZ3EOezfrubzng3
> csTL3iYyEJ6yOa6jWC0WKAUCH65aA6Y+jBdeC/DrLwR+Z7+CZiRcBRRDjgORfB3U
> nNReYlHx3aOVaNlZczHt
> =lpN0
> -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 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/CAP0YRgagOqSYL-Wo4atJ%3D-PJ7o%2BJYCo942RVk9dX89TGXqVi-g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


lspci
Description: Binary data


dmesg
Description: Binary data


Re: [qubes-users] [3.2-rc2] issue with detaching usb flashes fat32

2016-07-31 Thread Andrew David Wong
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-07-31 15:13, Eva Star wrote:
> 
>> Which style/theme are you using?
> 
> Does not know. Now I tried to find the answer at my System Tools menu and
> found that ALL ICONs from ALL domains also show on "System Tools" list :)
> Is it tracked?
> 

By "ALL ICONs from ALL domains," do you mean all shortcuts to start programs
in AppVMs?

- -- 
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJXnnhbAAoJENtN07w5UDAwrUQQAL6EPBw+/XZgCSA0ZwNcUcJ1
jfC4cBK1kYNHQJyzRGqZXWCaO9xa7orHUKFjDYFNZkniiBOa7SGSY5uo0jQCfjXG
DpUrZYNrR4zaH3e6ZGrA5vSg0dmVez7W3csPbobSez0KY+BwXMsI3rKvhm/9T9w4
CAsNqPK2loKlJCrHVxINkOGeEjTxR3/R9IPNG5IKPdMAWmIVq6xQZ+PmWa3WS6Qo
9zqkHukWzcKZMzTnUJ2XK+Ertm1QIBx9pCZ9yhFygQ1sRp0pFZWwc6W5tGcf8u9B
bA4x91QUceosZkt4yB7S5xVriQOhU8KN2MczYDuRyVOi3q5c1LmoqJ81hIpil5vX
O1tSB7Crp24zH3rtj0vSvAM+tLROAVQjE2qygCqbBRZJkR8n18Limw0RoFp5IhyV
t+2m1szMEK5t0E+Lrkm9tSdq0dwb8Pci5r9SBmnzlCiQtDcxoIEMXueeLXFrPx0Z
IABbxpSLcc1D+DRc7FMx5QeizJyLtrLHPj2xqy3A0FuSrG2PSu5Ub2mpcA5ra/rH
z+EV1CIPtQWG3xQxgNgcE2V+AJiP6ipAUNOHtdGK+XVB5DPoVqCPnhhZpZiDvSQP
F3/gmd0NUnJzwzwX7BxH0z62ahPdL7qpGLQ0a8Cz7yI1pMmkZikhJHrK6OMRLpdd
mS3mHLQPaA7CEhsDknKu
=cx2o
-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 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/a87e705c-e1f4-6bcd-6ff4-21ad2195af43%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] [3.2-rc2] issue with detaching usb flashes fat32

2016-07-31 Thread Andrew David Wong
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-07-31 15:06, Eva Star wrote:
> Does not know is it normal or not? But "Klipper" icon is transparent:
> 
> https://i.imgur.com/VKQ3aeW.png
> 
> On scrreenshot, "Klipper" icon before sound icon.
> 
> 

Tracking:

https://github.com/QubesOS/qubes-issues/issues/2216

- -- 
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJXnnfgAAoJENtN07w5UDAwAk0QALYNEznbKj+6DwIwmAjAlc2h
Ao14nDJqnm5zF8j5pm0fSZZC/IffDzytBezrs+/Mywofn31tVpMpM4PcT6GH2WM1
mghF0N7TopNFbY4ZAH6SP2314xKl83Sh92WngbkfY7obbqzhjb3KMPFQrY4Gi/mZ
X4vdsF4G2FwTbKRvU5rlYZyTByxPdc8ksoNxhvbogO6MDbTprrHYUFgB6zaxKc2N
DCvbON4EuN3NwFUa/JFBetGYBcXhWw3thH0gwz20n34bxuFDfFQAZTmBvUrWWL2T
EhvxQ5M2wDa3ZwJltSrkEbDDGDFwBe4L4xzwGBHKIw2fIAeK0N6HOR1VGTdUFCQq
wczBXGtnTXBosowMRDB9KVALqAImrNcgIqtizd7vP82/U7g9Wj0dLZG0V15pfXUA
LeifTAzTdHjqY5YiJIKQepvqmb8EeU0MsJ3g96qLUsqrO3PKYO5gpKGVPljph7/T
XvBfSDD10n9lq7LskXv3pulDBnZzKeXe7Lyojh91U07yURtB55j8eRbGs+AHnVC8
UzyoA5V7DtBzKHv85aUaEp6D99ttZTKKxtkNNgUstj45A0fEzT8Kfw6cELEIVAj5
Xu1Jvi1JAhnPWE3+xodina6EjzjaUSspCpndscIlmG17STUgZgFWT54hKhF62t7Y
DVxVQhcTF2qryi+fQLo5
=ROPx
-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 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/f64ec36c-5ccd-e9e1-d13f-4a00e099b491%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Configuring OpenDNS in Qubes

2016-07-31 Thread Qubed One
m...@lamarciana.com:
> Hi,
> 
> I'm trying to figure out how I can change my DNS settings for an
> AppVM. I'm relatively new to Qubes, so other related issues in this
> forum have clarified me some ideas but I am still quite puzzled.
> 
> This is what I have done so far:
> 
> 1 - I have created a ProxyVM, which in turns connect to sys-firewall
> as NetVM. This ProxyVM uses debian-8 as template, because I'm
> following some tutorials in Internet about networking stuff using
> kali linux (configuring OpenDNS is one part). This ProxyVM is a
> StandaloneVM in order to keep changes in /.
> 
> 2 - I have added to it network-manager service
> 
> 3 - I have edited /etc/dhcp/dhclient.conf in my ProxyVM and I have
> added the following line with OpenDNS IPs:
> 
> prepend domain-name-servers 208.67.222.222, 208.67.220.220;
> 
> 4 - I have connected my AppVM to this ProxyVM as NetVM.
> 
> 5 - I have restarted my ProxyVM and my AppVM.
> 
> Now, I thought /etc/resolv.conf in my AppVM and ProxyVM should have
> changed. But no, they still have:
> 
> nameserver 10.137.5.1 nameserver 10.137.5.254
> 
> I see that my AppVM takes its /etc/dhcp/dhclient.conf from the
> ProxyVM, because that line is also added there.
> 
> Going to https://dnsleaktest.com confirms that I'm still using my ISP
> DNS server.
> 
> I guess that there is a way to do that without having to create a
> StandaloneVM for my ProxyVM, but I tried to do everything manual to
> learn how everything is tied. But anyway it doesn't work...
> 
> Thanks!



If I understand correctly, permanently changing /etc/resolv.conf in the
ProxyVM to show:

 nameserver 208.67.222.222
 nameserver 208.67.220.220

should achieve that in a standalone ProxyVM.

Were it a TemplateBasedVM, you could have /rw/config/rc.local copy a
file containing the above two lines to /etc/resolv.conf on boot
(replacing /etc/resolv.conf), then call
/usr/lib/qubes/qubes-setup-dnat-to-ns.

I haven't tested this myself on a standalone ProxyVM.

-- 
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/687d366a-c5fe-dd4c-4354-74f2373f72e2%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] [3.2-rc2] issue with detaching usb flashes fat32

2016-07-31 Thread Andrew David Wong
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-07-31 15:02, Eva Star wrote:
> Also issue with colors. Yellow color was fixed. But black color now at rc2
>  damaged.
> 
> https://i.imgur.com/OrZcNJ0.png
> 

Known issue:

https://github.com/QubesOS/qubes-issues/issues/2120#issuecomment-231750733

Which style/theme are you using?

- -- 
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJXnnb4AAoJENtN07w5UDAwj04P/2Cd/3XVy//pT05ycy0b6Ev8
tJOr2A5aLscfvsqWJtYFnTKAXqkBW77G7b88ouVa8aW9C2G+HgM9+DUkUgSyMmSt
MrKmojJbMmZtXhtFoU4fWykb0sqRRZz/7LV96ebJhguqXmYrDXZLdXZKUMJjbr3C
13KA6RdDbdPzYbJMtY1pVcPWYRNeueXo3nGHh5rZUcdtpY/83n+/uXlbMg3i3lr+
FIXM9XbX7qQknJHcgPtx3TpM3/uQNHodlsRJeLPvP3tx1lHR5X/WUh/21HEdrXBa
xQnJz/EUw1M4EfkrH8NvBZXJ034GI9oTbQ/mtymUDd1jiHE9jcq0MfsShshjqfvL
dTJlPSLt/qmODHIA9DCLI9RsVTn7tvXGROxI9duthhMbEwKQjnC6VRWzJFbowQqA
abj9ngHBHMyDxbAai1RpLrxqt1HTif8QJTWVgQGZTtAhJ2Rdfr+iWuY1Y8LU/YrL
U1c8mHjdlpf1URppTDLWZ8JglU+q1AnqMxiGdjh3mB75vf3QhStbAFqkiG0Eewxp
eonnq0f4x/PkOaLuWRq5yEvgbh/yMlJ8We5QY8JaaHQuUvlmhaCxdH9TXBkvdaSz
pmvgIFc893fmpD3HVtLUY784UwhVOjVLdM3FF3T6Oc9bZvoeaKIu5ES1dKgjCBCf
KN2mlNQLa7h9/W96SKJ/
=ymq0
-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 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/a4b2c31a-5d76-395f-7b46-feee5341b17c%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] [3.2-rc2] issue with detaching usb flashes fat32

2016-07-31 Thread Eva Star

Does not know is it normal or not? But "Klipper" icon is transparent:

https://i.imgur.com/VKQ3aeW.png

On scrreenshot, "Klipper" icon before sound icon.


--
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/452c5988-6dae-9402-34b3-0e3837dbe35b%40openmailbox.org.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] [3.2-rc2] issue with detaching usb flashes fat32

2016-07-31 Thread Andrew David Wong
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-07-31 14:58, Eva Star wrote:
> If flash card was attached to VM, then it can not be detached, Related
> error message: https://i.imgur.com/fPARrpk.png
> 
> 
> I guess it's related only to fat32 usb flash.
> 
> Details: When usb flash attached/detached first time, I see only error
> message with title of the windows like on screenshot, but without message.
> Next, I remove flash from usb port and Qubes Manager ask to restart. After
> restarted I see unattached flash on the QM. When I tried to detach it next
> time got the error on the screenshot.
> 
> Thanks :)
> 

Already tracking here:

https://github.com/QubesOS/qubes-issues/issues/2094

Added link to your thread.

- -- 
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJXnnZLAAoJENtN07w5UDAwlxkQAJ3Uc5qwjI83A4WrqjndNdNV
abT7/DyLvJLmS51r8LD/9imGv+q/B33+eNZUa+UL/AyoDpn9Xo/4w4mCYLcn7x33
nHgC2jx8fHC9Snow7NjFddnXKrFgGEHc14FTw+/uogxqjpBQ8TShU+amf/uHUoUq
Vdo6MmbKs1/YyE0vducnYEiRDzc6KYg4Sx8otJ43E6oer4M7ErsupG2Ovbamu0T9
2ctlB2t3Ey3wqPIq1F2NPqlDdU1dwJkSFc4ZKS/Gqhnl813UCCUjXEW56XRh82j4
meGdrr8OW0cMkMPdpt2CVQEkclrFtQND65RAW/9REXRxWhEoSq39DFedFp/nrG/z
bMskyhzkp2wO3sjRIMn0iJ502YxyVyQqLNTZLF0b6BgmPZF3ZveFfWYBIAm6KbLS
/2LHYK+qgyzf+9gAb+bbsYQkAD+p6Xre8ZdMUmkeMGsEcvbe5LXPLYb7uO/xE2Q1
q7k8i9K7/5SXHTgke6mBMhDmQ5bxTEeL6kiGSW26RARsfTBzTddhKyvYQxS9mK4M
UVQMwfl0+XmZgV7sKOQvaMQa7hypEAs7uZwVWB1KonGTlX7QdDo4xYPF16s9iRXY
7QR6BnEkAUfWAqPsBjKpqX92VcNs5MQ/os1vAR9ovrouwRIqGwaX3tbev6Uzo2PF
v6Bb1ynkA0Y+BwtAp4KJ
=M5sx
-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 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/c076b749-719b-e34b-36a3-245aaefa336a%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Qrexec-daemon not always loading

2016-07-31 Thread jmarkdavis86
Entering sudo xl console sys-net returns "sys-net is an invalid domain 
identifier (rc=-6)‎." this does not work for any other vm.

Status of qrexec agent returns:
Loaded: not found (reason: no such file or directory)
Active: inactive(dead)

Trying to start qrexec agent returns
Failed to restart qubes-qrexec-service: unit qubes-qrexec-agent.service failed 
to load: no such file or directory.

-- 
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/33c72ab6-cd67-4407-877f-176859380cd4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] 3.2 RC2 - laptop screen lock bug

2016-07-31 Thread Andrew David Wong
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-07-30 16:11, arthur.summ...@gmail.com wrote:
> Ah, right you are - it DOES have to do with the sound card. My system was 
> failing to go to sleep when I closed my laptop lid (I actually hate that 
> setting). This was because my sound card wasn't configured properly. I 
> couldn't launch any of the audio mixer programs, and dmesg was giving the 
> error: snd_hda_intel :03:00.1: Cannot lock devices!
> 
> I "fixed" it with the hack of adding the following to a modprobe.d conf 
> file: options snd-hda-intel enable=0,1,0
> 
> Now, the system goes to sleep properly when I close the lid. However,
> since my sound card worked in 3.1, this means that there is an issue with
> the snd_hda_intel module in 3.2 RC2. Do you need more info about my
> system?
> 

I've been trying to think about how we would file a useful bug report for
this, but it seems like there's not much to go on (yet).

Can we say anything more concrete than just "the sound card worked in 3.1, but
it doesn't work in 3.2-rc2"?

Is this an accurate summary?

"Standby works by itself. The sound card works by itself. But standby only
works when the sound card is disabled, and enabling the sound card causes
standby not to work."

Also, did you already give the exact model of the sound card?

- -- 
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJXnnV4AAoJENtN07w5UDAwMCoQAIAwDkrWt5POuB+osrEuqoT7
CIoofWTqNEJHGSX5TiKR3fWwnI8ZEGnZ6SyRxVe2OK8+crloJXSOTWdBGhVS5cAh
NH0XflsIMYNmIusiZXYWRX/CVWdblgYSqNUz1RLVPX3xNIDUiKyMcI4XsXJU0v1C
b8QhkR1ZlWiG3eOpkYHeAefL6ft9YvfbkZ88OD3NmLGfqcvXrkNt0FY/wXbJkSNf
8AJxtuxdzLXiKAUpqh051CHYgS8AWPm/w2XbiLlNkQ/PBvrJfIUCbxyN4VVaA3+R
zkDekvJg/f27Og9Z9a8RyZeAC85T/ma3175dd9r7KBY7ARXGXFnBj2gtBYPDzNRw
tXX7JNTy5OSRUNDzBkqmX+UGeehpM5ysaHminpjKT6FFrpOc7d9gTLQsPa+2VP0S
odtM99nKao2YUolqy4H4NiVxkBAmWiXP2g4fpZ5Znu2q9vlcVVg4VbnGt1PgS8Um
dhnTt6dRQH0Ncj6e8rqhdR248LfB6qZ0cM2ZLiBLDLHqJpaCCcGKIsIWlTnF2LbH
b9XLrkRMsEu7jPjlhwAvW5oulavRcJUUhfqo/j1n+VPnbr8r+WZ3EOezfrubzng3
csTL3iYyEJ6yOa6jWC0WKAUCH65aA6Y+jBdeC/DrLwR+Z7+CZiRcBRRDjgORfB3U
nNReYlHx3aOVaNlZczHt
=lpN0
-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 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/1005c26e-5500-5bf9-76be-b98598ea712c%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] [3.2-rc2] issue with detaching usb flashes fat32

2016-07-31 Thread Eva Star

Also issue with colors.
Yellow color was fixed.
But black color now at rc2 damaged.

https://i.imgur.com/OrZcNJ0.png

--
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/d7044006-fe8e-d16d-e6e3-9b4fa8399e77%40openmailbox.org.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] AEM with Linux 4.4 causes hard reboot (cont... Trying to resolve issue)

2016-07-31 Thread Andrew David Wong
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-07-31 13:45, Andrew David Wong wrote:
> On 2016-07-31 13:42, Andrew David Wong wrote:
>> On 2016-07-31 13:38, Marek Marczykowski-Górecki wrote:
>>> On Sun, Jul 31, 2016 at 01:30:42PM -0700, Andrew David Wong wrote:
 On 2016-07-31 10:41, donoban wrote:
> On 07/30/2016 11:52 PM, Marek Marczykowski-Górecki wrote:
>> On Sat, Jul 30, 2016 at 02:44:24PM -0700, tel wrote:
>>> Sorry for the delay, Chris. I was waiting for 3.2-rc2, which I
>>>  just installed. It seems to come with the latest AEM package,
>>> so I didn't have to install that package myself.
> 
>>> I added the parameter to the tboot line. It didn't reboot, but 
>>> it hung before asking for the password with "Waiting for 
>>> /dev/disk/by-label/aem* to be connected..."
> 
>>> Not sure where to go from here.
> 
>> Do you use also USB VM? In that case, dom0 has no access to USB 
>> controllers...
> 
>> But you can re-enable it just for boot time by editing 
>> /etc/default/grub and removing the line with "hide_all_usb" (or 
>> just comment it out). Then rerun `grub2-mkconfig -o 
>> /boot/grub2/grub.cfg`. It will expose dom0 for all connected USB 
>> devices for a short time during system startup.
> 
> 
> 
> Nice, this should be added to: 
> https://www.qubes-os.org/doc/usb/#tocAnchor-1-1-4
> 
> With some warning: "Caution! Enabling usb-vm with LUKS encryption
> and a USB keyboard could stop you from booting your system"
> 
> :)
> 
> 
 If a USB keyboard is detected, the installer does not allow the
 option of creating a USB qube, so it should not be possible for a
 user to accidentally get him- or herself into this predicament.
> 
>>> But using USB qube will not stop you from creating AEM usb stick (or
>>> the other way around).
> 
> 
>> So, the problem is that if rd.qubes.hide_all_usb is added to grub.cfg
>> when the USB qube is created, but the user later decides to create an AEM
>> USB stick, then the user must be told to remove rd.qubes.hide_all_usb, or
>> else it will not work. Is that correct?
> 
> 
> (And, as you said, the converse: If a user creates an AEM USB stick, then 
> later decides to create a USB qube, they should be warned not to add 
> rd.qubes.hide_all_usb to grub.cfg.)
> 

Ok, added a new section to the USB documentation explaining hiding USB devices
from dom0:

https://github.com/QubesOS/qubes-doc/commit/15d418b778a8879323091c79fdc1084d
ecb890cb

And a pull request to the AEM README with a warning about using an AEM USB
device with a USB qube:

https://github.com/QubesOS/qubes-antievilmaid/pull/15

- -- 
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJXnnGCAAoJENtN07w5UDAwAXwP/jk/ikAjiWs+k4abrUzfyKdJ
kPsgmyKKXTuj5YWbLI+OgAgrlcqsZee1M1riTren2khpQOZOMe6MgQiKZ17kJ5Gw
4HzX615zJZCqRH/0YqDKfhdgS0VXmSutvTtAT+TX6/zHVTSNYBQWO8L/Dg6Hpuqt
01x2JgJuhAp97dMLfS3y66McwZK/KDM6teTVp7RgF14yWJCqLdSnUd0VhHAgcXAm
whBictNSdk169BtirC5jhUnNt0pIonVWVIOTwRaXV2kVxAWD74a04JNqKfLED11I
XhjY89+AkK+NGo+1piKCNztyB4x44IOab5AEb5W2ScInXOsh6oA5ZY7fwd3zUbPY
C2wgw7+7T9XhVlN/jrK58qsEZmXBws4jUSn7KqPon80sS7hz4uF21DCFexsFuxoG
Amum3d0zpZ5wjCTa1Y1CdaltV+Wq7vDZI5O3e8TUQpgHKxKZ0Iox1S4pP5Cn+MJM
b1aeR8bQce6zQswV7o5sH/2wC93bcdcWFlxoQYcwxZN55VAASqVW0FcE6RQzQ8ds
CMrqbI/FQOU6LasapdNUppEEglqhoAGiqmyZcL/ZjrobCFSPRk9WIY4Nhr2iAK3A
HhoXVMEeXRKzG+UkeWVesNQNJXC9b/sBXIccGA8Z5O4uAAdNCZIAOFLogFtwJj6D
m1t9f2ghBFUvuwQUM1ER
=j+oe
-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 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/a658ad08-8b76-ca0c-d529-639fc484ed21%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: Qubes 3.2 rc2 has been released!

2016-07-31 Thread Andrew "Arthur" Summers
Awesome! I figured going through the release notes would be the best thing
to do, but I imagine that there are some more specific tests that the team
would like to have executed. I'll wait for Marek to respond first.

Note that for me, I couldn't get the installer for RC1 to load. 3.1 worked
just fine, though. So far, the only big difference I've found is my
soundcard not being configured correctly, and it caused things like standby
and resume to not work right (already reported, but happy to provide more
details - just ask).

On Sun, Jul 31, 2016, 4:32 PM Andrew David Wong  wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> On 2016-07-31 14:10, arthur.summ...@gmail.com wrote:
> > Two questions: 1) Do you have a list of specific things that you would
> > like users to check based on changes/fixes you made from RC1 to RC2? I've
> > got RC2 installed and would gladly provide feedback.
>
> Thank you for offering to test it! It would be great if you could
> specifically
> test the new changes from the previous release candidate. (Marek, do we
> have a
> fine-grained way to view those changes? It looks like our lowest level of
> granularity is point releases, e.g., R3.1 to R3.2, but not R3.2-rc1 to
> R3.2-rc2.)
>
> Here are the release notes for R3.2:
>
> https://www.qubes-os.org/doc/releases/3.2/release-notes/
>
> As that page points out, you can find more detailed descriptions and
> discussions in completed GitHub issues with the "Release 3.2" milestone:
>
>
> https://github.com/QubesOS/qubes-issues/issues?q=is%3Aissue+sort%3Aupdated-desc+
> milestone%3A%22Release+3.2%22+label%3Arelease-notes+is%3Aclosed
> 
>
> (But as I mentioned above, this doesn't really distinguish between changes
> that occurred in R3.2-rc1 and R3.2-rc2. I think it would still be helpful
> to
> test both, though.)
>
> > 2) As a new user to the community, where is the preferred place to post
> > bugs? So far, I've just been dumping them in the qubes-users section (I
> > reported my snd_hda_intel issue), but I'm not sure if that's where you
> > want them to go.
>
> Thanks for asking! All bugs have to go into qubes-issues on GitHub
> eventually
> so that we can track what gets fixed, so if you're certain that something
> is a
> bug and you don't mind using GitHub to report it, please feel free to open
> an
> issue on GitHub. However, if you're not sure that something is a bug or if
> you
> don't want to use GitHub for any reason, then it's perfectly fine to write
> to
> the mailing list instead. (Not a big deal either way.)
>
> - --
> Andrew David Wong (Axon)
> Community Manager, Qubes OS
> https://www.qubes-os.org
> -BEGIN PGP SIGNATURE-
>
> iQIcBAEBCgAGBQJXnm50AAoJENtN07w5UDAwGqIP/3HOrxxmEUJyWyB6kvqxh4yc
> TqwwdQ2uliiDJXplMJSJ40NzSajsKpZxfQMBIOMs5brdi0qDWRWBk3aZW8LHWxNY
> B/RTd4fU879UUv6/QVgg+RGfyRwN1Fm8qJOEH7ISzcjHrXTKbMptC2uVv9KS1+bB
> fq6XqeySieRjDI/jrMTpbz9SfyzVEgj5U3xNZJOcLpRCOfJpINHzp1I1JjLT5lOo
> 35GvlyMuYNbJzTJCMH07Tp2ZyYMkoIKdX87qsVEabfs47JxkhvFrRdTDKlb+aMXS
> SgfUbLKvVb2aS+j99ceDbIJTIaHd69F0rgkUK+qvG8dvJUIOK1vO9epN59IaYUtB
> xRAe7/fi2Q0EKniH/uAZkfuhs6ld5ooUp35aLnIv0dAXS0AGcQ1nrMcyLfB+RCui
> ZlvKrLYaY3U16SNWvjKXnkckDHWgC+8sCn2a4p7JFMOCpETS0A9See3+Dl3WQDdf
> V+FmajnrrGrQwOJ/7vYnethdFZFQKpNk8LYBG4gUi3UdKgf63n2lsmRsVMT/Urxk
> zFC5CPynPcDxRvmL9drB9hxHORTMADc/ehDQCTuqchSFn5Q8GzZ3VAPwXNoStSGP
> IOWwnXh0Fi/XNnCPod+HxkV+aKIndrpfVxdiEFv6OwvQ1IKpmQpLWdJkakQyfIp7
> dxgoMFDLsnMk5/jpCY6G
> =mzPm
> -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 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/CAP0YRgb1LEYy_YUzApewQmaWxWbKyYj5e0LcVWorTGgKe-ujfw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: Qubes 3.2 rc2 has been released!

2016-07-31 Thread Andrew David Wong
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-07-31 14:10, arthur.summ...@gmail.com wrote:
> Two questions: 1) Do you have a list of specific things that you would
> like users to check based on changes/fixes you made from RC1 to RC2? I've
> got RC2 installed and would gladly provide feedback.

Thank you for offering to test it! It would be great if you could specifically
test the new changes from the previous release candidate. (Marek, do we have a
fine-grained way to view those changes? It looks like our lowest level of
granularity is point releases, e.g., R3.1 to R3.2, but not R3.2-rc1 to
R3.2-rc2.)

Here are the release notes for R3.2:

https://www.qubes-os.org/doc/releases/3.2/release-notes/

As that page points out, you can find more detailed descriptions and
discussions in completed GitHub issues with the "Release 3.2" milestone:

https://github.com/QubesOS/qubes-issues/issues?q=is%3Aissue+sort%3Aupdated-desc+
milestone%3A%22Release+3.2%22+label%3Arelease-notes+is%3Aclosed

(But as I mentioned above, this doesn't really distinguish between changes
that occurred in R3.2-rc1 and R3.2-rc2. I think it would still be helpful to
test both, though.)

> 2) As a new user to the community, where is the preferred place to post 
> bugs? So far, I've just been dumping them in the qubes-users section (I 
> reported my snd_hda_intel issue), but I'm not sure if that's where you
> want them to go.

Thanks for asking! All bugs have to go into qubes-issues on GitHub eventually
so that we can track what gets fixed, so if you're certain that something is a
bug and you don't mind using GitHub to report it, please feel free to open an
issue on GitHub. However, if you're not sure that something is a bug or if you
don't want to use GitHub for any reason, then it's perfectly fine to write to
the mailing list instead. (Not a big deal either way.)

- -- 
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJXnm50AAoJENtN07w5UDAwGqIP/3HOrxxmEUJyWyB6kvqxh4yc
TqwwdQ2uliiDJXplMJSJ40NzSajsKpZxfQMBIOMs5brdi0qDWRWBk3aZW8LHWxNY
B/RTd4fU879UUv6/QVgg+RGfyRwN1Fm8qJOEH7ISzcjHrXTKbMptC2uVv9KS1+bB
fq6XqeySieRjDI/jrMTpbz9SfyzVEgj5U3xNZJOcLpRCOfJpINHzp1I1JjLT5lOo
35GvlyMuYNbJzTJCMH07Tp2ZyYMkoIKdX87qsVEabfs47JxkhvFrRdTDKlb+aMXS
SgfUbLKvVb2aS+j99ceDbIJTIaHd69F0rgkUK+qvG8dvJUIOK1vO9epN59IaYUtB
xRAe7/fi2Q0EKniH/uAZkfuhs6ld5ooUp35aLnIv0dAXS0AGcQ1nrMcyLfB+RCui
ZlvKrLYaY3U16SNWvjKXnkckDHWgC+8sCn2a4p7JFMOCpETS0A9See3+Dl3WQDdf
V+FmajnrrGrQwOJ/7vYnethdFZFQKpNk8LYBG4gUi3UdKgf63n2lsmRsVMT/Urxk
zFC5CPynPcDxRvmL9drB9hxHORTMADc/ehDQCTuqchSFn5Q8GzZ3VAPwXNoStSGP
IOWwnXh0Fi/XNnCPod+HxkV+aKIndrpfVxdiEFv6OwvQ1IKpmQpLWdJkakQyfIp7
dxgoMFDLsnMk5/jpCY6G
=mzPm
-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 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/8bdf8f44-1435-6592-8b99-55242d6a4310%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] [3.2rc2] Default VMs failed to get created after installation

2016-07-31 Thread kototamo
Hi,

I gave up on installing on a USB stick and managed to get my hands on a second 
disk and installed Qubes on it. Everything went fine but after the first boot 
when configuring the VMs the following error appeared "A VM with the name 
'sys-firewall' does not exist in the system".

Can I somehow restart this configuration process without reinstalling 
everything? Or how can I create the default VMs (personal, work, vault etc)? 
Has someone experience the same error?

Thanks for your help & thanks for your 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 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/47676b1d-7728-4969-99e6-b4728498ab80%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] AEM with Linux 4.4 causes hard reboot (cont... Trying to resolve issue)

2016-07-31 Thread Andrew David Wong
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-07-31 13:42, Andrew David Wong wrote:
> On 2016-07-31 13:38, Marek Marczykowski-Górecki wrote:
>> On Sun, Jul 31, 2016 at 01:30:42PM -0700, Andrew David Wong wrote:
>>> On 2016-07-31 10:41, donoban wrote:
 On 07/30/2016 11:52 PM, Marek Marczykowski-Górecki wrote:
> On Sat, Jul 30, 2016 at 02:44:24PM -0700, tel wrote:
>> Sorry for the delay, Chris. I was waiting for 3.2-rc2, which I 
>> just installed. It seems to come with the latest AEM package, so
>> I didn't have to install that package myself.
 
>> I added the parameter to the tboot line. It didn't reboot, but
>> it hung before asking for the password with "Waiting for 
>> /dev/disk/by-label/aem* to be connected..."
 
>> Not sure where to go from here.
 
> Do you use also USB VM? In that case, dom0 has no access to USB 
> controllers...
 
> But you can re-enable it just for boot time by editing 
> /etc/default/grub and removing the line with "hide_all_usb" (or
> just comment it out). Then rerun `grub2-mkconfig -o
> /boot/grub2/grub.cfg`. It will expose dom0 for all connected USB
> devices for a short time during system startup.
 
 
 
 Nice, this should be added to: 
 https://www.qubes-os.org/doc/usb/#tocAnchor-1-1-4
 
 With some warning: "Caution! Enabling usb-vm with LUKS encryption and
 a USB keyboard could stop you from booting your system"
 
 :)
 
> 
>>> If a USB keyboard is detected, the installer does not allow the option 
>>> of creating a USB qube, so it should not be possible for a user to 
>>> accidentally get him- or herself into this predicament.
> 
>> But using USB qube will not stop you from creating AEM usb stick (or the
>>  other way around).
> 
> 
> So, the problem is that if rd.qubes.hide_all_usb is added to grub.cfg when
> the USB qube is created, but the user later decides to create an AEM USB
> stick, then the user must be told to remove rd.qubes.hide_all_usb, or else
> it will not work. Is that correct?
> 

(And, as you said, the converse: If a user creates an AEM USB stick, then
later decides to create a USB qube, they should be warned not to add
rd.qubes.hide_all_usb to grub.cfg.)

- -- 
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJXnmNKAAoJENtN07w5UDAwnj0P/2uVn7FhDYbF8Zus0kx8MZKo
A1h6LBqepzZjpesfWifQ3sbgX5FnjADOgrWsFPWQyEtGxrw1Bb2UtJl3cPcqIBGG
4KQVWLL9bGmdS9d9VdZVL0snRKIHlr4z5R4A/1UDoKUhbGs/OtP7iN3w0zAUD8/3
DY1FLejTFCSu7jhTpd3pwAOe8b18g8PKnfBHuY4J2nXMxcHLhLjZiPYNvmXEFgnb
nXEChbBHshg/DtwuK8cx6oYZyK7Y3v2yr6ZGACv4ZGSfNThNZXpPralblBB7FPFT
fvAIjKzPZ0yUOjBVeAEqwO1h+P5+ruZPWsKo/CLJwG7h9ZuPXiNHCVGy1LTmHBRe
dvYQF9hl1WCwjbicmWRg/UqgbKA1lHMKqK/Ty/90SNbMpvqio6+g0GINf+c8Qw6Y
uYYmsHkTjr+N77xf1994jtk4aMTPu3NovAGj6jFOBrfuq+6z+GWQ99aqzo8bARdV
e83SDowqMv21XmV19gEVN36O8fJG/Lds1KUIqOVF/ZS6gysnWKqiEb7jSH5KZG3g
BBuduYca0JKGW0Vdeqt/MlDa8VShpX2LfvsLkRvocGxDor8fbWZXEKT3mFOyFpFi
27E0Paya6SiBwFU2N9pKS17XAfVfbW/grFgTLZ+Nh6ko0kVkGOkKExceVcP4MTSp
x8rVryXIsEqs2s0MfJwU
=cat0
-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 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/d2983f7e-ea7e-4bf4-79f9-9b64d4254409%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] AEM with Linux 4.4 causes hard reboot (cont... Trying to resolve issue)

2016-07-31 Thread Andrew David Wong
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-07-31 13:38, Marek Marczykowski-Górecki wrote:
> On Sun, Jul 31, 2016 at 01:30:42PM -0700, Andrew David Wong wrote:
>> On 2016-07-31 10:41, donoban wrote:
>>> On 07/30/2016 11:52 PM, Marek Marczykowski-Górecki wrote:
 On Sat, Jul 30, 2016 at 02:44:24PM -0700, tel wrote:
> Sorry for the delay, Chris. I was waiting for 3.2-rc2, which I
> just installed. It seems to come with the latest AEM package, so I
> didn't have to install that package myself.
>>> 
> I added the parameter to the tboot line. It didn't reboot, but it
> hung before asking for the password with "Waiting for 
> /dev/disk/by-label/aem* to be connected..."
>>> 
> Not sure where to go from here.
>>> 
 Do you use also USB VM? In that case, dom0 has no access to USB 
 controllers...
>>> 
 But you can re-enable it just for boot time by editing
 /etc/default/grub and removing the line with "hide_all_usb" (or just
 comment it out). Then rerun `grub2-mkconfig -o /boot/grub2/grub.cfg`.
 It will expose dom0 for all connected USB devices for a short time
 during system startup.
>>> 
>>> 
>>> 
>>> Nice, this should be added to: 
>>> https://www.qubes-os.org/doc/usb/#tocAnchor-1-1-4
>>> 
>>> With some warning: "Caution! Enabling usb-vm with LUKS encryption and a
>>> USB keyboard could stop you from booting your system"
>>> 
>>> :)
>>> 
> 
>> If a USB keyboard is detected, the installer does not allow the option
>> of creating a USB qube, so it should not be possible for a user to
>> accidentally get him- or herself into this predicament.
> 
> But using USB qube will not stop you from creating AEM usb stick (or the 
> other way around).
> 

So, the problem is that if rd.qubes.hide_all_usb is added to grub.cfg when the
USB qube is created, but the user later decides to create an AEM USB stick,
then the user must be told to remove rd.qubes.hide_all_usb, or else it will
not work. Is that correct?

- -- 
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJXnmLMAAoJENtN07w5UDAw1H8P/if8V4KAF7/QR+jNEiJkg7sN
STv9tLfVxk08HmTUTVRGK4GjezZakUjhtEGOGyF/mKPs39uJ1NOzIY4QtO21M7nH
A8M3yNNUuFbfdykvs4yP1c3gkLmkJcVdsLIGMFHye9VP51TBjsEmHT8s3DltmG1l
7HRzvhTvWcWmP6n3ZGBUEdNEiWt68CuK6lKWOaTWRFIDfHEeCJJymw4r5yA/81Oy
vQcOBCdBZR/8yU9veHrQeTvAfttJTBUO/uiudO1q006eCK7LHmcrEQ5M39LZk5H8
X5mycno2p7kGwDSrcgEnsakqcSJlPu9untfw1bdVQwxvPP2Lnkk03zwTu/fh+n+B
hNKdNwW+8NzqlyRP2cguk4qJjtV3VIB1STNulhNMMspoO+e6T44JvpYWCCGiYSXn
SLSrkzTHzFjr956dXPMGg2jZJaEEaixYAAxTeQMae9YLIjVFMIsyu/ttNrOmI5Y6
gN7GL7B7bj1zmHlHykvrGi8fIoQWXLQ/23RvqtGzqY5OXCsJ46nuMLn+qpqiSehB
/3s7hL2pNk/lEacfVfpa0X/EdATFzQS3CK5Bds+rqtVH0hTE8Y+R6wz7BoD2wQQ1
seJN7aiIOdTKOeQ3yR90VXyLffnjwOzdirYmfbJDgG6xRiWegc0fu2Pi6ANWPPxR
g8cJxWORzkmZCp4ECH2G
=WHkx
-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 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/49d0ddb6-df8a-f6ba-5040-cada6bbc2c1f%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] AEM with Linux 4.4 causes hard reboot (cont... Trying to resolve issue)

2016-07-31 Thread donoban
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 07/30/2016 11:52 PM, Marek Marczykowski-Górecki wrote:
> On Sat, Jul 30, 2016 at 02:44:24PM -0700, tel wrote:
>> Sorry for the delay, Chris. I was waiting for 3.2-rc2, which I
>> just installed. It seems to come with the latest AEM package, so
>> I didn't have to install that package myself.
> 
>> I added the parameter to the tboot line. It didn't reboot, but it
>> hung before asking for the password with "Waiting for
>> /dev/disk/by-label/aem* to be connected..."
> 
>> Not sure where to go from here.
> 
> Do you use also USB VM? In that case, dom0 has no access to USB 
> controllers...
> 
> But you can re-enable it just for boot time by editing
> /etc/default/grub and removing the line with "hide_all_usb" (or
> just comment it out). Then rerun `grub2-mkconfig -o
> /boot/grub2/grub.cfg`. It will expose dom0 for all connected USB
> devices for a short time during system startup.
> 
> 

Nice, this should be added to:
https://www.qubes-os.org/doc/usb/#tocAnchor-1-1-4

With some warning: "Caution! Enabling usb-vm with LUKS encryption and
a USB keyboard could stop you from booting your system"

:)
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJXnjhcAAoJEBQTENjj7Qilj+kP/2x7HDB3szCBsdd2fvywlRNc
mSULDpcl5PI+R3xcmlCs+8EHRJOxpaCCcmJWxtTuGQPSJz68Otnms4gTJ2k3t88z
0WuWufkuxg4/W9Y2VGm2NXghp3N4hQDB9rCxrYjBaprdAiJgr5JRwNG1yVFJgo3A
jKP9dGy/TIutjj9vj9LQ95k9Epf9yQFFcEOz26GE/0IeQLJnmM9Y4k+Fw3i5R+RY
Prq4ABX7H27H2sp4C7QNWgK74rktmqblgUfg4+svXdNhr1i9BoC1ql2hEO/MlcPu
eRCVAXiEQuJQaLNZTFJx4frHswlJNKaouMbKC8sK3qSS66L0S6bUKCuCXjMJ5x99
sVceKcXIJmY08jUxn5bXHYTytWLExmYRPJ/m7VLsKqOnZqYoj/UjggVo2xRN+RBz
NmzJL8fjKs74iNHxrNMwsuiUpDjy5wGYmVzgiI9SeVlOFr+WJbnTex60Z+v2CybO
Hekl47ZVna3a2yzOdzPuRAidroUdLPA8DNSVpTXN8cKEsCEqaqS0GN5KWxHqTY1Q
bbMxHMp0NWhah6q89KaU6InZ/hnmmQa5Ceca9O8RAoX8qKWj62nsYAnHuRtdgKu0
QE5jECeu8y5pRittzowkHwj9cNnQEVDHGhfzsrpQuOHUF09Wf3TATvWX2cqBxMoM
Bv2bNVtwQfpUKjzAW/xF
=uKAd
-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 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/2084e121-9f53-4aa5-a671-a7062bf4fafe%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Upgrading from Qubes 3.1 to 3.2 fail

2016-07-31 Thread donoban

On 07/31/2016 03:36 PM, Marek Marczykowski-Górecki wrote:

On Sun, Jul 31, 2016 at 01:53:26PM +0200, donoban wrote:

- I have sys-usb working fine but only with Fedora template, could I

migrate

it to Debian?


What are the problems with Debian template there?


USB keyboard and mouse doesn't work.


Make sure you have qubes-input-proxy package installed. It is not
included in default template image.



Installed qubes-input-proxy-sender and works fine now, thanks Marek.


--
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/e494cc9b-d39d-21ac-4dae-256a6f978db9%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Configuring OpenDNS in Qubes

2016-07-31 Thread marc
Hi,

I'm trying to figure out how I can change my DNS settings for an AppVM. I'm 
relatively new to Qubes, so other related issues in this forum have clarified 
me some ideas but I am still quite puzzled.

This is what I have done so far:

1 - I have created a ProxyVM, which in turns connect to sys-firewall as NetVM. 
This ProxyVM uses debian-8 as template, because I'm following some tutorials in 
Internet about networking stuff using kali linux (configuring OpenDNS is one 
part). This ProxyVM is a StandaloneVM in order to keep changes in /.

2 - I have added to it network-manager service

3 - I have edited /etc/dhcp/dhclient.conf in my ProxyVM and I have added the 
following line with OpenDNS IPs:

prepend domain-name-servers 208.67.222.222, 208.67.220.220;

4 - I have connected my AppVM to this ProxyVM as NetVM.

5 - I have restarted my ProxyVM and my AppVM.

Now, I thought /etc/resolv.conf in my AppVM and ProxyVM should have changed. 
But no, they still have:

nameserver 10.137.5.1
nameserver 10.137.5.254

I see that my AppVM takes its /etc/dhcp/dhclient.conf from the ProxyVM, because 
that line is also added there.

Going to https://dnsleaktest.com confirms that I'm still using my ISP DNS 
server.

I guess that there is a way to do that without having to create a StandaloneVM 
for my ProxyVM, but I tried to do everything manual to learn how everything is 
tied. But anyway it doesn't work...

Thanks!




-- 
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/78684271-4bcf-426d-9428-ee706ebe0381%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Play Audio from AppVm on device attached to USB Cube

2016-07-31 Thread Torsten Grote
On 07/30/2016 08:51 PM, Connor Page wrote:
> Read the last part at https://www.qubes-os.org/doc/usb/
> This should solve your problem unless you want to mix sound from multiple vms.

Yes, like I wrote, I ideally want to mix sounds from multiple VMs. So I
would prefer to find a solution for that.

However, as a temporary solution I would be fine to use my output device
only from one VM. The problem with that is that the output device is
connected via Bluetooth and I don't really like to expose that to other
domains. But even then, the Bluetooth adapter (which is part of the WiFi
card) fails to properly attach to different VMs and when trying that the
USB cube does no longer routes mouse input from the USB mouse to dom0
until I restart it.

So if somebody has an idea for how to expose an external audio device to
pulsaudio globally, I would appreciate some hints.

Thanks,
Torsten

-- 
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/783ba8e1-b2ec-bdbd-041a-f915f0913a4d%40grobox.de.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature


[qubes-users] Re: VM seemingly all of a suddon will no longer start up? (yellow dot)

2016-07-31 Thread gaikokujinkyofusho
On Saturday, July 30, 2016 at 9:42:25 PM UTC+3, gaikokuji...@gmail.com wrote:
> On Saturday, July 30, 2016 at 9:39:22 PM UTC+6:30, gaikokuji...@gmail.com 
> wrote:
> > I just managed to install a second hard drive on my laptop then tried 
> > restarting, everything started off fine except when I tried to start my 
> > "media vm" which mainly had Kodi media center on it. I don't see how the 
> > new hard drive would affect this appvm starting up but that is the only 
> > difference between earlier today when I last used this vm/kodi and now.
> > 
> > Now I am noticing the I can't start anything from the MediaVM, and my 
> > workvm shows up as a yellow dot but I can start firefox from there (so far 
> > at least), and the sys-firewall had a mementary error/yellow triangle, 
> > something about using/requesting more memory than available?
> > 
> > I noticed the failed to connect to gui-agent error from the logs (below) as 
> > it was about the only error that pops up, apart from that I am not sure. My 
> > qubes setup has been running pretty well lately, until now... thoughts?
> > 
> > Icon size: 128x128
> > libvchan_is_eof
> > release_all_mapped_mfns running
> > Obtained 8 stack frames.
> > Icon size: 128x128
> > Failed to connect to gui-agent
> 
> Sorry, the reoccuring error is "can not start qubes guid"

Solved.

It was apparently private storage max size was reached, so I increased it and 
everything was roses again (at least with that VM).

-- 
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/fd72cfaf-e7d8-4564-8090-fd0226d5f548%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] VPN Link Up, NetVM set to VpnVM but AppVMs still don't have net access?

2016-07-31 Thread gaikokujinkyofusho
On Tuesday, July 26, 2016 at 5:32:04 PM UTC+2, gaikokuji...@gmail.com wrote:
> On Monday, July 25, 2016 at 5:12:42 PM UTC-10, Chris Laprise wrote:
> > On 07/25/2016 04:25 PM, gaikokujinkyofu...@gmail.com wrote:
> > > On Thursday, July 21, 2016 at 9:41:57 PM UTC+12, gaikokuji...@gmail.com 
> > > wrote:
> > >> On Wednesday, July 20, 2016 at 4:17:32 PM UTC-8, Chris Laprise wrote:
> > >>> On 07/20/2016 02:59 PM, gaikokujinkyofu...@gmail.com wrote:
> >  On Saturday, July 16, 2016 at 5:09:48 PM UTC-4, gaikokuji...@gmail.com 
> >  wrote:
> > > I tried the 'sudo iptables -L -v -t nat' anyway and to be honest I am 
> > > not sure I understand the output:
> > >
> > > [user@VPN ~]$ sudo iptables -L -v -t nat
> > > Chain PREROUTING (policy ACCEPT 0 packets, 0 bytes)
> > >pkts bytes target prot opt in out source   
> > > destination
> > >   0 0 PR-QBS all  --  anyany anywhere 
> > > anywhere
> > >   0 0 PR-QBS-SERVICES  all  --  anyany anywhere   
> > >   anywhere
> > >
> > > Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
> > >pkts bytes target prot opt in out source   
> > > destination
> > >
> > > Chain OUTPUT (policy ACCEPT 432 packets, 30668 bytes)
> > >pkts bytes target prot opt in out source   
> > > destination
> > >
> > > Chain POSTROUTING (policy ACCEPT 0 packets, 0 bytes)
> > >pkts bytes target prot opt in out source   
> > > destination
> > >   0 0 ACCEPT all  --  anyvif+anywhere 
> > > anywhere
> > >   3   192 ACCEPT all  --  anylo  anywhere 
> > > anywhere
> > >  12   812 MASQUERADE  all  --  anyany anywhere
> > >  anywhere
> > >
> > > Chain PR-QBS (1 references)
> > >pkts bytes target prot opt in out source   
> > > destination
> > >   0 0 DNAT   udp  --  anyany anywhere 
> > > 10.137.4.1   udp dpt:domain to:10.137.2.1
> > >   0 0 DNAT   tcp  --  anyany anywhere 
> > > 10.137.4.1   tcp dpt:domain to:10.137.2.1
> > >   0 0 DNAT   udp  --  anyany anywhere 
> > > 10.137.4.254 udp dpt:domain to:10.137.2.254
> > >   0 0 DNAT   tcp  --  anyany anywhere 
> > > 10.137.4.254 tcp dpt:domain to:10.137.2.254
> > >
> > > Chain PR-QBS-SERVICES (1 references)
> > >pkts bytes target prot opt in out source   
> > > destination
> >  Hi, I don't think I am using Network Manager to connect, that is I 
> >  went only by the Qubes VPN wiki but while trying to diag the problem I 
> >  read about /etc/resolv.conf in some other doc while searching so 
> >  thought I'd try (obviously no luck).
> > 
> >  As for the sudo sg qvpn -c ping whateversite, does returning one thing 
> >  back and hanging count for anything? I am thinking not as I am not 
> >  able to connect to the net via the VpnVM.
> > 
> >  Any thoughts on the DNS dnat rules?
> > >>> Pinging from my vpn vm is probably the same as yours, now that I've
> > >>> checked it: I get a DNS response but the pings themselves aren't 
> > >>> permitted.
> > >>>
> > >>> I think the real problem is shown in your PR-QBS chain above. You see
> > >>> that the 'to' addresses on the right are still pointing to a Qubes
> > >>> internal subnet '10.137.x.x'. Something about the DHCP fetching of your
> > >>> DNS servers or the way qubes-vpn-handler.sh is executing is not working.
> > >>> You can verify this by taking the IP address for 'whateversite' and
> > >>> pinging it from your appvm (connected to vpn vm)... that should work
> > >>> even though DNS doesn't.
> > >>>
> > >>> Cause of the problem should be a misconfigured .ovpn (the 3 lines for
> > >>> scripting) or the qubes-vpn-handler.sh script itself can't execute
> > >>> because the execute flag is not set, or the shebang at the start was
> > >>> left out, etc.
> > >>>
> > >>> Chris
> > >> well you are right about being able to ping an IP from the appvm that is 
> > >> connected to the vpnvm, it works fine.
> > >>
> > >> As for the misconfigured .opvn I can't make heads or tails of that as 
> > >> the first time I just used the exact same file that I had backed up, I 
> > >> rechecked it and I think its ok (I also got a new pre-configured one 
> > >> from my vpn provider, c/p the needed edits in, and still get the same 
> > >> error). I checked the permissions user of the two files and I think they 
> > >> are ok?
> > >>
> > >> -rw-r--r-- 1 root root  423 Jul 21 21:28 openvpn-client.ovpn
> > >> -rwxr-xr-x 1 root root 1089 Jul 10 21:15 

Re: [qubes-users] Upgrading from Qubes 3.1 to 3.2 fail

2016-07-31 Thread Marek Marczykowski-Górecki
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Sun, Jul 31, 2016 at 01:32:25PM +, donoban wrote:
> 
> 
> El 31 de julio de 2016 14:33:00 CEST, "Marek Marczykowski-Górecki" 
>  escribió:
> >-BEGIN PGP SIGNED MESSAGE-
> >Hash: SHA256
> >
> >On Sun, Jul 31, 2016 at 01:53:26PM +0200, donoban wrote:
> >> - I have sys-usb working fine but only with Fedora template, could I
> >migrate
> >> it to Debian?
> >
> >What are the problems with Debian template there?
> 
> USB keyboard and mouse doesn't work.

Make sure you have qubes-input-proxy package installed. It is not
included in default template image.

- -- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJXnf7lAAoJENuP0xzK19csM1AH/3Lln7b2ZR9FQaMA7gNRyzW5
bm84Uu6K6DHRAPyS28k0eoJ30XsGd03Z5kIc51AlqAW8xDnFXegcx1rutz1JuHzw
Or6y4wypzBPkLzbbJo2jQ9ZdEO57zknRE3qUiQU8sTEM2NHKpNcj9P2dRmk20l1O
VX/0T8TIy+djLqVwQgNYgDF7dMW9FM2tfliaEFedTbLq2lSacXNrCl72KsfbaNCN
Z2fhqf1mgS1T89T36Rakc1OdtCi0UGKpUqlUIbzLK1zoQPqeNt8XtBGf7/5cbXou
C8o9l0VTkcVFbafXPdMLP6EVjrpTPcRl1VNFfP1GyK5eH1+rwoDKBXrqAemuhpQ=
=IJSL
-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 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/20160731133635.GG32095%40mail-itl.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Qrexec-daemon not always loading

2016-07-31 Thread Marek Marczykowski-Górecki
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Sun, Jul 31, 2016 at 05:55:09AM -0700, jmarkdavi...@gmail.com wrote:
> On qubes 3.2 when I start it up the qrexec-daemon will not start. This causes 
> all other VMs besides dom0 to not load.
> Loading the vm with qvm-start shows that it times out when trying to connect 
> to qrexec-daemon.
> If I reboot several times it eventually boots correctly and works fine.
> Dom0 log file does not show anything about qrexec is there another log to 
> look at?
> 
> Is there a way to manually initialize qrexec-daemon?

Depending on why it fails. Try this:
1. Open terminal in dom0
2. Access VM console (place actual VM name in place of VMNAME):

sudo xl console VMNAME

3. Login as root (shouldn't as for password)
4. Check status of `qubes-qrexec-agent` service:

systemctl -l status qubes-qrexec-agent

5. Note any errors there
6. Restart the service:

systemctl restart qubes-qrexec-agent

- -- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJXnfuZAAoJENuP0xzK19csKl0H/RXz9L5/pY2K/jPQ9cV7C/U1
tl4LjeKapOuToUlp6nBhRS/Pk81Tva1CKVx7dCglQlwsVMHhLPnt5nzuTLi++IpV
yVebnoGCgIkEDNcKgWtprgdXMwZJe8tXGtGBTfWM6gm/SMJ0RcODXVZQmT/dyoOB
5hdKEG4WFkXIrIQAK/eXRkrtQuZvQyoI/DjRk4AtefYLjP8fRfrkcx/yXk9y3fA3
FU88u56L/RUYTKl4is2o/x1TN1/JIuEkLEiDf0PMbJMaUzR1NpT+79jw8DelT4Pf
5ulk4df4IaUcVuaP+3yVCPvRw7A49T7x/VUctSBP/zTL/7IsQ9ciHj2OTPIXH98=
=bfhr
-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 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/20160731132232.GF32095%40mail-itl.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: vpnleak or my vpn

2016-07-31 Thread jmarkdavis86
On mine this happened when I did not create a proxy vm with network manager.   
My vpn had an option for a script file to initialize the .Ovpn file inside the 
appvm. Doing this hid the ip but the dns stayed the same. I guess because the 
dns settings are in one of the service vms.

-- 
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/6c8d8a2f-518c-4229-8116-427a36e60cda%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] [3.2rc2] Cannot execute Qubes configuration after installing

2016-07-31 Thread kototamo
Yes it was the same before. The option was unchecked. I would have expect the 
option to be enabled if the message is "blabla disabled" and the checked option 
off.

Anyway, not sure how to investigate further from here.

-- 
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/710bd8b5-5797-45ef-bf25-d176555a2328%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Upgrading from Qubes 3.1 to 3.2 fail

2016-07-31 Thread Marek Marczykowski-Górecki
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Sun, Jul 31, 2016 at 01:53:26PM +0200, donoban wrote:
> Hi,
> 
> I tried to do the experimental process for upgrading to Qubes 3.2. I
> followed the steps from https://www.qubes-os.org/doc/upgrade-to-r3.2/
> 
> 
> All went fine until I rebooted the system (step 7). After rebooting I had a
> lot of packages for update on dom0 (more than 1000), and when I tried to
> update them it failed because some dependency problems (I remember some perl
> packages but maybe there were more packages with problems).

Those packages should be already handled in step 4.

> I didn't extract logs because I needed the computer working ASAP so I
> installed it from scratch and restored my backup but I have another computer
> on 3.1 which I would like to upgrade to 3.2 and I could try to do the
> process again and extract useful information.
> 
> I had all my VM's with Debian template, I had indeed fedora template
> removed, maybe this could affect to the upgrade process.

Yes, this could affect the upgrade. If that's the case it is a bug we
should fix before final release.

> Some comments after fresh install 3.2:
> 
> - Debian and Whonix-GW seems up to date after install, while fedora-23 and
> Whonix-WS needed updates. I don't know why...

This shouldn't matter as it's good practice to update the system after
installation anyway. In a month all the templates will have some updates
pending.

> - I have sys-usb working fine but only with Fedora template, could I migrate
> it to Debian?

What are the problems with Debian template there?

- -- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJXne/9AAoJENuP0xzK19csiPEH/21rgzz3P1xlDnJeZ2wLs3Iw
n/dCwMqQ665NevJyHhZrtmhUoXsN86/fs9kO76+cQnKRR5WMtzNeRxAK2dcW7O4Y
efGoR6jZnpKbwXSQKt1+sgUS4c46BEF2FqQs0u4hwwY4wmS8wi+UIUlR8fN7800H
E6TtPK9BZfO0gEoDs0W49epXXv3xu64LKYKMOPAPNGi4jmYZvaWluW0m6tl8CwO4
0BnaXYjLnKdxzPK9vRZe4YMs20nCsg5SlPjPQJiO0K21ytwYPpWlxnO04zg0XU9e
2xa6Y4Eo4XxMMsMQ7V2QDMpaTAa3qyiMnHqJVGGOdOTr3S3uHwyg0b1wI3hk0GI=
=bRcX
-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 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/20160731123300.GE32095%40mail-itl.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] [3.2rc2] Cannot execute Qubes configuration after installing

2016-07-31 Thread Marek Marczykowski-Górecki
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Sun, Jul 31, 2016 at 05:17:50AM -0700, kotot...@gmail.com wrote:
> I retried, booting with a USB keyboard plugged in, without success. Even if 
> the keyboard works, I cannot check the option "USB Qube configuration 
> disabled".

That's ok - the option is already disabled and you can't enable USB
qube.

If it was the same before, then the problem is somewhere else.

> I have the option 'default system qubes', 'default applications VMs' and 
> 'create Whonix' checked.
> 


- -- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJXne6dAAoJENuP0xzK19csfqMH/2losMdSX0+oFqKu7oGLd5GZ
CJrs3kmRimvBmED8eDuvlQSzw25pyW/0gZkrToB+P4XnUg4BSq+yatmeNmc96pwe
NNuFFJ4yQgwil9YVqkP2YfryMrpVF1kmc4KsZOziDm162gu7Oiclt7UqGoMNqt8H
KIUqT8hBKtLrOg/mnMIX+cqtKioEED0pkCA/kJ2yIDKUuytYer7ZQdvEK+D2aqnQ
iXx6mhW2J41dgrU3zMO3k8iEyEOCQVfN+REbQSZmFVuFkjBsAjtEReI/jOGxTTGQ
Sku/k5kwYrmjN31CdyLJzTroLJAv713/WGZ82jp8BuoLb4s5aBervJHbpUzGbqc=
=i+fk
-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 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/20160731122708.GD32095%40mail-itl.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] [3.2rc2] Cannot execute Qubes configuration after installing

2016-07-31 Thread kototamo
I retried, booting with a USB keyboard plugged in, without success. Even if the 
keyboard works, I cannot check the option "USB Qube configuration disabled".

I have the option 'default system qubes', 'default applications VMs' and 
'create Whonix' checked.

-- 
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/c13a8ad6-43e7-4f0d-8497-76676d16ce10%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: networking on Dom0 - can I have it please?

2016-07-31 Thread zv . odd . 101
On Friday, 29 July 2016 09:38:41 UTC+10, facu@gmail.com  wrote:
> El jueves, 25 de febrero de 2016, 23:26:21 (UTC-3), Nom  escribió:
> > Is there anyway to get networking on Dom0 to work?
> > 
> > Before everyone screams "UNACCEPTABLE!", (Don't pretend you weren't going 
> > to). I know it doesn't fit the security model of the OS. But my threat 
> > model - quite reasonably doesn't require it. I would like to be able to 
> > still have some of the benefits of the OS's secure design with the chosen 
> > compromise of networking in Dom0. So can we just leave it at; I need 
> > network access on Dom0 for "reasons", OK?
> > 
> > I tried running the old 'qubes-dom0-network-via-netvm' that was removed in 
> > this patch: 
> > https://github.com/QubesOS/qubes-core-admin/commit/bb9d8bbf7881ce13023ac905f98511beaeaaeae7
> > 
> > Running 'qubes-dom0-network-via-netvm up' it gets as far as doing 'modprobe 
> > xen-netfront' successfully and fails on line 70 when calling 
> > 'qvm_collection[0].attach_network(...)' and reports:
> > 'Dom0 does not have libvirt object'.
> > 
> > Is there a work around?
> 
> Nom, you found solution? I want to do the same :P

Sorry, never did find a solution.

It really would be nice to be able to use some form of networked desktop 
interface (RDP, KVM, etc) to control dom0. As the only Qubes compatible 
hardware I have is a big old dual Xeon blade server, that doesn't fit in my 
office. Considering the hardware limitations of Qubes. It makes sense to use 
server hardware with an ethernet connection to a thin client (like Raspberry 
Pi).

Community seems to think it's wrong.

-- 
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/889155ac-3746-4591-baaa-089b8749d3b7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Upgrading from Qubes 3.1 to 3.2 fail

2016-07-31 Thread donoban

Hi,

I tried to do the experimental process for upgrading to Qubes 3.2. I 
followed the steps from https://www.qubes-os.org/doc/upgrade-to-r3.2/



All went fine until I rebooted the system (step 7). After rebooting I 
had a lot of packages for update on dom0 (more than 1000), and when I 
tried to update them it failed because some dependency problems (I 
remember some perl packages but maybe there were more packages with 
problems).


I didn't extract logs because I needed the computer working ASAP so I 
installed it from scratch and restored my backup but I have another 
computer on 3.1 which I would like to upgrade to 3.2 and I could try to 
do the process again and extract useful information.


I had all my VM's with Debian template, I had indeed fedora template 
removed, maybe this could affect to the upgrade process.


Some comments after fresh install 3.2:

- Debian and Whonix-GW seems up to date after install, while fedora-23 
and Whonix-WS needed updates. I don't know why...


- I have sys-usb working fine but only with Fedora template, could I 
migrate it to Debian?


Well, it looks very nice. Thanks for your work guys.

Regards.

--
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/6e805caf-5abc-2d72-6117-4ef6f8929993%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] [3.2rc2] Cannot execute Qubes configuration after installing

2016-07-31 Thread Marek Marczykowski-Górecki
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Sun, Jul 31, 2016 at 04:21:48AM -0700, kotot...@gmail.com wrote:
> > What settings have you enabled in that step?
> 
> During the installation I setup one administrator user with encryption for 
> the disk.
> 
> After reboot I used the default options to create the default VMs. Also I 
> think the USB isolation was on (because Qubes noticed that I didn't have a 
> USB keyboard).
> 
> Is it possible that the USB isolation locked me out of the usb stick on which 
> Qubes is installed? 

Most likely. In theory it should also detect when you're using USB disk,
but maybe it didn't worked.

- -- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJXneLjAAoJENuP0xzK19csYm8H/3HLMJbYK5dXtW4udmV6kTji
edWtcn/3M10OUQzrBfQpL25yUJcKq8e1UwY85H7SJGGqG8hjV7ZyDV2bxDT4aSlL
ubsQMiFnhP3jJdr25hwmgfuX61dYr+KbTsXQ7hvVLJItdd6YYMz89lGGGdv7BKoI
SLXufIYUrItVpVXP5o3YSE35uleaL6XTwEwsGQApUhxu+XtsKL3Ddj48gFrKF97Q
ELH8l1HbKDuAAtQqf18f22EOH6MBxfmuqYMDr73zjg+uqOmXsagUMZOJVLjlIbmJ
C6YqiLZvPnwfybzYjlvlw4sD6Fz+NiJ+cndTTbT4dZ+PBbcnlgsxP1d/X4EYgdE=
=BBHg
-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 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/20160731113707.GC32095%40mail-itl.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] usb 3.0

2016-07-31 Thread David Hobach

On 07/30/2016 12:23 PM, Nicola Schwendener wrote:

Hello all,
sorry if I bother you but I haven't understood if USB 3.0 (I've a lot of 
external disks with usb 3.0) is supported or not. I want to migrate from my 
actual windows 8.1 OS to Qubes (I've to do a Windows HVW for some applications) 
but, the USB 3.0 should work correctly.
could you please help me?
best regards
Nick



In dom0 it is well supported (it's just a standard Linux kernel after all).

PCI passthrough of your USB controller (= USB VM) however heavily 
depends on the combination of Xen and your USB controller, i.e. might 
not be supported (I guess your bets would be best if you had some server 
controller). It tends to work with USB 2 though. Maybe the new qvm-usb 
also helps.

https://www.qubes-os.org/doc/assigning-devices/
https://www.qubes-os.org/doc/usb/

I suggest you just test it (maybe use the live USB 
https://www.qubes-os.org/doc/live-usb/).


--
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/4873dbf5-4164-4fd7-4b62-fe8021a9d480%40hackingthe.net.
For more options, visit https://groups.google.com/d/optout.


smime.p7s
Description: S/MIME Cryptographic Signature