Re: [qubes-users] clock nightmare

[haaber]

On 24/01/2019 12.11 AM, haaber wrote:

Hello, could someone please help me out of the clock nightmare?
dom0 keeps setting itself at -1day, and helpless sys-whonix
follows, which disturbs tor, the time stamp of this email ETC.
Concrete question: in which timezone should live  respectively dom0
and whonix-* ? How/Where do I configure TZ without messing all up?
Thank you, Bernhard



Seen these?

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

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

TL;DR: In the TemplateVM on which sys-net is based:

$ sudo chmod 0700 /var/lib/private/


yes I saw it & did it:   ls -lah /var/lib/  gives

dwrx-  /var/lib/private


Yet, it does not help. Therefore I ask here ... cheers, Bernhard


I forgot to specify that I use fedora-28-minimal as net-vm (and
clock-vm). Is the problem in the "minimal" ?

--
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/65fb6b80-5d93-8ac0-d1de-64539c629e50%40web.de.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] clock nightmare

[haaber]

On 24/01/2019 12.11 AM, haaber wrote:

Hello, could someone please help me out of the clock nightmare?
dom0 keeps setting itself at -1day, and helpless sys-whonix
follows, which disturbs tor, the time stamp of this email ETC.
Concrete question: in which timezone should live  respectively dom0
and whonix-* ? How/Where do I configure TZ without messing all up?
Thank you, Bernhard



Seen these?

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

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

TL;DR: In the TemplateVM on which sys-net is based:

$ sudo chmod 0700 /var/lib/private/


yes I saw it & did it:   ls -lah /var/lib/  gives

dwrx-  /var/lib/private


Yet, it does not help. Therefore I ask here ... cheers, Bernhard

--
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/199b94eb-aa29-2d78-bfcf-e768f84b213b%40web.de.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] clock nightmare

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 24/01/2019 12.11 AM, haaber wrote:
> Hello, could someone please help me out of the clock nightmare?
> dom0 keeps setting itself at -1day, and helpless sys-whonix
> follows, which disturbs tor, the time stamp of this email ETC. 
> Concrete question: in which timezone should live  respectively dom0
> and whonix-* ? How/Where do I configure TZ without messing all up?
> Thank you, Bernhard
> 

Seen these?

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

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

TL;DR: In the TemplateVM on which sys-net is based:

$ sudo chmod 0700 /var/lib/private/

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

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlxKrQYACgkQ203TvDlQ
MDBaZRAAjf0K2pHsPKGNuerDvl6s+LVOAhAZhKJgaXKTbRFO/zthUUintmHBHuUR
LOzyyN6EXIPi3F1gYNJ1EMTMucQklVsmQaY7KGfPEUungyumXHWlRBPdvDZXsyN0
59Cp4GBwk5xi24PoJuyzHAw4kQYG+chApk8qrC5wL0Hhy5Y/U02rqJiv26/VjTjm
Mfs7gTRkoq21RubiBvibcCvaUyk3sfXKeejIcVlITBxWAooFTkD8WYyRGBZx46XE
AryJTypn/qFXrkvW+FINyc0muyXUPAtF4T3Em/ficx1X9n8rrEILrBR8MYWI1Rue
VLuZ4lWb+aqZpTzAPQQBIIUpMm2ATcJMERFeINDIKlXcH5i2n4uzeOwofb7GQJvs
NcuqTA4jFM1FIIkbkhYDOfO+kRx9yR7Rv+lX3KQ8g4/HdRocwiXwNNNujfnXwXwm
RXSLKhreNW4QC70aoYV4KbDA5bzy7SaUoCHN6K/uV3HoUPBFi2VAdNQQaaotXRDN
FNXoLYKTg28XouwvEOe6hhHGf9EFmC7vH/aooiRjpx1In9osZGSf8KTc1CbXa1MQ
4AqqOqInhe6e0BsEkDsnYrcehLE2sO/4UhvrgExLXArWSSTmYcaQvGP1+wrU868y
DUb4swHrLzUL1LQ+XuOuKJj+eJWOfHsg8mDzbKGBfqnajxP0Ue0=
=d6XS
-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/c4181b04-a972-7290-1078-6ac4143664ef%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] clock nightmare

[haaber]

Hello, could someone please help me out of the clock nightmare? dom0
keeps setting itself at -1day, and helpless sys-whonix follows, which
disturbs tor, the time stamp of this email ETC.
Concrete question: in which timezone should live  respectively dom0  and
whonix-* ? How/Where do I configure TZ without messing all up? Thank
you, Bernhard

--
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/c1320510-00e4-e7cf-f5d8-a28f38d6c3e0%40web.de.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Qubes 4.0.1 installer no grub menu

[gunnarmarino]

I can't get to the GRUB menu of the 4.0.1 installer, is there one? I can't 
successfully install qubes without it.

When I try to boot the installer from UEFI, some text appears at the top left 
of the screen and then it goes black. The text says: 
Xen 4.8.4 (c/s ) EFI loader 
Using configuration file 'BOOTX64.cfg'"

How do I get to the GRUB menu?

-- 
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/04e75094-a4c9-4a72-8037-1e57f080a8eb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Don't give focus to new windows in certain work-spaces

[Frozentime345]

I like when it automatically gives focus to new windows most of the 
time, but when Im entering passwords it's sometimes a pain. Any way to 
off the feature for just one workspace?


--
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/4d15cb1b-3e1f-560f-f601-5bf636080e4d%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: QSB #46: APT update mechanism vulnerability

[pixel fairy]

On Thursday, January 24, 2019 at 7:35:59 PM UTC-8, Andrew David Wong wrote:

> pixel fairy, please let us know of fully removing the old template first
> doesn't fix the problem.

thats what i ended up doing. i had to reinstall to delete them. then it worked. 

then, with whonix, sys-firewall was full. changed the templates system storage 
max size to 20G. that problems hit me a few times before, but i think this 
should fix it. dnf clean all was not enough, probably because of how much is 
installed in the template.
 
> >> Why would using
> >> qubes*testing instead fix whatever is causing that command to fail?
> >> Would that somehow force cache busting for some reason?
> > 
> > No. But it would be easier - no need to think in which repository given
> > template is. In this particular case, it should be fine as given
> > template is only in one of those repositories.
> > 
> 
> Sure, I can see it being easier. I'd specify it as
> `qubes-templates*testing` to be safe, though. Otherwise, user error
> could easily lead to pulling updates from `qubes-dom0-current-testing`
> that they didn't mean to get and aren't prepared to deal with.
> 
> >>> Also, using the 'upgrade' action is a lot less confusing. The official
> >>> steps are needlessly painful.
> > 
> >> Would it be worth updating the QSB? (CC: Marek)
> > 
> 
> PR: https://github.com/QubesOS/qubes-secpack/pull/26
> 
> - -- 
> Andrew David Wong (Axon)
> Community Manager, Qubes OS
> https://www.qubes-os.org
> 
> -BEGIN PGP SIGNATURE-
> 
> iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlxKhAcACgkQ203TvDlQ
> MDBmVQ//dSU4Jyi/Cg2m7+YkdGyjJB3W8TmS1HFDrGEFlVKsTl5WL8TSxjNPb0tS
> yHMRlOzDDA5POiTBPmLAPk6zwUDkiDSMt+DQ1GZ5b7NIxcnKNZjHM5EMOCzcCoW2
> 7DB/wYpp5AndG+3pHM8TWcCTOC7cSAqMxj5pgqUMnOOunG5Ic8nVnUEU1YdBSM51
> uPJuXeR7/sZ33eWUKN5QrRP/Yb4TLORYjouWR6tI60j8ReE7xyYre5TpTBnroIZE
> Aq4+IYBrjqqSZcBJRhqcshtgDF6A2/AUhLeZZpokA9eL7KDxCG2L1QVjiO6c6DhM
> ARc0SxsKhAOzxRUj1PqHQvtQCEhX5MvjkjgfwY7aDD9IGMmZU7/7+CR8QrilMICq
> p4dJQWyiMmvwyQS0xBJEPEkUuHO89CTZ7VNs8/S1jhPwyo6myDwekKhmAS7Nc/Iz
> G71YjwrV3+C7I31JiEEwe2y30RLncZdn9t+oySoCeznrvwtoK8cFzeJ9616As5Yz
> smXgoGKQmyKnRw7WIto1MuLbvVr8NUGzY7PWCOmPASDu2UAnWgkIn6aTrJd9KWPB
> 4TZHhu+YVHVahkqugZSQ8g7aoaJ/7aURERlURASz1yDEPsmbmLt+4oI4PZUpCjHC
> 2fpXTSCqOPK1GqX1Hyxi5EnldbBCyoMbU+LwikD+8k+zc02U/iY=
> =DiKo
> -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/7d5de408-2582-411a-934b-17dde3d5cc1d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] system-config-printer fails

[haaber]

Hi I start system-config-printer, find the network printer, provide a
ppd file, all fine. The last step "describe printer" will ignore me
clicking on "Apply" to finish. I can ony go back or cancel, so I am
stuck.  Some hints? Thanks

