[qubes-users] Broadcom BCM4312 device not appearing [network, hardware, troubleshooting]

[Project 9501]

Good morning everyone,

I'm having trouble getting my BCM4312 working under Qubes.  I've poked around 
the archives a bit and I know from experience that Broadcom and Linux haven't 
always been the best of friends, but maybe there's a solution I'm missing.

The card shows up in lspci without any issues.  I have the latest b43 drivers 
installed in the netVM template.  Nevertheless, the drivers don't auto-load, 
and modprobing them doesn't cause the card to show up as a network device.

I tried making a Debian netVM because I know Broadcom support on Debian is 
slightly better, but no joy there either.

I have wireless working on a USB adapter but that has issues of its own, so I'd 
like to get the internal working if possible.  Any tips or assistance would be 
very much appreciated.

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/d15815b9-b71e-4d55-aa6a-994be6125f4c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: debian-9 sys-net, random MAC buggy

[Chris Laprise]

On 12/15/2016 01:58 PM, Reg Tiangha wrote:

On 12/15/2016 11:50 AM, qubenix wrote:

I've used the docs[1] to randomize my MAC on sys-net with debian-9 as
it's template. At first everything was working normal, but I've noticed
now that my MAC is only randomized until I connect to a network. At that
point it switches back to the original MAC. Anyone else experiencing this?

Second issue is that it seems my eth0 is never randomized. Any users
with the same experience?

[1] https://www.qubes-os.org/doc/anonymizing-your-mac-address/


I've had that happen ever since I tried it so I just assumed it was a
bug or a hardware issue that doesn't allow my wifi adapter to change. If
there's a workaround or an extra package to install to make it work
properly, I'd love to hear it. I get the same issue with NM on Debian 9
or Fedora 25, as well as the macchanger method. It does scramble the MAC
address when it's not connected to an access point, but reverts to the
original one once it connects to a network.



The main issue here is that the correct config keyword 
"cloned-mac-address" reverted to an incorrect (non-)keyword 
"assigned-mac-address" that was used in an earlier version (see 
https://github.com/tasket/qubes-doc/commit/27dcc6f142d627293d7788cbd5610b4f6b4f2df5 
).


Somehow this got changed back to the original, mistaken keyword here: 
https://github.com/QubesOS/qubes-doc/commit/a9a82bedf092eec13e774dc50cbc6f83f0ef2182


The "assigned-mac-address" is a property for NM's dbus interface ...not 
in the config parser where "cloned-mac-address" is used (see gnome.org 
link below).


--

With that said, there is an actual NM bug where it ignores randomization 
settings when connecting to an AP. This bug bit me and the workaround 
was to use a newly-created netVM instead of existing one so that old NM 
connection data was not present in the new configuration. That's why the 
instructions say to create a new netVM.


https://mail.gnome.org/archives/networkmanager-list/2016-October/msg00019.html


Chris

--
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/d48883d4-6ebb-56ba-c70b-a2d1d16286fa%40openmailbox.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Split GPG: thunderbird+enigmail stopped cache password

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-12-15 13:57, cubit wrote:
> 15. Dec 2016 21:53 by cu...@tutanota.com:
> 
>> I updated templates and dom0 today and rebooted computer.  Now 
>> when I try to look at encrypted email I am prompted to enter my 
>> gpg key password every time I look at an encrypted email.   Also 
>> if I look at an encrypted email, go to a different program and 
>> then tab back to thunderbird I am immediately asked for gpg key 
>> password for the email I was looking at.
>> 
> Another problem I discover.  If a PGP/MIME email has an
> attachment. I try open it asks for password to open it.  Put
> correct password in and it just ask again and again and again :(
> 

I recommend disabling your key's passphrase (i.e., using a blank
passphrase).

See our "note on passphrases":

"You may experience trouble when attempting to use a PGP key with a
passphrase along with Split-GPG and Enigmail. If you do, you may need
to remove the passphrase from your (sub)key(s) in order to get
Split-GPG working correctly. As mentioned above, we do not believe PGP
key passphrases to be significant from a security perspective."

The reasoning can be found throughout the document (search for
"passphrase").

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

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

iQIcBAEBCgAGBQJYU4KhAAoJENtN07w5UDAwMkMP/3xLSOdj5qjNprwgfiMEKMPe
XUmsjT55gSja0MQ9bKSVMZ58Mk4mp7tkbFpcSVQW7OpAodLUIIoNDg1vC+KwocUA
pAaWXFt2TsjVPNbIL2DJEwCM1z2ElXLciQj57YAzUj4ZvVTHKJAmrP6H8BmI7w0M
DdDhBHZG07KoYyvJ2zpUAj6OY56vOoUs8o9zYj9v6jZ5KOHnHbQVi9MHPQeWZz2f
SPQ4vlcVHpWLFj6pD9e5E1fISLHecmK1q4xmfM3YbtpP24PuFxX0BH1ReYWDKUoj
DZODmBok+Fl4VYx6DIs9bQ/TpKmD+72eN37lEL4QYwYq3SPQbkS2d+7v9H7u5t4u
Cj4ll4Dz9TtFNquLJxXD+TcWzNKTDve5aJP3UQwhZkj71nDuzBD+tKmWkVKMIVwy
X79TQtC0nYZUD/pDIOOiirIuAFwlOAf4l8J8tW/9+dafVB2rfVoRjj0n4jN42IQt
YpSZKOe3KlQAsuVy5tho3wP9WSP4NJIQuCLgCFj401DVD8ZJ21IFSHwiF1pnxOm9
Lsjer+BW3WIPIthoR+pFZhln8cVu7Ol3iCN790rOP3PH+uJLWK6V37cJAw4uPzac
VLEtpVJF4ncSNIf6UYkUoIkBbedfZ2y9ZxMQAEtep9eHFo67mrY18VRyglDKmYw+
fkSpUkgqL0+48a1HX/ht
=JM+z
-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/ddb61ce2-3a19-1fcf-efaf-62e1d59fdec7%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: debian-9 sys-net, random MAC buggy

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-12-15 21:52, Andrew David Wong wrote:
> On 2016-12-15 10:58, Reg Tiangha wrote:
>> On 12/15/2016 11:50 AM, qubenix wrote:
>>> I've used the docs[1] to randomize my MAC on sys-net with debian-9 as
>>> it's template. At first everything was working normal, but I've noticed
>>> now that my MAC is only randomized until I connect to a network. At that
>>> point it switches back to the original MAC. Anyone else experiencing this?
>>>
>>> Second issue is that it seems my eth0 is never randomized. Any users
>>> with the same experience?
>>>
>>> [1] https://www.qubes-os.org/doc/anonymizing-your-mac-address/
>>>
> 
>> I've had that happen ever since I tried it so I just assumed it was a
>> bug or a hardware issue that doesn't allow my wifi adapter to change. If
>> there's a workaround or an extra package to install to make it work
>> properly, I'd love to hear it. I get the same issue with NM on Debian 9
>> or Fedora 25, as well as the macchanger method. It does scramble the MAC
>> address when it's not connected to an access point, but reverts to the
>> original one once it connects to a network.
> 
> 
> This is a known issue:
> 
> https://github.com/QubesOS/qubes-issues/issues/938#issuecomment-247272139
> 
> Please view the link for a potential workaround.
> 

If the non-macchanger method also doesn't work, then you may be
experiencing a bug that goes beyond the one linked above. Added:

https://github.com/QubesOS/qubes-issues/issues/938#issuecomment-267522839

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

iQIcBAEBCgAGBQJYU4HAAAoJENtN07w5UDAwtUsP/A13547jK6rxAPYOyd7ru3vw
3GNenoLihHIR/1BhNdYSVsQvljJfqkHvr0EjLD5aO9FskBgNPq9p3M67ePX4x7D+
K7vbSc67Hl0LeMCEN+BeUDx2W0ZJbqtodAwYtHMLom7QSox6btwn1HAwtC+qKoRM
4kC93bAHcfHmaEmJoVVHifPggFcxjQY0JiHLWcuxalp/r0NhwnzzFC5933NNddM0
cYHZKLr5FjAoLe+OkcgUUR8pqrS4gMsL+r2KeggMUHQG7dwwTpQqKX9REeJgyWCx
o1ZZoGmxf3nh4GJJ45Pkeafx7kVW/S3b+0/aV3nADlDadbUemHn+P59iPy1qPyxp
78XI6vvp5FCwoW8SJwrmuNqcLIns4OzHprl3ZovTh4lwSbDh61BQUWVVLtBfSyXo
AfrlU6i6Ar3nVFLNOFr4497Qw72mzjvEaMetKLhb3/4kRNhdfALOgFQLVUqp8uw/
ZZVK5sXX8qSmmUuVmobv3uTOVimkaCMDB3art4LzqmY751jZntY+xG7b8Np1b5Ti
BNMgiQfojvxzsFRGYgwwHIYCJl5+RrGauzb+B+K7BmVJNj1b+nzjXFeS+hu27t3z
xHipsz9MNQrFMiXE8EP9A7Ri2KAASZVxoEt9yKadYyHiNkY49oTLQF1y+oU5QkgT
/Dewh3CaBbyASCXWbnXU
=MFiZ
-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/2d828f71-540e-5483-4696-611e1c0108af%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: debian-9 sys-net, random MAC buggy

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-12-15 10:58, Reg Tiangha wrote:
> On 12/15/2016 11:50 AM, qubenix wrote:
>> I've used the docs[1] to randomize my MAC on sys-net with debian-9 as
>> it's template. At first everything was working normal, but I've noticed
>> now that my MAC is only randomized until I connect to a network. At that
>> point it switches back to the original MAC. Anyone else experiencing this?
>>
>> Second issue is that it seems my eth0 is never randomized. Any users
>> with the same experience?
>>
>> [1] https://www.qubes-os.org/doc/anonymizing-your-mac-address/
>>
> 
> I've had that happen ever since I tried it so I just assumed it was a
> bug or a hardware issue that doesn't allow my wifi adapter to change. If
> there's a workaround or an extra package to install to make it work
> properly, I'd love to hear it. I get the same issue with NM on Debian 9
> or Fedora 25, as well as the macchanger method. It does scramble the MAC
> address when it's not connected to an access point, but reverts to the
> original one once it connects to a network.
> 

This is a known issue:

https://github.com/QubesOS/qubes-issues/issues/938#issuecomment-247272139

Please view the link for a potential workaround.

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

iQIcBAEBCgAGBQJYU4EsAAoJENtN07w5UDAwGYIP/ihgE1PKPJCHyWPef6Z3Ofhp
geNZiD2Q6Uty4nBhmJToNgWUzBcos4XVGyifVd9CvyAWnJ7xjk6EcRyAEcTZc7hX
2Tujw4riI84KkC00cS14jO64ZJMw0oQb5yNTHYuhGr6w4nippiApytkHaL7A8jcc
xC/GAqNUje2jgIaDpw3GjZdG72/dBgNTRs4A6sSOp2/35Q9fEeWMBx/sIbktvlfa
r4wKKqu7S92xrmdOGo9WTKLZ3H2hIx1lDa576L96LGC2tla223GErlUUReVBTzIS
RgWC477czw5U03q+PZFMB8/MLWs8j0N3YbCp3Q/Fh2K+keKjagwpZP80qJCHjmme
bnzmif71ZObcpueSZCqV6eoKa/bCQP7NZv0Pv6z+YK5QmOgQf2WJNKIDKdRx4quu
+4OiptGlPv5s1BmTfke9U+nO4RnFSaygDY1rmAsuUSkaUC54WOJOV8Ye9kOdb4sl
DpMrcztN4D/3YNoUoQLuGwMH9VbaVXAB6RqeEArArVyqSefSJNkIGnVtKNXxcu62
If+Zw2H+BQktQYN2tFIJBYBMarSNrNpAuEmKhYHvasCnTuquQrEYLQtcTlcL2X7h
liXw9/h6hBQ4om7Rq3UY6Vqm5IcMhAMPUg5WB22pwjjPJIUeO9QgZk/Y5ZSRAGXe
2bFAe2mlDekDKtnROC7O
=J2vH
-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/2649e9de-ad3a-552c-f9b2-8d00f60ba11e%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: [qubes-devel] Qubes Canary #10

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-12-15 13:46, Qru wrote:
> 
> On 2016-12-14 13:42, Andrew David Wong wrote:
>> We have just published Qubes Canary #10.
> 
> this announcement should go to  [qubes-announce] as well :-)
> 
> Qru
> 

No, qubes-announce is strictly for QSBs and new Qubes OS releases:

https://www.qubes-os.org/mailing-lists/#qubes-announce

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

