date:20190109

On 1/9/19 7:54 PM, Stumpy wrote:

On 1/9/19 7:32 PM, Marek Marczykowski-Górecki wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Wed, Jan 09, 2019 at 07:11:50PM -0500, Chris Laprise wrote:

On 01/09/2019 06:41 PM, Stumpy wrote:

On 1/8/19 7:59 PM, 'awokd' via qubes-users wrote:

Stumpy wrote on 1/9/19 12:07 AM:

On 1/8/19 7:04 PM, Stumpy wrote:

I thought I had snap installed but the app i installed via
snap now does not seem to be working? I installed snapd in
dom0 then tried installing a snap package in one of appvms
but I am getting errors. If i try to run a snap from dom0:
qvm-run gfx /snap/bin/xnview

I get:
Running '/snap/bin/xnview/ on gfx
gfx: command failed with code: 1

when i try to run it within the appvm i get:
user@gfx:~$ xnview
Can not open
/var/lib/snapd/seccomp/profiles//snap.xnview.xnview (No such
file or directory)
aborting: No such file or directory

thoughts? please?

oh, and if i try to reinstall the app I get:
user@gfx:~$ sudo snap install xnview
snap "xnview" is already installed

Nothing should be installed to dom0. You'd have to install snapd in
a template, and possibly the snap package. You might want to create
a Standalone VM and install everything in there, instead of
templates & AppVMs.

Thanks, I had thought I had to install on dom0 as well, perhaps not,
though when I try to:

sudo snap install xnview from the template I get:
user@debian-9:~$ sudo snap install xnviewmp
error: cannot install "xnviewmp": Get
https://search.apps.ubuntu.com/api/v1/snaps/details/core?channel=stable=anon_download_url%2Carchitecture%2Cchannel%2Cdownload_sha3_384%2Csummary%2Cdescription%2Cdeltas%2Cbinary_filesize%2Cdownload_url%2Cepoch%2Cicon_url%2Clast_updated%2Cpackage_name%2Cprices%2Cpublisher%2Cratings_average%2Crevision%2Cscreenshot_urls%2Csnap_id%2Csupport_url%2Ctitle%2Ccontent%2Cversion%2Corigin%2Cdeveloper_id%2Cprivate%2Cconfinement:

dial tcp: lookup search.apps.ubuntu.com on 10.137.3.254:53: dial udp
10.137.3.254:53: connect: network is unreachable

So i was thinking that doing a qubes-dom0-update something so it could
get through? For the life of me i cant figure out what I did on my
other

computer to make it work but it works fine there.

I forgot to mention, it is installed in the appvm:

user@debian-9:~$ sudo apt-get install snapd
Reading package lists... Done
Building dependency tree
Reading state information... Done
snapd is already the newest version (2.21-2+b1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

ideas?

Only apt is configured to access servers through the special Qubes
proxy.
Since templates have networking turned off by default, that means
nothing

else can download packages or data.

In the short term, you can try enabling networking temporarily for the
template while you install snap packages. Just set the netvm in the
template's settings.

In the long term, Qubes users may benefit from a special
accommodation of
snap, which has become a versatile and important way to install
software.

Support could include access through the update proxy and even special
storage capabilities. Would be a good idea to open an enhancement
issue for

this. :)

There is some progress on this already:
https://github.com/QubesOS/qubes-issues/issues/2766

The current state is: you can install "qubes-snapd-helper" package in
_template_, to be able to install snaps in qubes _based on that
template_.

- -- 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-

iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlw2kq8ACgkQ24/THMrX
1yzNvwgAhc0/O9VIzBGH1WDg8l+1sH3yLxxySFannO2ihUUXbUA80cf4+uxrxk/1
Rg+jR0XfdBXD91h817luvs3mIdqwcluq1YHxbGIb0J/vALPLHRhZ8YLasXSdpDIG
MyiVTk1ogAOG6jH30245V/GRPWALJmysYnW4DUki3ZefG/EyCFHWi7lpJZ9XS00F
QbVv7MoDx6GbHiSfHMzYk016fSaEAFlXGUUXczSHgDpJjumP6+MfVkz0l4diYbm5
wGOPIknWLBBSQMMOS0IoaB1iq1hYbZNULt6/gaOOFBIC2I9D2m4Q8KHKeDz95qln
HEzk2d5IJJlv8M1xpoNyzS0+IJNHMQ==
=hL/D
-END PGP SIGNATURE-

Thanks Marek! I thought there was something, I will recheck what I have
done and make sure I tried the snapd helper in the right place.

That got it Yeah!! Thank you soo much.
Made notes on how it got done this time :)

--
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/9102519c-818a-51f5-f777-c2490110eef7%40posteo.net.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Installing snaps in appvms?

On 1/9/19 7:32 PM, Marek Marczykowski-Górecki wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Wed, Jan 09, 2019 at 07:11:50PM -0500, Chris Laprise wrote:

On 01/09/2019 06:41 PM, Stumpy wrote:

On 1/8/19 7:59 PM, 'awokd' via qubes-users wrote:

Stumpy wrote on 1/9/19 12:07 AM:

On 1/8/19 7:04 PM, Stumpy wrote:

I get:
Running '/snap/bin/xnview/ on gfx
gfx: command failed with code: 1

when i try to run it within the appvm i get:
user@gfx:~$ xnview
Can not open
/var/lib/snapd/seccomp/profiles//snap.xnview.xnview (No such
file or directory)
aborting: No such file or directory

thoughts? please?

oh, and if i try to reinstall the app I get:
user@gfx:~$ sudo snap install xnview
snap "xnview" is already installed

Thanks, I had thought I had to install on dom0 as well, perhaps not,
though when I try to:

So i was thinking that doing a qubes-dom0-update something so it could
get through? For the life of me i cant figure out what I did on my other
computer to make it work but it works fine there.

I forgot to mention, it is installed in the appvm:

ideas?

Only apt is configured to access servers through the special Qubes proxy.
Since templates have networking turned off by default, that means nothing
else can download packages or data.

In the short term, you can try enabling networking temporarily for the
template while you install snap packages. Just set the netvm in the
template's settings.