--
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/ca0ed539-6231-8183-0aa8-74b6f6babc6f%40web.de.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] post-apt-reinstall-issues sys-whonix not connecting to tor

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 24/01/2019 9.03 PM, Andrew David Wong wrote:
> On 24/01/2019 7.53 AM, qubes-...@tutanota.com wrote:
>> hi, I reinstalled successfully the whonix-ws-14, whonix-gw-14 and debian-9 
>> templates as described here: 
>> https://www.qubes-os.org/news/2019/01/23/qsb-46/ 
>> 
> 
>> With this kind of installation no sys-whonix is created by default. I 
>> created therefore a new AppVM named sys-whonix, based on template 
>> whonix-gw-14, NetVM set to sys-firewall. After running Connection Wizard it 
>> stops at 5% if connecting directly to Tor, or at 10% if connecting with 
>> Bridges. It stops in the bootstrap phase connecting to a relay directory. 
>> Whonix check say gave up waiting. In the Arm it keeps popping up duplicates 
>> hidden. 
>> After few moments it tells me (when using bridges): [WARN] Proxy Client: 
>> unable to connect to IP-address:443 "general SOCKS server failure" . 
> 
>> Is there any setting in the original sys-whonix that is missing if the 
>> sys-whonix I just created manually? 
>> What is the solution for this issue? 
>> I live in non-censored area, clearnet internet connection is working 
>> smoothly.
>> Thank you!
> 
> 
> The correct way to (re)create sys-whonix is:
> 
>   $ sudo qubesctl state.sls qvm.anon-whonix
> 
> For details, see: https://www.whonix.org/wiki/Qubes/Install
> 
> We neglected to include this in the QSB.
> 

PR: https://github.com/QubesOS/qubes-secpack/pull/26

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

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlxKhCkACgkQ203TvDlQ
MDAH0g/9EeSTQHx5WqS99WEbtAay4G1oYoyA/ES0VZG0BRdzWCNvQRsYgsytT6pR
0jPUXHopUZ9I+CBxc4FBq+UjcjsqdYkUEmU9tahbCXAcFGfSatc66k/kY94Z5G3Y
VZJUlxuDqLqYC+LqFdAcgmBy9a47hdmnoLWo6FzBR4uynyuK8CBV10cF8n3HSS78
tpqeH4TYEFwqAp11QBmIdo+k7D8zjO0T1S0FyJl9yxQx62igwjC5LbredCSQ34mp
MogR4ci4RPDEn2iRyNSFDDJHvQ4nqR9DMe/LXDCJhy56WBL+ynpySCdGnrKx764s
pK5Z+yC25VWXeJzkhmu2Lo3M2DYdLmd/9Qrkn8gCmIaloKRui5Y20X70RYTwvvdw
k2CBShPJtqAEcmOY3fKfpwa42re26eFXNp+flPnWAYxxdUOTZE2p534poZwp4h7x
KMM5+rofC0r7YP2QKY5+iZ3us7uUTCDUataZUQXWJ4iq3b8ZwckFCt+LleP3VD74
686Hes0iYVTuP2UdnTQGGbDNIgSE6J7CSMdr95DK5iDZjdefG+jgnd+rWPS3b8FQ
SY5bwDYefS3Sv7tL8InldAMgkrkxmJv3naaHpVvlJZ0/d3TxPEuXYgWylDpeTAzG
ZRoPV2ArLHQameUdIhwTELNAvjMeWw9CDEdMaxCcjidrzWgbgqE=
=c2zv
-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/9758ab25-c039-019a-5e77-c8765d0d1103%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: QSB #46: APT update mechanism vulnerability

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 24/01/2019 9.15 PM, Marek Marczykowski-Górecki wrote:
> On Thu, Jan 24, 2019 at 08:57:16PM -0600, Andrew David Wong wrote:
>> On 23/01/2019 11.54 PM, Chris Laprise wrote:
>>> On 01/23/2019 10:39 PM, Andrew David Wong wrote:
 On 23/01/2019 9.36 PM, pixel fairy wrote:
> On Wednesday, January 23, 2019 at 7:24:57 PM UTC-8, Andrew David Wong
> wrote:
>  
>> The Whonix packages are in qubes-templates-community-testing.
>
>
> $ sudo qubes-dom0-update
> --enablerepo=qubes-templates-community-testing
> qubes-template-whonix-gw-14
> Using sys-firewall as UpdateVM to download updates for Dom0; this may
> take some time...
> Last metadata expiration check: 1:08:18 ago on Wed Jan 23 18:22:56 2019.
> No match for argument: qubes-template-whonix-gw-14
> Error: Unable to find a match
>

 That's strange. I was just able to install them with the same command.
 Maybe try it again with --clean?
>>>
>>> That's why I found its better to just specify qubes*testing for the
>>> templates:
>>>
>>> https://groups.google.com/d/msgid/qubes-users/f4d997d5-7191-06d0-e7bb-ef42745a7db5%40posteo.net
>>>
> 
>> I don't understand. How would that help here? To recap, this command
>> worked for me:
> 
>> $ sudo qubes-dom0-update --enablerepo=qubes-templates-community-testing 
>> qubes-template-whonix-gw-14
> 
>> The very same command failed for pixel fairy. 
> 
> I think the issue is about the previous point in the patching
> instruction: remove buggy template version. Otherwise it will fail
> exactly like this (indeed the message is confusing...). Feature request
> about simplifying this process is tracked here:
> https://github.com/QubesOS/qubes-issues/issues/4518
> 

Oh, the old template is still installed? Ok, that makes sense.

pixel fairy, please let us know of fully removing the old template first
doesn't fix the problem.

>> Why would using
>> qubes*testing instead fix whatever is causing that command to fail?
>> Would that somehow force cache busting for some reason?
> 
> No. But it would be easier - no need to think in which repository given
> template is. In this particular case, it should be fine as given
> template is only in one of those repositories.
> 

Sure, I can see it being easier. I'd specify it as
`qubes-templates*testing` to be safe, though. Otherwise, user error
could easily lead to pulling updates from `qubes-dom0-current-testing`
that they didn't mean to get and aren't prepared to deal with.

>>> Also, using the 'upgrade' action is a lot less confusing. The official
>>> steps are needlessly painful.
> 
>> Would it be worth updating the QSB? (CC: Marek)
> 

PR: https://github.com/QubesOS/qubes-secpack/pull/26

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

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlxKhAcACgkQ203TvDlQ
MDBmVQ//dSU4Jyi/Cg2m7+YkdGyjJB3W8TmS1HFDrGEFlVKsTl5WL8TSxjNPb0tS
yHMRlOzDDA5POiTBPmLAPk6zwUDkiDSMt+DQ1GZ5b7NIxcnKNZjHM5EMOCzcCoW2
7DB/wYpp5AndG+3pHM8TWcCTOC7cSAqMxj5pgqUMnOOunG5Ic8nVnUEU1YdBSM51
uPJuXeR7/sZ33eWUKN5QrRP/Yb4TLORYjouWR6tI60j8ReE7xyYre5TpTBnroIZE
Aq4+IYBrjqqSZcBJRhqcshtgDF6A2/AUhLeZZpokA9eL7KDxCG2L1QVjiO6c6DhM
ARc0SxsKhAOzxRUj1PqHQvtQCEhX5MvjkjgfwY7aDD9IGMmZU7/7+CR8QrilMICq
p4dJQWyiMmvwyQS0xBJEPEkUuHO89CTZ7VNs8/S1jhPwyo6myDwekKhmAS7Nc/Iz
G71YjwrV3+C7I31JiEEwe2y30RLncZdn9t+oySoCeznrvwtoK8cFzeJ9616As5Yz
smXgoGKQmyKnRw7WIto1MuLbvVr8NUGzY7PWCOmPASDu2UAnWgkIn6aTrJd9KWPB
4TZHhu+YVHVahkqugZSQ8g7aoaJ/7aURERlURASz1yDEPsmbmLt+4oI4PZUpCjHC
2fpXTSCqOPK1GqX1Hyxi5EnldbBCyoMbU+LwikD+8k+zc02U/iY=
=DiKo
-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/cbbf08bc-841a-54e3-6a61-e0ca64131d7f%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: QSB #46: APT update mechanism vulnerability

