[qubes-users] best mini pc for qubes os

[randallrbaker]

Hi there, im currently using a 4000$ gaming pc running windows 10 (qubes 
wouldnt install on it) and want to downgrade to a more minimal product. What 
would you guys recomend for a mini pc that can screw on the back of a monitor? 
it needs to be web fast for my buisness and should be able to run photoshop and 
illustrator if i boot windows from separate drive with no wifi on of course lol

-- 
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/b00e2f36-910b-4b4c-aac0-ed3c181e6060%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] qubes 4 documentation

[Ray Joseph]

On Saturday, October 28, 2017 at 2:58:48 PM UTC-5, Andrew David Wong wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> On 2017-10-21 09:39, Roy Bernat wrote:
> > Hi 
> > 
> > there are a lot of changes between qubes 3.2 and qubes 4 .  
> > 
> > for example - dispvm ,  qvm command and more is there somewhere dedicated
> > 
> > docs for it ? 
> > 
> > Roy  
> > 
> 
> Since Qubes 4.0 stable has not yet been released, most of the
> documentation for it is still being written. You can find these
> tasks in individual qubes-issues with the "doc" label:
...
Andrew,

Thank you, that opened a whole new set of information.


-- 
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/860c580c-b803-4b7a-90c4-282cc0941c92%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] anyone experiencing issues with whonix-ws ?

[Francesco Rmp]

Hi,
i'm experiencing a weird issue with whonix-ws template and anon-whonix appVM.

The VM starts up properly, i can confirm by the logs reaching the login, and by 
the fact that i can attach to the console for interacting with it.

The problem is that i cant run any application.

By trying to run an application (like xterm) from the attached console, the VM 
says it cant connect to the X server. Generally this is obvious in many 
distributions when you run a command from the terminal that requires an X 
server to be available, but i tried to do the same thing with the personal 
domain, based on fedora and if i type xterm, the terminal pops up in the dom0 
window manager with the appropriate window decoration for the specific domain.

Is there anything i can try to solve the problem?

Thanks in advance for your kind help.

-- 
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/5f58bec6-e4f6-4db6-8092-f05a916dc2a3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Qubes 4.0-rc2 :: VMs fail to start

[aphidfarmer]

On Wednesday, October 25, 2017 at 10:26:51 AM UTC-7, [799] wrote:
> Hello,
> 
> As at least one other Qubes user has the same problem, that VMs won't start, 
> I'll add this as special topic.
> 
> I've made a clean install of Qubes 4-rc2 but ~70% of the time I can't boot 
> the VMs.
> This includes sys-net, sys-firewall, but also others.
> 
> I tried to check the logs but I don't get any valuable information.
> See screenshot.
> 
> I started the following command in dom0:
> 
> watch -n 1 xl list
> 
> When I try to launch a VM I can see that the VMs appears in the xl list 
> output, but the State is -- and the Time(s) is 0.0.
> After ~30sec the start is aborted with error message: Cannot execute 
> qrexec-daemon.
> 
> Questions:
> 1) is anyone running Qubes 4.0-rc2 on a Lenovo X230?
> 2) is someone additionaly running Coreboot?
> 3) I am running the Qubes Installation with the default settings, any options 
> to tweak on the Grub command line
> 
> [799]
> 
> 
> 
> 
> 
> Gesendet von ProtonMail mobile

I'm testing Qubes 4.0rc2 on an X230 with SeaBIOS+Coreboot.

I can start sys-net always but cannot start sys-firewall and other VMs 
consistently ("Cannot execute qrexec-daemon").

One difference between our setups may be, I am not using the stock Intel wifi 
card but an Atheros one 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/e83d6b06-1ea7-4343-aef2-c1f7cc2bf8ae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] qubes 4 documentation

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2017-10-21 09:39, Roy Bernat wrote:
> Hi 
> 
> there are a lot of changes between qubes 3.2 and qubes 4 .  
> 
> for example - dispvm ,  qvm command and more is there somewhere dedicated
> 
> docs for it ? 
> 
> Roy  
> 

Since Qubes 4.0 stable has not yet been released, most of the
documentation for it is still being written. You can find these
tasks in individual qubes-issues with the "doc" label:

https://github.com/QubesOS/qubes-issues/issues?q=is%3Aopen+is%3Aissue+label%3A%22C%3A+doc%22

For example, you asked about DispVm and qvm-* commands. Here's a
sampling of some of the open issues we have on documenting these:

https://github.com/QubesOS/qubes-issues/issues/3017
https://github.com/QubesOS/qubes-issues/issues/3060
https://github.com/QubesOS/qubes-issues/issues/3024
https://github.com/QubesOS/qubes-issues/issues/2993

We can always use help with writing documentation! Qubes documentation
is a community effort:

https://www.qubes-os.org/doc/doc-guidelines/

As they're completed, the future 4.0 docs will still be available in the
same place as the existing docs, i.e.:

https://www.qubes-os.org/doc/

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

iQIcBAEBCgAGBQJZ9OFwAAoJENtN07w5UDAw81wP/iHtlXsjMfg0/93FfcY6C+F5
baiG/xeQtdTkDXqggNPwMchtjZWjQI85mS9XHLPMNk0EsGIUiHeXTAOm/ScNFdTe
cOaygRdIrqRAJqNJZfSIg6Iy62tVViSM3lyjRBfAIw/J41KzTB7DKDJMUPlfM5Gi
szpGm78V2JQLK6VxTqqQHZik4rEPRNEya2CNmjOURPvpt8kpF5DtLLjWurAGrscN
iDMmnMoDT20eGaiZtRqm1+3+ABS8HXh0qhqWsofyNTHV5Sdy06YtkWGFy6l+2swh
8AgxPIzQMgpHVpKSywasO173oQrM/dbJ9uLuNhP2tjbrE5ep9DbiC/geTAQK8w0G
GeuzdfEk8IYREMJkmxjEARCHUUyYjyl6bfwRlkD9qDq3WDqr4izgp1kA3paEGSxe
dWjqB4eH9+PA3m01HV1tlcpn6kPV3Srs8R7dHL2Btwm68qomqIeBplueOPiLCANO
UQ5SGeYfMmvFZdSD+OPTEYNNJW63CRT5a2Wq7x/JZEVI7bw9er9HHu37H3vx6oVY
APUOIQ6NykRe6h27EnonMWccjSBnAKEk1H3nku44/0nPgB1c9i7GyWoL4ELPnn+O
uivTZ/MnavIqZcmigqdC2h0h4gNOzEaMpemZuLkm7uT8kzMiw4VXanM6vOwwhAyB
fWkg+DD6OsTQHB+oa3lV
=KuMo
-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/2be77818-3b5f-395d-0fcf-448afce04ec8%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Where is Documentation for v4.0

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2017-10-28 14:37, Ray Joseph wrote:
> I would like to get off to a safe and efficient start.  Where might I find 
> the latest documentation.
> 

Since Qubes 4.0 stable has not yet been released, most of the
documentation for it is still being written. You can find these
tasks in individual qubes-issues with the "doc" label:

https://github.com/QubesOS/qubes-issues/issues?q=is%3Aopen+is%3Aissue+label%3A%22C%3A+doc%22

We can always use help with writing documentation! Qubes documentation
is a community effort:

https://www.qubes-os.org/doc/doc-guidelines/

As they're completed, the future 4.0 docs will still be available in the
same place as the existing docs, i.e.:

https://www.qubes-os.org/doc/

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

iQIcBAEBCgAGBQJZ9OCbAAoJENtN07w5UDAw8xwQAIC9aWRw3sikDGKtp61d9nsy
ByswLnGPqaCq9i7a5v/henZPfp58Bjj60C0x3XPcja3Qkln7V/NT+kQXsQSBM8rL
BOMfY8uI5z8qKMmIxwn9HbISVBZYH2OuPro+mouiIiDWoxawpWgVp3zFqjRtwr6o
u+0+GtypmjNanVyevhOtZJsQzb8xlV43Q+c3b/zcpYXj4SpaF1sSwvQ1bHkU8tl8
/OfWvFM5t8azTx1bCO2Bf2LJzT+OHZ3PG3ThY0WxiQhkcDYLapq4MwfUYcrv03nw
fIVfJ2C0e4/MjIyi/HoeKgL18tQS+cqRurFhMHTYSXPvUuNrd4bn2/VYbnb0pzmi
bjSxPVu7gkJ+UbhO+yWKQ41dz7R/EERHUL0yPd4MrdpfMG92wxdOJ9N8OfmSUG0q
lDQ3wRThX5qjgvkq0oLVDGNnOVMqeSc4Kxh1DfXg1afWhuaWu+pkcIJ15XnPWKWx
QCPV0FH93dl9KsPNnF0TYnafc+//4KdZHUs7NQ8iOFUvLUfap8NIGdkopClj6kH0
Wb93M1/SoxzRCdWK3UV3NpZD2xZ6WnDLyFq+DjK0zyuuG8IwcNZ5iSm68DQxPRD2
0mxsLqYsGieKcUnGB4qdK+75jqrkB4Vcgrndas7s8RmZHEbsJ+n6ux5YkOkff3wj
aCPxdCZoxJ2TI6iTUNzD
=baws
-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/f6ede27c-616e-7776-253a-1528980cd278%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Where is Documentation for v4.0

[Ray Joseph]

I would like to get off to a safe and efficient start.  Where might I find the 
latest documentation.

-- 
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/152280fa-ffa6-4adc-9980-ff2290ed4ec8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] How to Get Wireless Network Connected

[Ray Joseph]

I would like to get networking running on v3.2.  I installed from a download to 
a USB from Debian 8.  I have now replaced Debian 8 with Qubes OS v3.2.  When 
installing, I had both a w ireless hotspot and a USB3 connected Ethernew dock.  
Neither one worked on boot up.

I am running version 3.2 on a Toshiba laptop.  I have used this machine to run 
Debian 8 with wireless.  I am not getting a connection.  

I get an error window about 120 seconds after booting:
   ERROR:  Tor Bootstrap Result:
   Whonixcheck gave up waiting. 
   Tor Circuit: not established
   Bootstrapping 5% done
...
   Possible issues:
 - is the host's internet connection working?
 - Whonix-Gateway will need a few moments for bootstrapping the Tor network.
 - Do you live in a censored area?

I am using the same Verizon access point I used on Debian.  A listing of points 
from a terminal in sys-net shows the access point.  

Inside sys-net:
  dmesg | grep iwlwifi produces:
Direct firmware load for iwlwifi-7265D-19  failed with error -2
Direct firmware load for iwlwifi-7265D-18  failed with error -2
Direct firmware load for iwlwifi-7265D-17  failed with error -2
Loaded firmware version 16.242414.0 op_mode iwlmvm
...
wlp0s0: renamed from wlan0

I have some concerns: 
1) The system is trying 7265D-19, -18, -17, and fails then loads -16.  In 
Debian, it tried 25, 24, 23 and loaded 22.  It would not load 26 which is the 
newest I could find.  Is there a concern for using such old drivers?  If so, is 
there anything I should do?
2) The wifi name was renamed.  Where does this happen and why?  Are there any 
implications?

lsmod shows the iwlmvm and iwlwifi are loaded.  

modinfo iwlmvm shows iwlwifi,mac80211,cfg80211

ip a  
shows wlp0s0 to be down.
ifup wlp0s0 says it is not configured.  

sudo rmmod iwlmvm says it is not loaded.
sudo modprobe iwlmvm  there was no response

ip a shows wlp0s0 still down.

I am not sure where to go from here.

Any help  would be appreciated.  I plan to change to v4.0 this coming week.

-- 
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/1d6365fc-a1a7-4406-bbdd-8e899d07cae9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Why is there no qubes manager in V4.0?

[Ray Joseph]

On Saturday, October 28, 2017 at 12:40:21 PM UTC-5, Sergio Matta wrote:
> Em sábado, 28 de outubro de 2017 09:14:29 UTC-2, [799]  escreveu:
> > Hello,
> > 
> > > While I do know how to use the cli tools I
> > > enjoy a gui for at a glance viewing and tasks,
> > > it is much easier to press start/stop on a
> > > nice list rather than type two commands.
> > 
> > While I appreciate the new features in Qubes 4, the lack of a graphical 
> > frontend like Qubes Manager is a step backwards, as Linux is always about 
> > choice.
> > Can't someone program a very simple GUI which offers the following 
> > functions:
> > 
> > 1) show all VMs with the option to hide:
> > - internal VMs (I really hope to get this setting back from Qubes 3.2)
> > - Template VMs
> > - all VMs which are not running
> > 
> > 2) indicate which VMs are running
> > 
> > 3) offer the option to do the following actions on a VM:
> > - start
> > - restart
> > - shutdown
> > - kill
> > - open preferences
> > 
> > Nice to have:
> > 
> > 4) maybe also: attach/remove USB and Block-Devices
> > 
> > 5) show an icon if an USB/Block-Device is mounted 
> > 
> > I think that having the options 1 - 3 is perfectly fine, as this will make 
> > the interaction with VMs easier (also for newbies who come from any other 
> > OS).
> > 
> > Please don't get me wrong, I like the new widgets as they offer additional 
> > options, but a central cockpit to do basic tasks is missing.
> > 
> > I can live without additional features like performance metrics in Qubes 
> > Manager, but the basic tasks would be great.
...
> 
> There is many of those requests ready. The running vms you can see using xfce 
> bar with generic monitor (ls --fields ip,name,state). Look these pictures.

This solution looks appropriate.  I am new to quebes and found the vm manager 
challenging using v3.2.  I have not tried v4.  But I am not familiar with the 
xfce bar and the pictures didn't look like the xfce panel on v32.  

I will move to v4 this coming week.  I did not getting anything working on 
v3.2, I would like to get to a better start on v4.  I would apprecitate any 
suggestions on how to better use the tools provided to manage 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/c61edda6-6146-4c7c-b9af-31f428e5f8d9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Why is there no qubes manager in V4.0?

[mikihonzero]