In the long term, Qubes users may benefit from a special accommodation of
snap, which has become a versatile and important way to install software.
Support could include access through the update proxy and even special
storage capabilities. Would be a good idea to open an enhancement issue for
this. :)

There is some progress on this already:
https://github.com/QubesOS/qubes-issues/issues/2766

The current state is: you can install "qubes-snapd-helper" package in
_template_, to be able to install snaps in qubes _based on that template_.

- --
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-

Thanks Marek! I thought there was something, I will recheck what I have
done and make sure I tried the snapd helper in the right place.

--
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/57f86cd5-621f-1625-87b8-b9bc9c636ea0%40posteo.net.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] qubes dom0 update breaks template updating

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Wed, Jan 09, 2019 at 10:19:00PM +, qtpie wrote:
> The latest dom0 update broke updating my templates. I altered
> /etc/qubes-rpc/policy/qubes.UpdatesProxy to change the updateproxy to
> sys-whonix.

Can you explain what/how exactly it's broken?
/etc/qubes-rpc/policy/qubes.UpdatesProxy should not be overridden by an
update, so any local modifications should remain. Also, using sys-whonix
as updates proxy is a valid configuration we test regularly and did not
spotted any issues recently...

> My solution is to uncomment the lines starting with 'tag', while leaving
> the lines in the old formatting untouched.
> 
> This solution seems weird since here it is suggested that the lines
> starting with 'tag' should replace the other lines:
> https://github.com/QubesOS/qubes-mgmt-salt-dom0-virtual-machines/commit/ca27a33b0ec59f5ea2d4b334973eaa837f11ffc4
> 
> I'm not saying this is a bug, I can understand that an update is not
> compatible with certain customisations and it is the users responsiblity
> to fix this.
> 
> In any case - enjoying Qubes everyday!

- -- 
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-

iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlw2lpUACgkQ24/THMrX
1yw3PQf/YuxS53SSNvIjyjbUxNXjCMMRO6RU3p1JjdrPwYbmo+8adCFRdmyDJake
kH+1FginUxsUpqySOvX1Xw516p00Ct+1sKVOcgfmLKU9Ama7peNoUNcRBTr3jmst
FC3rRsrxofT3E3ceCmd/BXFJdIK/JEof130DXEYsBxKdf/9qm5BVYVkN+Q3VmvIA
uwz0VWstF3Z2vXvwgWLcMyTjpuxhdWBMuLeJSGqI0gWwltztgpyGERp24UjraK6E
xZtVIie+7MGnfXI6ZpONeLjdTAAW+VKGvvWs5YncbxKVQIdUucILbkQamwqiyD1m
XatKifnvLe9WO4MrrzZR22h79gua5A==
=WJ+F
-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/20190110004925.GE7536%40mail-itl.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] mooltipass hardware password manager

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Wed, Jan 09, 2019 at 03:26:02PM -0800, Benjamin Richter wrote:
> Hi,
> 
> I have a Mooltipass Mini Hardware Password manager 
> (https://www.themooltipass.com/), which identifies as a USB keyboard in order 
> to input passwords.
> 
> I can attach the USB device to a VM to connect to the mooltipass mini and put 
> in credentials, but I cannot get it to input the password, neither 

> by attaching it to a VM directly, 

This may be about permissions to /dev/input/event* device files in the
target qube. See X server log about it. If that's the case, you need an
udev rule to allow it, like this:

/etc/udev/rules.d/90-allow-input-for-qubes.rules:
KERNEL=="event*", GROUP="qubes", MODE="0660"

> nor by leaving it in the USB qube via the input proxy.
> The key events just don't seem to turn up anywhere.

I'm not sure how this device really works, but with input proxy it may
be missing some feedback channel (browser -> device), for example to
choose the right credentials.

> I'm running latest stable R4. My USB keyboard, touchpad and touchscreen work, 
> also I don't have any problems with other USB devices. How can I debug this 
> further?
> 
> journalctl output while connecting:
> 
> Jan 10 00:21:07 sys-usb kernel: usb 2-1: new full-speed USB device number 10 
> using xhci_hcd
> Jan 10 00:21:07 sys-usb kernel: usb 2-1: New USB device found, idVendor=16d0, 
> idProduct=09a0
> Jan 10 00:21:07 sys-usb kernel: usb 2-1: New USB device strings: Mfr=1, 
> Product=2, SerialNumber=0
> Jan 10 00:21:07 sys-usb kernel: usb 2-1: Product: Mooltipass
> Jan 10 00:21:07 sys-usb kernel: usb 2-1: Manufacturer: SE
> Jan 10 00:21:07 sys-usb kernel: hid-generic 0003:16D0:09A0.001B: 
> hiddev96,hidraw1: USB HID v1.11 Device [SE Mooltipass] on 
> usb-:00:07.0-1/input0
> Jan 10 00:21:07 sys-usb kernel: input: SE Mooltipass as 
> /devices/pci:00/:00:07.0/usb2/2-1/2-1:1.1/0003:16D0:09A0.001C/input/input36
> Jan 10 00:21:07 sys-usb kernel: hid-generic 0003:16D0:09A0.001C: 
> input,hidraw2: USB HID v1.11 Keyboard [SE Mooltipass] on 
> usb-:00:07.0-1/input1
> Jan 10 00:21:07 sys-usb mtp-probe[30635]: checking bus 2, device 10: 
> "/sys/devices/pci:00/:00:07.0/usb2/2-1"
> Jan 10 00:21:07 sys-usb mtp-probe[30635]: bus: 2, device: 10 was not an MTP 
> device
> Jan 10 00:21:07 sys-usb kernel: audit: type=1130 audit(1547076067.807:236): 
> pid=1 uid=0 auid=4294967295 ses=4294967295 
> msg='unit=qubes-input-sender-keyboard@event6 comm="systemd" 
> exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
> Jan 10 00:21:07 sys-usb audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 
> ses=4294967295 msg='unit=qubes-input-sender-keyboard@event6 comm="systemd" 
> exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
> Jan 10 00:21:07 sys-usb systemd[1]: Started Qubes input proxy sender 
> (keyboard).

This looks promising. What do you have in
/etc/qubes-rpc/policy/qubes.InputKeyboard in dom0? As your USB keyboard
works, you probably have it configured correctly already, but see 
https://www.qubes-os.org/doc/usb/#how-to-use-a-usb-keyboard

You can also see qrexec connections log in dom0 with
`journalctl SYSLOG_IDENTIFIER=qrexec` (or simply grep for qrexec, if you
hate to type that long field name...)

Checking if X server in dom0 sees the device (xinput tool) also may be
helpful. evtest in dom0 may also give some hints.

> Jan 10 00:21:07 sys-usb systemd-logind[436]: Watching system buttons on 
> /dev/input/event6 (SE Mooltipass)

(...)

> Testing ... (interrupt to exit)
> ***
>   This device is grabbed by another process.

This is most likely the input proxy. Which means it's running.

- -- 
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-

iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlw2liwACgkQ24/THMrX
1yyIcAf/R5t1JsBeH4V9bOJtevq7qbjwhCW17jWgNyZuAX9KR5EmdzIgXg5w8kwI
XvY3M+rfy5IPEyk8le4IifX4c8OhbfXAkETqAibUxX+qrtRZHTBoIsgsCDWpKj90
T+CYEsGx+I4ilb0ygBzn4v7zDZ/VTiDixJalIY1oQ4+xaDHS/BrFEcZ+EeG9eqeh
vncKoRmPrdA1OR5xvwfG7NBm2pUJHumPP0yu072yKh/a59aAe3ZRxgxZTwbWkbgo
LinsbjG6G57JTjnS9oNAVrMjdTaB3xWG3cMA2343nIZCg8bEEjeiw+qjxo25jyLl
z+uTpLuBbXeUNiKaqLjWhc2ta1Vq0w==
=94WL
-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/20190110004740.GD7536%40mail-itl.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Installing snaps in appvms?

On 1/9/19 7:11 PM, Chris Laprise wrote:

On 01/09/2019 06:41 PM, Stumpy wrote:

On 1/8/19 7:59 PM, 'awokd' via qubes-users wrote:

Stumpy wrote on 1/9/19 12:07 AM:

On 1/8/19 7:04 PM, Stumpy wrote:
I thought I had snap installed but the app i installed via snap now
does not seem to be working? I installed snapd in dom0 then tried
installing a snap package in one of appvms but I am getting errors.
If i try to run a snap from dom0:

qvm-run gfx /snap/bin/xnview

I get:
Running '/snap/bin/xnview/ on gfx
gfx: command failed with code: 1

when i try to run it within the appvm i get:
user@gfx:~$ xnview
Can not open /var/lib/snapd/seccomp/profiles//snap.xnview.xnview
(No such file or directory)

aborting: No such file or directory

thoughts? please?

oh, and if i try to reinstall the app I get:
user@gfx:~$ sudo snap install xnview
snap "xnview" is already installed

Nothing should be installed to dom0. You'd have to install snapd in a
template, and possibly the snap package. You might want to create a
Standalone VM and install everything in there, instead of templates &
AppVMs.

Thanks, I had thought I had to install on dom0 as well, perhaps not,
though when I try to:

So i was thinking that doing a qubes-dom0-update something so it could
get through? For the life of me i cant figure out what I did on my
other computer to make it work but it works fine there.

I forgot to mention, it is installed in the appvm:

ideas?

Only apt is configured to access servers through the special Qubes
proxy. Since templates have networking turned off by default, that means
nothing else can download packages or data.

In the short term, you can try enabling networking temporarily for the
template while you install snap packages. Just set the netvm in the
template's settings.

In the long term, Qubes users may benefit from a special accommodation
of snap, which has become a versatile and important way to install
software. Support could include access through the update proxy and even
special storage capabilities. Would be a good idea to open an
enhancement issue for this. :)