[Marek Marczykowski-Górecki]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Thu, Jan 24, 2019 at 08:57:16PM -0600, Andrew David Wong wrote:
> On 23/01/2019 11.54 PM, Chris Laprise wrote:
> > On 01/23/2019 10:39 PM, Andrew David Wong wrote:
> >> On 23/01/2019 9.36 PM, pixel fairy wrote:
> >>> On Wednesday, January 23, 2019 at 7:24:57 PM UTC-8, Andrew David Wong
> >>> wrote:
> >>>  
>  The Whonix packages are in qubes-templates-community-testing.
> >>>
> >>>
> >>> $ sudo qubes-dom0-update
> >>> --enablerepo=qubes-templates-community-testing
> >>> qubes-template-whonix-gw-14
> >>> Using sys-firewall as UpdateVM to download updates for Dom0; this may
> >>> take some time...
> >>> Last metadata expiration check: 1:08:18 ago on Wed Jan 23 18:22:56 2019.
> >>> No match for argument: qubes-template-whonix-gw-14
> >>> Error: Unable to find a match
> >>>
> >>
> >> That's strange. I was just able to install them with the same command.
> >> Maybe try it again with --clean?
> > 
> > That's why I found its better to just specify qubes*testing for the
> > templates:
> > 
> > https://groups.google.com/d/msgid/qubes-users/f4d997d5-7191-06d0-e7bb-ef42745a7db5%40posteo.net
> > 
> 
> I don't understand. How would that help here? To recap, this command
> worked for me:
> 
> $ sudo qubes-dom0-update --enablerepo=qubes-templates-community-testing 
> qubes-template-whonix-gw-14
> 
> The very same command failed for pixel fairy. 

I think the issue is about the previous point in the patching
instruction: remove buggy template version. Otherwise it will fail
exactly like this (indeed the message is confusing...). Feature request
about simplifying this process is tracked here:
https://github.com/QubesOS/qubes-issues/issues/4518

> Why would using
> qubes*testing instead fix whatever is causing that command to fail?
> Would that somehow force cache busting for some reason?

No. But it would be easier - no need to think in which repository given
template is. In this particular case, it should be fine as given
template is only in one of those repositories.

> > Also, using the 'upgrade' action is a lot less confusing. The official
> > steps are needlessly painful.
> 
> Would it be worth updating the QSB? (CC: Marek)

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

iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlxKfzYACgkQ24/THMrX
1yy/RQf/aHFY61ViLRp9IRosZegJ/CybS5uioPxQf/GEy/d5JbkXMYEKWyTgyA7c
HsPB1z/HVfA+I7CRidrtKufr9jgeuE5KGrposFNxG/yCvzDh7nQaVF6svw3gozJw
pO4ULJ02zRg8YaJF+aBv25/p6jI7CQYs93OFZ0x0pVli4+BlkUY8gzhTgrf0V/bU
cpaC9UmzKfWR8TxR6gFTTmVqs5K+WxcBo3LfXF1yNoBlHCgJdhfK5kqmvANE5apS
gw5pM0ccsNYV//cmVr8fULAa05gRPRIQgepPUoj/442fGesfHDMVCm48pta/uhZ2
OPh0sBdqAgmlbRjrAGFi3a0b36ewww==
=7+Ci
-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/20190125031501.GD1429%40mail-itl.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: [qubes-devel] QSB #46: APT update mechanism vulnerability

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 23/01/2019 3.52 PM, Chris Laprise wrote:
> On 01/23/2019 12:05 PM, Marek Marczykowski-Górecki wrote:
> 
>> Patching
>> =
>>
>> If you are a Qubes user, you should remove all APT-based (including
>> Debian and Whonix) TemplateVMs and StandaloneVMs, then install fresh
>> ones. You can do this by performing the following steps on each such
>> TemplateVM:
> 
> 
> A shortened update procedure for debian-9:
> 
> 1. If your "debian-9" template is customized or contains data, you may
> wish to back it up with qvm-clone first...
> 
> [dom0]$ qvm-clone debian-9 d9-backup
> 
> 2. Run the upgrade command...
> 
> [dom0]$ sudo qubes-dom0-update qubes-template-debian-9 \
> --enablerepo=qubes*testing --action=upgrade
> 
> This will display package info as it begins downloading. The package
> version-date should begin with "4.0.1-20190123" or later.
> 

Will this step work with templates where installed_by_rpm = false?

> 3. Shutdown all VMs so the upgrade can take effect...
> 
> [dom0]$ qvm-shutdown --all --wait --timeout=30
> 
> This method also works with whonix-gw-14 and whonix-ws-14 templates.
> 

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

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlxKfqsACgkQ203TvDlQ
MDDe8xAAoEDmpIWBbhdeRUtQQsIbsKS/RexE8tRZoWgl68IIHMCL/SBsPU4aw4sl
lmp+AUXkiko3mMutWBP+AujscnF2V+rTuGAKRSBwf90qd0sHkL4MUq2jVhwELnOq
xT8N8vQOGBQckeTN9iqGw+6Yg4lrPSmB2evi/Ma7B7f5x9rfkk22tZNEB3oGDSyk
z6NCjxRWvNKHYi/h3UzGvfrFHJdMrC1s6gcd9+h+Tw9WOU5/ZkLqIGB1mDV9FKQF
EzwgU2zy1QiUaNEihjDghohqJOoxDPvqA3muil2qpReKLhqGkBrtpJGN8mjnjIdW
lmtUWipBOCFEgnrPfvPD9wbmwp64mc86qFDlTIskKHvZYjEMJV5ILw7w3s5hZTnk
KlAz6iAyW09E5JE1hQplZdpKAx+Z+Oc5mAdJzHI8j1ytKiHfk40nupyM07QCm/GR
iiXlZTYMRgsy5+s8SkBVhLFL9CLWWje7eH63TLQ5hwHm+rJTshjI3BycV5m+3fdv
StIvgg5u6LVXITkfSUxwOlOR1somjwddWB+zSVME6vAQJ7+LfBRqB/eD0mcSrmtQ
nhDHgyOfulu3IHjm3TbSLl5d8bqk2/GTTBsvsIfoKeo9eSdGO/+nuQb4G5AhqOJ2
bD0NWIQaMqNdhi7V3hzIYiYkh2fQVV0fSzHjmeUbqUShxt0IOfg=
=UuFd
-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/d2c553bf-709f-1ee8-b3e2-1a823a1856e2%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] post-apt-reinstall-issues sys-whonix not connecting to tor

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 24/01/2019 7.53 AM, qubes-...@tutanota.com wrote:
> hi, I reinstalled successfully the whonix-ws-14, whonix-gw-14 and debian-9 
> templates as described here: https://www.qubes-os.org/news/2019/01/23/qsb-46/ 
> 
> 
> With this kind of installation no sys-whonix is created by default. I created 
> therefore a new AppVM named sys-whonix, based on template whonix-gw-14, NetVM 
> set to sys-firewall. After running Connection Wizard it stops at 5% if 
> connecting directly to Tor, or at 10% if connecting with Bridges. It stops in 
> the bootstrap phase connecting to a relay directory. Whonix check say gave up 
> waiting. In the Arm it keeps popping up duplicates hidden. 
> After few moments it tells me (when using bridges): [WARN] Proxy Client: 
> unable to connect to IP-address:443 "general SOCKS server failure" . 
> 
> Is there any setting in the original sys-whonix that is missing if the 
> sys-whonix I just created manually? 
> What is the solution for this issue? 
> I live in non-censored area, clearnet internet connection is working smoothly.
> Thank you!
> 

The correct way to (re)create sys-whonix is:

  $ sudo qubesctl state.sls qvm.anon-whonix

For details, see: https://www.whonix.org/wiki/Qubes/Install

We neglected to include this in the QSB.

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

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlxKfF0ACgkQ203TvDlQ
MDCZjQ/+Oa//xX6mwYSo4v7xUEXVkFyMA7UNTOW4mqYa3bf5pUfhFhAu3M2qViJ0
L/wuD/AA1EvlPDw3toVQL+7Zo/irKdwZ0ZkIUcNyggpxqfujqGfIMo9t3Xvsi8n1
axGsRUDuevYLbAaeNyunpSInIzp3pwIE34GyrZ3NpLFrHa8/IFpe7sQLmTj8cnBK
UIcq1MhIQQJQfuWvUyJ76MTvS8Dal72vAqaGTTVIQWDqLXwMPYlyW8/s5eyc7vPi
sYiKS9lh7juknBqpFAstz0zZy8nzEBeZju7yiqEqKrm0ecTNqTv1ZDTGiqMgFjzq
2fMPGg81OSIWfnuudIw4Lmbr5uoqzjDZ0a20kqJ8yeSmKYLFcGkzVlRmF0A1P0TZ
WV6eDH+FSGzrANNHjP2Uuqk3Ce2sFm/gswzXscmIZH/6AgVhS1xJoEbP6/gfsXQ1
dSRL32f64CAxdpckvC9v8f9bugDZsN9NGzpgpMZwtGZHML6gGL88fjGvalH6iNMr
MeB2m3oTSteVPB0kHhmhHaZ8Unt+LvVNoTygUbeaZ053NFS2uFvVFmUlZwW9eS42
0j2PnREhTnfU5vyv4PRbNyEiPJXtW3jh4IJS6LkCoN9utlKwHtJdKJVjsqFusD9F
Lx7SNjjI+l2I8rBwTtEFGeRLmrU3/Ih1OONPwTEM0tNCcYLOON8=
=RY4C
-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/995fd88e-8937-3072-a837-f8a110168eeb%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: QSB #46: APT update mechanism vulnerability

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 23/01/2019 11.54 PM, Chris Laprise wrote:
> On 01/23/2019 10:39 PM, Andrew David Wong wrote:
>> On 23/01/2019 9.36 PM, pixel fairy wrote:
>>> On Wednesday, January 23, 2019 at 7:24:57 PM UTC-8, Andrew David Wong
>>> wrote:
>>>  
 The Whonix packages are in qubes-templates-community-testing.