On Saturday, October 28, 2017 at 5:40:21 PM UTC, Sergio Matta wrote:
> Em sábado, 28 de outubro de 2017 09:14:29 UTC-2, [799]  escreveu:
> > Hello,
> > 
> > > While I do know how to use the cli tools I
> > > enjoy a gui for at a glance viewing and tasks,
> > > it is much easier to press start/stop on a
> > > nice list rather than type two commands.
> > 
> > While I appreciate the new features in Qubes 4, the lack of a graphical 
> > frontend like Qubes Manager is a step backwards, as Linux is always about 
> > choice.
> > Can't someone program a very simple GUI which offers the following 
> > functions:
> > 
> > 1) show all VMs with the option to hide:
> > - internal VMs (I really hope to get this setting back from Qubes 3.2)
> > - Template VMs
> > - all VMs which are not running
> > 
> > 2) indicate which VMs are running
> > 
> > 3) offer the option to do the following actions on a VM:
> > - start
> > - restart
> > - shutdown
> > - kill
> > - open preferences
> > 
> > Nice to have:
> > 
> > 4) maybe also: attach/remove USB and Block-Devices
> > 
> > 5) show an icon if an USB/Block-Device is mounted 
> > 
> > I think that having the options 1 - 3 is perfectly fine, as this will make 
> > the interaction with VMs easier (also for newbies who come from any other 
> > OS).
> > 
> > Please don't get me wrong, I like the new widgets as they offer additional 
> > options, but a central cockpit to do basic tasks is missing.
> > 
> > I can live without additional features like performance metrics in Qubes 
> > Manager, but the basic tasks would be great.
> > 
> > Can maybe someone outside of the Qubes Team program this?
> > 
> > [799]
> 
> There is many of those requests ready. The running vms you can see using xfce 
> bar with generic monitor (ls --fields ip,name,state). Look these pictures.

I personally won't upgrade since there is no qubes-manager, for reasons already 
mentioned here and on github. Is there a possibility of people doing a fork of 
qubes-manager for 4.0? 
@Sergio Matta The pictures look really promising (I miss templates/net-vm used 
and ordering by color was extremely useful).
Is there a possibility to make that an actual open (updated) window on the 
desktop (no popup)?   

-- 
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/ccb5cf51-9370-4ed8-bff5-ce01beacf120%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: 4.RC2 CANT create / install VM from local iso

[Filip Magic]

On 10/28/17 11:29, Foppe de Haan wrote:
> On Saturday, October 28, 2017 at 11:27:36 AM UTC+2, Foppe de Haan wrote:
>> On Saturday, October 28, 2017 at 9:49:19 AM UTC+2, Roy Bernat wrote:
>>> On Friday, 27 October 2017 11:26:01 UTC-4, Outback Dingo  wrote:
 So we need updated docs or somethings broken...

 i copied the iso to /home/user from the AppVM tried to create an hvm
 appvm got a unrecognized argument... ok
 then tried without --hvm... seems ok however. qvm-start
 results in a traceback

 [dingo@dom0 ~]$ qvm-create BSD --hvm --label blue
 usage: qvm-create [-h] [--verbose] [--quiet] [--class CLS]
   [--property NAME=VALUE] [--pool VOLUME_NAME=POOL_NAME]
   [-P POOL_NAME] [--template VALUE] [--label VALUE]
   [--help-classes]
   [--root-copy-from FILENAME | --root-move-from FILENAME]
   [VMNAME]
 qvm-create: error: unrecognized arguments: --hvm
 [dingo@dom0 ~]$ qvm-create BSD  --label blue
 sudo qvm-start BSD --cdrom=/home/dingo/FreeBSD-11.1-RELEASE-amd64-disc1.iso
 Traceback (most recent call last):
   File "/bin/qvm-start", line 9, in 
 load_entry_point('qubesadmin==4.0.9', 'console_scripts', 'qvm-start')()
   File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start.py",
 line 160, in main
 drive_assignment = get_drive_assignment(args.app, args.drive)
   File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start.py",
 line 98, in get_drive_assignment
 backend_domain_name, ident = drive_str.split(':', 1)
 ValueError: not enough values to unpack (expected 2, got 1)
 [dingo@dom0 ~]$ qvm-start BSD
 --cdrom=/home/dingo/FreeBSD-11.1-RELEASE-amd64-disc1.iso
 Traceback (most recent call last):
   File "/usr/bin/qvm-start", line 9, in 
 load_entry_point('qubesadmin==4.0.9', 'console_scripts', 'qvm-start')()
   File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start.py",
 line 160, in main
 drive_assignment = get_drive_assignment(args.app, args.drive)
   File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start.py",
 line 98, in get_drive_assignment
 backend_domain_name, ident = drive_str.split(':', 1)
 ValueError: not enough values to unpack (expected 2, got 1)
 [dingo@dom0 ~]$ qvm-start BSD
 --cdrom=/home/dingo/FreeBSD-11.1-RELEASE-amd64-disc1.iso
 Traceback (most recent call last):
   File "/usr/bin/qvm-start", line 9, in 
 load_entry_point('qubesadmin==4.0.9', 'console_scripts', 'qvm-start')()
   File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start.py",
 line 160, in main
 drive_assignment = get_drive_assignment(args.app, args.drive)
   File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start.py",
 line 98, in get_drive_assignment
 backend_domain_name, ident = drive_str.split(':', 1)
 ValueError: not enough values to unpack (expected 2, got 1)

 [user@personal dom0]$
>>> You dont need to use --hvm . it is the default in version 4. 
>>> Regarding the cdrom i have also the same issue it seems that this switch 
>>> has beed deprecated .
>>>
>>>
>>> Roy
>> try qubes-vm-boot-from-device or qvm-start VMNAME --cdrom=VMNAME:/path ; or 
>> use the interface from the second page of the VM settings GUI.
> (Btw, if you type qvm-, or qubes-, bash spits out a list 
> of commands starting with those characters; you can usually find the command 
> you are looking for that way; beyond that, --help or 'man qvm-command' will 
> also provide hints as to available switches, except in the case of qvm-pci 
> currently.)
>
Is qubes-vm-boot-from-device working for you guys ? I'm not able to
install any OS from ISO in StandaloneVM.

-- 
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/6ed50cea-b002-52e1-dc52-a0e7a8f2e2c9%40magicadu.sk.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Why is there no qubes manager in V4.0?

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2017-10-27 23:24, taii...@gmx.com wrote:
> While I do know how to use the cli tools I enjoy a gui for at a 
> glance viewing and tasks, it is much easier to press start/stop on 
> a nice list rather than type two commands.
> 
> Thanks ADW!
> 

Thanks for your feedback in this thread, everyone. Just to briefly
address the original question in the subject line, the reasons for
removing the Qubes VM Manager from Qubes 4.0 are discussed in this
issue:

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

However, na-- recently opened a new issue that reflects many of the
same concerns as in this thread:

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

We're looking into what can be done to improve the user experience in
4.0. Thank you for testing, everyone!

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

iQIcBAEBCgAGBQJZ9LWcAAoJENtN07w5UDAwmQ4P/jVhDfQPQKYxrTvK5psOS8aM
dyOHae12t8Jkb0GrjfYIuk3u+/gNFaw+4dMG58BCfMAV6gZMKvBiTqtH13fX/RNT
3/D5owRtPgj+P6MjWumKO16D929HI/L3wHC51vZPhC8a+to7mi8cG6XEHlfvZcD7
iJwXzRGyUz+qMD/fwGy0cbfqvyrmQgX5QULJMvfK4+YfvwwEs/M9dMsA30XE6s1p
Sc8bc3pXbBFlwGQaN3RFOOa25QeqMHcdKgRmZpagqcdIJuzw01IwkDn4/IGwEOKU
gyB2++1w0/q4a3M4btNHthZHWNnfEPSULCSpZVxL/IXTR5hIw5oAOR0B97HRnFKO
qd1MULj2HUdLXH7oicIok+p/IGEK0SElXJtGTtgwturvyDfAr7BkRwxGF7BGdQBA
5NQfD7Ya87oSAM1PhI/X48HxG9Xia9izrqWHBAjT57gNhgYPZDv2YT1sVEfvhbyX
jzDED9tubE8sSQHbyF/5L5d+5+213yhcmA+J+0FBB5MerD71Flr/+LsVMB7iKnmD
dozUgjJFlopfneRcalotMWgf1XERGX/QC4bBnCJ3hpNmhKqJyk7I+xBPZiaMueoc
FlMU8wYT9BR+PFkODDjOgqdrc/ACp9vXdPjpWJiaHLXZik8iZ0YuwTMY6LLn2i5r
p08JqthOTHM4Gt74UXYM
=+HEQ
-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/03cc413d-b431-4224-10a8-e1fc02fa2359%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Wifi problems on recent updates