thanks for that.
I had thought that work that https://github.com/maximilize did and Marek
packaged https://github.com/QubesOS/qubes-app-linux-snapd-helper was
supposed to address the installing from templates as well ad bind
directories? or something like that?

--
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/ff39b9a9-49a3-c8c9-0dac-a4acde6139ab%40posteo.net.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Installing snaps in appvms?

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Wed, Jan 09, 2019 at 07:11:50PM -0500, Chris Laprise wrote:
> On 01/09/2019 06:41 PM, Stumpy wrote:
> > On 1/8/19 7:59 PM, 'awokd' via qubes-users wrote:
> > > Stumpy wrote on 1/9/19 12:07 AM:
> > > > On 1/8/19 7:04 PM, Stumpy wrote:
> > > > > I thought I had snap installed but the app i installed via
> > > > > snap now does not seem to be working? I installed snapd in
> > > > > dom0 then tried installing a snap package in one of appvms
> > > > > but I am getting errors. If i try to run a snap from dom0:
> > > > > qvm-run gfx /snap/bin/xnview
> > > > > 
> > > > > I get:
> > > > > Running '/snap/bin/xnview/ on gfx
> > > > > gfx: command failed with code: 1
> > > > > 
> > > > > when i try to run it within the appvm i get:
> > > > > user@gfx:~$ xnview
> > > > > Can not open
> > > > > /var/lib/snapd/seccomp/profiles//snap.xnview.xnview (No such
> > > > > file or directory)
> > > > > aborting: No such file or directory
> > > > > 
> > > > > thoughts? please?
> > > > > 
> > > > 
> > > > oh, and if i try to reinstall the app I get:
> > > > user@gfx:~$ sudo snap install xnview
> > > > snap "xnview" is already installed
> > > 
> > > Nothing should be installed to dom0. You'd have to install snapd in
> > > a template, and possibly the snap package. You might want to create
> > > a Standalone VM and install everything in there, instead of
> > > templates & AppVMs.
> > > 
> > > 
> > 
> > Thanks, I had thought I had to install on dom0 as well, perhaps not,
> > though when I try to:
> > 
> > sudo snap install xnview from the template I get:
> > user@debian-9:~$ sudo snap install xnviewmp
> > error: cannot install "xnviewmp": Get 
> > https://search.apps.ubuntu.com/api/v1/snaps/details/core?channel=stable=anon_download_url%2Carchitecture%2Cchannel%2Cdownload_sha3_384%2Csummary%2Cdescription%2Cdeltas%2Cbinary_filesize%2Cdownload_url%2Cepoch%2Cicon_url%2Clast_updated%2Cpackage_name%2Cprices%2Cpublisher%2Cratings_average%2Crevision%2Cscreenshot_urls%2Csnap_id%2Csupport_url%2Ctitle%2Ccontent%2Cversion%2Corigin%2Cdeveloper_id%2Cprivate%2Cconfinement:
> > dial tcp: lookup search.apps.ubuntu.com on 10.137.3.254:53: dial udp
> > 10.137.3.254:53: connect: network is unreachable
> > 
> > So i was thinking that doing a qubes-dom0-update something so it could
> > get through? For the life of me i cant figure out what I did on my other
> > computer to make it work but it works fine there.
> > 
> > 
> > I forgot to mention, it is installed in the appvm:
> > 
> > 
> > user@debian-9:~$ sudo apt-get install snapd
> > Reading package lists... Done
> > Building dependency tree
> > Reading state information... Done
> > snapd is already the newest version (2.21-2+b1).
> > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
> > 
> > 
> > ideas?
> > 
> 
> Only apt is configured to access servers through the special Qubes proxy.
> Since templates have networking turned off by default, that means nothing
> else can download packages or data.
> 
> In the short term, you can try enabling networking temporarily for the
> template while you install snap packages. Just set the netvm in the
> template's settings.
> 
> In the long term, Qubes users may benefit from a special accommodation of
> snap, which has become a versatile and important way to install software.
> Support could include access through the update proxy and even special
> storage capabilities. Would be a good idea to open an enhancement issue for
> this. :)