>>>
>>>
>>> $ sudo qubes-dom0-update
>>> --enablerepo=qubes-templates-community-testing
>>> qubes-template-whonix-gw-14
>>> Using sys-firewall as UpdateVM to download updates for Dom0; this may
>>> take some time...
>>> Last metadata expiration check: 1:08:18 ago on Wed Jan 23 18:22:56 2019.
>>> No match for argument: qubes-template-whonix-gw-14
>>> Error: Unable to find a match
>>>
>>
>> That's strange. I was just able to install them with the same command.
>> Maybe try it again with --clean?
> 
> That's why I found its better to just specify qubes*testing for the
> templates:
> 
> https://groups.google.com/d/msgid/qubes-users/f4d997d5-7191-06d0-e7bb-ef42745a7db5%40posteo.net
> 

I don't understand. How would that help here? To recap, this command
worked for me:

$ sudo qubes-dom0-update --enablerepo=qubes-templates-community-testing 
qubes-template-whonix-gw-14

The very same command failed for pixel fairy. Why would using
qubes*testing instead fix whatever is causing that command to fail?
Would that somehow force cache busting for some reason?

> 
> Also, using the 'upgrade' action is a lot less confusing. The official
> steps are needlessly painful.
> 

Would it be worth updating the QSB? (CC: Marek)

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

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlxKev0ACgkQ203TvDlQ
MDBgmw/+IgsI5x0xAjdetKXzcdsOJUyeMd4ksZc0EWItQhQRN/ZD56KEODRQNryc
f1NkApyRi9WdH6PC+G2X5UiVXWNwx3Zu52J718qsWB1WkRnvQKlUvPI24uBXZH5x
f1f8L2OulK0dDikxSYTPSnRkPNQ+kmOyr0W50lJLbPufHH+tRhIKWCHIVdU45QXD
qpLnARlkNusH3uJA8lRmMZjhyg/ipsz6bM+z31n7Odf9M6sp+cD7mIgRCUqv4K20
3KbA+QWfREV67sgvgZ4NYFkGof/qJa4SF+rMbc0LOYbn9gzvnzNabLsQFHZhuCVk
DXyFGqXauLsF9ksmmyd2sskaiv3Y+mIiBXgL/F3Ks0AR8KsQZ+vJyIKnCG3o9doJ
brUucluIaPtDfD0fmSlRyHfM3XQOEuHHIOrkwY6QxfyBOpuMSPB2lAY1yfg9Er9z
NWbi8bcDknjiS9U1ZMih3Ox0bLthef/B3V1M6A4x3lINp5J/1aJ6VB7BwmkU6tON
2oBl0IY+KkrcA5eX3OkDt5ZRuo8syFDdB9CvHft1WKweL8FkQmhfOR2HDB52IRGr
YGSsd9m9V999dKs7zkPcExhdU3BNhK11aEp84ZX3S11NeXf2iqSZw6ORN3qi5Nf2
Y++BFwE3vjLnssWCTCj8YcI69C8jUoLaPmZkdEVIUqTvGQL9YEY=
=BVTN
-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/4f7f59e8-703b-fc85-888e-83aa21327035%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] fedora-26-dvm always shows updates pending, can't delete it.

[cooloutac]

did a -v and saw that it said metadata errors.

So sudo dnf clean metadata fixed the issue.

-- 
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/6b72124a-941a-46af-a5d9-1524aefbcd8d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: [qubes-devel] QSB #46: APT update mechanism vulnerability

[Fidel Ramos]

‐‐‐ Original Message ‐‐‐
On Wednesday, January 23, 2019 9:52 PM, Chris Laprise  wrote:

> On 01/23/2019 12:05 PM, Marek Marczykowski-Górecki wrote:
>
> > Patching
> >
> > =
> >
> > If you are a Qubes user, you should remove all APT-based (including
> > Debian and Whonix) TemplateVMs and StandaloneVMs, then install fresh
> > ones. You can do this by performing the following steps on each such
> > TemplateVM:
>
> A shortened update procedure for debian-9:
>
> 1.  If your "debian-9" template is customized or contains data, you may
> wish to back it up with qvm-clone first...
>
> [dom0]$ qvm-clone debian-9 d9-backup
>
> 2.  Run the upgrade command...
>
> [dom0]$ sudo qubes-dom0-update qubes-template-debian-9 \
> --enablerepo=qubes*testing --action=upgrade
>
> This will display package info as it begins downloading. The package
> version-date should begin with "4.0.1-20190123" or later.
>
> 3.  Shutdown all VMs so the upgrade can take effect...
>
> [dom0]$ qvm-shutdown --all --wait --timeout=30
>
> This method also works with whonix-gw-14 and whonix-ws-14 templates.

Also in case people don't know there is an easy procedure to store the list of 
installed packages from the old debian 9 template and reinstall the same 
packages in the fresh template:

https://unix.stackexchange.com/questions/176134/installing-packages-by-importing-the-list-with-dpkg-set-selections/177187#177187

I reproduce the steps here for convenience:

debian-9-old$ dpkg --get-selections > /tmp/dpkg_selections.txt
debian-9-old$ qvm-copy-to-vm debian-9 /tmp/dpkg_selections.txt

debian-9$ avail=`mktemp`
debian-9$ apt-cache dumpavail > "$avail"
debian-9$ dpkg --merge-avail "$avail"
debian-9$ rm -f "$avail"
debian-9$ sudo dpkg --set-selections < 
~/QubesIncoming/debian-9-old/dpkg-selections.txt
debian-9$ sudo apt-get dselect-upgrade

That should do the trick. Of course check dpkg-selections.txt, it's a simple 
text file.

Note that with this procedure the information of which packages have been 
installed manually and which automatically as a dependency is not kept. If you 
want to transfer this information use this procedure:

debian-9-old$ apt-mark showmanual > pkgs_manual.lst
debian-9-old$ apt-mark showauto > pkgs_auto.lst
debian-9-old$ qvm-copy-to-vm debian-9 pkgs_auto.lst pkgs_manual.lst

debian-9$ sudo apt-mark manual $(cat QubesIncoming/debian-9-old/pkgs_manual.lst)
debian-9$ sudo apt-mark auto $(cat QubesIncoming/debian-9-old/pkgs_auto.lst)

https://askubuntu.com/questions/101931/restoring-all-data-and-dependencies-from-dpkg-set-selections/108760#108760

Hope that's useful.

Fidel Ramos
PGP 7F07 1B7C 479F EDD1
https://www.fidelramos.net

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

Re: [qubes-users] Re: Making a Qubes USB Installer USB with Fedora LiveCD

[Alex Winter]

No I never got UEFI to work.  I ended up having to revert to legacy install
which worked flawlessly for me using rufus.

On Thu, Jan 24, 2019, 4:13 PM Aly Abdellatif  You can follow what I wrote for my installation !
>
>
> https://groups.google.com/forum/m/#!msg/qubes-users/5-qFYKN0esM/E07fmEHZHAAJ
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "qubes-users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/qubes-users/aYL3fQSNapU/unsubscribe.
> To unsubscribe from this group and all its topics, 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/35e25d4a-608e-4184-8d2d-d66e1e54f3e3%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/CAAX4w40yDGE_rSHs-WGxyxn8Nf%3DduaD9H-34ZYbUNn3oGf_KsQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Making a Qubes USB Installer USB with Fedora LiveCD

[Aly Abdellatif]

You can follow what I wrote for my installation !

https://groups.google.com/forum/m/#!msg/qubes-users/5-qFYKN0esM/E07fmEHZHAAJ

-- 
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/35e25d4a-608e-4184-8d2d-d66e1e54f3e3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Making a Qubes USB Installer USB with Fedora LiveCD

[Aly Abdellatif]

Hi everyone,

Don’t bother yourself with fedora-live-cd,I have a new thinkpad(p52) and I did 
the iso with rufus and it worked.
Fedora live cd and dd didn’t work for me !

Best regards
Aly Abdellatif

-- 
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/3e5a9f47-e23b-49cc-8c49-c237ab1ca109%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Making a Qubes USB Installer USB with Fedora LiveCD

[Jean Proesmans]