[Dan Ballard]

the intel wifi laptop has this in sys-net on boot

Oct 27 07:56:09 sys-net kernel: Intel(R) Wireless WiFi driver for Linux
Oct 27 07:56:09 sys-net kernel: Copyright(c) 2003- 2015 Intel Corporation
Oct 27 07:56:09 sys-net kernel: iwlwifi :00:00.0: Xen PCI mapped GSI18 to 
IRQ26
Oct 27 07:56:09 sys-net kernel: iwlwifi :00:00.0: pci frontend enable msi 
failed for dev 0:0
Oct 27 07:56:09 sys-net kernel: iwlwifi :00:00.0: Xen PCI frontend error: 
-22!
Oct 27 07:56:09 sys-net kernel: iwlwifi :00:00.0: pci_enable_msi failed - 
-22
Oct 27 07:56:09 sys-net kernel: iwlwifi :00:00.0: loaded firmware version 
18.168.6.1 op_mode iwldvm
Oct 27 07:56:09 sys-net kernel: iwlwifi :00:00.0: CONFIG_IWLWIFI_DEBUG 
enabled
Oct 27 07:56:09 sys-net kernel: iwlwifi :00:00.0: CONFIG_IWLWIFI_DEBUGFS 
enabled
Oct 27 07:56:09 sys-net kernel: iwlwifi :00:00.0: 
CONFIG_IWLWIFI_DEVICE_TRACING disabled
Oct 27 07:56:09 sys-net kernel: iwlwifi :00:00.0: Detected Intel(R) 
Centrino(R) Wireless-N 1030 BGN, REV=0xB0
Oct 27 07:56:09 sys-net kernel: iwlwifi :00:00.0: L1 Enabled - LTR Disabled
Oct 27 07:56:09 sys-net kernel: iwlwifi :00:00.0: RF_KILL bit toggled to 
disable radio.
Oct 27 07:56:09 sys-net kernel: ieee80211 phy0: Selected rate control algorithm 
'iwl-agn-rs'
Oct 27 07:56:09 sys-net kernel: iwlwifi :00:00.0 wlp0s0: renamed from wlan0


the kernel is clearly disabling it for some reason

-- 
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/83d8a8e8-3137-4b64-8315-1621bdf82aff%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Wifi problems on recent updates

[Dan Ballard]

On Tuesday, October 24, 2017 at 8:50:18 PM UTC-7, Dan Ballard wrote:
> I upgraded my netbook from Linux 4.4.67 to 4.9.35 and lost wifi ability on 
> it. I believe it was an Atheros chip using the ath9k driver. At least with it 
> I've been able to boot the old 4.4.67 kernel and retain wireless. 
> 
> This week I upgraded my laptop to 4.9.45 and it also lost wifi ability with 
> an Intel iwlwifi driver. And worse, booting old 4.4 kernels is not working 
> for it.
> 
> What data do I need to gather to help troubleshoot this and fix it?

Intel wifi laptop on boot has this in sys-net. the kernel is clearly disabling 
it for some reason.

Oct 27 07:56:09 sys-net kernel: Intel(R) Wireless WiFi driver for Linux
Oct 27 07:56:09 sys-net kernel: Copyright(c) 2003- 2015 Intel Corporation
Oct 27 07:56:09 sys-net kernel: iwlwifi :00:00.0: Xen PCI mapped GSI18 to 
IRQ26
Oct 27 07:56:09 sys-net kernel: iwlwifi :00:00.0: pci frontend enable msi 
failed for dev 0:0
Oct 27 07:56:09 sys-net kernel: iwlwifi :00:00.0: Xen PCI frontend error: 
-22!
Oct 27 07:56:09 sys-net kernel: iwlwifi :00:00.0: pci_enable_msi failed - 
-22
Oct 27 07:56:09 sys-net kernel: iwlwifi :00:00.0: loaded firmware version 
18.168.6.1 op_mode iwldvm
Oct 27 07:56:09 sys-net kernel: iwlwifi :00:00.0: CONFIG_IWLWIFI_DEBUG 
enabled
Oct 27 07:56:09 sys-net kernel: iwlwifi :00:00.0: CONFIG_IWLWIFI_DEBUGFS 
enabled
Oct 27 07:56:09 sys-net kernel: iwlwifi :00:00.0: 
CONFIG_IWLWIFI_DEVICE_TRACING disabled
Oct 27 07:56:09 sys-net kernel: iwlwifi :00:00.0: Detected Intel(R) 
Centrino(R) Wireless-N 1030 BGN, REV=0xB0
Oct 27 07:56:09 sys-net kernel: iwlwifi :00:00.0: L1 Enabled - LTR Disabled
Oct 27 07:56:09 sys-net kernel: iwlwifi :00:00.0: RF_KILL bit toggled to 
disable radio.
Oct 27 07:56:09 sys-net kernel: ieee80211 phy0: Selected rate control algorithm 
'iwl-agn-rs'
Oct 27 07:56:09 sys-net kernel: iwlwifi :00:00.0 wlp0s0: renamed from wlan0

-- 
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/5baec713-d227-46af-9e0d-b029e53534de%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Properly setup a qube dns cache server

[nicholas roveda]

Up to now, I've thought of 2 possible solutions:

Of course Dom0 or a NetManagementVM (thanks to the new Admin API) has to store 
the DNS settings for the VMs with Networking and the easy way is to store only 
the infos about VMs that don't use the standars DNS (10.139.1.1 and 10.139.1.2).
So, adjustments have to be made to let the user specify a dnsVM in 'VM 
Settings', when Networking in not '(none)' and a default 'DNS Backend' field 
(new field in the GUI Qubes Global Settings) where the default value '(none)' 
or 'sys-net' corresponds to '10.139.1.1' and '10.139.1.2'.


Method a)
1) Every time a vif+ interface goes up in the FirewallVM (or the NetVM 
backend), this would have to run `qubes-setup-dnat-to-ns` like VMs that provide 
network do, but this time the script will retrieve the DNS through a rpc 
service instead of '/etc/resolv.conf'.
2) The rpc service will ask Dom0 (or the NetManagementVM) to update the net 
configurations, so Dom0 will retrive the list of current running VMs attached 
to the FirewallVM (or the NetVM backend) and provide it a list of VMs that 
don't use the default configurations and their the custom DNS backend IPs.
3) The FirewallVM (or the NetVM backend) will than update the iptables with 
secific DNAT of packets destinated to port 53 to specific IPs thanks to the 
infos received from Dom0 and maintain the general rule that DNAT all packets 
destinated to port 53 of '10.139.1.1' and '10.139.1.2' to the DNS specified in 
'/etc/resolv.conf'.