There is some progress on this already:
https://github.com/QubesOS/qubes-issues/issues/2766

The current state is: you can install "qubes-snapd-helper" package in
_template_, to be able to install snaps in qubes _based on that template_.


- -- 
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-

iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlw2kq8ACgkQ24/THMrX
1yzNvwgAhc0/O9VIzBGH1WDg8l+1sH3yLxxySFannO2ihUUXbUA80cf4+uxrxk/1
Rg+jR0XfdBXD91h817luvs3mIdqwcluq1YHxbGIb0J/vALPLHRhZ8YLasXSdpDIG
MyiVTk1ogAOG6jH30245V/GRPWALJmysYnW4DUki3ZefG/EyCFHWi7lpJZ9XS00F
QbVv7MoDx6GbHiSfHMzYk016fSaEAFlXGUUXczSHgDpJjumP6+MfVkz0l4diYbm5
wGOPIknWLBBSQMMOS0IoaB1iq1hYbZNULt6/gaOOFBIC2I9D2m4Q8KHKeDz95qln
HEzk2d5IJJlv8M1xpoNyzS0+IJNHMQ==
=hL/D
-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/20190110003247.GC7536%40mail-itl.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Debian minimal template

2019-01-09 Thread unman

On Thu, Jan 10, 2019 at 12:14:59AM +, unman wrote:
> If any one is interested there's a prebuilt debian-9-minimal template
> currently available in itl-testing.
> You can install it:
> qubes-dom0-update --enablerepo=qubes-template-itl-testing 
> qubes-template-debian-9-minimal
> 
> The template is a little smaller than stock stretch, and somewhat
> leaner. To get root you'll need to use 'qvm-run -u root  xterm';
> install qubes-core-agent-passwordless-root (and polkit) if you want
> that feature.

Forget the polkit. Dont know what I was thinking.

> 
> If you have any comments or suggestions for debian minimal post them here.
> There's no documentation as yet, but the Fedora-minimal guide should come
> in handy.
> 
> Enjoy
> 
> unman

-- 
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/20190110003008.xgubprjthq2bcn3t%40thirdeyesecurity.org.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Debian minimal template

2019-01-09 Thread unman

If any one is interested there's a prebuilt debian-9-minimal template
currently available in itl-testing.
You can install it:
qubes-dom0-update --enablerepo=qubes-template-itl-testing 
qubes-template-debian-9-minimal

The template is a little smaller than stock stretch, and somewhat
leaner. To get root you'll need to use 'qvm-run -u root  xterm';
install qubes-core-agent-passwordless-root (and polkit) if you want
that feature.

If you have any comments or suggestions for debian minimal post them here.
There's no documentation as yet, but the Fedora-minimal guide should come
in handy.

Enjoy

unman

-- 
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/20190110001459.4zjw4r4r5lvng7q7%40thirdeyesecurity.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Installing snaps in appvms?

2019-01-09 Thread Chris Laprise

On 01/09/2019 06:41 PM, Stumpy wrote:

On 1/8/19 7:59 PM, 'awokd' via qubes-users wrote:

Stumpy wrote on 1/9/19 12:07 AM:

qvm-run gfx /snap/bin/xnview

I get:
Running '/snap/bin/xnview/ on gfx
gfx: command failed with code: 1

when i try to run it within the appvm i get:
user@gfx:~$ xnview
Can not open /var/lib/snapd/seccomp/profiles//snap.xnview.xnview (No
such file or directory)

aborting: No such file or directory

thoughts? please?

oh, and if i try to reinstall the app I get:
user@gfx:~$ sudo snap install xnview
snap "xnview" is already installed

Nothing should be installed to dom0. You'd have to install snapd in a
template, and possibly the snap package. You might want to create a
Standalone VM and install everything in there, instead of templates &
AppVMs.

Thanks, I had thought I had to install on dom0 as well, perhaps not,
though when I try to:

So i was thinking that doing a qubes-dom0-update something so it could
get through? For the life of me i cant figure out what I did on my other
computer to make it work but it works fine there.

I forgot to mention, it is installed in the appvm:

ideas?

Only apt is configured to access servers through the special Qubes
proxy. Since templates have networking turned off by default, that means
nothing else can download packages or data.

In the short term, you can try enabling networking temporarily for the
template while you install snap packages. Just set the netvm in the
template's settings.

In the long term, Qubes users may benefit from a special accommodation
of snap, which has become a versatile and important way to install
software. Support could include access through the update proxy and even
special storage capabilities. Would be a good idea to open an
enhancement issue for this. :)

Chris Laprise, tas...@posteo.net
https://github.com/tasket
https://twitter.com/ttaskett
PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886