Le mercredi 16 janvier 2019 11:52:33 UTC-5, alex...@gmail.com a écrit :
> Hey, I am having an Issue putting a qubes 4.0.1-x86_64.iso image onto a Flash 
> Drive.  The laptop I am using is Lenovo X1 Carbon Gen 6.  I am using the 
> method described here https://www.qubes-os.org/doc/thinkpad-troubleshooting/. 
>  Here is my output of the command:
> 
> [liveuser@localhost ~]$ sudo livecd-iso-to-disk --format --efi 
> /run/media/liveuser/Windows/Users/Alex/Desktop/Qubes-R4.0.1-x86_64.iso 
> /dev/sdc
> Verifying image...
> /run/media/liveuser/Windows/Users/Alex/Desktop/Qubes-R4.0.1-x86_64.iso:   
> 9d20945f71a1e4066e742d95cfe61fb5
> Fragment sums: d8d4876194afaad8b914cbf9e342df1b73a1578abc8529e135e2b8f6a3fc
> Fragment count: 20
> Supported ISO: no
> Press [Esc] to abort check.
> Checking: 100.0%
> 
> The media check is complete, the result is: PASS.
> 
> It is OK to use this media.
> /Packages found, will copy source packages to target.
> 
> WARNING: This will DESTROY All DATA on: /dev/sdc !!
> 
> Press Enter to continue, or Ctrl C to abort.
> 
> Waiting for devices to settle...
> mkfs.fat 4.1 (2017-01-24)
> 
> Copying LiveOS image to target device...
> squashfs.img
> 411,631,616 100%  342.82MB/s0:00:01 (xfr#1, to-chk=0/1)
> 
> Syncing filesystem writes to disc.
> Please wait, this may take a while...
> Setting up /EFI/BOOT
> Unable to find an EFI configuration file.
> 
> I am using Fedora-Workstation-Live-x86_64-29-1.2.iso which I downloaded off 
> of there website and I used Fedora Media Creater to put it on the Flash 
> Drive.  Any Ideas as too why I am getting this error.

I've got exactly the same issue. Did you find a solution ?

-- 
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/df33d5bc-cbf2-4334-9022-4c04d71e0df2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] automatic start dropbox in VM

[marlluslustosa]

The only solution that solved my problem was to add the following line in this 
file '/home/user/.bash_profile':

sh ~/.dropbox-dist/dropboxd &

thanks a lot

-- 
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/cd5e3176-9473-4038-957b-091df97196bb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[SOLVED] Re: [qubes-users] ssh giving me locale error

[billollib]

Thanks everybody.  The problem was solved with setting the locale.  The only 
"trick" was that I kept banging on localectl, and it seemed to accept the 
command, but I kept getting the error and it didn't seem to "take"  -- until I 
rebooted.  Doh.

-- 
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/d4391029-4d7b-480b-9ef6-95e18ec0ee81%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Backup stops when the backup file reaches 3Gb

[Mike Keehan]

On Thu, 24 Jan 2019 11:27:00 -0500
Chris Laprise  wrote:

> On 01/24/2019 06:29 AM, unman wrote:
> > On Thu, Jan 24, 2019 at 01:00:15AM -0500, Chris Laprise wrote:  
> >> On 01/23/2019 08:15 PM, js...@bitmessage.ch wrote:  
> >>> Mike Keehan:  
>  Hi,
> 
>  I'm using Qubes Backup to save some of my qubes into another VM.
>  The backup VM has 18 Gb of storage available, but whenever the
>  backup file reaches 3Gb, the backup process just hangs.
> 
>  No CPU usage, no error messages, just stops.  The backup window
>  shows 40% complete, but never moves any further (different % for
>  different combinations of qubes in the backup list).
> 
>  After waiting a considerable time (well, 5-10 minutes), hitting
>  Cancel in the backup window does cancel it.  The rest of the
>  system is continuing to work without problem.  Happens every
>  time I try to use Qubes backup.
> 
>  The Qubes Disk Space widget shows less than 50% disk used
>  overall, the backupVM shows only 18% disk used when the 3Gb file
>  has been saved.
> 
>  I'm stumped.
> 
>  Mike.  
> >>>
> >>> Hi,
> >>>
> >>> You may have to wait longer than 5-10 minutes. I experience
> >>> something similar when doing a full backup, except it's worse
> >>> because i'm backing up like 2.5TB. It appears to hang for several
> >>> hours at a time (and this happens more than once), but it does
> >>> eventually make visible progress again. The whole process takes
> >>> over 24 hours. This is why i do full backups very infrequently.
> >>>
> >>> For you it shouldn't take nearly as long because it's a lot less
> >>> data, but the progress appearing to hang for a while seems to be
> >>> normal.
> >>>
> >>> I'm using 3.2 tho, and i know they made changes to the backup
> >>> mechanism under the hood in 4.0, so i'm not sure if this issue
> >>> still applies in 4.0.  
> >>
> >> Marek,
> >>
> >> Isn't this the null bytes bug in GNU tar?
> >>
> >> https://groups.google.com/d/msgid/qubes-users/f4d997d5-7191-06d0-e7bb-ef42745a7db5%40posteo.net
> >>
> >> It would be a good idea to update this in dom0. My own backup tool
> >> uses GNU tar as well.
> >>
> >> -- 
> >>
> >> Chris Laprise, tas...@posteo.net
> >> https://github.com/tasket
> >> https://twitter.com/ttaskett
> >> PGP: BEE2 20C5 356E 764A 73EB  4AB3 1DC4 D106 F07F 1886  
> > 
> > It seems a little early to judge.
> > 
> > Mike - it looks from your comment as if you have been trying with
> > subsets of the qubes? Can you confirm if these are running or
> > stopped.
> > 
> > Like jsnow, I'm regularly able to backup far more than 3G without
> > issue, so it looks as if there's something particular about this
> > scenario. It would be helpful if you could confirm the issue when
> > all qubes you are backing up are stopped.
> > Then try bisecting the qubes backup group - keep bisecting if you
> > hit the problem again until you either find the problematic qubes
> > or have backed them all up.
> >   
> 
> Oops, I pasted the wrong link. Here is the correct one:
> 
> https://utcc.utoronto.ca/~cks/space/blog/sysadmin/TarFindingTruncateBug
> 
> The symptoms sound remarkably the same... potentially hours-long
> delays with no adverse effect on data. Trigger condition is not about
> size, but due to corner cases that involve backing up nulls.
> 

I left a backup running before I left home this morning - it was stuck
at 1.8Gb then (confirming that size is not the issue), and it was still
at 1.8Gb when I got home this evening.  That was about 8 hours or so.

I have a recollection from my dim and distant past, that I had a similar
stuck tar issue when it could not handle fifos.  Not Linux in those
days.  There is no mention of fifos (or sockets etc.) in the tar
manpage, so I don't know if gnu tar is supposed to handle them or not.
I had to use cpio to backup systems which contained those things.

Anyway, I'll investigate further tomorrow.  You have given me a number
of things to look into.  Thanks,

Mike.

-- 
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/20190124193856.01f80d02.mike%40keehan.net.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: QSB #46: APT update mechanism vulnerability

[Lorenzo Lamas]