Method b)
Every time a qube is started from Dom0, Dom0 launch a rpc-service in its NetVM 
and passes to it any custom DNS configuration, if present, and the rpc service 
again, is the one responsible for executing a modified `qubes-setup-dnat-to-ns` 
to update the iptables.


So, the current 'sys-firewall' NAT table looks like this:
-N PR-QBS
-N PR-QBS-SERVICES
-A PREROUTING -j PR-QBS
-A PREROUTING -j PR-QBS-SERVICES
-A POSTROUTING -o vif+ -j ACCEPT
-A POSTROUTING -o lo -j ACCEPT
-A POSTROUTING -j MASQUERADE
-A PR-QBS -d 10.139.1.1/32 -p udp -m udp --dport 53 -j DNAT --to-destination 
10.139.1.1
-A PR-QBS -d 10.139.1.1/32 -p tcp -m tcp --dport 53 -j DNAT --to-destination 
10.139.1.1
-A PR-QBS -d 10.139.1.2/32 -p udp -m udp --dport 53 -j DNAT --to-destination 
10.139.1.2
-A PR-QBS -d 10.139.1.2/32 -p tcp -m tcp --dport 53 -j DNAT --to-destination 
10.139.1.2

And, the new 'sys-firewall' NAT table will look like this (with both methods):
-N PR-QBS
-N PR-QBS-SERVICES
-A PREROUTING -j PR-QBS
-A PREROUTING -j PR-QBS-SERVICES
-A POSTROUTING -o vif+ -j ACCEPT
-A POSTROUTING -o lo -j ACCEPT
-A POSTROUTING -j MASQUERADE

-A PR-QBS -i vifX -d 10.139.1.1/32 -p udp -m udp --dport 53 -j DNAT 
--to-destination 
-A PR-QBS -i vifX -d 10.139.1.1/32 -p tcp -m tcp --dport 53 -j DNAT 
--to-destination 
-A PR-QBS -i vifX -d 10.139.1.2/32 -p udp -m udp --dport 53 -j DNAT 
--to-destination 
-A PR-QBS -i vifX -d 10.139.1.2/32 -p tcp -m tcp --dport 53 -j DNAT 
--to-destination 

-A PR-QBS -i vifY -d 10.139.1.1/32 -p udp -m udp --dport 5353 -j DNAT 
--to-destination 
-A PR-QBS -i vifY -d 10.139.1.1/32 -p tcp -m tcp --dport 5353 -j DNAT 
--to-destination 
-A PR-QBS -i vifY -d 10.139.1.2/32 -p udp -m udp --dport 5354 -j DNAT 
--to-destination 
-A PR-QBS -i vifY -d 10.139.1.2/32 -p tcp -m tcp --dport 5354 -j DNAT 
--to-destination 
...

# Defaults
-A PR-QBS -d 10.139.1.1/32 -p udp -m udp --dport 53 -j DNAT --to-destination 
10.139.1.1
-A PR-QBS -d 10.139.1.1/32 -p tcp -m tcp --dport 53 -j DNAT --to-destination 
10.139.1.1
-A PR-QBS -d 10.139.1.2/32 -p udp -m udp --dport 53 -j DNAT --to-destination 
10.139.1.2
-A PR-QBS -d 10.139.1.2/32 -p tcp -m tcp --dport 53 -j DNAT --to-destination 
10.139.1.2


It seems to me that the first solution is more elegant and flexible, since it 
allows the FirewallVM to query other machines than Dom0 for networking 
configurations. That is the case described also in the Docs where, thanks to 
the new Admin API, a new ManagmmentVM can install a custom Template and manage 
all the AppVMs that use that Template and their settings.


ISSUES:
1) I haven't discovered yet, how retrive the vif backend interface name of a 
specific VM from Dom0 (querying the Xen DB I think), in order to pass to the 
FirewallVM (or the NetVM backend) the infos in this format:   
[ ... ].
Now, for testing purposed one could use the format:   [ ... 
] and the iptables rules: `sudo iptables -t nat -A PR-QBS -s  -d 
10.139.1.1/32 -p udp -m udp --dport 53 -j DNAT --to-destination `

2) I don't know if I can use udev rules to or Fedora/Debian cutoms system 
launch a script that interact with Dom0 and launch `qubes-setup-dnat-to-ns`.

I've found the file '/etc/udev/rules.d/99-qubes-network.rules' wich cointains 
the following line:
SUBSYSTEMS=="xen", KERNEL=="eth*", ACTION=="add", 
ENV{ID_NET_DRIVER}=="vif", RUN+="/usr/lib/qubes/setup-ip"
, but it doesn't seem to do anything (I've tried to remove it, restart udev and 
start a VMs, but the connection works fine).

Re: Re: [qubes-users] Why is there no qubes manager in V4.0?

[Franz]

On Sat, Oct 28, 2017 at 10:02 AM, cooloutac  wrote:

> I mean maybe there is security implications?  I dunno does gui
> automatically equal risk?  lol  but like 799 say options is good.
>
>
It may be better to wait that something like google manager appears before
installing version 4.  I cannot live without it.

-- 
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/CAPzH-qBMYBHwhGk3q1r-HNjc2c6qi8AUoOYj6s5vU%2B9RUFY8mQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] 4.0rc2 debian template issue

[Jon Solworth]

When install Qubes 4.0rc2, I accidentally hit configure twice. (The second time 
it errored out).  The result is that there is no debian template.

I tried to install debian-9, (sudo qubes-dom0-update qubes-template-debian-9),
but have others have pointed out that template is not working.

I tried to reinstall debian-8.  (sudo qubes-dom0-update qubes-template-debian-8)
This was unsuccessful, even after doing: sudo yum remove qubes-template-debian-8
which returned an error.

Any ideas on how to proceed?

thanks,
Jon


-- 
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/1dbe7b10-4d9a-4592-a2d4-4bba24fa32f1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Re: [qubes-users] Why is there no qubes manager in V4.0?

[cooloutac]

I mean maybe there is security implications?  I dunno does gui automatically 
equal risk?  lol  but like 799 say options is good.

-- 
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/c091bb86-c07d-40b0-b911-a6d881df6073%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Is Qubes OS compatible w/ Dell Inspiron 15R N5110?

[cooloutac]

On Friday, October 27, 2017 at 12:58:13 AM UTC-4, anthon...@gmail.com wrote:
> Is Qubes OS compatible w/ Dell Inspiron 15R N5110?
> http://www.dell.com/support/home/ca/en/cabsdt1/product-support/servicetag/6h9clp1/configuration
> 
> Please let me know. Thanks.

download the live usb and try it out.

-- 
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/07263631-4750-4051-a843-0b6dd8fbc722%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Re: [qubes-users] Why is there no qubes manager in V4.0?

[cooloutac]