--
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/7fff72d9-d9c6-cef7-d6bc-64005271bc6e%40posteo.net.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Dom0 Error

2019-01-09 Thread unman

On Wed, Jan 09, 2019 at 02:59:09PM -0800, remresalexan...@gmail.com wrote:
> sry but the log itself says strict reset mode is not enabled or i get 
> something wrong?
> 
Not sure what log you are referring to - the extract you most recently
posted said the kernel did not support reset which is why you should try
disabling it. (Which I suggested some time back.)
Give it a go and see if it has any effect.

-- 
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/20190109235611.chilrvemp3oua3wz%40thirdeyesecurity.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Installing snaps in appvms?

On 1/8/19 7:59 PM, 'awokd' via qubes-users wrote:

Stumpy wrote on 1/9/19 12:07 AM:

qvm-run gfx /snap/bin/xnview

I get:
Running '/snap/bin/xnview/ on gfx
gfx: command failed with code: 1

when i try to run it within the appvm i get:
user@gfx:~$ xnview
Can not open /var/lib/snapd/seccomp/profiles//snap.xnview.xnview (No
such file or directory)

aborting: No such file or directory

thoughts? please?

oh, and if i try to reinstall the app I get:
user@gfx:~$ sudo snap install xnview
snap "xnview" is already installed

Nothing should be installed to dom0. You'd have to install snapd in a
template, and possibly the snap package. You might want to create a
Standalone VM and install everything in there, instead of templates &
AppVMs.

Thanks, I had thought I had to install on dom0 as well, perhaps not,
though when I try to:

So i was thinking that doing a qubes-dom0-update something so it could
get through? For the life of me i cant figure out what I did on my other
computer to make it work but it works fine there.

I forgot to mention, it is installed in the appvm:

ideas?

--
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/4de33c03-197c-5b63-2d65-f7b114c1682f%40posteo.net.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] mooltipass hardware password manager

2019-01-09 Thread Benjamin Richter

Hi,

I have a Mooltipass Mini Hardware Password manager 
(https://www.themooltipass.com/), which identifies as a USB keyboard in order 
to input passwords.

I can attach the USB device to a VM to connect to the mooltipass mini and put 
in credentials, but I cannot get it to input the password, neither by attaching 
it to a VM directly, nor by leaving it in the USB qube via the input proxy.
The key events just don't seem to turn up anywhere.

I'm running latest stable R4. My USB keyboard, touchpad and touchscreen work, 
also I don't have any problems with other USB devices. How can I debug this 
further?

journalctl output while connecting:

Jan 10 00:21:07 sys-usb kernel: usb 2-1: new full-speed USB device number 10 
using xhci_hcd
Jan 10 00:21:07 sys-usb kernel: usb 2-1: New USB device found, idVendor=16d0, 
idProduct=09a0
Jan 10 00:21:07 sys-usb kernel: usb 2-1: New USB device strings: Mfr=1, 
Product=2, SerialNumber=0
Jan 10 00:21:07 sys-usb kernel: usb 2-1: Product: Mooltipass
Jan 10 00:21:07 sys-usb kernel: usb 2-1: Manufacturer: SE
Jan 10 00:21:07 sys-usb kernel: hid-generic 0003:16D0:09A0.001B: 
hiddev96,hidraw1: USB HID v1.11 Device [SE Mooltipass] on 
usb-:00:07.0-1/input0
Jan 10 00:21:07 sys-usb kernel: input: SE Mooltipass as 
/devices/pci:00/:00:07.0/usb2/2-1/2-1:1.1/0003:16D0:09A0.001C/input/input36
Jan 10 00:21:07 sys-usb kernel: hid-generic 0003:16D0:09A0.001C: input,hidraw2: 
USB HID v1.11 Keyboard [SE Mooltipass] on usb-:00:07.0-1/input1
Jan 10 00:21:07 sys-usb mtp-probe[30635]: checking bus 2, device 10: 
"/sys/devices/pci:00/:00:07.0/usb2/2-1"
Jan 10 00:21:07 sys-usb mtp-probe[30635]: bus: 2, device: 10 was not an MTP 
device
Jan 10 00:21:07 sys-usb kernel: audit: type=1130 audit(1547076067.807:236): 
pid=1 uid=0 auid=4294967295 ses=4294967295 
msg='unit=qubes-input-sender-keyboard@event6 comm="systemd" 
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 10 00:21:07 sys-usb audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 
ses=4294967295 msg='unit=qubes-input-sender-keyboard@event6 comm="systemd" 
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 10 00:21:07 sys-usb systemd[1]: Started Qubes input proxy sender (keyboard).
Jan 10 00:21:07 sys-usb systemd-logind[436]: Watching system buttons on 
/dev/input/event6 (SE Mooltipass)



lsusb output of the device:

Bus 002 Device 010: ID 16d0:09a0 MCS 
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   2.00
  bDeviceClass0 
  bDeviceSubClass 0 
  bDeviceProtocol 0 
  bMaxPacketSize032
  idVendor   0x16d0 MCS
  idProduct  0x09a0 
  bcdDevice1.00
  iManufacturer   1 SE
  iProduct2 Mooltipass
  iSerial 0 
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength   66
bNumInterfaces  2
bConfigurationValue 1
iConfiguration  0 
bmAttributes 0x80
  (Bus Powered)
MaxPower  100mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   2
  bInterfaceClass 3 Human Interface Device
  bInterfaceSubClass  0 
  bInterfaceProtocol  0 
  iInterface  0 
HID Device Descriptor:
  bLength 9
  bDescriptorType33
  bcdHID   1.11
  bCountryCode0 Not supported
  bNumDescriptors 1
  bDescriptorType34 Report
  wDescriptorLength  28
 Report Descriptors: 
   ** UNAVAILABLE **
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02  EP 2 OUT
bmAttributes3
  Transfer TypeInterrupt
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0040  1x 64 bytes
bInterval   1
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81  EP 1 IN
bmAttributes3
  Transfer TypeInterrupt
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0040  1x 64 bytes
bInterval   1
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber1
  bAlternateSetting   0
  bNumEndpoints   1
  bInterfaceClass 3 Human Interface Device
  bInterfaceSubClass  1 Boot Interface Subclass
  bInterfaceProtocol  1 Keyboard
  iInterface  0

Re: [qubes-users] Dom0 Error

sry but the log itself says strict reset mode is not enabled or i get something 
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/0ebcbc42-8c8f-4b17-9c2f-37e379a3359f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] qubes dom0 update breaks template updating