iQIcBAEBCgAGBQJYU38WAAoJENtN07w5UDAwus0QAIj146UvOA0m+82CELkWecn3
yqAVs3oLRLpzLw1xdZ4YDB0iPVss9clsMltRoHi0quR0KYPV6IDcn00nM6fpFMGZ
2yZkMmOQWuk0pIIXxj/jKTEm86Sl99IYK09hQ/I0ZX/JViBlNzIuQWp5nU0bSdeP
YNFkfsT6Q9OIw9gJ9ngrgvm2GwZlbbfMw2ohHJCCQGo3rJcvyIov0QfR0XlzPGgG
qPT7g0mo46gH3tQA8ghJR9cYUhruuXTYqUI3Eczh8Cy8gtzVYZyZQFP/V83gj1pe
x8MJaHQzmH/OHJ1+hrMNPbuZbYADfUSta7W3CwzaUB4JLhBrp5XVnsThoV2hRtZZ
16Q/W+94CnW0VQcM2a6gFK2RFlZrdRoQypwY6Q08EE9yqWnU4Au6XWpG9SSguqAq
F4qhJHJ1A7OmmKZQVhx3xU/KoUbxQwSBrc1iSuaV45EhMa7uNUiN4Xblf/wEPH3C
QGo/6UQsuSYWAxIQyhIeu0aSX35t+2XOCpYd8gGho8M+FyWejJb//McgYpvoTd09
gMfCDI9dIwGb9ps7Ex5a8qNV/TJ/vStAqxRYS87tUCPI98VODEfH/h7CHA17K8EU
nk06uiRFevFI+PAFzWyXwp2fx1+QbXRcNQCP+ZcWBs+JR89NNBjvFUhtokDWbCrc
/zhT3EK/LxinoQkAlO8J
=SOKM
-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/c2cfafdf-860a-d7b7-b9ec-a329a0e72719%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Talos Secure Workstation Crowdfunding

[Jeremy Rand]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi everyone,

As those of you who've read Joanna's paper "Intel x86 Considered
Harmful" are well aware, the Intel ME and other closed-source firmware
pose a threat to trustworthy computing.  We can do all the awesome
hypervisor and isolation stuff we want (e.g. Qubes OS), but this
doesn't help when the firmware is evil (and closed-source firmware
should probably be assumed to be evil).

x86 is not likely to improve much on this front (although Trammel
Hudson's recent work is pretty cool), which means we should seriously
be looking into alternative architectures.  POWER8 is probably the
best contender for a serious alternative to x86.  As you may have
heard, Raptor Engineering is doing a crowdfund campaign on Crowd
Supply to produce the Talos Secure Workstation, a POWER8
desktop/workstation with fully libre firmware that is comparable in
performance to current Intel hardware.  In addition, most of the
mainboard logic is implemented using FPGA's with libre bitstreams and
libre toolchains instead of ASICs, which adds to the auditability and
control by the user.

Features particularly of interest to people who use Qubes include HVM,
IOMMU, and TPM, as well as some very interesting engineering relating
to preventing evil maid attacks.  Raptor has done an excellent writeup
of the latter; see the following links:

https://www.crowdsupply.com/raptor-computing-systems/talos-secure-workst
ation/updates/talos-fpga-functions-and-responsibilities-part-1

https://www.crowdsupply.com/raptor-computing-systems/talos-secure-workst
ation/updates/talos-fpga-functions-and-responsibilities-part-2

(People who enjoy reading Joanna's technical writeups are likely to
enjoy the above Raptor writeups too.)

And of course, as a workstation class machine, Talos supports plenty
of RAM for running lots of VM's simultaneously, as Qubes users tend to
do.

Raptor Engineering already has a solid track record of Coreboot and
Libreboot development (among other relevant areas of expertise), so
unlike most of the projects that have done crowdfunding in this space,
Raptor has an understanding of the tasks involved and is likely to
actually deliver.

Fedora and Debian already support POWER8, so the Qubes dom0 and AppVM
components shouldn't be hard to port.  Xen does not support POWER8 at
the moment, so Qubes won't run on Talos when the Talos ships.
However, there is interest in adding POWER8 support to Xen, and POWER8
support for Xen is much more likely to happen, and much faster, if
Talos meets their funding goal.

Yes, the price for a Talos is sadly quite high.  Note that it is much
more powerful than most consumer PC's (e.g. the low-end "Desktop
Edition" comes with 128 GiB of RAM), and that small production runs
are naturally more expensive.  If they meet their funding goal, it is
likely that price decreases will happen later in the product
lifecycle, as well as producing a new version based on POWER9.

If you're in a financial position to order a mainboard (or a complete
system), please support them.  For the far greater number of you who
are not (I definitely can't afford a mainboard), please consider the
$250 SSH option, and if you can't do that, please consider donating
$10.  If you have friends who understand that closed firmware is a
threat, tell them about Talos.  If you have friends who ideologically
are aligned (e.g. who support privacy rights) but who aren't aware of
the technical concerns about x86 and closed firmware, explain the
issue to them.  There are industry players watching to see how this
campaign goes and how diverse the support is; every $10 donation is a
vote that signals "We want this to happen."  $10 really does make a
difference here.

The crowdfund campaign ends in 29 days on Jan 14.

You can support them here:

https://www.crowdsupply.com/raptor-computing-systems/talos-secure-workst
ation

Cheers,
- -Jeremy Rand
-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJYU3gOAAoJELPy0WV4bWVwO+IQAIr+UtgNk+29oFRjvd+UKMUF
QkWkXrn+PqWDYs63NSX4LWnyO3apo1wY/yjmBkSiKKvEnK+1v3nDOAxGxPSKyWC1
9DWhESfBzM1dagy2spGEB7YpuAM4yrp1Ih58PxT1e/mRRca14NomwzNiNiqDpw94
rZWQXxQ/igMQ8VTLivFosjB6aMKB2TyM8xFYMDg8+yefumG5wGrDKhSacM21L7MM
uLilg0eTJLkttYXNnnZOATcIsymuT3Wi84hCkGzbDWekNen2/ZJfZO5+K39tzUXo
xsK+ndi6RSU2khOJ2+/laU37aDV0iKAKRlWi0T40fmTaO/skedZSNIJ2Br7iXwGh
UyUSAnhy26oH1wYJ8Y+oAd+liJStlxCRf5TCDWo4SsojR1IYV9qoIjfFOjPmUxT6
pLNhuEKP5UdP1yDvCjF+DLr+LtCjmkP63hCz+Asj0sesO7zcO4EYQEwyATx2b60S
Uonczt9QFznxLy9wQdo8qi3beBDY3ap2dTvikvQydSMSSsh9kP3yVDhRkAxHMCn6
2u68jSUVszRQv5C15PG96bZa3cZ2oR570RJ9Yb+PfrOjRxd7z0e3+ApqIWyu68kf
hMQeJCkPpI/GKOqjnJaweu9cuoMfh0mGYGRs1tIfDuJBFFzt5A/8RA10O+aViZMO
h0OR5a2svxdfqY97t74y
=pROL
-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] Re: Installing on macOS Macbook

[dumbcyber]

On Friday, 16 December 2016 01:09:30 UTC+11, pixel fairy  wrote:
> On Wednesday, December 14, 2016 at 3:38:24 AM UTC-8, dumbcyber wrote:
> 
> > I am reading and responding to this thread on a Macbook Pro 11,1 running 
> > Qubes R3.2.  Andrew and others are right: yes it works, but you need to 
> > work hard to make it work. I had the keyboard not working issue and in fact 
> > i had to build my Qubes disk on a Lenovo to get past the install issues the 
> > Macbook was giving me.
> > 
> 
> i had the same problem on my 11,3. how did you get it working?

On the Macbook I could not get past the initial installation menu (four 
choices) which kept failing regardless of which option I chose. So I build the 
Qubes disk on a Lenovo desktop. The same disk boots fine and works fine on the 
Macbook Pro.

-- 
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/f6f29b33-1ab1-48f8-84a8-bbd6df9c0647%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Split GPG: thunderbird+enigmail stopped cache password

[Marek Marczykowski-Górecki]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Thu, Dec 15, 2016 at 10:53:56PM +0100, cubit wrote:
> Halo!
> 
> I have run into more problems with thunderbird+enigmail on qubes and wonder 
> if anyone else has problems.
> 
> I have a work appvm as Debian 8 with icedove 45.5.1 and enigmail 1.8.2
> I have a vault appvm with my gpg keys as Debian 8 to do split gpg.
> 
> I updated templates and dom0 today and rebooted computer.  Now when I try to 
> look at encrypted email I am prompted to enter my gpg key password every time 
> I look at an encrypted email.   Also if I look at an encrypted email, go to a 
> different program and then tab back to thunderbird I am immediately asked for 
> gpg key password for the email I was looking at.
> 
> I do notice that the password prompt window looks different from pre reboot.
> 
> Some other package info:
> 
> ii  pinentry-gtk2   0.8.3-2
> ii  gnupg  1.4.18-7+deb8u3 
> ii  gnupg-agent   2.0.26-6+deb8u1 
> ii  gnupg2   2.0.26-6+deb8u1
> ii  gpgv 1.4.18-7+deb8u3  
> ii  libgpg-error0:amd64   1.17-3    
> ii  libgpgme11:amd64  1.5.1-6  
> ii  qubes-gpg-split   2.0.24-1+deb8u1    

The solution is easy - remove password from your keys, especially when
you're using split gpg. It is inconvenient illusion of security. If
someone gets access to your private keyring, he/she will be able to get
your password the same way. Especially when you're relying on caching it
in RAM...

The only case when password protected keys makes some sense is
protection after hardware theft, but since Qubes use full disk
encryption anyway, it doesn't add anything extra in this case.

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

iQEcBAEBCAAGBQJYU2FfAAoJENuP0xzK19csfhwH/2jdT7GbbdhRXlQdw1xPmdgx
f0TchBo2w6UkAowm3JjRhY8iw832qQMTcvKwKqG0JW23VsGsUnU/bqvjd4sDwE9V
7UgTOnAWXqra+wSJHsUjX+L6G+Lxxp+skXq6FKdVcCEsrVYf3BHzxfVeNevf2wG+
HJyIHjHCzwrZyHVscxKUq6rBtOvyOS+zSLNPTn7Nd6V0Kl3eMQwfu0FPvlvdfbre
lkUZ+wcGGo2nDUS+v2qbGiYXvs6+wfAwTFoSuNSC9t7ruofB6NaTTnbZXTEXaXcm
hSM0qzE4RCYjoQAqNNJ0tHfe398xdyowCMeouWrchr8uZpZ2I+Zb3Bb4OlQ3J5o=
=FBVc
-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/20161216033701.GV1239%40mail-itl.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] help updating dom0 - no network - stuck with lots of pending updates

[Marek Marczykowski-Górecki]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Thu, Dec 15, 2016 at 07:10:12AM -0800, jasonwalshismyn...@gmail.com wrote:
> 
> > - From this thread:
> > 
> > https://groups.google.com/d/topic/qubes-users/s3FJWqKw6Ps/discussion
> > 
> > 'Please check "sudo systemctl status qubes-qmemman", or better "sudo
> > journalctl -u qubes-qmemman" for error messages. Then you can restart
> > the service with "sudo systemctl restart qubes-qmemman".'
> 
> 
> 
> results for "sudo systemctl status qubes-qmemman" (I'm not able to transfer 
> logs to another computer from dom0 at the moment so i need to write the logs 
> ...) :
> 
> Active: failed (Results: exit-code)
> Process: 2081 ExecStart=/usr/lib/qubes/qmemman_deamon.py (code=exited, 
> status=1/FAILURE)
> Main PID: 2081 (code-exited, status=1/FAILURE)
> 
> qmemman_deamon.py[2081]: self.connect_unixsocket(address)
> qmemman_deamon.py[2081]: File "/usr/lib64/python2.7/logging/handlers.py" line 
> 789, in connect_unixsocket
> qmemman_deamon.py[2081]: self.socket.connect(address)
> qmemman_deamon.py[2081]: File "/usr/lib64/python2.7/socket.py", line 228, in 
> meth
> qmemman_deamon.py[2081]: return getadttr(self._sock,name)(*args)
> qmemman_deamon.py[2081]: socket.error: [errno 111] Connection refused

This looks like a problem with connecting to syslog. Do you have
/dev/log in place? It should be something like this:

[marmarek@dom0 ~]$ ls -l /dev/log
lrwxrwxrwx 1 root root 28 Dec 13 23:57 /dev/log -> 
/run/systemd/journal/dev-log

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

iQEcBAEBCAAGBQJYU1b5AAoJENuP0xzK19cs3jQIAI2HSt3yo5VWeoKwHaSlD0j4
JJ6EUlxDvq2LNmBXGRIEZhtmFSSqVvIaDsb2WLeC9B6D1N+3MV1BMGpfC5bPWq1u
IiYe1kG1454W9wMTjZOx7QfqAU3eXSnWSeTCg+6itts7RBcu/1ShWg9H0S5Krq+e
Lz1AWEUc8fOfhKf3Vq6on3rc+ACA8/OV+4jS3xG4pRFDu5TdUNBvl1p2GiDuS4HY
HwqiigW1yJxLvObqRxN8bfncgQadugnkJy7q9kNab21Khs+YNVUe+Ni62KHnoQdB
N3UzeiXl6q3lTG1LQGwBCcAtCvKISK5AysE83gZnEDL3Xaela5GFwkEczvi/PL0=
=g9mO
-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/20161216025239.GT1239%40mail-itl.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Qubes-Whonix DisposableVM documentation created

[Patrick Schleizer]

https://www.whonix.org/blog/qubes-whonix-dispvm

Before we had just a [stub][1]. Now [Qubes-Whonix][2] [DisposableVMs][3]
are fully [documented][4] thanks to [contributions][5] by the
[community][6]. ([wiki history][7])

**What are DisposableVMs?**

Under the Qubes TemplateVM model, any changes made to a
TemplateBasedVM's root filesystem are lost upon reboot. This is
advantageous for several reasons: it allows centralized (and therefore
faster) updates for all applications (most) inside the root filesystem,
saves time and disk space.