On Saturday, October 28, 2017 at 7:50:54 AM UTC-4, [799] wrote:
> Hello, 
> 
> > What original Qubes Manager did wrong:
> > Didn't expose all per-VM settings (qvm-prefs)
> > Didn't expose all global settings (guid.conf)
> > Didn't expose all device options (USB mostly,
> > block devices were available) Duplicated
> > some functionality of the Applications menu
> > Was non-resizable (serious issue when
> > screen real estate is at a premium)
> > Those are some of the reasons it was
> > scrapped.
> 
> Thanks for the feedback, the most annoying thing was the non-resizable 
> window, specifically when using a tiling window manager.
> 
> Still I think dropping Qubes Manager totally is a not the best solution as 
> everyone who didn't like Qubes Manager had the choice to close it or not use 
> it at all.
> 
> All other users who could live with the above 'problems' and would like to 
> use Qubes Manager or something similar are now lost.
> As mentioned I understand if Qubes Team thinks (!) that Qubes Manager is not 
> that good and that they drop support for it, but I just a bad taste as it 
> currently seems that the loss of Qubes Manager is trying to be sold as a good 
> feature.
> It's not. Users should always have the choice, that's what is so great about 
> Linux.
> 
> Thereof I just want to raise my voice that a replacement for Qubes Manager 
> (maybe with less options) would be great.
> 
> I'm fine with using the CLI to setup machines. Change complicated options 
> etc. but for daily use Qubes Manager was great.
> 
> Maybe we should start to collect voices to bring a Qubes GUI App back to 4.0.
> 
> Thereof: 
> My vote for Qubes GUI-Manager.
> Willing to pay 40 eur for a good replacement.
> Who is joining this "campaign"?
> Maybe someone likes to program this, if we throw in some budget.
> 
> [799]

One of the reasons I always have Qubes manager on screen,  not just to see 
updates,  but to see if an orange triangle pops up,  What vms using cpu/memory, 
etc..   always wanted i/o and network activity as well.

-- 
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/24dc2b20-609f-4b12-9705-bc8c71ff969d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Why is there no qubes manager in V4.0?

[cooloutac]

On Saturday, October 28, 2017 at 7:35:20 AM UTC-4, Yethal wrote:
> W dniu sobota, 28 października 2017 13:14:29 UTC+2 użytkownik [799] napisał:
> > Hello,
> > 
> > > While I do know how to use the cli tools I
> > > enjoy a gui for at a glance viewing and tasks,
> > > it is much easier to press start/stop on a
> > > nice list rather than type two commands.
> > 
> > While I appreciate the new features in Qubes 4, the lack of a graphical 
> > frontend like Qubes Manager is a step backwards, as Linux is always about 
> > choice.
> > Can't someone program a very simple GUI which offers the following 
> > functions:
> > 
> > 1) show all VMs with the option to hide:
> > - internal VMs (I really hope to get this setting back from Qubes 3.2)
> > - Template VMs
> > - all VMs which are not running
> > 
> > 2) indicate which VMs are running
> > 
> > 3) offer the option to do the following actions on a VM:
> > - start
> > - restart
> > - shutdown
> > - kill
> > - open preferences
> > 
> > Nice to have:
> > 
> > 4) maybe also: attach/remove USB and Block-Devices
> > 
> > 5) show an icon if an USB/Block-Device is mounted 
> > 
> > I think that having the options 1 - 3 is perfectly fine, as this will make 
> > the interaction with VMs easier (also for newbies who come from any other 
> > OS).
> > 
> > Please don't get me wrong, I like the new widgets as they offer additional 
> > options, but a central cockpit to do basic tasks is missing.
> > 
> > I can live without additional features like performance metrics in Qubes 
> > Manager, but the basic tasks would be great.
> > 
> > Can maybe someone outside of the Qubes Team program this?
> > 
> > [799]
> 
> What original Qubes Manager did wrong:
> Didn't expose all per-VM settings (qvm-prefs)
> Didn't expose all global settings (guid.conf)
> Didn't expose all device options (USB mostly, block devices were available)
> Duplicated some functionality of the Applications menu
> Was non-resizable (serious issue when screen real estate is at a premium)
> 
> Those are some of the reasons it was scrapped.

pretty sure it had all options?  I thought single usb device was added maybe 
I'm wrong.  Don't see why it couldn't be. I thought qubesmanager was removed 
for cosmetic reasons. I never have to use cli in 3.2 unless I accidentally shut 
down instead of restarting sys-usb which I use mouse proxy with.

If things popped up in task manager to alert us that would indeed be better 
then having to keep qubes manager on screen all the time to glance at, but if 
we lose user friendly options in favor of terminal commands, I don't think 
thats a good idea.  Even if commercializing.   Similar to how I initially 
thought moving to xfce was a good idea,  but realizing afterwards that kde's 
customization was very fitting for qubes shortcuts and menus. Seems like Qubes 
keeps getting less user friendly instead of more so.
  
I thought Joanna addressed all my concerns in a blog post regarding qubes 
manager,  I didn't think we would lose any gui options but I guess we have to 
see what happens.

-- 
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/93bb2060-bbc7-413d-b6f8-2e3e3f4094a8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

AW: Re: [qubes-users] Why is there no qubes manager in V4.0?

['[799]' via qubes-users]

Hello,

> What original Qubes Manager did wrong:
> Didn't expose all per-VM settings (qvm-prefs)
> Didn't expose all global settings (guid.conf)
> Didn't expose all device options (USB mostly,
> block devices were available) Duplicated
> some functionality of the Applications menu
> Was non-resizable (serious issue when
> screen real estate is at a premium)
> Those are some of the reasons it was
> scrapped.

Thanks for the feedback, the most annoying thing was the non-resizable window, 
specifically when using a tiling window manager.

Still I think dropping Qubes Manager totally is a not the best solution as 
everyone who didn't like Qubes Manager had the choice to close it or not use it 
at all.

All other users who could live with the above 'problems' and would like to use 
Qubes Manager or something similar are now lost.
As mentioned I understand if Qubes Team thinks (!) that Qubes Manager is not 
that good and that they drop support for it, but I just a bad taste as it 
currently seems that the loss of Qubes Manager is trying to be sold as a good 
feature.
It's not. Users should always have the choice, that's what is so great about 
Linux.

Thereof I just want to raise my voice that a replacement for Qubes Manager 
(maybe with less options) would be great.

I'm fine with using the CLI to setup machines. Change complicated options etc. 
but for daily use Qubes Manager was great.

Maybe we should start to collect voices to bring a Qubes GUI App back to 4.0.

Thereof:
My vote for Qubes GUI-Manager.
Willing to pay 40 eur for a good replacement.
Who is joining this "campaign"?
Maybe someone likes to program this, if we throw in some budget.

[799]

-- 
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/qOHhumU7cKdGlZxgDDB-RxOOI5WjwCXmvNKu0whHmWcbC8Jr18Sc5zaLpVIjf29kv0TEiXG5SxyIeQbo04RCHhnVygNArS-i8ELWaZtjdM8%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Why is there no qubes manager in V4.0?

[Yethal]

W dniu sobota, 28 października 2017 13:14:29 UTC+2 użytkownik [799] napisał:
> Hello,
> 
> > While I do know how to use the cli tools I
> > enjoy a gui for at a glance viewing and tasks,
> > it is much easier to press start/stop on a
> > nice list rather than type two commands.
> 
> While I appreciate the new features in Qubes 4, the lack of a graphical 
> frontend like Qubes Manager is a step backwards, as Linux is always about 
> choice.
> Can't someone program a very simple GUI which offers the following functions:
> 
> 1) show all VMs with the option to hide:
> - internal VMs (I really hope to get this setting back from Qubes 3.2)
> - Template VMs
> - all VMs which are not running
> 
> 2) indicate which VMs are running
> 
> 3) offer the option to do the following actions on a VM:
> - start
> - restart
> - shutdown
> - kill
> - open preferences
> 
> Nice to have:
> 
> 4) maybe also: attach/remove USB and Block-Devices
> 
> 5) show an icon if an USB/Block-Device is mounted 
> 
> I think that having the options 1 - 3 is perfectly fine, as this will make 
> the interaction with VMs easier (also for newbies who come from any other OS).
> 
> Please don't get me wrong, I like the new widgets as they offer additional 
> options, but a central cockpit to do basic tasks is missing.
> 
> I can live without additional features like performance metrics in Qubes 
> Manager, but the basic tasks would be great.
> 
> Can maybe someone outside of the Qubes Team program this?
> 
> [799]