On Thursday, January 24, 2019 at 4:13:36 PM UTC+1, Lorenzo Lamas wrote:
> Please help, after updating dom0 with security-testing(which installed not 
> only qubes-desktop-linux-manager and qubes-manager, but also 
> qubes-mgmt-salt-dom0-update-4.0.5-1 and reboot, no VM at all will start.
> Failed to connect to qmmemman:[Errno 2] No such file or directory.
> Text boot shows:
> Failed to start Qubes memory management daemon.
> 
> systemctl status qubes-qmemman.service shows:
> "qubes-qmemman.service - Qubes memory management daemon
> Loaded: loaded (/usr/lib/systemd/system/qubes-qmemman.service; enabled; 
> vendor preset: enabled)
> Active: failed (Result: exit code) since Thu 2019-01-24 15:41:40 CET; 1min 1s 
> ago
> Proces: 2094 ExecStart=/usr/bin/qmemmand (code=exited, status=1/FAILURE]
> Main PID: 2094 (code-exited, status=1/FAILURE)
> 
> Jan 24 15:41:40 dom0 qmemmand[2094]: sys.exit(main())
> Jan 24 15:41:40 dom0 qmemmand[2094]: File 
> "/usr/lib/python3.5/site-packages/qubes/tools/qmemmand.py", line 261, in main
> Jan 24 15:41:40 dom0 
> qmemmand[2094]:qubes.utils.parse_size(config.get('global', vm-min-mem'))
> Jan 24 15:41:40 dom0 qmemmand[2094]: File 
> "/usr/lib/python3.5/site-packages/qubes/utils.py", line 107, in parse_size
> Jan 24 15:41:40 dom0 qmemmand[2094]: raise qubes.exc.QubesException("Invalid 
> size: {0}.".format(size))
> Jan 24 15:41:40 dom0 qmemmand[2094]: qubes.exc.QubesException: Invalid size 
> 190MIB.
> Jan 24 15:41:40 dom0 systemd[1]: qubes-qmemman.service: Main proces exited, 
> code-exited, status=1/FAILURE
> Jan 24 15:41:40 dom0 systemd[1]: Failed to start Qubes memory management 
> daemon.
> Jan 24 15:41:40 dom0 systemd[1]: qubes-qmemman.service: Unit entered failed 
> state.
> Jan 24 15:41:40 dom0 systemd[1]: qubes-qmemman.service: Failed with result 
> 'exit-code'.
> 
> I tried to undo the update with dnf history undo but it says the package is 
> not available.

Well, thanks to the help of someone more knowledgeable than me, I was able to 
fix it.
The trick was to edit /etc/qubes/qmemman.conf.
In the line vm-min-mem = 190MIB replace with 190M
In the line dom0-mem-boost = 333MIB replace with 333M.
Maybe a typo in one of the patches?

-- 
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/7ca4c96e-4499-4837-9090-7639891ea82b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Backup stops when the backup file reaches 3Gb

[Mike Keehan]

On Thu, 24 Jan 2019 11:27:00 -0500
Chris Laprise  wrote:

> On 01/24/2019 06:29 AM, unman wrote:
> > On Thu, Jan 24, 2019 at 01:00:15AM -0500, Chris Laprise wrote:  
> >> On 01/23/2019 08:15 PM, js...@bitmessage.ch wrote:  
> >>> Mike Keehan:  
>  Hi,
> 
>  I'm using Qubes Backup to save some of my qubes into another VM.
>  The backup VM has 18 Gb of storage available, but whenever the
>  backup file reaches 3Gb, the backup process just hangs.
> 
>  No CPU usage, no error messages, just stops.  The backup window
>  shows 40% complete, but never moves any further (different % for
>  different combinations of qubes in the backup list).
> 
>  After waiting a considerable time (well, 5-10 minutes), hitting
>  Cancel in the backup window does cancel it.  The rest of the
>  system is continuing to work without problem.  Happens every
>  time I try to use Qubes backup.
> 
>  The Qubes Disk Space widget shows less than 50% disk used
>  overall, the backupVM shows only 18% disk used when the 3Gb file
>  has been saved.
> 
>  I'm stumped.
> 
>  Mike.  
> >>>
> >>> Hi,
> >>>
> >>> You may have to wait longer than 5-10 minutes. I experience
> >>> something similar when doing a full backup, except it's worse
> >>> because i'm backing up like 2.5TB. It appears to hang for several
> >>> hours at a time (and this happens more than once), but it does
> >>> eventually make visible progress again. The whole process takes
> >>> over 24 hours. This is why i do full backups very infrequently.
> >>>
> >>> For you it shouldn't take nearly as long because it's a lot less
> >>> data, but the progress appearing to hang for a while seems to be
> >>> normal.
> >>>
> >>> I'm using 3.2 tho, and i know they made changes to the backup
> >>> mechanism under the hood in 4.0, so i'm not sure if this issue
> >>> still applies in 4.0.  
> >>
> >> Marek,
> >>
> >> Isn't this the null bytes bug in GNU tar?
> >>
> >> https://groups.google.com/d/msgid/qubes-users/f4d997d5-7191-06d0-e7bb-ef42745a7db5%40posteo.net
> >>
> >> It would be a good idea to update this in dom0. My own backup tool
> >> uses GNU tar as well.
> >>
> >> -- 
> >>
> >> Chris Laprise, tas...@posteo.net
> >> https://github.com/tasket
> >> https://twitter.com/ttaskett
> >> PGP: BEE2 20C5 356E 764A 73EB  4AB3 1DC4 D106 F07F 1886  
> > 
> > It seems a little early to judge.
> > 
> > Mike - it looks from your comment as if you have been trying with
> > subsets of the qubes? Can you confirm if these are running or
> > stopped.
> > 
> > Like jsnow, I'm regularly able to backup far more than 3G without
> > issue, so it looks as if there's something particular about this
> > scenario. It would be helpful if you could confirm the issue when
> > all qubes you are backing up are stopped.
> > Then try bisecting the qubes backup group - keep bisecting if you
> > hit the problem again until you either find the problematic qubes
> > or have backed them all up.
> >   
> 
> Oops, I pasted the wrong link. Here is the correct one:
> 
> https://utcc.utoronto.ca/~cks/space/blog/sysadmin/TarFindingTruncateBug
> 
> The symptoms sound remarkably the same... potentially hours-long
> delays with no adverse effect on data. Trigger condition is not about
> size, but due to corner cases that involve backing up nulls.
> 

Thanks to all of you !!

I've been out today, but will have a look at tracking down the culprit
tomorrow:)

Mike.

-- 
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/20190124184812.24128610.mike%40keehan.net.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: XScreenSaver for dom0 pops up

[Pete Howell]

Thanks Opal!  Disabling the Compositor definitely fixes this issue.

On Monday, February 27, 2017 at 5:10:57 PM UTC-7, Opal Raava wrote:
> On Monday, February 27, 2017 at 9:41:20 PM UTC+1, ianr...@gmail.com wrote:
> > On Wednesday, October 26, 2016 at 8:43:12 AM UTC-4, John Maher wrote:
> > > I'm getting the strangest thing on my screen. I'll be working and the 
> > > XScreenSaver dialog pops up (indicating the screen is locked) and the 
> > > screen goes black. However, the screen is not locked. I have to move a 
> > > window around to redraw my screen. This has always happened since I 
> > > started using Qubes about 3 weeks ago. There appears to be no pattern 
> > > that prompts this response. Bizarre! Any thoughts?
> > > 
> > > Thanks.
> > > 
> > > John
> > 
> > I found that this happened when I had the Qubes VM Manager set to appear on 
> > all desktops ("Always on Visible Worksace").  When I stopped that, it 
> > stopped the problem.  Tried this 5 or 6 times on 2 different machines.  
> > Running v.3.2 with and without Feb. updates; no difference.
> > 
> > HTH,
> > 
> > --Ian
> 
> Oh that's interesting, I found that disabling the compositor (Menu>System 
> Tools>Window Manager Tweaks>Compositor) solves the problem for me and also 
> for somebody else on the github tracker entry. 
> 
> I can't find the 'always on visible workspaces' settings, but I also lost the 
> tray icon for the Qubes VM Manager somehow.

-- 
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/1471dbfd-ea56-478f-ad82-c5713abfbd0d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Qubes 4.0.x - Linux kernel 4.19.15 package available in testing repository

[Patrik Hagara]

On 1/20/19 1:57 AM, Marek Marczykowski-Górecki wrote:
> Hi all,
> 
> There is updated "kernel" package available in current-testing
> repository - it's a Linux long term support 4.19.x series, as an update
> over 4.14.x before. Since the upgrade switches to the next major LTS
> branch, I'll keep it in current-testing repository longer than usual 1-2
> weeks. This also applies to kernel package for VMs: kernel-qubes-vm.
> Please report new issues the usual way, at qubes-issues[1], or
> simply by replying here. In either case, please mark it clearly it
> happens after updating to 4.19, preferably including a link to the
> update:
> https://github.com/QubesOS/updates-status/issues/850
> 
> 4.19.x kernel was already available as kernel-latest package for some
> time. Users of kernel-latest will see the update to 4.19.15 too, but
> kernel-latest soon will carry 4.20.x kernel version.
> 
> [1] https://github.com/QubesOS/qubes-issues/issues
> 
> 

I get weird graphical artifacts with the new kernel after ~an hour of
usage. Windows from AppVMs turn all white sometimes when switching
workspaces in i3wm. Events like mousing over an interactive table rows
in a browser (when the current row gets highlighted) return that
particular section of the window back to normal (but not the whole
window, for that I need to trigger a repaint of the whole window by eg.
making it full-screen and immediately switching back to non-full-screen).

Haven't had to time to debug this issue yet, will look closer over the
next weekend or two. For now I've reverted to using the old kernel from
stable repo and the issue went away.

Cheers,
Patrik

-- 
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/8f187918-75d0-abd0-d068-e8336511c374%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] ssh giving me locale error

[unman]

On Thu, Jan 24, 2019 at 03:25:49PM +0100, Zrubi wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> On 1/24/19 3:00 PM, unman wrote:
> 
> > I think you have a locale set in the qube whihc cannot be generated
> > on the server. Can you check this by looking at locale settings in
> > both.
> > 
> 
> I think the problem is that there is NO locale set in the default
> template.
> 
> You can check this by the localectl command.
> 
> As this is used in a lot of place, it is wise to correct it by setting
> a valid locale in a template.
> 
> - -- 
> Zrubi

really? There is in debian templates, even minimal.
Let's see what OP reports.
In any case, the resolution would be the same.

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

Re: [qubes-users] Backup stops when the backup file reaches 3Gb

[Chris Laprise]

On 01/24/2019 06:29 AM, unman wrote:

On Thu, Jan 24, 2019 at 01:00:15AM -0500, Chris Laprise wrote:

On 01/23/2019 08:15 PM, js...@bitmessage.ch wrote:

Mike Keehan:

Hi,

I'm using Qubes Backup to save some of my qubes into another VM.
The backup VM has 18 Gb of storage available, but whenever the
backup file reaches 3Gb, the backup process just hangs.

No CPU usage, no error messages, just stops.  The backup window
shows 40% complete, but never moves any further (different % for
different combinations of qubes in the backup list).

After waiting a considerable time (well, 5-10 minutes), hitting
Cancel in the backup window does cancel it.  The rest of the
system is continuing to work without problem.  Happens every
time I try to use Qubes backup.

The Qubes Disk Space widget shows less than 50% disk used overall,
the backupVM shows only 18% disk used when the 3Gb file has been
saved.

I'm stumped.

Mike.


Hi,

You may have to wait longer than 5-10 minutes. I experience something
similar when doing a full backup, except it's worse because i'm backing
up like 2.5TB. It appears to hang for several hours at a time (and this
happens more than once), but it does eventually make visible progress
again. The whole process takes over 24 hours. This is why i do full
backups very infrequently.

For you it shouldn't take nearly as long because it's a lot less data,
but the progress appearing to hang for a while seems to be normal.

I'm using 3.2 tho, and i know they made changes to the backup mechanism
under the hood in 4.0, so i'm not sure if this issue still applies in
4.0.


Marek,

Isn't this the null bytes bug in GNU tar?

https://groups.google.com/d/msgid/qubes-users/f4d997d5-7191-06d0-e7bb-ef42745a7db5%40posteo.net

It would be a good idea to update this in dom0. My own backup tool uses GNU
tar as well.

--

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


It seems a little early to judge.

Mike - it looks from your comment as if you have been trying with
subsets of the qubes? Can you confirm if these are running or stopped.

Like jsnow, I'm regularly able to backup far more than 3G without issue,
so it looks as if there's something particular about this scenario.
It would be helpful if you could confirm the issue when all qubes you
are backing up are stopped.
Then try bisecting the qubes backup group - keep bisecting if you hit
the problem again until you either find the problematic qubes or have
backed them all up.



Oops, I pasted the wrong link. Here is the correct one:

https://utcc.utoronto.ca/~cks/space/blog/sysadmin/TarFindingTruncateBug

The symptoms sound remarkably the same... potentially hours-long delays 
with no adverse effect on data. Trigger condition is not about size, but 
due to corner cases that involve backing up nulls.


--

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

--
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/e7181586-a839-0f44-f7a5-1d1d654f5d58%40posteo.net.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: QSB #46: APT update mechanism vulnerability

[Lorenzo Lamas]

Please help, after updating dom0 with security-testing(which installed not only 
qubes-desktop-linux-manager and qubes-manager, but also 
qubes-mgmt-salt-dom0-update-4.0.5-1 and reboot, no VM at all will start.
Failed to connect to qmmemman:[Errno 2] No such file or directory.
Text boot shows:
Failed to start Qubes memory management daemon.

systemctl status qubes-qmemman.service shows:
"qubes-qmemman.service - Qubes memory management daemon
Loaded: loaded (/usr/lib/systemd/system/qubes-qmemman.service; enabled; vendor 
preset: enabled)
Active: failed (Result: exit code) since Thu 2019-01-24 15:41:40 CET; 1min 1s 
ago
Proces: 2094 ExecStart=/usr/bin/qmemmand (code=exited, status=1/FAILURE]
Main PID: 2094 (code-exited, status=1/FAILURE)

Jan 24 15:41:40 dom0 qmemmand[2094]: sys.exit(main())
Jan 24 15:41:40 dom0 qmemmand[2094]: File 
"/usr/lib/python3.5/site-packages/qubes/tools/qmemmand.py", line 261, in main
Jan 24 15:41:40 dom0 qmemmand[2094]:qubes.utils.parse_size(config.get('global', 
vm-min-mem'))
Jan 24 15:41:40 dom0 qmemmand[2094]: File 
"/usr/lib/python3.5/site-packages/qubes/utils.py", line 107, in parse_size
Jan 24 15:41:40 dom0 qmemmand[2094]: raise qubes.exc.QubesException("Invalid 
size: {0}.".format(size))
Jan 24 15:41:40 dom0 qmemmand[2094]: qubes.exc.QubesException: Invalid size 
190MIB.
Jan 24 15:41:40 dom0 systemd[1]: qubes-qmemman.service: Main proces exited, 
code-exited, status=1/FAILURE
Jan 24 15:41:40 dom0 systemd[1]: Failed to start Qubes memory management daemon.
Jan 24 15:41:40 dom0 systemd[1]: qubes-qmemman.service: Unit entered failed 
state.
Jan 24 15:41:40 dom0 systemd[1]: qubes-qmemman.service: Failed with result 
'exit-code'.

I tried to undo the update with dnf history undo but it says the package is not 
available.

-- 
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/43c0921f-3f54-4fe2-8a2a-5dfba7959e01%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] ssh giving me locale error

[Zrubi]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 1/24/19 3:00 PM, unman wrote:

> I think you have a locale set in the qube whihc cannot be generated
> on the server. Can you check this by looking at locale settings in
> both.
> 

I think the problem is that there is NO locale set in the default
template.

You can check this by the localectl command.

As this is used in a lot of place, it is wise to correct it by setting
a valid locale in a template.

- -- 
Zrubi
-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEmAe1Y2qfQjTIsHwdVjGlenYHFQ0FAlxJyuYACgkQVjGlenYH
FQ0+PQ/+ODuvTQNuG8FlX6m0jsH1DwbPuZ3b6eE2uF2Hq53tA02tjPPbgTZyu+X1
i4hjTcB/SJtiIX6qHmZXJnPr/Afcm344keQCBJ8xvsTd4l/1gjhaQCHaj5jccM43
UQf6uYiAaKkdKyUTKF8AmFxL9ky0eFH86v9HnPxKX3k0BJelqoap7dwGnM2DVOh3
lQ8O3EF+Jkta/P+tTsZFTIFOCoT2NBJDoIhGcu3ENukTSX7AROpCsBcBQHWQUu5z
MP4ggHYdMfynUjtq1HQh1KVGu6xEa1BXCwTRM7d3bP6Hz5HFISGWcLhyuU4gX8pS
RCfuVMh0+wutl9lA0FJD/j1QtUFn6H++4KOIXLb8nta1fv8V+0Iwi33uNrbDs2Jj
ziu3MhDPfXmfAQbi/mps5W5ephh/hCx4EKrsSZYczrTjVtjmmJanDlDkwZ3tIv9n
hWJWOzAmjLK/KwenT9ovQ95Tp2B43UK9kzQ/3S+fi60nyer6v7gFefJCq6sEMBDN
GU7ELcVC5jfoyVF1RRXCMH++6etTnhoJ29NyvviUHEU+u69ZcKTs9XBuzVoB03O0
UXNeiL6gOCSZuKG78eUcNPxO9zCJf4A6jO31x9De4upY5zczFQ6sAxP9fGy67kS6
94YAvVkseQMi96HbZYp94wX5Bxc56Zkalxetpbys94wer3tP5UM=
=0Nu/
-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/b3df3b11-d2b9-35b1-ad33-3238a2a8bd97%40zrubi.hu.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] post-apt-reinstall-issues sys-whonix not connecting to tor

[qubes-fan]

hi, I reinstalled successfully the whonix-ws-14, whonix-gw-14 and debian-9 
templates as described here: https://www.qubes-os.org/news/2019/01/23/qsb-46/ 


With this kind of installation no sys-whonix is created by default. I created 
therefore a new AppVM named sys-whonix, based on template whonix-gw-14, NetVM 
set to sys-firewall. After running Connection Wizard it stops at 5% if 
connecting directly to Tor, or at 10% if connecting with Bridges. It stops in 
the bootstrap phase connecting to a relay directory. Whonix check say gave up 
waiting. In the Arm it keeps popping up duplicates hidden. 
After few moments it tells me (when using bridges): [WARN] Proxy Client: unable 
to connect to IP-address:443 "general SOCKS server failure" . 

Is there any setting in the original sys-whonix that is missing if the 
sys-whonix I just created manually? 
What is the solution for this issue? 
I live in non-censored area, clearnet internet connection is working smoothly.
Thank you!

-- 
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/LX-7pQR--3-1%40tutanota.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] ssh giving me locale error

[unman]

On Thu, Jan 24, 2019 at 04:58:26AM -0800, billol...@gmail.com wrote:
> I have recently installed 4.0.1 with KDE Plasma as my Desktop.  I tried to 
> ssh to another computer through my "untrusted" domain, and received the 
> following error.   I don't have trouble talking to the site for other stuff 
> -- it's my personal virtual server that I use for email and such, and my 
> email client syncs just fine.  The port is correct -- I can connect from 
> other machines.
> 
> Any instructions on how to fix this would be appreciated.  The same thing 
> happens with my "personal" domain.
> 
> [user@untrusted ~]$ ssh -p 2225 
> The authenticity of host '[someplace.com]:2225 ([123.456.789.123]:2225)' 
> can't be established.
> 's password: 
> Last login: Tue Jan 22 20:31:55 2019 from 11.22.33.44
> perl: warning: Setting locale failed.
> perl: warning: Please check that your locale settings:
>   LANGUAGE = (unset),
>   LC_ALL = (unset),
>   LANG = "C.UTF-8"
> are supported and installed on your system.
> perl: warning: Falling back to the standard locale ("C").
> perl: warning: Setting locale failed.
> perl: warning: Please check that your locale settings:
>   LANGUAGE = (unset),
>   LC_ALL = (unset),
>   LANG = "C.UTF-8"
> are supported and installed on your system.
> perl: warning: Falling back to the standard locale ("C").
> perl: warning: Setting locale failed.
> perl: warning: Please check that your locale settings:
>   LANGUAGE = (unset),
>   LC_ALL = (unset),
>   LANG = "C.UTF-8"
> are supported and installed on your system.
> perl: warning: Falling back to the standard locale ("C").
> perl: warning: Setting locale failed.
> perl: warning: Please check that your locale settings:
>   LANGUAGE = (unset),
>   LC_ALL = (unset),
>   LANG = "C.UTF-8"
> are supported and installed on your system.
> perl: warning: Falling back to the standard locale ("C").
> perl: warning: Setting locale failed.
> perl: warning: Please check that your locale settings:
>   LANGUAGE = (unset),
>   LC_ALL = (unset),
>   LANG = "C.UTF-8"
> are supported and installed on your system.
> perl: warning: Falling back to the standard locale ("C").
> 
I think you have a locale set in the qube whihc cannot be generated on the
server. Can you check this by looking at locale settings in both.

If this is the case, then there are a few options. The easiest is to
stop accepting locale on the server - look in /etc/ssh/sshd_config in the
"remote" and see if you have AcceptEnv set . 
Or in local file, comment out SendEnv in /etc/ssh/ssh_config.

Try one of those and see if it fixes the issue.

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

Re: [qubes-users] Re: Qubes 4.0.x - Linux kernel 4.19.15 package available in testing repository

[Frédéric Pierret]

The kernel in dom0 and VM is working fine, at least for me as I tested
it several days, but there is no reason now it should not.

For the bug with graphical boot we are looking at what is the problem.
It appears again if you try to boot directly on the linux kernel like
you would do in Fedora for example but it disappears in normal boot xen
kernel.

Frédéric

On 1/20/19 7:52 PM, seshu wrote:
> On Sunday, January 20, 2019 at 12:57:48 AM UTC, Marek Marczykowski-Górecki 
> wrote:
> Hi all,
>
> There is updated "kernel" package available in current-testing
> repository - it's a Linux long term support 4.19.x series, as an update
> over 4.14.x before. Since the upgrade switches to the next major LTS
> branch, I'll keep it in current-testing repository longer than usual 1-2
> weeks. This also applies to kernel package for VMs: kernel-qubes-vm.
> Please report new issues the usual way, at qubes-issues[1], or
> simply by replying here. In either case, please mark it clearly it
> happens after updating to 4.19, preferably including a link to the
> update:
> https://github.com/QubesOS/updates-status/issues/850
>
> 4.19.x kernel was already available as kernel-latest package for some
> time. Users of kernel-latest will see the update to 4.19.15 too, but
> kernel-latest soon will carry 4.20.x kernel version.
>
> [1] https://github.com/QubesOS/qubes-issues/issues
>
> > I noticed that there were kernel updates for the fedora 29 templates.
I did the update and the templates have been working well. Was this from
the Qubes team or an update that is from Fedora? > > Since the templates
and qubes are working fine, would that indicate the new kernel would
work fine on dom0? Just wondering if I should give it a try or not. >

-- 
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/0d110fd5-46b3-0588-e372-5c0610f4a977%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

[qubes-users] Re: ssh giving me locale error

[billollib]

I should add that, by the way, I connect fine.  It just an irritating message.

-- 
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/a21d6d7d-a55d-46cd-9116-d1d0b085244d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Networking widget in KDE on qubes

[billollib]

Thanks for the info!  I won't worry about it, then.

-- 
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/4aaadd27-93db-4ca1-b1a2-2beabe33785e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] ssh giving me locale error

[billollib]

I have recently installed 4.0.1 with KDE Plasma as my Desktop.  I tried to ssh 
to another computer through my "untrusted" domain, and received the following 
error.   I don't have trouble talking to the site for other stuff -- it's my 
personal virtual server that I use for email and such, and my email client 
syncs just fine.  The port is correct -- I can connect from other machines.

Any instructions on how to fix this would be appreciated.  The same thing 
happens with my "personal" domain.

[user@untrusted ~]$ ssh -p 2225 
The authenticity of host '[someplace.com]:2225 ([123.456.789.123]:2225)' can't 
be established.
's password: 
Last login: Tue Jan 22 20:31:55 2019 from 11.22.33.44
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LANG = "C.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LANG = "C.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LANG = "C.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LANG = "C.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LANG = "C.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").