2019-01-09 Thread qtpie

The latest dom0 update broke updating my templates. I altered
/etc/qubes-rpc/policy/qubes.UpdatesProxy to change the updateproxy to
sys-whonix.

My solution is to uncomment the lines starting with 'tag', while leaving
the lines in the old formatting untouched.

This solution seems weird since here it is suggested that the lines
starting with 'tag' should replace the other lines:
https://github.com/QubesOS/qubes-mgmt-salt-dom0-virtual-machines/commit/ca27a33b0ec59f5ea2d4b334973eaa837f11ffc4

I'm not saying this is a bug, I can understand that an update is not
compatible with certain customisations and it is the users responsiblity
to fix this.

In any case - enjoying Qubes everyday!

-- 
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/33669b5d-75f8-1f55-3906-c5e47633557b%40disroot.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] restoring dom0/Fedora baseline

2019-01-09 Thread Ivan Mitev

Hi Sven,

On 1/9/19 9:39 PM, Sven Semmler wrote:
> This is probably more a Fedora question then a Qubes question, but
> it's in the context of Qubes.
> 
> I have installed i3, gnome-tweak-tools, qt5cl and redshift in dom0.
> Meanwhile I removed both gnome-tweak-tools and qt5cl but a lot of the
> dependencies that got installed with it have not been automatically
> removed.
> 
> My goal would be to return to a standard dom0 (+i3 and redshift). I
> understand it's not a security issue and doesn't matter that those
> extra packages remain installed, but I'm kind of OCD about a "clean"
> system.
> 
> So is there a smarter, less severe way than reinstalling Qubes and
> restoring my qubes from backup? Is there some dnf magic to remove
> those other packages while making sure everything that qubes actually
> needs stays?

- magic: use `dnf history ... ` commands to rollback/undo some
transactions. I haven't used those so I have no idea if dnf uses dnf.*
log files (which might have been logrotated/deleted if the transactions
are old) or if the transactions are stored in a db somewhere.

- same as above but manually: extract the list of dependencies you want
to remove from the packages listed in dnf.rpm.log* ; again that's if you
didn't install gnome-tweak-tools and qt5cl too long ago. If you
installed the additional packages at once you probably won't be able to
differentiate the dependencies pulled by gnome-tweak-tools and qt5cl vs
the ones pulled by i3 and redshift; in that case simply re-install the
latter packages if they end up being removed by dnf.

- heavy-handed approach (!): do a clean install on another machine and
compare the rpms installed in dom0 vs the ones in your current install
(or have a trusted user send you his/her list of packages).

Hopefully other users will point to better solutions. IIRC unman posted
an email about dnf and transaction rollback a week or so ago - can't
find the post atm, got to get some sleep :)

Cheers,
Ivan

-- 
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/c4bb61bf-b22f-593c-7191-f5009a39116c%40maa.bz.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] restoring dom0/Fedora baseline

2019-01-09 Thread Sven Semmler

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

This is probably more a Fedora question then a Qubes question, but
it's in the context of Qubes.

I have installed i3, gnome-tweak-tools, qt5cl and redshift in dom0.
Meanwhile I removed both gnome-tweak-tools and qt5cl but a lot of the
dependencies that got installed with it have not been automatically
removed.

My goal would be to return to a standard dom0 (+i3 and redshift). I
understand it's not a security issue and doesn't matter that those
extra packages remain installed, but I'm kind of OCD about a "clean"
system.

So is there a smarter, less severe way than reinstalling Qubes and
restoring my qubes from backup? Is there some dnf magic to remove
those other packages while making sure everything that qubes actually
needs stays?

Thank you for your consideration!

/Sven
-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE18ry22WNibwI1qeq2m4We49UH7YFAlw2TeUACgkQ2m4We49U
H7aL3w/8Ct4LE75jXjDaQV7D8XBDRptfB+9rDsqEiwd1DFLeKbGfAVKzw5mcfpwA
yBGTm8ioXZ9B4V72sRZvZ0ULOUcLCipiAem1vcV3jKWgrU+p03hgQpKxEeATL01z
Y3fEtaWG4FAEaXsJpjgbxvK5exTT7BHNux82R+rkFhQ4xiUK5UnZVQLZed1bYinV
6MiOsob3VTS7qKwFnBQrr6gjSFqVrWoDE2lla+7NWKQr+BdO/eU1kRc15xQntFjC
KwPz9cwBdM374dBkHp78C/zS1PK8GygqpG8aPbRCI+BKNY02HcWwS9+Fe+QEwUUV
SOXEq1VYdC/za/hFwUeEzksEsVAtzdPzyyADWd/vQ/3aYqUD0LIosfmsvh0rYlyt
SznxEVKlxYfdfFL2oA/VyQbJ+augH5KiTYWxnFEXh/Zv07w63FbQ83gx6VybKumq
HDvsS6TQqtk5nf/W9GrhS92puYt5HLSHgjT78AwXSfr3ks0QaIHPTzdLZj4Opx5J
X7YIqg8n5i8G6vpQP+F9p/1ELqbmA4EevZjxruvLHKqKNJDU8m/sAGTwv3SesLpp
klTO9/3E7F299pnZ2jKoKbltdaP2Rj5KjNDf28kK//PnnmwRb+o7gQbSudaHF2Rr
BUweYmyqbBDxMtHUdm3CEFHN+BUSbEGzoXOG+NgKfl5BzbQuDOc=
=6qJR
-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/038700e1-fbdb-a1dc-9de0-1ba2619d6864%40SvenSemmler.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Qubes OS 4.0.1 has been released!

2019-01-09 Thread Lorenzo Lamas