What original Qubes Manager did wrong:
Didn't expose all per-VM settings (qvm-prefs)
Didn't expose all global settings (guid.conf)
Didn't expose all device options (USB mostly, block devices were available)
Duplicated some functionality of the Applications menu
Was non-resizable (serious issue when screen real estate is at a premium)

Those are some of the reasons it was scrapped.

-- 
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/a720b022-23d5-4ff8-b7f3-920702df32e2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

AW: [qubes-users] Why is there no qubes manager in V4.0?

['[799]' via qubes-users]

Hello,

> While I do know how to use the cli tools I
> enjoy a gui for at a glance viewing and tasks,
> it is much easier to press start/stop on a
> nice list rather than type two commands.

While I appreciate the new features in Qubes 4, the lack of a graphical 
frontend like Qubes Manager is a step backwards, as Linux is always about 
choice.
Can't someone program a very simple GUI which offers the following functions:

1) show all VMs with the option to hide:
- internal VMs (I really hope to get this setting back from Qubes 3.2)
- Template VMs
- all VMs which are not running

2) indicate which VMs are running

3) offer the option to do the following actions on a VM:
- start
- restart
- shutdown
- kill
- open preferences

Nice to have:

4) maybe also: attach/remove USB and Block-Devices

5) show an icon if an USB/Block-Device is mounted

I think that having the options 1 - 3 is perfectly fine, as this will make the 
interaction with VMs easier (also for newbies who come from any other OS).

Please don't get me wrong, I like the new widgets as they offer additional 
options, but a central cockpit to do basic tasks is missing.

I can live without additional features like performance metrics in Qubes 
Manager, but the basic tasks would be great.

Can maybe someone outside of the Qubes Team program this?

[799]

-- 
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/PMUSHJUSM_YjHGdqMIJTlwz5I5fdL3SeNQPW_v5p4i2y2RpQ35uqwaYGwmofav8wd6RNzuLf-ZJXQs2HYV6H5qmKpE7AA3Q7RbEpZ5XWfVc%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Windows 8.1 HVM - Windows mouse pointer moves at wrong speed

[Robin Green]

After my Windows 8.1 VM updated itself today, first the Windows mouse pointer 
disappeared entirely, and then when I rebooted it, it stopped moving as far as 
the Qubes mouse pointer, so the two mouse pointers became out of sync.