-- 
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/1e93dce9-c1e9-4e6c-9db0-d7dce05ab377%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Cant get it to install

[billollib]

Well, I guess I'm pretty useless, then.  Sorry.  I sympathize.  It took me 
about five attempts of reinstalling Qubes and/or KDE neon to get them both to 
work. I swear that Qubes partitioned automatically on installation, but I guess 
my memory was wrong.  That's always the problem when you bang your head against 
a wall fifteen times, you can forget exactly which combination worked.  A 
apologize for leading you down the wrong path and costing you an extra useless 
installation attempt.

-- 
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/11b0a0f1-7023-4fbd-83c9-570c3a57e427%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] diff files across appvms

[unman]

On Wed, Jan 23, 2019 at 08:15:53AM -0800, john.e.ma...@gmail.com wrote:
> 
> unman, thank you for being so generous with your time. I appreciate the 
> education. Yes, I was looking in appvms. I'm starting to understand better 
> what needs to be done. I'll see how far I get.
> 
> John
> 
No problem. Remember that at the monment all management is done in dom0,
so it is there that policy decisions are set.
If you hit any more problems dont hesitate to come back.

unman

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

Re: [qubes-users] Backup stops when the backup file reaches 3Gb

[unman]

On Thu, Jan 24, 2019 at 01:00:15AM -0500, Chris Laprise wrote:
> On 01/23/2019 08:15 PM, js...@bitmessage.ch wrote:
> > Mike Keehan:
> > > Hi,
> > > 
> > > I'm using Qubes Backup to save some of my qubes into another VM.
> > > The backup VM has 18 Gb of storage available, but whenever the
> > > backup file reaches 3Gb, the backup process just hangs.
> > > 
> > > No CPU usage, no error messages, just stops.  The backup window
> > > shows 40% complete, but never moves any further (different % for
> > > different combinations of qubes in the backup list).
> > > 
> > > After waiting a considerable time (well, 5-10 minutes), hitting
> > > Cancel in the backup window does cancel it.  The rest of the
> > > system is continuing to work without problem.  Happens every
> > > time I try to use Qubes backup.
> > > 
> > > The Qubes Disk Space widget shows less than 50% disk used overall,
> > > the backupVM shows only 18% disk used when the 3Gb file has been
> > > saved.
> > > 
> > > I'm stumped.
> > > 
> > > Mike.
> > 
> > Hi,
> > 
> > You may have to wait longer than 5-10 minutes. I experience something
> > similar when doing a full backup, except it's worse because i'm backing
> > up like 2.5TB. It appears to hang for several hours at a time (and this
> > happens more than once), but it does eventually make visible progress
> > again. The whole process takes over 24 hours. This is why i do full
> > backups very infrequently.
> > 
> > For you it shouldn't take nearly as long because it's a lot less data,
> > but the progress appearing to hang for a while seems to be normal.
> > 
> > I'm using 3.2 tho, and i know they made changes to the backup mechanism
> > under the hood in 4.0, so i'm not sure if this issue still applies in
> > 4.0.
> 
> Marek,
> 
> Isn't this the null bytes bug in GNU tar?
> 
> https://groups.google.com/d/msgid/qubes-users/f4d997d5-7191-06d0-e7bb-ef42745a7db5%40posteo.net
> 
> It would be a good idea to update this in dom0. My own backup tool uses GNU
> tar as well.
> 
> -- 
> 
> Chris Laprise, tas...@posteo.net
> https://github.com/tasket
> https://twitter.com/ttaskett
> PGP: BEE2 20C5 356E 764A 73EB  4AB3 1DC4 D106 F07F 1886

It seems a little early to judge.

Mike - it looks from your comment as if you have been trying with
subsets of the qubes? Can you confirm if these are running or stopped.

Like jsnow, I'm regularly able to backup far more than 3G without issue,
so it looks as if there's something particular about this scenario.
It would be helpful if you could confirm the issue when all qubes you
are backing up are stopped.
Then try bisecting the qubes backup group - keep bisecting if you hit
the problem again until you either find the problematic qubes or have
backed them all up.

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

[qubes-users] Seahorse and split GPG

[Achim Patzner]

Hi!

I'm fighting a hard case of MacOSinitis ("why should I use a command
line if there is a GUI tool wheelchair-for-the-mind?") with one of my
minions. Is there a way of getting Seahorse to play nicely with the
split PGP tools? Or do I have to perform a neural implant with an ice
pick on him?


Achim


-- 
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/20a0eda5db0508c0362732a90943e505221cc902.camel%40noses.com.
For more options, visit https://groups.google.com/d/optout.