On Wednesday, January 9, 2019 at 11:11:31 AM UTC+1, Marek Marczykowski-Górecki 
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> On Wed, Jan 09, 2019 at 01:35:42AM -0800, Lorenzo Lamas wrote:
> > I see the hashes are different to 4.0.1-RC2 What has changed compared to 
> > RC2?
> 
> Minor fix to update widget[1] plus a rebuild with "4.0.1" as a version,
> instead of "4.0.1-rc2".
> 
> [1] https://github.com/QubesOS/qubes-issues/issues/4667
> 
> - -- 
> 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-
> 
> iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlw1yMsACgkQ24/THMrX
> 1ywoBAf+Nad/7dZEMepMvmLeWjAbKpFF2P1wM9bVHwRY3j+ZB0ahCmRntAN1soeC
> 1p3A7eppOGIfr5IuhtozeBim/ZdswT1fc/zLPG4UCIfr4Oo0SbZpfI7THijHoc5u
> PgmAOu2FGzQ3IwufkFp74b6pN+MiP2MP1aCabKBCA8kF0am24buism5VBZoBwblT
> umQGYePGSEFepPN1qbPGbYzy/+Z+aVXOIBdxT61RSQteB8yGJLz+kwmaoOlO6o0r
> oTYGaCD8TNvzJFarnaa5/xPvBCptL7BecsbZkn6gNzKNTI3+gT++hMbQ6AJIYatv
> sKHmHKC4ti1PW6DBJxNLX6unMNTwVg==
> =LZWx
> -END PGP SIGNATURE-

Thanks for the reply! And also thanks for the 4.0.1 release, this has made it 
easier for me to migrate from 3.2.

-- 
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/36da0d17-8ffc-47be-9174-f6cde9e25152%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] RE: Qubes OS 4.0.1 fresh install reboot halt

2019-01-09 Thread Robert Rettig

Solved with the help of: https://www.qubes-os.org/doc/uefi-troubleshooting/

```
mapbs=1
noexitboot=1
```

From: qubes-users@googlegroups.com  On Behalf Of 
Robert Rettig
Sent: Wednesday, 9 January 2019 14:38
To: qubes-users@googlegroups.com
Subject: [qubes-users] RE: Qubes OS 4.0.1 fresh install reboot halt


Maybe I should add some options to XEN.CFG?
Current File:
```
[global]
default=4.14.74-1.pvops.qubes.x86_64

[4.14.74-1.pvops.qubes.x86_64]
options=loglvl=all dom0_mem=min:1024M dom0_mem=max:4096M iommu=no-igfx 
ucode=scan smt=off
kernel=vmlinuz-4.14.74-1.pvops.qubes.x86_64 root=/dev/mapper/qubes_dom0-root 
rd.lvm.lv=qubes_dom0/root rd.lvm.lv=qubes_dom0/swap i915.alpha_support=1 rhgb 
quiet
ramdisk=initramfs-4.14.74-1.pvops.qubes.x86_64.img
```
Maybe console=vga … ?
https://wiki.xen.org/wiki/Xen_EFI


From: mailto:qubes-users@googlegroups.com  
On Behalf Of Robert Rettig
Sent: Wednesday, 9 January 2019 14:31
To: mailto:qubes-users@googlegroups.com
Subject: [qubes-users] Qubes OS 4.0.1 fresh install reboot halt

Hello,

just used the new release
https://groups.google.com/d/msg/qubes-users/qbu6fL1FBk0/Kdu0g43bAgAJ

For reproduction I always use wipefs to cleanup the target disk before 
installation.
I tested 2 times, because I have another disk in the system.
1. enabled
2. disabled
the second disk from BIOS. The target disk is always /dev/sda in both cases.

The installation media is transferred to an usb flash storage.
The installation proceeds without errors.
After clicking on reboot the machine reboots as expected.
There is a short info about the Xen Kernel, than screen is blank.
The CPU cooler fan is getting loud and no keyboard hit is accepted anymore ( 
“Ctrl Alt PrintScr rseinub” is not working too ).

Is it possible to boot the usb flash storage as a rescue media?
Otherwise I have some additional rescue media like knoppix …
I do not have any hints because the screen is blank.

Thanks
Robert
-- 
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 mailto:qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to mailto:qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/AM0PR04MB59069B8A01E2ED57472994C7D28B0%40AM0PR04MB5906.eurprd04.prod.outlook.com?utm_medium=email_source=footer.
For more options, visit https://groups.google.com/d/optout.
-- 
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 mailto:qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to mailto:qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/AM0PR04MB590637CF500680A13C4FF115D28B0%40AM0PR04MB5906.eurprd04.prod.outlook.com?utm_medium=email_source=footer.
For more options, visit https://groups.google.com/d/optout.

-- 
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/AM0PR04MB5906E25E4DFF44EE108450D7D28B0%40AM0PR04MB5906.eurprd04.prod.outlook.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Dom0 Error

2019-01-09 Thread 'awokd' via qubes-users


remresalexan...@gmail.com wrote on 1/9/19 11:04 AM:

no strict reset is enabled in sys-net cube


and
> libxl_pci.c:1176:libxl__device_pci_reset: The kernel doesn't support 
reset from sysfs for PCI device :00:14.0


That's why sys-net isn't starting. Check with lspci in dom0 to see what 
device is :00:14.0. Then in sys-net's Qube Settings/Devices tab, use 
the "Configure strict reset" button to disable the requirement for that 
device.


--
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/e3d6bbd7-e65b-6c25-c53f-60996f4b0495%40danwin1210.me.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] RE: Qubes OS 4.0.1 fresh install reboot halt

2019-01-09 Thread Robert Rettig


Maybe I should add some options to XEN.CFG?
Current File:
```
[global]
default=4.14.74-1.pvops.qubes.x86_64

[4.14.74-1.pvops.qubes.x86_64]
options=loglvl=all dom0_mem=min:1024M dom0_mem=max:4096M iommu=no-igfx 
ucode=scan smt=off
kernel=vmlinuz-4.14.74-1.pvops.qubes.x86_64 root=/dev/mapper/qubes_dom0-root 
rd.lvm.lv=qubes_dom0/root rd.lvm.lv=qubes_dom0/swap i915.alpha_support=1 rhgb 
quiet
ramdisk=initramfs-4.14.74-1.pvops.qubes.x86_64.img
```
Maybe console=vga … ?
https://wiki.xen.org/wiki/Xen_EFI


From: qubes-users@googlegroups.com  On Behalf Of 
Robert Rettig
Sent: Wednesday, 9 January 2019 14:31
To: qubes-users@googlegroups.com
Subject: [qubes-users] Qubes OS 4.0.1 fresh install reboot halt

Hello,

just used the new release
https://groups.google.com/d/msg/qubes-users/qbu6fL1FBk0/Kdu0g43bAgAJ

For reproduction I always use wipefs to cleanup the target disk before 
installation.
I tested 2 times, because I have another disk in the system.

  1.  enabled
  2.  disabled
the second disk from BIOS. The target disk is always /dev/sda in both cases.

The installation media is transferred to an usb flash storage.
The installation proceeds without errors.
After clicking on reboot the machine reboots as expected.
There is a short info about the Xen Kernel, than screen is blank.
The CPU cooler fan is getting loud and no keyboard hit is accepted anymore ( 
“Ctrl Alt PrintScr rseinub” is not working too ).

Is it possible to boot the usb flash storage as a rescue media?
Otherwise I have some additional rescue media like knoppix …
I do not have any hints because the screen is blank.

Thanks
Robert
--
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/AM0PR04MB59069B8A01E2ED57472994C7D28B0%40AM0PR04MB5906.eurprd04.prod.outlook.com.
For more options, visit https://groups.google.com/d/optout.

-- 
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/AM0PR04MB590637CF500680A13C4FF115D28B0%40AM0PR04MB5906.eurprd04.prod.outlook.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Qubes OS 4.0.1 fresh install reboot halt

2019-01-09 Thread Robert Rettig

Hello,

just used the new release
https://groups.google.com/d/msg/qubes-users/qbu6fL1FBk0/Kdu0g43bAgAJ

For reproduction I always use wipefs to cleanup the target disk before 
installation.
I tested 2 times, because I have another disk in the system.

  1.  enabled
  2.  disabled
the second disk from BIOS. The target disk is always /dev/sda in both cases.

The installation media is transferred to an usb flash storage.
The installation proceeds without errors.
After clicking on reboot the machine reboots as expected.
There is a short info about the Xen Kernel, than screen is blank.
The CPU cooler fan is getting loud and no keyboard hit is accepted anymore ( 
"Ctrl Alt PrintScr rseinub" is not working too ).

Is it possible to boot the usb flash storage as a rescue media?
Otherwise I have some additional rescue media like knoppix ...
I do not have any hints because the screen is blank.

Thanks
Robert

-- 
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/AM0PR04MB59069B8A01E2ED57472994C7D28B0%40AM0PR04MB5906.eurprd04.prod.outlook.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Dom0 Error

no strict reset is enabled in sys-net cube

-- 
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/b8c585b4-1f77-453f-b232-d4634b8e370b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Dom0 Error

That prompt occured while the installation process of qubes itself

-- 
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/484f9ce4-f4d3-4b40-ac97-6ea6650686f3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Dom0 Error

Im completely new

-- 
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/41ecb591-399c-4657-b181-c41174341e67%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Dom0 Error

Oh sry
How dumb iam this is not recommend 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/e58bf6d7-b887-436f-a05b-8538af0d013b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Dom0 Error

If i try to attach the wireless controller i.e. to the whonix qube it says 
ERROR: Devices tab: Can't attach PCI device to VM in pvh mode

-- 
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/b36a9cf4-bbbc-4cb6-a7a3-e81ef6b40261%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Qubes OS 4.0.1 has been released!

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Wed, Jan 09, 2019 at 01:35:42AM -0800, Lorenzo Lamas wrote:
> I see the hashes are different to 4.0.1-RC2 What has changed compared to RC2?

Minor fix to update widget[1] plus a rebuild with "4.0.1" as a version,
instead of "4.0.1-rc2".

[1] https://github.com/QubesOS/qubes-issues/issues/4667

- -- 
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-

iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlw1yMsACgkQ24/THMrX
1ywoBAf+Nad/7dZEMepMvmLeWjAbKpFF2P1wM9bVHwRY3j+ZB0ahCmRntAN1soeC
1p3A7eppOGIfr5IuhtozeBim/ZdswT1fc/zLPG4UCIfr4Oo0SbZpfI7THijHoc5u
PgmAOu2FGzQ3IwufkFp74b6pN+MiP2MP1aCabKBCA8kF0am24buism5VBZoBwblT
umQGYePGSEFepPN1qbPGbYzy/+Z+aVXOIBdxT61RSQteB8yGJLz+kwmaoOlO6o0r
oTYGaCD8TNvzJFarnaa5/xPvBCptL7BecsbZkn6gNzKNTI3+gT++hMbQ6AJIYatv
sKHmHKC4ti1PW6DBJxNLX6unMNTwVg==
=LZWx
-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/20190109101123.GB7536%40mail-itl.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Dom0 Error

typed by hand with love *facepalm*

-- 
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/be0c4c31-f94a-4380-ae90-8562bffea577%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Dom0 Error

Laptop has both wireless and cable onboard

libxl-driver.log
libxl: libxl.c:1853:libxl_console_get_tty: unable to read console tty path 
`/local/domain/1/console/tty':Resource temporarily unavailable

libxl: libxl.c:1853:libxl_console_get_tty: unable to read console tty path 
`/local/domain/2/console/tty':Resource temporarily unavailable

libxl: libxl.c:1853:libxl_console_get_tty: unable to read console tty path 
`/local/domain/3/console/tty':Resource temporarily unavailable

libxl: libxl.c:1853:libxl_console_get_tty: unable to read console tty path 
`/local/domain/4/console/tty':Resource temporarily unavailable

libxl: libxl.c:1853:libxl_console_get_tty: unable to read console tty path 
`/local/domain/5/console/tty':Resource temporarily unavailable

libxl:
libxl_pci.c:1176:libxl__device_pci_reset: The kernel doesn't support reset from 
sysfs for PCI device :00:14.0

https://www.file-upload.net/download-13462842/IMG_20190109_105836.jpg.html

-- 
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/e525fbbd-a398-4d47-a93f-e2b0c8b63ffd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Dom0 Error

Laptop has both wireless and cable

-- 
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/771d5667-c18a-496c-90c1-bbdf20c1d27a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Dom0 Error