The solution was to go into the Control Panel in Windows and in Mouse Settings, 
disable "Enhance pointer precision" (which is a bit tricky to do while the 
mouse isn't working properly).

-- 
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/66a337c0-29b5-493d-8d6e-8ac82aacb733%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: 4.RC2 CANT create / install VM from local iso

[Foppe de Haan]

On Saturday, October 28, 2017 at 11:27:36 AM UTC+2, Foppe de Haan wrote:
> On Saturday, October 28, 2017 at 9:49:19 AM UTC+2, Roy Bernat wrote:
> > On Friday, 27 October 2017 11:26:01 UTC-4, Outback Dingo  wrote:
> > > So we need updated docs or somethings broken...
> > > 
> > > i copied the iso to /home/user from the AppVM tried to create an hvm
> > > appvm got a unrecognized argument... ok
> > > then tried without --hvm... seems ok however. qvm-start
> > > results in a traceback
> > > 
> > > [dingo@dom0 ~]$ qvm-create BSD --hvm --label blue
> > > usage: qvm-create [-h] [--verbose] [--quiet] [--class CLS]
> > >   [--property NAME=VALUE] [--pool VOLUME_NAME=POOL_NAME]
> > >   [-P POOL_NAME] [--template VALUE] [--label VALUE]
> > >   [--help-classes]
> > >   [--root-copy-from FILENAME | --root-move-from FILENAME]
> > >   [VMNAME]
> > > qvm-create: error: unrecognized arguments: --hvm
> > > [dingo@dom0 ~]$ qvm-create BSD  --label blue
> > > sudo qvm-start BSD 
> > > --cdrom=/home/dingo/FreeBSD-11.1-RELEASE-amd64-disc1.iso
> > > Traceback (most recent call last):
> > >   File "/bin/qvm-start", line 9, in 
> > > load_entry_point('qubesadmin==4.0.9', 'console_scripts', 
> > > 'qvm-start')()
> > >   File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start.py",
> > > line 160, in main
> > > drive_assignment = get_drive_assignment(args.app, args.drive)
> > >   File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start.py",
> > > line 98, in get_drive_assignment
> > > backend_domain_name, ident = drive_str.split(':', 1)
> > > ValueError: not enough values to unpack (expected 2, got 1)
> > > [dingo@dom0 ~]$ qvm-start BSD
> > > --cdrom=/home/dingo/FreeBSD-11.1-RELEASE-amd64-disc1.iso
> > > Traceback (most recent call last):
> > >   File "/usr/bin/qvm-start", line 9, in 
> > > load_entry_point('qubesadmin==4.0.9', 'console_scripts', 
> > > 'qvm-start')()
> > >   File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start.py",
> > > line 160, in main
> > > drive_assignment = get_drive_assignment(args.app, args.drive)
> > >   File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start.py",
> > > line 98, in get_drive_assignment
> > > backend_domain_name, ident = drive_str.split(':', 1)
> > > ValueError: not enough values to unpack (expected 2, got 1)
> > > [dingo@dom0 ~]$ qvm-start BSD
> > > --cdrom=/home/dingo/FreeBSD-11.1-RELEASE-amd64-disc1.iso
> > > Traceback (most recent call last):
> > >   File "/usr/bin/qvm-start", line 9, in 
> > > load_entry_point('qubesadmin==4.0.9', 'console_scripts', 
> > > 'qvm-start')()
> > >   File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start.py",
> > > line 160, in main
> > > drive_assignment = get_drive_assignment(args.app, args.drive)
> > >   File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start.py",
> > > line 98, in get_drive_assignment
> > > backend_domain_name, ident = drive_str.split(':', 1)
> > > ValueError: not enough values to unpack (expected 2, got 1)
> > > 
> > > [user@personal dom0]$
> > 
> > You dont need to use --hvm . it is the default in version 4. 
> > Regarding the cdrom i have also the same issue it seems that this switch 
> > has beed deprecated .
> > 
> > 
> > Roy
> 
> try qubes-vm-boot-from-device or qvm-start VMNAME --cdrom=VMNAME:/path ; or 
> use the interface from the second page of the VM settings GUI.

(Btw, if you type qvm-, or qubes-, bash spits out a list of 
commands starting with those characters; you can usually find the command you 
are looking for that way; beyond that, --help or 'man qvm-command' will also 
provide hints as to available switches, except in the case of qvm-pci 
currently.)

-- 
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/3174c27d-c46d-4326-917b-6ce7aa78768f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: 4.RC2 CANT create / install VM from local iso

[Foppe de Haan]

On Saturday, October 28, 2017 at 9:49:19 AM UTC+2, Roy Bernat wrote:
> On Friday, 27 October 2017 11:26:01 UTC-4, Outback Dingo  wrote:
> > So we need updated docs or somethings broken...
> > 
> > i copied the iso to /home/user from the AppVM tried to create an hvm
> > appvm got a unrecognized argument... ok
> > then tried without --hvm... seems ok however. qvm-start
> > results in a traceback
> > 
> > [dingo@dom0 ~]$ qvm-create BSD --hvm --label blue
> > usage: qvm-create [-h] [--verbose] [--quiet] [--class CLS]
> >   [--property NAME=VALUE] [--pool VOLUME_NAME=POOL_NAME]
> >   [-P POOL_NAME] [--template VALUE] [--label VALUE]
> >   [--help-classes]
> >   [--root-copy-from FILENAME | --root-move-from FILENAME]
> >   [VMNAME]
> > qvm-create: error: unrecognized arguments: --hvm
> > [dingo@dom0 ~]$ qvm-create BSD  --label blue
> > sudo qvm-start BSD --cdrom=/home/dingo/FreeBSD-11.1-RELEASE-amd64-disc1.iso
> > Traceback (most recent call last):
> >   File "/bin/qvm-start", line 9, in 
> > load_entry_point('qubesadmin==4.0.9', 'console_scripts', 'qvm-start')()
> >   File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start.py",
> > line 160, in main
> > drive_assignment = get_drive_assignment(args.app, args.drive)
> >   File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start.py",
> > line 98, in get_drive_assignment
> > backend_domain_name, ident = drive_str.split(':', 1)
> > ValueError: not enough values to unpack (expected 2, got 1)
> > [dingo@dom0 ~]$ qvm-start BSD
> > --cdrom=/home/dingo/FreeBSD-11.1-RELEASE-amd64-disc1.iso
> > Traceback (most recent call last):
> >   File "/usr/bin/qvm-start", line 9, in 
> > load_entry_point('qubesadmin==4.0.9', 'console_scripts', 'qvm-start')()
> >   File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start.py",
> > line 160, in main
> > drive_assignment = get_drive_assignment(args.app, args.drive)
> >   File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start.py",
> > line 98, in get_drive_assignment
> > backend_domain_name, ident = drive_str.split(':', 1)
> > ValueError: not enough values to unpack (expected 2, got 1)
> > [dingo@dom0 ~]$ qvm-start BSD
> > --cdrom=/home/dingo/FreeBSD-11.1-RELEASE-amd64-disc1.iso
> > Traceback (most recent call last):
> >   File "/usr/bin/qvm-start", line 9, in 
> > load_entry_point('qubesadmin==4.0.9', 'console_scripts', 'qvm-start')()
> >   File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start.py",
> > line 160, in main
> > drive_assignment = get_drive_assignment(args.app, args.drive)
> >   File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start.py",
> > line 98, in get_drive_assignment
> > backend_domain_name, ident = drive_str.split(':', 1)
> > ValueError: not enough values to unpack (expected 2, got 1)
> > 
> > [user@personal dom0]$
> 
> You dont need to use --hvm . it is the default in version 4. 
> Regarding the cdrom i have also the same issue it seems that this switch has 
> beed deprecated .
> 
> 
> Roy

try qubes-vm-boot-from-device or qvm-start VMNAME --cdrom=VMNAME:/path ; or use 
the interface from the second page of the VM settings GUI.

-- 
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/7a2da4e4-ee69-4de3-80fc-182b65a07614%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: 4.RC2 CANT create / install VM from local iso

[Roy Bernat]

On Friday, 27 October 2017 11:26:01 UTC-4, Outback Dingo  wrote:
> So we need updated docs or somethings broken...
> 
> i copied the iso to /home/user from the AppVM tried to create an hvm
> appvm got a unrecognized argument... ok
> then tried without --hvm... seems ok however. qvm-start
> results in a traceback
> 
> [dingo@dom0 ~]$ qvm-create BSD --hvm --label blue
> usage: qvm-create [-h] [--verbose] [--quiet] [--class CLS]
>   [--property NAME=VALUE] [--pool VOLUME_NAME=POOL_NAME]
>   [-P POOL_NAME] [--template VALUE] [--label VALUE]
>   [--help-classes]
>   [--root-copy-from FILENAME | --root-move-from FILENAME]
>   [VMNAME]
> qvm-create: error: unrecognized arguments: --hvm
> [dingo@dom0 ~]$ qvm-create BSD  --label blue
> sudo qvm-start BSD --cdrom=/home/dingo/FreeBSD-11.1-RELEASE-amd64-disc1.iso
> Traceback (most recent call last):
>   File "/bin/qvm-start", line 9, in 
> load_entry_point('qubesadmin==4.0.9', 'console_scripts', 'qvm-start')()
>   File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start.py",
> line 160, in main
> drive_assignment = get_drive_assignment(args.app, args.drive)
>   File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start.py",
> line 98, in get_drive_assignment
> backend_domain_name, ident = drive_str.split(':', 1)
> ValueError: not enough values to unpack (expected 2, got 1)
> [dingo@dom0 ~]$ qvm-start BSD
> --cdrom=/home/dingo/FreeBSD-11.1-RELEASE-amd64-disc1.iso
> Traceback (most recent call last):
>   File "/usr/bin/qvm-start", line 9, in 
> load_entry_point('qubesadmin==4.0.9', 'console_scripts', 'qvm-start')()
>   File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start.py",
> line 160, in main
> drive_assignment = get_drive_assignment(args.app, args.drive)
>   File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start.py",
> line 98, in get_drive_assignment
> backend_domain_name, ident = drive_str.split(':', 1)
> ValueError: not enough values to unpack (expected 2, got 1)
> [dingo@dom0 ~]$ qvm-start BSD
> --cdrom=/home/dingo/FreeBSD-11.1-RELEASE-amd64-disc1.iso
> Traceback (most recent call last):
>   File "/usr/bin/qvm-start", line 9, in 
> load_entry_point('qubesadmin==4.0.9', 'console_scripts', 'qvm-start')()
>   File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start.py",
> line 160, in main
> drive_assignment = get_drive_assignment(args.app, args.drive)
>   File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start.py",
> line 98, in get_drive_assignment
> backend_domain_name, ident = drive_str.split(':', 1)
> ValueError: not enough values to unpack (expected 2, got 1)
> 
> [user@personal dom0]$

You dont need to use --hvm . it is the default in version 4. 
Regarding the cdrom i have also the same issue it seems that this switch has 
beed deprecated .


Roy 

-- 
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/d29a6079-78cc-4b98-9bb2-6d2749d2c92f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: attaching to VM consoles for debugging purposes

[Francesco Rmp]

Il giorno sabato 28 ottobre 2017 07:19:52 UTC+2, Foppe de Haan ha scritto:
> you can try 'qvm-start-gui --all' first, to see if that helps; otherwise, 
> your best bet is 'sudo xl console -t pv VMNAME'

Ok i can use xl to reach the console.

here are my findings.
if i attach to my "personal" domain using xl, log in as root and launch xterm 
from the console, i get the terminal window appearing on the desktop and 
everything works.

On the other end, if i do the same with whonix and try to run a graphical 
application, i get a "cannot open display" error, which suggests me that it 
cant connect to the x server? or the qubes services are not properly running in 
the 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/29a2d735-2560-47d0-be83-411a096e8205%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.