However, certain directories are designed to persist between reboots in
order to store files and settings. These directories are stored in /rw/
and include /home/user as well as additional directories defined by
"[bind directory][8]" settings.

To ensure that all changes to the filesystem are discarded after a
session, Qubes offers [DisposableVMs][9]. When a DisposableVM is
shutdown, the VM is removed from Qubes and all related VM images are
deleted from the host filesystem.

**What is a Whonix-Workstation DisposableVM?**

As the name suggests, this is a [Qubes][10] DisposableVM template based
on the Whonix-Workstation. This allows [Qubes-Whonix][2] users to create
throw-away instances of their Whonix-Workstation.

**Why Should I Consider Using a Whonix-Workstation DisposableVM?**

Whonix-Workstation DisposableVMs:

* Are quickly generated;
* Are disposed of (deleted) when the user has finished browsing and
other activities in a single session; and
* Will not remember any of the user's activities across DisposableVM
sessions, unless customized.

The major benefit of this approach is that the Whonix-Workstation
DisposableVM can be created in order to host a single application
usually the Tor Browser  mitigating the risk that a compromise of the
browser will affect any of your other VMs.

Critically, a Tor Browser exploit will not effect (poison) later
instances of the Tor Browser running in a subsequent DisposableVM
session, because the DisposableVM is always started in its original state.

**Can I Customize Whonix-Workstation DisposableVMs?**

Yes. For advanced users, the instructions include steps to create a
customized savefile that will remember specific changes, such as
personalized Tor Browser settings. Due to concerns over possible
fingerprinting issues, users should carefully read the wiki warnings
before proceeding on this course of action.

**Can I Easily Add DisposableVM Entries to the Qubes Menu?**

Not yet for Qubes R3.2 XFCE 4, but you can [edit existing DispVM start
menu entries][11] and [desktop shortcuts can be created][12].

**What Else Should I Know?**

Due to a few usability issues affecting anonymity, do not use
Whonix-Workstation DisposableVMs until:

* You understand Whonix-WS DispoableVMs are NOT yet amnesic; and
* Have carefully read and understood the available Qubes-Whonix
DisposableVM documentation.

Alternatively, you may wish to wait for Qubes 4.0 before you start using
Qubes DisposableVMs, due to [significant enhancements][13] planned for
the later release.

_Credits:_
_This blog post [was written][14] by [torjunkie][14]._

[1]:
https://www.whonix.org/w/index.php?title=Qubes/Disposable_VM=24228
[2]: https://www.qubes-os.org/doc/whonix/
[3]: https://www.qubes-os.org/doc/dispvm/
[4]: https://www.whonix.org/wiki/Qubes/Disposable_VM
[5]:
https://forums.whonix.org/t/using-whonix-workstation-as-a-disposablevm-dispvm
[6]: https://forums.whonix.org/t/qubes-dispvm-technical-discussion
[7]:
https://www.whonix.org/w/index.php?title=Qubes/Disposable_VM=history
[8]: https://www.qubes-os.org/doc/bind-dirs/
[9]: https://theinvisiblethings.blogspot.de/2010/06/disposable-vms.html
[10]: https://www.qubes-os.org
[11]: http://Qubes/Disposable_VM#Edit_Qubes_DisposableVM_start_menu
[12]:
https://www.whonix.org/wiki/Qubes/Disposable_VM#Adding_desktop_shortcut
[13]:
https://github.com/QubesOS/qubes-issues/issues/866#issuecomment-220495485
[14]: https://forums.whonix.org/t/qubes-dispvm-technical-discussion

-- 
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/6b8eee33-52e3-dee9-682d-7e29b67ed172%40riseup.net.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: FYI: Experimental Qubes coldkernel support now available

[Foppe de Haan]

On Thursday, December 15, 2016 at 10:11:31 PM UTC+1, Colin Childs wrote:
> Hi everyone,
> 
> Sorry for not getting on this list sooner, however it looks like testing
> of coldkernel on Debian is largely going well! I see the most recent
> issue from foppe, and will be attempting to reproduce later this evening.
> 
> If you run into issues that require coldhak attention, please do not
> hesitate to open tickets at
> https://github.com/coldhakca/coldkernel/issues, or email us directly at
> cont...@coldhak.ca.
> 
> Thanks, and happy testing!
> 
> -- 
> Colin Childs
> Coldhak
> https://coldhak.ca
> Twitter: @coldhakca

Thanks. If you want/need more information than that log contains, please tell 
me, I still have the offending templateVM :)

-- 
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/b698a990-34a0-4b6d-b0b9-daa2effb6927%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] help updating dom0 - no network - stuck with lots of pending updates

[jasonwalshismyname]

> And what happens when you restart qubes-qmemman?

this :

Job for qubes-qmemman.service failed because the control process exited with 
error code.  See "systemctl status qubes-qmemman.service" and "journalctl -xe" 
for details.

"sudo systemctl status qubes-qmemman.service" returns the same kind of error as 
"sudo systemctl status qubes-qmemman" and "sudo journalctl -xe" is a bit long 
to copy, let me know if there is something specific to look there.
 

-- 
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/c400bfad-3f75-4955-b03c-544e85f033ea%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] qvm-create-default-dvm modifying initial memory value?

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 12/15/16 05:58, Marek Marczykowski-Górecki wrote:
> On Thu, Dec 15, 2016 at 05:49:18AM -0800, Andrew David Wong wrote:
>> On 2016-12-15 05:45, Marek Marczykowski-Górecki wrote:
>>> On Thu, Dec 15, 2016 at 01:40:00PM +, Joonas Lehtonen wrote:
>>>
>> When I look at whonix-ws-dvm "initial memory" it says:
>> ~2800MB
>
>> I changed that to 1000MB and everything works again.
>
> Why that high?
>>>
 since its preset value was over 2800 I didn't want to reduce it
 to much but I just found out that something changes that value.
 (I did set it to 1000 it is now at >1500MB).
>>>
 Is this a bug? Or can I disable this auto-adjustment?
>>>
>>> Ah, I forgot it's adjusted at qvm-create-default-dvm call time.
>>> Based on memory usage inside of VM.
> 
>> I don't understand. Isn't the target TemplateVM shut down when
>> qvm-create-default-dvm is called? How could it be using any memory
>> while it's shut down?
> 
> It's about whonix-ws-dvm - it is started to create savefile out of it.
> 

On 12/15/16 06:05, Joonas Lehtonen wrote:
> This is not about the initial memory of the used templateVM (in this
> case whonix-ws) but about whonix-ws-dvm. (qubes manger -> show interal VMs)
> 

Ok, but why would a DVM template require so much memory just upon
starting up? Is that expected for some reason?

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

iQIcBAEBCgAGBQJYUsvSAAoJENtN07w5UDAwC/oP/igbdy+faDGuiLYcN0Gxq1iw
932f5TbcRshc11HVrhSLFlixs0roXE3ayW7aOVk8o5pN8Yf5wC4YNQCeRkoLWveT
DfyNsXNFnP+DuP/6yZWQPA8df7NaVea+Sqqk+Hh7TyyP4SmDobGtMx+HKjb9KWa3
UvMF+HckEFLO2YS/aUffMy63lKIHuLR8YQYTseiYcjQ5uadKLWaCWmcXBNONqLAR
/Ong4l9QKczlIIpzB59WN7SSAWzr8s5ARiO94d9fefxAolATUaFOngHQFAIdKCn2
ZRtXlIIHdCD9THwWAruGwtpR1o+8PkJ+ml+XiUq02+rdolLGV3StZs/DfrB1kZv6
gTIQPjhkY/pL4ERrjoOtgbRz47MA3PP7IGJrBT3ZUVqfep/V/Aw/gWKChMUJR7Y6
ScVfbKHh7B+T5/PGylN/CMU1M97tTHawNEbCjQ+DepXcvTOcdqbum68KhzgdAa7f
sdi/72FPKjOfllP+WgnCEdau/hD2hkN72CkHmrHXYm3E2mcVX7j8wuTXWd0K1CRX
ldfCQcm/n0m6YV7z5vUlShJgtYiy+H9pVzZ8q6rFRZhxteS9lM/9REljxJi0VQJY
r3R764828FmvnnFEX/g0lNDivWYcgI+CDWJUng5IXNkhd9guWdNjLLlurRv6vkKy
+ehHz/h20Ptb8dAD0a0t
=eOC3
-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/c74986ee-e797-e1dd-ccfe-c97296bd817f%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: FYI: Experimental Qubes coldkernel support now available

[Reg Tiangha]

On 12/15/2016 09:48 AM, Reg Tiangha wrote:
> On 12/15/2016 09:43 AM, Foppe de Haan wrote:
>> On Thursday, December 15, 2016 at 2:15:20 PM UTC+1, Reg Tiangha wrote:
>>> On 12/15/2016 06:01 AM, Reg Tiangha wrote:
 On 12/15/2016 05:00 AM, Foppe de Haan wrote:
> Okay, stuck again. Downloaded a fresh d8 template, updated it and built 
> kernel again to have a clean slate to work from. Everything builds, no 
> error beside the expected ones afterwards. But when i switch to pvgrub2 
> and boot, it shuts down seconds after boot attempt. Full log attached.
>
> ..[30m.[47mWelcome to GRUB!
>
>
> ..[37m.[40m.[37m.[40m.[37m.[40merror: no such device: 
> /boot/xen/pvboot-x86_64.elf.
>
> Reading (xen/xvda/boot/grub/grub.cfg
>
> ..[H.[J.[1;1Herror: file `/boot/grub/fonts/unicode.pf2' not found.
>
> error: no suitable video mode found.
>
 I can't replicate, but none of my systems have UEFI or if they do, I'm
 using legacy boot because Qubes wouldn't install if UEFI mode was enabled.

 That said, if it worked for you before, it should still work now.

 Are you sure you set up grub correctly after the compile?

 sudo mkdir /boot/grub
 sudo update-grub2

 The only other thing I can think of is to switch to a regular kernel,
 try the two grub commands again and see if any errors pop up, and if
 not, switch back to pvgrub2 and see if it boots again.


>>> Oh, wait. When you said you downloaded a fresh Debian 8 template and
>>> updated, do you mean that you updated it to Debian 9 rather than just
>>> install the regular Debian 8 updates? I'm running another test system
>>> based on Stretch on bare metal, and I think there's something buggy in
>>> one of the packages that was released recently (maybe X?) as it's been
>>> locking up a lot for reason I can't figure out. I'm hoping I can just
>>> wait it out and it'll fix itself later in another update. It could be
>>> related to your problem if that's the case?
>>>
>>> And I just realized there was more to the log that you attached. Still
>>> can't figure out what caused the kernel panic from looking at it, sorry.
>> No, I mean running 8/stable, no other repos active. Would dom0 running uefi 
>> matter to the VM
>>
>> As for the rest, I've rerun every step a few times, so I can't imagine I 
>> missed anything. update-grub2 gave me the message below, but according to 
>> the qubes howto page, those errors don't matter.
>>
>> Anyway, thanks for your replies / time, I guess I'll poke around the log etc 
>> a bit more.
>>
>>
>> -
>> user@debian-8:/boot$ sudo update-grub2
>> Generating grub configuration file ...
>> Found linux image: /boot/vmlinuz-4.8.13-coldkernel-grsec-1
>> Found initrd image: /boot/initrd.img-4.8.13-coldkernel-grsec-1
>> /usr/sbin/grub-probe: error: cannot find a GRUB drive for 
>> /dev/mapper/dmroot.  Check your device.map.
>> /usr/sbin/grub-probe: error: cannot find a GRUB drive for 
>> /dev/mapper/dmroot.  Check your device.map.
>> /usr/sbin/grub-probe: error: cannot find a GRUB drive for 
>> /dev/mapper/dmroot.  Check your device.map.
>>   No volume groups found
>> done
>>
> Yeah, those particular errors don't matter.
>
> I guess later today, I'll try reinstalling the debian-8-template from
> the yum repository and try to build the kernel again from scratch, just
> to make sure. What I've been doing with every Qubes machine of mine is
> installing the templates from the DVD or the repository, updating it,
> and then immediately cloning it and working off of the clone. That way,
> all of my original template rpms are still pristine.
>
> However, I don't think there's any difference between what's on the 3.2
> iso and what's the latest debian 8 template from the repository so I
> don't know if that'll do much in my testing; I think they're the same
> version? I'm sure a dev will chime in if that's not the case.
>
> Your problem is very strange, especially if coldkernel had already
> worked before.
>
>

The last thing I can think of off the top of my head at the moment is
that every Qubes VM by default outside of sys-net have "nopat" set as a
kernel option. If you use pvgrub2 though, it ignores any of the
kernelopts options that are set by qvm-prefs.

To make your coldkernel template vm boot with the nopat option, you have
to make an /etc/default/grub file that contains
"GRUB_CMDLINE_LINUX="nopat" (along with any other kernel options you
would normally pass through) before running update-grub2. So if you
haven't done that yet, maybe try making that file and updating grub and
try again? That's the only thing I can think of at this point.


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

[qubes-users] Re: FYI: Experimental Qubes coldkernel support now available

[Reg Tiangha]

On 12/15/2016 09:43 AM, Foppe de Haan wrote:
> On Thursday, December 15, 2016 at 2:15:20 PM UTC+1, Reg Tiangha wrote:
>> On 12/15/2016 06:01 AM, Reg Tiangha wrote:
>>> On 12/15/2016 05:00 AM, Foppe de Haan wrote:
 Okay, stuck again. Downloaded a fresh d8 template, updated it and built 
 kernel again to have a clean slate to work from. Everything builds, no 
 error beside the expected ones afterwards. But when i switch to pvgrub2 
 and boot, it shuts down seconds after boot attempt. Full log attached.

 ..[30m.[47mWelcome to GRUB!


 ..[37m.[40m.[37m.[40m.[37m.[40merror: no such device: 
 /boot/xen/pvboot-x86_64.elf.

 Reading (xen/xvda/boot/grub/grub.cfg

 ..[H.[J.[1;1Herror: file `/boot/grub/fonts/unicode.pf2' not found.

 error: no suitable video mode found.

>>> I can't replicate, but none of my systems have UEFI or if they do, I'm
>>> using legacy boot because Qubes wouldn't install if UEFI mode was enabled.
>>>
>>> That said, if it worked for you before, it should still work now.
>>>
>>> Are you sure you set up grub correctly after the compile?
>>>
>>> sudo mkdir /boot/grub
>>> sudo update-grub2
>>>
>>> The only other thing I can think of is to switch to a regular kernel,
>>> try the two grub commands again and see if any errors pop up, and if
>>> not, switch back to pvgrub2 and see if it boots again.
>>>
>>>
>> Oh, wait. When you said you downloaded a fresh Debian 8 template and
>> updated, do you mean that you updated it to Debian 9 rather than just
>> install the regular Debian 8 updates? I'm running another test system
>> based on Stretch on bare metal, and I think there's something buggy in
>> one of the packages that was released recently (maybe X?) as it's been
>> locking up a lot for reason I can't figure out. I'm hoping I can just
>> wait it out and it'll fix itself later in another update. It could be
>> related to your problem if that's the case?
>>
>> And I just realized there was more to the log that you attached. Still
>> can't figure out what caused the kernel panic from looking at it, sorry.
> No, I mean running 8/stable, no other repos active. Would dom0 running uefi 
> matter to the VM
>
> As for the rest, I've rerun every step a few times, so I can't imagine I 
> missed anything. update-grub2 gave me the message below, but according to the 
> qubes howto page, those errors don't matter.
>
> Anyway, thanks for your replies / time, I guess I'll poke around the log etc 
> a bit more.
>
>
> -
> user@debian-8:/boot$ sudo update-grub2
> Generating grub configuration file ...
> Found linux image: /boot/vmlinuz-4.8.13-coldkernel-grsec-1
> Found initrd image: /boot/initrd.img-4.8.13-coldkernel-grsec-1
> /usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/mapper/dmroot. 
>  Check your device.map.
> /usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/mapper/dmroot. 
>  Check your device.map.
> /usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/mapper/dmroot. 
>  Check your device.map.
>   No volume groups found
> done
>

Yeah, those particular errors don't matter.

I guess later today, I'll try reinstalling the debian-8-template from
the yum repository and try to build the kernel again from scratch, just
to make sure. What I've been doing with every Qubes machine of mine is
installing the templates from the DVD or the repository, updating it,
and then immediately cloning it and working off of the clone. That way,
all of my original template rpms are still pristine.

However, I don't think there's any difference between what's on the 3.2
iso and what's the latest debian 8 template from the repository so I
don't know if that'll do much in my testing; I think they're the same
version? I'm sure a dev will chime in if that's not the case.

Your problem is very strange, especially if coldkernel had already
worked before.


-- 
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/o2uhgn%24l9r%241%40blaine.gmane.org.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: FYI: Experimental Qubes coldkernel support now available

[Foppe de Haan]

On Thursday, December 15, 2016 at 2:15:20 PM UTC+1, Reg Tiangha wrote:
> On 12/15/2016 06:01 AM, Reg Tiangha wrote:
> > On 12/15/2016 05:00 AM, Foppe de Haan wrote:
> >> Okay, stuck again. Downloaded a fresh d8 template, updated it and built 
> >> kernel again to have a clean slate to work from. Everything builds, no 
> >> error beside the expected ones afterwards. But when i switch to pvgrub2 
> >> and boot, it shuts down seconds after boot attempt. Full log attached.
> >>
> >> ..[30m.[47mWelcome to GRUB!
> >>
> >>
> >> ..[37m.[40m.[37m.[40m.[37m.[40merror: no such device: 
> >> /boot/xen/pvboot-x86_64.elf.
> >>
> >> Reading (xen/xvda/boot/grub/grub.cfg
> >>
> >> ..[H.[J.[1;1Herror: file `/boot/grub/fonts/unicode.pf2' not found.
> >>
> >> error: no suitable video mode found.
> >>
> > I can't replicate, but none of my systems have UEFI or if they do, I'm
> > using legacy boot because Qubes wouldn't install if UEFI mode was enabled.
> >
> > That said, if it worked for you before, it should still work now.
> >
> > Are you sure you set up grub correctly after the compile?
> >
> > sudo mkdir /boot/grub
> > sudo update-grub2
> >
> > The only other thing I can think of is to switch to a regular kernel,
> > try the two grub commands again and see if any errors pop up, and if
> > not, switch back to pvgrub2 and see if it boots again.
> >
> >
> Oh, wait. When you said you downloaded a fresh Debian 8 template and
> updated, do you mean that you updated it to Debian 9 rather than just
> install the regular Debian 8 updates? I'm running another test system
> based on Stretch on bare metal, and I think there's something buggy in
> one of the packages that was released recently (maybe X?) as it's been
> locking up a lot for reason I can't figure out. I'm hoping I can just
> wait it out and it'll fix itself later in another update. It could be
> related to your problem if that's the case?
> 
> And I just realized there was more to the log that you attached. Still
> can't figure out what caused the kernel panic from looking at it, sorry.

No, I mean running 8/stable, no other repos active. Would dom0 running uefi 
matter to the VM

As for the rest, I've rerun every step a few times, so I can't imagine I missed 
anything. update-grub2 gave me the message below, but according to the qubes 
howto page, those errors don't matter.

Anyway, thanks for your replies / time, I guess I'll poke around the log etc a 
bit more.


-
user@debian-8:/boot$ sudo update-grub2
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.8.13-coldkernel-grsec-1
Found initrd image: /boot/initrd.img-4.8.13-coldkernel-grsec-1
/usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/mapper/dmroot.  
Check your device.map.
/usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/mapper/dmroot.  
Check your device.map.
/usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/mapper/dmroot.  
Check your device.map.
  No volume groups found
done

-- 
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/3e453ac5-2d18-4eab-bc6c-35ba27b0a03f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] xfce4 some questions

[Eva Star]

On 12/15/2016 07:27 PM, Andrew David Wong wrote:


#!/bin/bash
qvm-shutdown --wait --all \
- --exclude=sys-net \
- --exclude=sys-firewall \
- --exclude=sys-usb \
- --exclude=sys-whonix \
- --exclude=sys-whonix \
- --exclude=sys-other-1 \
- --exclude=sys-other-2 \
qvm-shutdown --wait --all
sleep 3
shutdown now

Works every time. The idea is to exclude all service VMs from the
first pass of qvm-shutdown so that it doesn't jam up (#1826), so
if you use VPN VMs, exclude those too.

Good advice. Thanks. I have the problem with my ProxyVMs. It's great 
idea to shutdown workVMs first, then ProxyVms, then all other Vms.

I do not know about `exclude` option before :)



--
Regards

--
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/0d9d6ff9-22b4-dc80-2aed-071fd67487c3%40openmailbox.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] help updating dom0 - no network - stuck with lots of pending updates

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 12/15/16 07:10, jasonwalshismyn...@gmail.com wrote:
> 
>> - From this thread:
>>
>> https://groups.google.com/d/topic/qubes-users/s3FJWqKw6Ps/discussion
>>
>> 'Please check "sudo systemctl status qubes-qmemman", or better "sudo
>> journalctl -u qubes-qmemman" for error messages. Then you can restart
>> the service with "sudo systemctl restart qubes-qmemman".'
> 
> 
> 
> results for "sudo systemctl status qubes-qmemman" (I'm not able to transfer 
> logs to another computer from dom0 at the moment so i need to write the logs 
> ...) :
> 
> Active: failed (Results: exit-code)
> Process: 2081 ExecStart=/usr/lib/qubes/qmemman_deamon.py (code=exited, 
> status=1/FAILURE)
> Main PID: 2081 (code-exited, status=1/FAILURE)
> 
> qmemman_deamon.py[2081]: self.connect_unixsocket(address)
> qmemman_deamon.py[2081]: File "/usr/lib64/python2.7/logging/handlers.py" line 
> 789, in connect_unixsocket
> qmemman_deamon.py[2081]: self.socket.connect(address)
> qmemman_deamon.py[2081]: File "/usr/lib64/python2.7/socket.py", line 228, in 
> meth
> qmemman_deamon.py[2081]: return getadttr(self._sock,name)(*args)
> qmemman_deamon.py[2081]: socket.error: [errno 111] Connection refused
> 
> systemd[1]: qubes-qmemman.service: Main process exited, code=exited, 
> status=1/FAILURE
> systemd[1]: Failed to start Qubes memory management deamon
> systemd[1]: qubes-qmemman.service: Unit entered failed state.
> systemd[1]: qubes-qmemman.service: Failed with result 'exit-code'
> 
> it seams to be the same error for "sudo journalctl -u qubes-qmemman"
> 

And what happens when you restart qubes-qmemman?

> In Qubes VM manager, when I right click on dom0 and then click on VM 
> settings, nothing happens, I can infinitly click on "VM settings".  This does 
> not apply to other VMs.
> 

That menu option doesn't do anything for dom0, so what you describe is normal. 
(But admittedly sub-optimal from a UX perspective. We're working on that.)

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

iQIcBAEBCgAGBQJYUsWtAAoJENtN07w5UDAwh1gQAI5+SFxp5jtNF4DPfhsSei45
gaI8OQq9RyWvEzLp2lbm/QSefPkLaD8Y7sEi+RYV4n/WRbO/yqIbQK+9ZK5anJ7f
xxIzZYepoSDQYbcuCrBrJFioStby4oqF6XJRsmY12MfAKo4A2kdjz5Xu/ZES+si7
6CndMBoUReEtWFhrODr/e5Fwr6m4WcugkejqgooiIUt6IAPhsDlyFOxuvt44UMmX
5cI0aPJPiKlCCkQ2p+ML7QXinb6Ua7KlYyhcN53YejXxrTt06JxWBdEsFiY2n11k
xcI7cOm4awNdKl2OGT4mLacr85wspPGohjgQ1mzfpQ+CO+LOdxLoCpF2oYgrxAL6
BWZTVRsyJ2hv4N7HftsDL5WpFaNtIiM99vxspwhV8h4D8YQd+Ho7ryZeCdR6eJKe
gJL6VqaYRPPYo3E54Z7e1DO2CbwVLZ7aSu3KnNCu0GE55iaQesc6U2cFzjrs39Dt
i10urGtRPndeaDbBiHbWVedaUGxXW7GQPC5KYtyKILzKPrwewn6WXiN8oVzWsIbK
vw4KXrVuX6KKZij80zyTVoqx1MyNoir/24hSscSYXoFyD7zHFs/bxmsSSXoOvNYm
+V02F2UDS1FS2O4VE6pCYilHyyClf9qVGtq5drEQEZm7Rnims5NA6wNgSn5GBgv9
0KxZ0TCW9zw0/3f6i1he
=cMkb
-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/04c01d32-1c81-2f2d-6ebc-d963a437ae74%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: [qubes-devel] Re: Announcement: Qubes OS Begins Commercialization and Community Funding Efforts

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 12/15/16 07:43, je wrote:
> Hello,
> 
> 1. have you thought about offering training, consulting and support for 
> companies who want to use Qubes OS in their enterprise?

Yes, this is something we've considered. We'd prefer to focus on selling
licenses rather than selling services, since this would scale better for
our small team, but we also realize that we'll want to offer support (to
some extent) to clients who purchase licenses.

> 2. have you thought about developing commercial management solution which 
> makes the deployment, remote administration and monitoring easy?
> 

I think the Salt management stack is meant to be this, at least to some
degree. I'm not sure if a more robust management solution than that
would be feasible for us to develop in the short-term, or whether it
would be worth the time and cost necessary to do so.

> I do not believe that developing a commercial operating system based on an 
> open source foundation will pay off on a long run.

Is there a specific reason you think it will not? Just curious.

> However, I agree with you that customized tool and plugin development
> can provide a valuable source of income.

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

iQIcBAEBCgAGBQJYUsGpAAoJENtN07w5UDAw/IwQAL6W6mZ3zkIskovm0+MH2Yze
xkzKVZ++INeFsO3hxkC+s8eF9kVpPKtbHEWwdK6aCBOZS4fYACk7L3YqkuVwaRnO
0mu/EtSqx4NrlVxn57R4/2+tdsTEICcHoMd1IC0AqhuNXGy7dfumgSickBRTc3qB
Zg9xuxj76hvVOVj8X2lCko/XiTOz+rmQF7HhzbQxmWAlFFqr+xq6MH0D945oux9I
9C8kSx9I/Il1ZFq5vQi8BJN/UFITCH9D/AvBbHNFb690uXk5bRzxYRY30culPayn
NJIplbu0+BnlqDAMwrGT1GX1yq6hGAVLO+6ZOzybUUqjoIcmBZB1i7hUrGRusnYD
AAfOLjH5qsJNHn3ZjN0t+jqQ1+jdshsPUrqMfePs/TmdilJJ31gPDRSmU4OVGkOK
MmDLRXxv/oK3QlEkS8zfnidJY41wlfcKM/+TYI9PXf/kvosi8pKMnUDb1UnElyn1
nDpAgAXr0Od3mDP040PRaBMtDSGFJIoXXcrcxSr/6efGQacc2f96EeO5mWFGg369
sbIxh8JK9R2tnDM35xge1wg+hxsrpuJdcSiy+4RHwdo0UBY9vqOu0b6YeBmO6PfB
SR68NYFE3Pd2mxDfuWgGBP3xyWozrR6SVbvZ0NXlVwEJpqLHyeUvu1G1mE5v1/la
tqYENe2TwclBOi3k9rHe
=ScqY
-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/3bf80ddb-0cd6-7572-ab15-34df800d949b%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] xfce4 some questions

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 12/15/16 08:19, Eva Star wrote:
> On 12/15/2016 07:10 PM, Andrew David Wong wrote:
> 
>>
>> Hm. Not sure if this'll make a difference, but try shutting down
>> all VMs, then shutting down from the command-line. For example:
>>
>> $ qvm-shutdown --wait --all
>> $ shutdown now
>>
> 
> I wrote the bash script and at it to the xfce4 launcher. Then I start the 
> script with mouse. The first step the same, but then I call standard shutdown 
> from menu (describe above). Then problem, that execution of qvm-shutdown 
> --wait --all not always end (known problem)

FWIW, I've been using simple shutdown and reboot scripts to work
around this issue (I think since I first started using Qubes).
Here's an example:

#!/bin/bash
qvm-shutdown --wait --all \
- --exclude=sys-net \
- --exclude=sys-firewall \
- --exclude=sys-usb \
- --exclude=sys-whonix \
- --exclude=sys-whonix \
- --exclude=sys-other-1 \
- --exclude=sys-other-2 \
qvm-shutdown --wait --all
sleep 3
shutdown now

Works every time. The idea is to exclude all service VMs from the
first pass of qvm-shutdown so that it doesn't jam up (#1826), so
if you use VPN VMs, exclude those too.

> and after computer reboot, the same console show on the desktop an my script 
> begin to execute (shutdown script begin to execute after reboot, because 
> console not closed, it somewhere stored at the session :( )
> 

Did you do an in-place upgrade or a clean install of 3.2? If you
did an in-place upgrade, perhaps some setting got carried over.

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

iQIcBAEBCgAGBQJYUsRdAAoJENtN07w5UDAwaj0P/34Rddgw8oiuLufC0URVWofL
SAa5B4tSGph0MsOoadVpVBHq8n2J0ewfii1eEN+HfT4Y8zmFJFIPHgoJGmO3gAzR
eEcnOxXYAJnklDm73E4izAlghmqsLnoyTK8AJIyyb3Q3EGeo25dDdf1bB3nrGFKH
q7t5QlYN9n358LaFdqvpcJuzKW45IjQZ1Lm/t7CAX5QH/4kIMij0r5NPqX2eganq
9OM0tIfcQb4plriYj9DHMcllWknqtJvEVv1juXFEzEyqWREvwLiN9W3Dtg4I3Y8e
JwtmxIP4Va7b5edh/3XeW8vJTHKH+mL0AfbxrCEgyDyFhNMxcGCzlcCyScBlrsC9
pw44fuKWGXckqjAUY7Kz6E1KzJvwckoDGFMHtciDkFOLiFZx6vk7/GUYF8xbwRt1
L0zkdhjzi4zLcheY5erxMXx/rafLmxtD4/iJKpz3E90qM6E8jHa61clKmhqxQUVT
WCXA6A8izQ4B5Hq+r0U+BuAPRwuU812MTJHQa0SKRvRtGVixGmLfdnCGiAQDovse
QBikYYaUMflBeJrhewUC5aufaiqE6NAmYMe/ReIDRCw78Nlvg7G+t/khD2zUcB2k
q0cGhWjzvY37azxttn7RbbPhMDIubdRQJtQrngfePVuIPlqYzmmmWfa8SCgXf3Z5
VGy5svUB9/KuGgpPO87R
=Gful
-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/788178a8-89f0-ac60-06c2-0582abbea32f%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] xfce4 some questions

[Eva Star]

On 12/15/2016 07:10 PM, Andrew David Wong wrote:



Hm. Not sure if this'll make a difference, but try shutting down
all VMs, then shutting down from the command-line. For example:

$ qvm-shutdown --wait --all
$ shutdown now



I wrote the bash script and at it to the xfce4 launcher. Then I start 
the script with mouse. The first step the same, but then I call standard 
shutdown from menu (describe above). Then problem, that execution of 
qvm-shutdown --wait --all not always end (known problem) and after 
computer reboot, the same console show on the desktop an my script begin 
to execute (shutdown script begin to execute after reboot, because 
console not closed, it somewhere stored at the session :( )




--
Regards

--
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/84051c94-ad06-d92f-2956-cafd5b41d154%40openmailbox.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] xfce4 some questions

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 12/15/16 07:57, Eva Star wrote:
> On 12/15/2016 04:52 PM, Andrew David Wong wrote:
>>
>> How did you enable this in the first place? My system doesn't do that.
>>
> 
> I do not enable this. It's look like session storage, but it's disabled here 
> `xfce4-sessions-settings`
> 
>>> 2) After reboot selected last virtual desktop. How to always
>>> select first one?
>>>
>>
>> (Same as previous.)
>>
>> Perhaps it has to do with the way you're shutting down the system. How
>> are you shutting down?
> 
> I run the bash script to shutdown all VMs, then I go to Alt-F1 -> LogOut -> 
> Shutdown. I do that with keyboard, because sys-usb shutdown very quick and 
> I'm without mouse :(
> 

Hm. Not sure if this'll make a difference, but try shutting down
all VMs, then shutting down from the command-line. For example:

$ qvm-shutdown --wait --all
$ shutdown now

> 
>>
>> Try this:
>>
>> Settings Manager -> Window Manager -> Focus -> New window focus
>>
>> Uncheck "Automatically give focus to newly created windows."
> Thanks, I will try this.
> 

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

iQIcBAEBCgAGBQJYUsBuAAoJENtN07w5UDAwqq8P/jOKJJt9s6i0YSwYClwFAzta
mkom/x+3Gd1ELJZ+3jj0OznzD6QVEftgWZu34INFc08ik/ciOxo5N//2SJLHq/WD
Dm0DjX8sj25IiIlO2TckMSk//UoA/qgGlKKM0YzPvKFCEIJQXPJrft89jtB+wW+k
0VDF0sshf+FbPg8QUOZn0HL+PQCF3snFzaP5jc1yem+mvcj297fzvNnaYjKteGPi
TJYnpWzpVXyRZbIi2joJWzRCoGVlClmk1AD36eyX+yfwtHOQRgimwgNZSghiaDXm
GPzHb+6OctbgRpl8nz3ilURzIwlkc2fxFIV2prHk86NFSv7J//jK3A1JoA4G8jc1
yZFowKqHA5YuWfk7FcsKsZ6eA4RJN5ukNG1P76QWx/u3lYC6A4qvNXIkkxfi95ee
prHP67mV/ihWQO6tyvnIOFvZAfW5KzWFpcVknG1R0mqZwn+Hho30Fd8+AD3PtKYe
5WP+3rnetAiMA90u7yVf4y2fVu01jj5lk/1EFCYiqc7iLkPvlm8ki/TFdAvU1V20
CFIOQrJqvIcaBanQHfCiTeqS16Qm9ltwVoWJpuL5QjpvMWQyPtSJgleJZUqaCqAd
Myrt5P3VIn1lMH0brovVkFmK1BAijCtZeGCGx4SVsvhwUDTDuas0I7FcvZZYI9fJ
0bkLF9WWXWPkG/vxH6oZ
=pGqY
-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/e9fcdfcc-007b-6d17-6475-f10c5d0ea9c7%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] xfce4 some questions

[Eva Star]

On 12/15/2016 04:52 PM, Andrew David Wong wrote:


How did you enable this in the first place? My system doesn't do that.



I do not enable this. It's look like session storage, but it's disabled 
here `xfce4-sessions-settings`



2) After reboot selected last virtual desktop. How to always
select first one?



(Same as previous.)

Perhaps it has to do with the way you're shutting down the system. How
are you shutting down?


I run the bash script to shutdown all VMs, then I go to Alt-F1 -> LogOut 
-> Shutdown. I do that with keyboard, because sys-usb shutdown very 
quick and I'm without mouse :(





Try this:

Settings Manager -> Window Manager -> Focus -> New window focus

Uncheck "Automatically give focus to newly created windows."

Thanks, I will try this.


--
Regards

--
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/f4d51c94-29ee-2a29-c753-90d1614c9d14%40openmailbox.org.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Announcement: Qubes OS Begins Commercialization and Community Funding Efforts

[je]

Hello,

1. have you thought about offering training, consulting and support for 
companies who want to use Qubes OS in their enterprise?
2. have you thought about developing commercial management solution which 
makes the deployment, remote administration and monitoring easy?

I do not believe that developing a commercial operating system based on an 
open source foundation will pay off on a long run. However, I agree 
with you that customized tool and plugin development can provide a valuable 
source of income.

-- 
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/98142ccf-a06e-4734-9f5b-656db466f228%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] help updating dom0 - no network - stuck with lots of pending updates

[jasonwalshismyname]

> - From this thread:
> 
> https://groups.google.com/d/topic/qubes-users/s3FJWqKw6Ps/discussion
> 
> 'Please check "sudo systemctl status qubes-qmemman", or better "sudo
> journalctl -u qubes-qmemman" for error messages. Then you can restart
> the service with "sudo systemctl restart qubes-qmemman".'



results for "sudo systemctl status qubes-qmemman" (I'm not able to transfer 
logs to another computer from dom0 at the moment so i need to write the logs 
...) :

Active: failed (Results: exit-code)
Process: 2081 ExecStart=/usr/lib/qubes/qmemman_deamon.py (code=exited, 
status=1/FAILURE)
Main PID: 2081 (code-exited, status=1/FAILURE)

qmemman_deamon.py[2081]: self.connect_unixsocket(address)
qmemman_deamon.py[2081]: File "/usr/lib64/python2.7/logging/handlers.py" line 
789, in connect_unixsocket
qmemman_deamon.py[2081]: self.socket.connect(address)
qmemman_deamon.py[2081]: File "/usr/lib64/python2.7/socket.py", line 228, in 
meth
qmemman_deamon.py[2081]: return getadttr(self._sock,name)(*args)
qmemman_deamon.py[2081]: socket.error: [errno 111] Connection refused

systemd[1]: qubes-qmemman.service: Main process exited, code=exited, 
status=1/FAILURE
systemd[1]: Failed to start Qubes memory management deamon
systemd[1]: qubes-qmemman.service: Unit entered failed state.
systemd[1]: qubes-qmemman.service: Failed with result 'exit-code'

it seams to be the same error for "sudo journalctl -u qubes-qmemman"

In Qubes VM manager, when I right click on dom0 and then click on VM settings, 
nothing happens, I can infinitly click on "VM settings".  This does not apply 
to other 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/af221208-9aad-4ecf-9416-5d4290e654c2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] qvm-create-default-dvm modifying initial memory value?

[Joonas Lehtonen]

 When I look at whonix-ws-dvm "initial memory" it says: ~2800MB
>>>
 I changed that to 1000MB and everything works again.
>>>
>>> Why that high? 
> 
>> since its preset value was over 2800 I didn't want to reduce it to much
>> but I just found out that something changes that value. (I did set it to
>> 1000 it is now at >1500MB).
> 
>> Is this a bug? Or can I disable this auto-adjustment?
> 
> Ah, I forgot it's adjusted at qvm-create-default-dvm call time. Based on
> memory usage inside of VM. It looks something use that much memory in
> Whonix-ws based DVM... Try running 'top' there (switch to sorting by
> memory with '>' key).

OK I played around some more and when setting initial memory to 400MB it
gets only increased to >420MB, that should be fine.

When starting a xterm-dvm 'top' says only 315MB memory are used.

I consider this as solved and I will reset it to 400MB from time to 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/dfb65df7-990a-b340-901a-b58efa31ff09%40openmailbox.org.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

[qubes-users] Re: Hardware acceleration in Chrome (or "make google maps great again!")

[pixel fairy]

On Saturday, December 10, 2016 at 10:52:29 PM UTC-8, Jean-Philippe Ouellet 
wrote:
> Hello,
> 
> Google Chrome disabled the chrome://flags mechanism to disable WebGL
> some time ago, but now it appears that it is back as "Use hardware
> acceleration when available" at the bottom of the Advanced section of
> chrome://settings.
> 
> Disabling this makes google maps not lag/crash for me! :)
> 
> Perhaps everyone has already done this and I'm just late to the party,
> but I don't remember seeing it discussed in a capacity other than
> "yeah... this is a problem", so I figured I'd share.
> 
> Cheers,
> Jean-Philippe

thanks! i was wondering about 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/2c8d4a49-41ea-48e0-9753-05b15cf39ad5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Installing on macOS Macbook

[pixel fairy]

On Wednesday, December 14, 2016 at 3:38:24 AM UTC-8, dumbcyber wrote:

> I am reading and responding to this thread on a Macbook Pro 11,1 running 
> Qubes R3.2.  Andrew and others are right: yes it works, but you need to work 
> hard to make it work. I had the keyboard not working issue and in fact i had 
> to build my Qubes disk on a Lenovo to get past the install issues the Macbook 
> was giving me.
> 

i had the same problem on my 11,3. how did you get it working? 

-- 
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/d25df66a-79e9-441d-bdb4-0597195f2144%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] qvm-create-default-dvm modifying initial memory value?

[Joonas Lehtonen]

Andrew David Wong:
> I don't understand. Isn't the target TemplateVM shut down when
> qvm-create-default-dvm is called? How could it be using any memory
> while it's shut down?

This is not about the initial memory of the used templateVM (in this
case whonix-ws) but about whonix-ws-dvm. (qubes manger -> show interal 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/5b4d6550-be8c-25ab-c39c-906ef6519539%40openmailbox.org.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] qvm-create-default-dvm modifying initial memory value?

[Marek Marczykowski-Górecki]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Thu, Dec 15, 2016 at 05:49:18AM -0800, Andrew David Wong wrote:
> On 2016-12-15 05:45, Marek Marczykowski-Górecki wrote:
> > On Thu, Dec 15, 2016 at 01:40:00PM +, Joonas Lehtonen wrote:
> > 
>  When I look at whonix-ws-dvm "initial memory" it says:
>  ~2800MB
> >>> 
>  I changed that to 1000MB and everything works again.
> >>> 
> >>> Why that high?
> > 
> >> since its preset value was over 2800 I didn't want to reduce it
> >> to much but I just found out that something changes that value.
> >> (I did set it to 1000 it is now at >1500MB).
> > 
> >> Is this a bug? Or can I disable this auto-adjustment?
> > 
> > Ah, I forgot it's adjusted at qvm-create-default-dvm call time.
> > Based on memory usage inside of VM.
> 
> I don't understand. Isn't the target TemplateVM shut down when
> qvm-create-default-dvm is called? How could it be using any memory
> while it's shut down?

It's about whonix-ws-dvm - it is started to create savefile out of it.

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

iQEcBAEBCAAGBQJYUqGHAAoJENuP0xzK19csIZAH/AwKtI/f3s6q16MAL2CU4Zj9
qaaRtOpYn3fkOb5c7CDUdfxM7gD63BqR6DE8xGFBsAbRUOcH0K8ezOi80cRoifG0
oHmQuDKgs1hWG4awY/WZs/zcIYJlACp1AQC+vlNd8e4I+du4CQ88zwC+6Re2br3a
xnsNm7lcAgvPvGEoONxecrmteMCNVO73yOVmVAfW+ZGx0/CW9qrg4oQX0eqE0bk0
WD8qd5bcOu5rc3VneYuXzAzhaFhNsoB+jsYGoSgN/WFI9nUDYZSdeBEwqfXdXSYJ
mzUtfjx8zefIPMfi01gOvPgx6bY1cSM9Aic2lTnkhYYZxtc4FT+QwOZhbxMWD/o=
=Zgkg
-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/20161215135832.GP1239%40mail-itl.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] xfce4 some questions

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-12-15 05:41, Eva Star wrote:
> Some questions:
> 
> 1) How to disable "restore windows" at startup? I mean when I
> shutdown Q and I have opened dom0 console, then this console show
> after reboot on the desktop. How to disable? I'm already tried
> "Sessions and Startup" - "Xfce Teminal" - Never. then after reboot
> it reset to default "if running"
> 

How did you enable this in the first place? My system doesn't do that.

> 2) After reboot selected last virtual desktop. How to always
> select first one?
> 

(Same as previous.)

Perhaps it has to do with the way you're shutting down the system. How
are you shutting down?

> 3) `xset b` can change beeper settings. It working only at current 
> setting and restore after reboot. How to save the changes forever?
> 
> 4) UpdateVM window get focus (Whonix Browser Update) and I time to
> time I click "confirm" without real confirmation. Because it get
> focus! How to fix this?
> 

Try this:

Settings Manager -> Window Manager -> Focus -> New window focus

Uncheck "Automatically give focus to newly created windows."

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

iQIcBAEBCgAGBQJYUqACAAoJENtN07w5UDAwNJIP+wRh8arTRB/QavYksjFthEcl
KpumBm80dDVAxF/2fizoQUWrZJ1oAWVvTFHvpgFHSrfo/R+6dn8TYfzqTukLcwHq
ZGT9ggQhbUs4geWOCyUjRbvSzDTLhy7duTZzRepgqHBGzg9iQtQIZwnSI28B8z/x
ZQp0SXhCQ0ejNiuQ1XRI8J7GCa092CdFSGrHAzenWTAbsMw/M2ZZ4leihBGBOSQ6
LyeCwe+TLcfPAcDJHFACpfSakQ690snmU3tpCmAaTEnEEn7f8alRLhmIh86mYPcW
fcpKbfFA6vn7z0sRFRqEMNb7A0s5eRC1VgVx+4fuuqcwsI0hJzc4xuTtMl5DgJkJ
yczoGmWMV0+RzzOPfC+6qOgRW4LrtMixyXLWoMnYtMDFsitzmoT90IkDg35UnKMN
ICuSotwikOaZdS4IHuvmlJvb6Z1vYKzkn+05NbzqeYwZThdypcIZ5GoTIKk8IpxX
dxWwHdVb5V7/JzuxIBwebbwOpYcFx4pbHavavLoOH/+JtXHSEm09RmC9wkCoIihA
X9U8jzRJ6iDFrjMNrf5CIgx/EyNKH+bTa5E6KzFGHIoLC7SdQWgopeZfdugFv2Mp
fzQG2O19CeTr+XodCp63g/xyeuq3RliymBF2GvqSbzJfeMDWQ99Qo8HSk8u0EOJq
gkIcYvwgH6W84kQWJyc/
=HzDX
-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/4bd5b200-9960-7da4-cd88-d607a3556d9f%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] qvm-create-default-dvm modifying initial memory value?

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-12-15 05:45, Marek Marczykowski-Górecki wrote:
> On Thu, Dec 15, 2016 at 01:40:00PM +, Joonas Lehtonen wrote:
> 
 When I look at whonix-ws-dvm "initial memory" it says:
 ~2800MB
>>> 
 I changed that to 1000MB and everything works again.
>>> 
>>> Why that high?
> 
>> since its preset value was over 2800 I didn't want to reduce it
>> to much but I just found out that something changes that value.
>> (I did set it to 1000 it is now at >1500MB).
> 
>> Is this a bug? Or can I disable this auto-adjustment?
> 
> Ah, I forgot it's adjusted at qvm-create-default-dvm call time.
> Based on memory usage inside of VM.

I don't understand. Isn't the target TemplateVM shut down when
qvm-create-default-dvm is called? How could it be using any memory
while it's shut down?

> It looks something use that much memory in Whonix-ws based DVM...
> Try running 'top' there (switch to sorting by memory with '>'
> key).
> 

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

iQIcBAEBCgAGBQJYUp9dAAoJENtN07w5UDAwUcsQAIceeQ+APPDNleqeR91l/KBA
LGwiLuAXJkBg7WhvkbjujF/sn6xXwk+DOOlq8hg79Ug/rZooEPqgHxuQdY5qcAZS
5YCCv879IdGqeSD/D5zDG+iNddnfVIE1k2dGnFU2jZ3AV7kQH+TqU7Vp5HAktaTd
VA/+twCB0+DrgsyhcaPJguRSEle/0PYsYbjPL9o1uV03AtuAMIQD26nSf33K9ERu
YZi7pZif7tN7C/INurTGFGaORoQzBqFErpLBN5xBrdrZ4/JkF2LsUzD36qVqZvLx
SfnOpzh9oejYqkxH3ZcPmM4sU8RHp40DXz4u9otVoeGQmPCrQZAwBw7cFP/t/qiF
fU3MX+llM1hz/tp457CAIuG3YyimPTSr2VAfAWCxzReH4K9NrnEaxTK5Z/UGvP5w
qXTA+ja3xUCZ9rsBvoa7qoWmCE98zRhyQm5twSQfneHCe6Q9RxhohU//lDbeR537
U3tW2bVnl6+ZWlB6W1UMoYyIwgLkakijN/megjPZ7h2BYNMYQCApDMBepsVVMrAs
4lwRA8Rd0xisana5nK/mK/JIAgQq/GHBuJGqx0ztbr2bMFm0FybT4/OhsLCszrIZ
SkPfyMhMAjaFC4cqIECiC7sEsJu8e8CmgyaU/Zm6eHJpUdbqp47LGREdgdmUonEX
dI25jiZEY4Y76ZSgJAAq
=LLf7
-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/d55f8dad-ef80-9165-7afc-6f198cfcdf6d%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] qvm-create-default-dvm modifying initial memory value?

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-12-15 05:40, Joonas Lehtonen wrote:
> 
>>> When I look at whonix-ws-dvm "initial memory" it says: ~2800MB
>> 
>>> I changed that to 1000MB and everything works again.
>> 
>> Why that high?
> 
> since its preset value was over 2800 I didn't want to reduce it to
> much but I just found out that something changes that value. (I did
> set it to 1000 it is now at >1500MB).
> 
> Is this a bug? Or can I disable this auto-adjustment?
> 

The default initial memory value should be 400 MB. At least, that's
what mine is.

>> Have you disabled dynamic memory management for this VM?
> 
> No
> 
>> Otherwise it needs to be only that high to allow booting the VM,
>> until dynamic memory management kicks in.
> 
> 

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

iQIcBAEBCgAGBQJYUp6rAAoJENtN07w5UDAwOcIP/jH+xCUjsbX4Ipl52+4bvgv5
GXYalAUjMktdHLKOVLniS+4BpGfcKecufRtz68FEZOhnpKmuB1icSlPM7Z6Kq/3a
dmwKcjdoKrLVDRFuGfTxbTTrXOTmiRa5rE/eU0pxDUmRnqtFemM1+3f88mYXrL2t
eCz7FFpHNjDTUTzpmv8Iphi4y1TvzaUX25KypP63Jeb6JsNLnrW3/kBSAB0q2j0K
RUCUP5QOuTMh2tcONvIXqTqatm24SIRmruHrvzmCWly6kLOigINU280TDInW8nKI
ht/lU+oVq4yD5bXtV+Dnv3OQcVn3aUz48n1d2eESWgcK7s0NLjfBW8my+kVJVUs3
O79yOFcFKb+UPZB/L+DNTnx6+/SJq4YVZ7RbZYqGrU+lslZ5wRKH6BTcXqA3qX3N
GyAASaQuBta7xnuMLzPSFEHOM9IYh4S8KYCxWYEwcU4/5yM2h0LNk8VnwYmuEl3R
v694TYwsed6WiXLbSkhuIbhmyYDzP/YOQ1u37y5ozNAKM1v5Z2NB4vZL1xaAKsoM
QEWom5u7mQMtgP/oYtSSi6sCyjtvE9sP8ViEjBgNoC7H7UhdVGDTkg5la15RTkIJ
zypsiUlUK73o9pGsd2rep1gWy20jhTPoHtF36dWfKEVtFIHBw7mHnbygAW90tbPw
RoYLDEsm2KkHQo5rDYr+
=OUQ2
-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/3cb95221-aef1-302d-d0ff-5e7382f7bc64%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] qvm-create-default-dvm modifying initial memory value?

[Marek Marczykowski-Górecki]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Thu, Dec 15, 2016 at 01:40:00PM +, Joonas Lehtonen wrote:
> 
> >> When I look at whonix-ws-dvm "initial memory" it says: ~2800MB
> > 
> >> I changed that to 1000MB and everything works again.
> > 
> > Why that high? 
> 
> since its preset value was over 2800 I didn't want to reduce it to much
> but I just found out that something changes that value. (I did set it to
> 1000 it is now at >1500MB).
> 
> Is this a bug? Or can I disable this auto-adjustment?

Ah, I forgot it's adjusted at qvm-create-default-dvm call time. Based on
memory usage inside of VM. It looks something use that much memory in
Whonix-ws based DVM... Try running 'top' there (switch to sorting by
memory with '>' key).

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

iQEcBAEBCAAGBQJYUp6DAAoJENuP0xzK19csUmsH/iW+5j0CZKbJY3q8snfRZgag
A+UaXXuDP96JFyw52fbcmQp/iOuu+Me7PKWces+GVrnPsSr4LkGkmrwIsTvOnRlc
oCqoIakzseoTjUV4wHdev8tpboRVTzzfAAUFTtna1ULzOKvZpDCcSaztimXyQ/LZ
Lz5Zk6RLiBmSyaXzdM197XvTfB1eh7uTRCPctKvO1w62a1aTRGDL9wfl0KmTVusp
zOyGqOgrYEolRLWQQO8ugizjzN959CP6n9KVPTzBUDsOKdwQcKDBCQ4ohYJPBEKh
GvRti/MEXxFMtoGk/Z2lX2jAoVDMSqLW8h5Sc0IFriHgekFgUPYfdiWW4+kezs4=
=cXCm
-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/20161215134540.GO1239%40mail-itl.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] help updating dom0 - no network - stuck with lots of pending updates

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-12-15 05:35, jasonwalshismyn...@gmail.com wrote:
> 
>> Yes, I see the problem. It sounds like your ServiceVMs are based
>> on debian-8. Have you tried basing them on the default Fedora
>> template instead?
> 
> Ok, I have now assign sys-net & sys-firewall to fedora-23
> TemplateVM, I still have the same qmemman error.
> 

- From this thread:

https://groups.google.com/d/topic/qubes-users/s3FJWqKw6Ps/discussion

'Please check "sudo systemctl status qubes-qmemman", or better "sudo
journalctl -u qubes-qmemman" for error messages. Then you can restart
the service with "sudo systemctl restart qubes-qmemman".'

> Is it normal that when I start my computer (after decryption) that
> my desktop looks like this (this is also how my desktop looked like
> before the upgrade) :
> 
> https://s23.postimg.org/tgs6vy8yj/006.jpg
> 
> and now (after the upgrade) looks like this :
> 
> https://s30.postimg.org/o1ot24zoh/007.jpg
> 

Looks pretty normal to me. Is there any particular part that seems
abnormal to you?

> In the last picture you can see that only dom0 is in active state
> with 3934 MB as MEM. (its always at 3934 MB)
> 

Since you don't have any other VMs running, all available memory is
allocated to dom0. Normally, it would be dynamically reallocated as
you start more VMs (but I know that you can't currently start any more
VMs).

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

iQIcBAEBCgAGBQJYUp5mAAoJENtN07w5UDAwfHYQAKuDJJ2joI//RxX2jNk0A8CP
/fQvhCeSu2rg6YD82TcItTiLUVSCaOp7DymJCosMxQDeW2VE9syjMtxI58nDWEjZ
i0UbeX/9S+Z+O90l3PKnPZRuNDMMPdxi/lT5k7QPT6eTBl7Lw5jaM4ROt1PJxHsf
FaqsfKVe436SSoutLnZWAvAT7CWUJ6LJJwKyZjCEzvM6D77LWGvKnzzxsyhZ71Vx
qvBn0jd5yJrHXawblDdhYFAaqSFa7+n70GLc+Oby7CbZXV3hB4XMf5xaqjddorE+
NU/rw8si1L08iz9o8qV7BH6xnUk0vX4u4lfJES7axPbBO8F554Bt3HIeLDuzIZO7
9ZqFuyfnud6WxB4B9oMjkXsjCLkvGqFKcBPgFG9MGccGF3sEiSPBnggnPMVCvYsE
nNx7OV6XkbGWzI8W+N+5Qzd5uZj/64kI8WMXjjBQoVK4UoQCppikNpjgxRylyOXI
wCP5Bn/bj09bouU7pYq8RMNxEUH2NNpIsqY5RkTYGvgEpJycgY9VrcgSMG2MlmMm
1Jy71by1k/NwNc19pW8rqnJ520+M1sCnD/+CHdvRMbERdqid+4bHC1nL+lHxXYlD
nURBd6fMWDiQ4FTFI9zKvDM/T5x8ko6pUo7ap15SVqYPCfA0yCYtNMSljuRFl/BZ
VZQfIlNB9Jyh19MWe2oU
=7FFV
-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/93bfac9f-c5c8-6b8a-af77-8fa4e0722e20%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] xfce4 some questions

[Eva Star]

Some questions:

1) How to disable "restore windows" at startup? I mean when I shutdown Q 
and I have opened dom0 console, then this console show after reboot on 
the desktop. How to disable? I'm already tried "Sessions and Startup" - 
"Xfce Teminal" - Never. then after reboot it reset to default "if running"


2) After reboot selected last virtual desktop. How to always select 
first one?


3) `xset b` can change beeper settings. It working only at current 
setting and restore after reboot. How to save the changes forever?


4) UpdateVM window get focus (Whonix Browser Update) and I time to time 
I click "confirm" without real confirmation. Because it get focus! How 
to fix this?


Thanks


--
Regards

--
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/3b7af3f0-6320-318e-d9a6-1c7ef23d4d10%40openmailbox.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] help updating dom0 - no network - stuck with lots of pending updates

[jasonwalshismyname]

> Yes, I see the problem. It sounds like your ServiceVMs are based on
> debian-8. Have you tried basing them on the default Fedora template
> instead?

Ok, I have now assign sys-net & sys-firewall to fedora-23 TemplateVM, I still 
have the same qmemman error.
 
Is it normal that when I start my computer (after decryption) that my desktop 
looks like this (this is also how my desktop looked like before the upgrade) :

https://s23.postimg.org/tgs6vy8yj/006.jpg

and now (after the upgrade) looks like this :

https://s30.postimg.org/o1ot24zoh/007.jpg

In the last picture you can see that only dom0 is in active state  with 3934 MB 
as MEM. (its always at 3934 MB)

-- 
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/f055f65e-811e-42d1-80b1-09276596d046%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] qvm-create-default-dvm running out of space

[Marek Marczykowski-Górecki]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Thu, Dec 15, 2016 at 01:24:00PM +, Joonas Lehtonen wrote:
> >> I haven't encountered this before, but it sounds like the Tor Browser
> >> update might've pushed you over the default 2 GB size limit. Maybe try
> >> increasing the size of your DVM template?
> > 
> > Storing savefile in /dev/shm (tmpfs - stored in RAM only) is an
> > optimization to load it faster. Normally this file takes about
> > 300-400MB, so should be well below 2GB limit... It's size depends on
> > memory amount used in DispVM. 
> > 
> > First I'd check what other files you have there and in /tmp - maybe some
> > old unused stuff. 
> 
> /tmp is basically empty (avail: 2GB)
> 
> I also tried to increase it to 3GB via
> mount /tmp -o remount,size=3G
> 
> but that did not help.
> 
> When I look at whonix-ws-dvm "initial memory" it says: ~2800MB
> 
> I changed that to 1000MB and everything works again.

Why that high? Have you disabled dynamic memory management for this VM?
Otherwise it needs to be only that high to allow booting the VM, until
dynamic memory management kicks in.

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

iQEcBAEBCAAGBQJYUpuDAAoJENuP0xzK19csIzAIAIczRWf43UQKNhhfHz0Ryrt/
TzLKf/0VUfrC8C3wmMyzgFMHx+jhDNnzlupYIp9Mb12Lj4bfkQXaVvyBVJm65vmg
Vskio7AinJ4JVzNs/VL3PHyM3OY1eiy7DaP0PQHKv+HoQtm6Pfk5hJQSsolZCl78
EUHN3TFHIirc0kCno3JoAowccmRRaD2eNc5W9QQVXrOQHWuqqC/Wpta7xdrHhIcl
XJ5+m4LPne9GA1MIcGLLCgiia/g9mvIbtBgkSysriVYnpkOjWDiGvkxVPcCddkfn
lFqGQgtkgKfMy+x+a1TXgBn9fvbk6wdmFkRa0k60E3ne8a8+0RfFYxLp3FO+amg=
=PJsi
-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/20161215133252.GN1239%40mail-itl.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] qvm-create-default-dvm running out of space

[Joonas Lehtonen]

>> I haven't encountered this before, but it sounds like the Tor Browser
>> update might've pushed you over the default 2 GB size limit. Maybe try
>> increasing the size of your DVM template?
> 
> Storing savefile in /dev/shm (tmpfs - stored in RAM only) is an
> optimization to load it faster. Normally this file takes about
> 300-400MB, so should be well below 2GB limit... It's size depends on
> memory amount used in DispVM. 
> 
> First I'd check what other files you have there and in /tmp - maybe some
> old unused stuff. 

/tmp is basically empty (avail: 2GB)

I also tried to increase it to 3GB via
mount /tmp -o remount,size=3G

but that did not help.

When I look at whonix-ws-dvm "initial memory" it says: ~2800MB

I changed that to 1000MB and everything works again.

-- 
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/e7220893-513a-b8e6-0890-1ea52b73669f%40openmailbox.org.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Kali VM no longer responding

[J. Eppler]

Hello @qubenix,

I am interested in your Kali installation process. Did you run into any trouble 
during the installation? Did you follow the KaliVM installation instructions: 
https://www.qubes-os.org/doc/pentesting/kali/?

regards
  j. Eppler

-- 
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/4a7b9915-e2c3-42c4-8b24-1c338d5a5063%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: FYI: Experimental Qubes coldkernel support now available

[Reg Tiangha]

On 12/15/2016 06:01 AM, Reg Tiangha wrote:
> On 12/15/2016 05:00 AM, Foppe de Haan wrote:
>> Okay, stuck again. Downloaded a fresh d8 template, updated it and built 
>> kernel again to have a clean slate to work from. Everything builds, no error 
>> beside the expected ones afterwards. But when i switch to pvgrub2 and boot, 
>> it shuts down seconds after boot attempt. Full log attached.
>>
>> ..[30m.[47mWelcome to GRUB!
>>
>>
>> ..[37m.[40m.[37m.[40m.[37m.[40merror: no such device: 
>> /boot/xen/pvboot-x86_64.elf.
>>
>> Reading (xen/xvda/boot/grub/grub.cfg
>>
>> ..[H.[J.[1;1Herror: file `/boot/grub/fonts/unicode.pf2' not found.
>>
>> error: no suitable video mode found.
>>
> I can't replicate, but none of my systems have UEFI or if they do, I'm
> using legacy boot because Qubes wouldn't install if UEFI mode was enabled.
>
> That said, if it worked for you before, it should still work now.
>
> Are you sure you set up grub correctly after the compile?
>
> sudo mkdir /boot/grub
> sudo update-grub2
>
> The only other thing I can think of is to switch to a regular kernel,
> try the two grub commands again and see if any errors pop up, and if
> not, switch back to pvgrub2 and see if it boots again.
>
>
Oh, wait. When you said you downloaded a fresh Debian 8 template and
updated, do you mean that you updated it to Debian 9 rather than just
install the regular Debian 8 updates? I'm running another test system
based on Stretch on bare metal, and I think there's something buggy in
one of the packages that was released recently (maybe X?) as it's been
locking up a lot for reason I can't figure out. I'm hoping I can just
wait it out and it'll fix itself later in another update. It could be
related to your problem if that's the case?

And I just realized there was more to the log that you attached. Still
can't figure out what caused the kernel panic from looking at it, sorry.


-- 
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/o2u50p%24br2%241%40blaine.gmane.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Unable to install qubes... (Intel GTX 970 problem)

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-12-15 04:00, r...@bluesentinel.net wrote:
> Hi Tim,
> 
> Drew White is correct.
> 
> This is an installer bug. There are two separate Qubes installers, 
> the GUI one and the Text one.  The problem is that the Text one
> has different options and has a fixed error that cannot be
> bypassed. The error is that LUKS encryption, either cannot be
> disabled or there is no error checking and no way to enter the
> encryption key.
> 
> Until this menu installer bug is fixed, those of us (a lot) with 
> Nvidia cards cannot even install Qubes.
> 
> If you have not installed Qubes via the Text menu, you will not 
> know what myself, Drew or Sergio are talking about.
> 

Since the installer is largely derived from Fedora, has anyone tested
whether this problem also exists on baremetal Fedora for the affected
hardware? (Perhaps this has been addressed in another thread?)

If it's actually an upstream (Fedora) problem, it should be reported
to them.

> The Qubes installation guide is next to useless, as the only line 
> in the "guide" is... Before proceeding with the installation, you 
> are encouraged to first read all the information on this page.
> When you’re ready, boot your system from the installation source
> and follow the on-screen instructions. The installer is very simple
> and asks very few questions. (It’s actually easier to install
> Qubes right now than most other Linux distributions!)
> 

It seems to me that this part of the guide is clearly targeted at
people using the GUI installer (the majority of users). So, while it
might be true that the guide is "useless" for people who are forced to
fall back on the text installer (insofar as it doesn't address that
installer), it would be inaccurate to call it useless overall.

> Also, it does not look like there is much active development with 
> Qubes, as this thread is over a year old and still no solution.
> 

It does not logically follow from the fact that this particular issue
has not been resolved that there has not been much active development
with Qubes. Anyone who takes a glance at GitHub can see that the
developers have actively been working on Qubes this entire time. Even
those who only pay attention to new releases can see that there have
been two releases since this thread was started.

I understand that it can be frustrating to have a problem for a long
period of time without finding a solution, but to say something that
one knows is untrue as a way of venting that frustration is rather
transparent.

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

iQIcBAEBCgAGBQJYUpVkAAoJENtN07w5UDAw78YQAM8v0Ve8bu/H+ZrazcPZX6O/
g1tUL10Y37/sQlBn3FQOnTb+U7tu/vzqoMMrtyoAvExZg6f+f+AjSrqHFVBJba5R
Osa6KmHPboAOKiaLfgs18sAs94zPYGJ6Wvl2LtXpWG5yCefeiKLTIs/MDZvBz/kA
eSYf+8Nagm14Z/cvLF5uzPscB7IIP8mo1qDG0lSObcY2NzPNYTT1/O1vTNXxn2n9
ZRhnvIEzbqy6/i/gO6J1vKpQ2UVga//Zw/rW9vXJHYnJZzGa+49LROBX4Ydy3xI8
dZXhdGc5R3G/Tq0JEQCrWbY81NaeleZW11zCpa5kHz3CVifoefPmskj9CKyrMiXT
jTJIIMnZO7jEKzvZYdfWbmz5cS3mJGdU9q428+asScwU8cfCAYlyW0TL5czjlGY/
G+yyqXtmE/aeAfDabAEoA5bwdP6iLoaf3NlpjzNVBoIsfmuLQ+LEJvONpQBHEpWJ
UbC8SzD2Eevc0H3Zb8sX4Ir/HEQI1o7KJB8rHVJlk6Hx0winbYTc1Z7d4bsgYn7J
jZGjG4om54ENrp7fI4nrrfhgcSkid5Vj2gEzUfnXt6+a8FN+QcLE7gy42I6dSUFZ
VhAzt98Rak3O600uoHZWY8hn/+myEpXFm47MeCvMFsefyfwYZAJr4XoMikc/n2za
OrKotnJboQv/Ts/aZzvK
=1Pwa
-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/708d2027-3a34-2f10-f8f1-715470a1f90d%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: FYI: Experimental Qubes coldkernel support now available

[Reg Tiangha]

On 12/15/2016 05:00 AM, Foppe de Haan wrote:
> Okay, stuck again. Downloaded a fresh d8 template, updated it and built 
> kernel again to have a clean slate to work from. Everything builds, no error 
> beside the expected ones afterwards. But when i switch to pvgrub2 and boot, 
> it shuts down seconds after boot attempt. Full log attached.
>
> ..[30m.[47mWelcome to GRUB!
>
>
> ..[37m.[40m.[37m.[40m.[37m.[40merror: no such device: 
> /boot/xen/pvboot-x86_64.elf.
>
> Reading (xen/xvda/boot/grub/grub.cfg
>
> ..[H.[J.[1;1Herror: file `/boot/grub/fonts/unicode.pf2' not found.
>
> error: no suitable video mode found.
>

I can't replicate, but none of my systems have UEFI or if they do, I'm
using legacy boot because Qubes wouldn't install if UEFI mode was enabled.

That said, if it worked for you before, it should still work now.

Are you sure you set up grub correctly after the compile?

sudo mkdir /boot/grub
sudo update-grub2

The only other thing I can think of is to switch to a regular kernel,
try the two grub commands again and see if any errors pop up, and if
not, switch back to pvgrub2 and see if it boots again.


-- 
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/o2u46r%24fck%241%40blaine.gmane.org.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Qubes 3.2 install stuck at LUKS encryption (Text based install)

[Rob]

Hi all,

Has anyone managed to work out how to get past the Text based LUKS installer 
bug?

Thanks,

Rob.

-- 
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/3a9855a5-5c60-4030-bf42-fdc9cb481ba6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: FYI: Experimental Qubes coldkernel support now available

[Foppe de Haan]

Okay, stuck again. Downloaded a fresh d8 template, updated it and built kernel 
again to have a clean slate to work from. Everything builds, no error beside 
the expected ones afterwards. But when i switch to pvgrub2 and boot, it shuts 
down seconds after boot attempt. Full log attached.

.[30m.[47mWelcome to GRUB!


.[37m.[40m.[37m.[40m.[37m.[40merror: no such device: 
/boot/xen/pvboot-x86_64.elf.

Reading (xen/xvda/boot/grub/grub.cfg

.[H.[J.[1;1Herror: file `/boot/grub/fonts/unicode.pf2' not found.

error: no suitable video mode found.

-- 
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/4af25603-980d-414b-94dd-59e71f4468e2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
.[30m.[47mWelcome to GRUB!


.[37m.[40m.[37m.[40m.[37m.[40merror: no such device: 
/boot/xen/pvboot-x86_64.elf.

Reading (xen/xvda/boot/grub/grub.cfg

.[H.[J.[1;1Herror: file `/boot/grub/fonts/unicode.pf2' not found.

error: no suitable video mode found.

.[3;36H  [ grub.cfg  4.09KiB  100%  3.66KiB/s 
].[3;1H.[?25l.[37m.[40m.[H.[J.[1;1H.[2;27HGNU GRUB  version 2.02~beta2


.[36m.[44m.[4;2H++.[5;2H|.[5;79H|.[6;2H|.[6;79H|.[7;2H|.[7;79H|.[8;2H|.[8;79H|.[9;2H|.[9;79H|.[10;2H|.[10;79H|.[11;2H|.[11;79H|.[12;2H|.[12;79H|.[13;2H|.[13;79H|.[14;2H|.[14;79H|.[15;2H|.[15;79H|.[16;2H++.[36m.[44m.[17;2H.[18;2H.[37m.[40m
 Use the ^ and v keys to select which entry is highlighted.  

  Press enter to boot the selected OS, `e' to edit the commands   

  before booting or `c' for a command-line. ESC to return 

  previous menu.  
.[5;80H .[37m.[44m.[5;3H*GNU/Linux  
.[36m.[44m.[5;78H.[37m.[40m.[36m.[44m.[6;3H Advanced 
options for GNU/Linux 
.[36m.[44m.[6;78H.[37m.[40m.[36m.[44m.[7;3H 
   
.[36m.[44m.[7;78H.[37m.[40m.[36m.[44m.[8;3H 
   
.[36m.[44m.[8;78H.[37m.[40m.[36m.[44m.[9;3H 
   
.[36m.[44m.[9;78H.[37m.[40m.[36m.[44m.[10;3H

.[36m.[44m.[10;78H.[37m.[40m.[36m.[44m.[11;3H   
 
.[36m.[44m.[11;78H.[37m.[40m.[36m.[44m.[12;3H   
 
.[36m.[44m.[12;78H.[37m.[40m.[36m.[44m.[13;3H   
 
.[36m.[44m.[13;78H.[37m.[40m.[36m.[44m.[14;3H   
 
.[36m.[44m.[14;78H.[37m.[40m.[36m.[44m.[15;3H   
 .[36m.[44m.[15;78H.[37m.[40m.[15;80H 
.[5;78H.[22;1H   The highlighted entry will be executed automatically in 5s.
 .[5;78H.[22;1H   The highlighted entry will be executed 
automatically in 4s. .[5;78H.[22;1H   The highlighted entry 
will be executed automatically in 3s. .[5;78H.[22;1H   The 
highlighted entry will be executed automatically in 2s. 
.[5;78H.[22;1H   The highlighted entry will be executed automatically in 1s.
 .[5;78H.[22;1H   The highlighted entry will be executed 
automatically in 0s. .[5;78H.[?25h.[H.[J.[1;1H.[H.[J.[1;1H  
Booting `GNU/Linux'


Loading Linux 4.8.13-coldkernel-grsec-1 ...

.[4;25H  [ vmlinuz-4.8.13-coldk  2.33MiB  63%  1.46MiB/s ].[4;1HLoading 
initial ramdisk ...

.[5;24H  [ initrd.img-4.8.13-co  10.79MiB  64%  6.49MiB/s ].[5;1H.[5;22H
  [ initrd.img-4.8.13-co  16.67MiB  100%  11.05MiB/s ].[5;1H[0.00] 
Linux version 4.8.13-coldkernel-grsec-1 (root@debian-8) (gcc version 4.9.2 
(Debian 4.9.2-10) ) #1 SMP Thu Dec 15 11:33:07 CET 2016
[0.00] Command line: root=/dev/mapper/dmroot ro
[0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point 
registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[0.00] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, 
using 'standard' format.

[qubes-users] Re: Unable to install qubes... (Intel GTX 970 problem)

[rob]

Hi Tim,

Drew White is correct.

This is an installer bug. 
There are two separate Qubes installers, the GUI one and the Text one.  The 
problem is that the Text one has different options and has a fixed error that 
cannot be bypassed.  The error is that LUKS encryption, either cannot be 
disabled or there is no error checking and no way to enter the encryption key.

Until this menu installer bug is fixed, those of us (a lot) with Nvidia cards 
cannot even install Qubes.

If you have not installed Qubes via the Text menu, you will not know what 
myself, Drew or Sergio are talking about.

The Qubes installation guide is next to useless, as the only line in the 
"guide" is...
Before proceeding with the installation, you are encouraged to first read all 
the information on this page. When you’re ready, boot your system from the 
installation source and follow the on-screen instructions. The installer is 
very simple and asks very few questions. (It’s actually easier to install Qubes 
right now than most other Linux distributions!)

Also, it does not look like there is much active development with Qubes, as 
this thread is over a year old and still no solution.

I will keep trying!  - I'll post again if I find workaround to the bug.

Thanks,

Rob.

-- 
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/ac941165-d47f-42df-9b43-21628ffd2ad3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] qvm-create-default-dvm running out of space

[Marek Marczykowski-Górecki]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Thu, Dec 15, 2016 at 03:01:09AM -0800, Andrew David Wong wrote:
> On 2016-12-15 01:40, Joonas Lehtonen wrote:
> > Hi,
> > 
> > when trying to recreate  the dvm after the latest torbrowser update I get:
> > 
> > qvm-create-default-dvm whonix-ws
> > 
> > [...]
> > DVM savefile created successfully.
> > cp: error writing '/dev/shm/qubes/current-savefile': No space left on device
> > 
> > 
> > And DVM starting fails after that obviously.
> > 
> > Do I have to resize /tmp to work around that problem? (2GB by default)
> > 
> > thanks,
> > Joonas
> > 
> 
> I haven't encountered this before, but it sounds like the Tor Browser
> update might've pushed you over the default 2 GB size limit. Maybe try
> increasing the size of your DVM template?

Storing savefile in /dev/shm (tmpfs - stored in RAM only) is an
optimization to load it faster. Normally this file takes about
300-400MB, so should be well below 2GB limit... It's size depends on
memory amount used in DispVM. 

First I'd check what other files you have there and in /tmp - maybe some
old unused stuff. But if it still does not fit, you can disable this
optimization by:

touch /var/lib/qubes/dvmdata/dont-use-shm

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

iQEcBAEBCAAGBQJYUn+LAAoJENuP0xzK19csJ7gH/1zI/imHn7Jdg1l7VcZTOp0s
oP4pkYH+/gqPFqsuy58QMWpt68CVR0q2pGO8YFq+1BQ3fceO+WlKRav5xt7vdfHE
eD11kjVQEPS48teH7GyC5fWY6GaaF8FuVLFRP0KaE5UNhV0P0dlR7JrPwWPN0lS7
CE6a/ZTXldbhv0xAsyR7ktbjHsRRXqCNVBoN/TVvu2kX3sn8qJ8ItIL0NqOpUjGS
dlxso0hT6/RLObtOPJyL0FyycxtJm7Zwq17Mwp52HktXzuiHKJsfwoORDDekhUCW
L+Sis17rNwtFoI4qyVdp3BgyMddfjwkdXKYiVnEe525E3L29ArhtqKXAFdGUTJQ=
=pshu
-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/20161215113330.GK1239%40mail-itl.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] qvm-create-default-dvm running out of space

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-12-15 01:40, Joonas Lehtonen wrote:
> Hi,
> 
> when trying to recreate  the dvm after the latest torbrowser update I get:
> 
> qvm-create-default-dvm whonix-ws
> 
> [...]
> DVM savefile created successfully.
> cp: error writing '/dev/shm/qubes/current-savefile': No space left on device
> 
> 
> And DVM starting fails after that obviously.
> 
> Do I have to resize /tmp to work around that problem? (2GB by default)
> 
> thanks,
> Joonas
> 

I haven't encountered this before, but it sounds like the Tor Browser
update might've pushed you over the default 2 GB size limit. Maybe try
increasing the size of your DVM template?

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

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJYUnfxAAoJENtN07w5UDAw8DUP/iJfAONCJSs5/0z1fRkyNeFp
9CO6gyiw04GbFxjztN+adBBHo2e8I2ErHXceMBD22Uoc7FOpmcwfVxnZcybezRtj
Ti+5YxBtTFAYmd5zuk1B5TjiCY/nV7KrfNUBZBQGNu0X6JDX3xg2yd5l5+9OYvVm
n5oI65MhpnSRVSznA3WJ2jk+joArCaxgmRU3jlQAinNdsQb/EUYolEAyFA4WF7M2
MZFaOpNoAEAdg7/mtIP6rFuI34CcXuhajyowIpqoI+xqBdJvwH5uCFcIp4FTZc4N
xwxV3inI9k192uF8FQ+36+p+bftQPOc1RJGWOKfNX+rrlKcQDazC14CHCG8LwR6X
gPvpdYAkV4g8DW/nMJlZcjy7C0OcM7Wh6gztRvi4/diOPNJWkGrYKWKfyCwqHx8t
Hx4EJ54n7CdGwkgMYUY+8bifUYiw/G+urFAtqNMHqsRWgbyDiBzdQMB+MiNDwpPf
U4Nf3hX2Z83jUSwhpNJ5Je3IWs241QytuOzozHXt+J4/9WziTgdtbrz34m/TdidV
0yeOLrxzit/V4TTFaswGTeoHiT/OaMoR6Epv46ab/XjG8TbI7T0qWTyfBj5AvF6G
hnKAbXWHpOnXIOLKEd6ZSooQwMDBVpwLeA04m7lNO7F+uwlv5BwZUQsbdim3b5Tm
uEAIkhjDL92PiZprsO0Y
=JO2K
-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/371dbe59-836d-0559-bac5-cc9d90082e6e%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] qvm-create-default-dvm running out of space

[Joonas Lehtonen]

Hi,

when trying to recreate  the dvm after the latest torbrowser update I get:

qvm-create-default-dvm whonix-ws

[...]
DVM savefile created successfully.
cp: error writing '/dev/shm/qubes/current-savefile': No space left on device


And DVM starting fails after that obviously.

Do I have to resize /tmp to work around that problem? (2GB by default)

thanks,
Joonas

-- 
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/ef15b350-f4ca-96cf-f66f-92f8f108564c%40openmailbox.org.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature