Re: [qubes-users] Bad GPG Signature is Good on 2nd Try?

2016-08-06 Thread Robin Schneider
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 06.08.2016 04:47, Andrew David Wong wrote:

> Well, it should only be unnerving if you know with certainty that GnuPG is 
> returning different results on the *exact same* sequence of bits. Since
> you didn't hash the ISO before the first (failed) verification attempt, we
> don't have any evidence that that's the case. It's much more likely that
> the bits changed (e.g., due to write caching, as you suggested).

Bad memory or bit flips in memory might be a second plausible cause to look
at. Maybe you can check that (bad memory) with memtest86+?

- -- 
Live long and prosper
Robin `ypid` Schneider
-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJXpZ+eAAoJEIb9mAu/GkD4X8oQANZ9cGCScw2W8JSsI2yvSmWD
H0SIrIz4QtamITtQhwpOVJT40hnMnoiilTfiR2OeOW9iKE7MbABYV3diyiYJh5Yg
XhkiEi3d4LoK0Kxn1Zn/9MI+DHTN+yKlWj5V0GH9V7x8mdSewksUD5P63Zsses+f
7s2Ant5cfUdnV12ysayXmzq5YlYG4C0vJptP8aMqbVW8wFytKZFczzM31sGPaRWw
7DJShhP4jILLbqtqL+v0Lmgkl4fjW8Z2wTUqeJJ9F0EmQdHm5ANDyVXb1m+od0vT
jK+wdoPDlgljHz4bkFiXHjMvrLggFXjboR54/2UcglhYgDcwggrAmmOKEzC1c7mK
wV0BtdIrv1+PWPOqxv5Xb3rOKZb3lbiNcHp3Upz/NaMTGmqn+vT50rg8f0kLxara
QUW1YlArN0Lp7csO22Gpnj7rQfIubjzwhNpdAh26gSUXkfKbGvkjOTr5MctR73sE
JG50NXGWCQpBj1Q0cAzuXhCGDW3YhGMl9OgPOos6ZG+BMVPw+Qxf85VgIxUcCfJb
2pBSWfShcPmBsZ1FzrFvVWE2O9StwpaKheezVYbLNxjcta2QL32AY0Wp3cXsYxGU
W7kisX0+HTH2xijdY4R60W2uXtNlXZCXPiqwu58Uleo7h5/qXaDWx06r0s5mf9QW
lnskN719dtd4jFwi3Rv3
=udik
-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/d513833b-e1e9-8746-021d-e20f867b85f3%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] this seems a bug [was express card USB controller]

2016-08-06 Thread Franz
On Fri, Jul 8, 2016 at 2:09 AM, Franz <169...@gmail.com> wrote:

> I need an additional USB controller that can be assigned to a VM different
> from sys-usb.
>
> Since I have an express card slot, should something like this work?
> https://www.thinkpenguin.com/gnu-linux/usb-30-expresscard-34mm
>
>
I bought it and it does not work. Only if I insert it before starting the
computer, then I can assign it to a VM with no errors.

But when I start the VM to which it is assigned, it does not start with the
error:

libvirtError: End of file while reading data: Input/output error

This is most likely a bug in the Qubes Manager


line: if ret == -1: raise libvirtError ('virDomainIsActive() failed', dom=self)
func: isActive
line no.: 1338
file: /usr/lib64/python2.7/site-packages/libvirt.py

line: if libvirt_domain.isActive():
func: get_power_state
line no.: 878
file: /usr/lib64/python2.7/site-packages/qubes/modules/000QubesVm.py

line: state = vm.get_power_state()
func: update_table
line no.: 698
file: /usr/lib64/python2.7/site-packages/qubesmanager/main.py


I got similar problems with other express card USB controllers, so this
seems a Qubes bug

best
Fran

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


Re: [qubes-users] Can NOT get Broadcom BCM43602 Wifi Card working , DELL XPS 15 9950- Qubes sys-net freezes/ crashes

2016-08-06 Thread skinny
On Friday, August 5, 2016 at 12:01:46 AM UTC+2, Jeral wrote:
> On Thursday, August 4, 2016 at 3:44:05 PM UTC+3, donoban wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA256
> > 
> > On 08/04/2016 02:16 PM, Jeral wrote:
> > > On Thursday, August 4, 2016 at 11:08:32 AM UTC+3, Marek
> > > Marczykowski-Górecki wrote: On Wed, Aug 03, 2016 at 07:05:00AM
> > > -0700, Michael wrote:
> >  Have a Broadcom BCM43602 Wifi Card in my dell xps 15 9950
> >  
> >  and I downloaded Qubes Release 3.2-rc2
> >  
> >  Problem: I can not connect to the internet cause my wifi card
> >  is not working with qubes: "If BCM43602, the wireless card is
> >  disabled in BIOS, installation succeeds, and afterwards it's
> >  possible to re-enable BCM43602 in BIOS and boot Qubes.
> >  However, subsecuantly adding BCM43602 device to the sys-netvm
> >  freezes the computer."
> >  
> >  -my boot setup has VT and VT-d options activated
> >  
> >  how can I make my network function ?
> > > 
> > > Do you have serial console in this computer (for example in
> > > docking station)? That would greatly ease collecting more
> > > information.
> > > 
> > > 
> > > I tried to compile and install wl driver into sys-net VM. 
> > > Unfortunately it didn't solve the problem, dom0 still freezes...
> > > :(
> > > 
> > 
> > I guess you have already tried with permissive mode, right? It seems
> > complicated to achieve. Also it is more related to Xen, Linux and the
> > card vendor than to Qubes.
> > 
> > Regards.
> > -BEGIN PGP SIGNATURE-
> > Version: GnuPG v2
> > 
> > iQIcBAEBCAAGBQJXoziQAAoJEBQTENjj7QilhBoP/Rbf0Gdot6gHgFWQ0LYp/J0I
> > FT6T2FPp22KyA66TDxmJ2hHrb5t/q/boZW7RFO0xBO9/S9X6Ixml6YoaLy91aIeG
> > 3g7znHxBhHDPaUAqbrQDfVeL9lr4qul3qZivinbpI/giUCmHyLATlgtnBbWrYP4n
> > kQVxfhAUo0Wm/KPE0Ai0z3GWJ7Zcttzm4gmJOygpv+hczqD0UMYgL4+BaPNK+Ql8
> > umLK1nm2D1ASLfHEzphbZrXeNWcHOAgkPW/5P6xm1snS91oV2bqmmCGAl525Q0YT
> > xptIfxcmBOFGZ+4eyq5/L422U9EAcOxsMGlAJKAWGSAG6nBkqxQO8CoLs+YG/SNy
> > 4Ktjfu8fCeMShdkCXbVv5aZ+HYay9u70Mk4EhrNm92/F4WBOJf9qNJHMOc6aW2CN
> > guW5103Ott8Q55S66yuqzK5YKkCoQJhSCDZqkxyZzorx19/gGWiZqcKqlVITnr87
> > zfqTweP5AS5tnH9kItWmVGFWpHglogrwdLYD+S+Vu1w8uiIDbiEvyhzxxthxr80Q
> > 1/rcaybKB+LSZhus2b9jSonAtN1AjRqCGbYohfLxRmuls/PNgYmGgAjO9j/LybwC
> > wZ6Pw0Cew4E3+C7Bit42DxViw4jvREE29EqTkJVNMJsD0BFT6yjhIXInzZ4jCsTA
> > sOlajHZER0hTlXQIyiSh
> > =TivY
> > -END PGP SIGNATURE-
> 
> Sure, I tried to solve this problem with permissive mode — dom0 still 
> freezes...
> Is it possible to install Ubuntu on HVM VM, and then set this VM as my 
> default sys-net?



I asked myself the same thing. I dont know

-- 
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/f1553334-f099-4e29-9fb1-6a6f7bec5de4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: this seems a bug [was express card USB controller]

2016-08-06 Thread Franz
On Sat, Aug 6, 2016 at 7:44 AM, Franz <169...@gmail.com> wrote:

>
>
> On Fri, Jul 8, 2016 at 2:09 AM, Franz <169...@gmail.com> wrote:
>
>> I need an additional USB controller that can be assigned to a VM
>> different from sys-usb.
>>
>> Since I have an express card slot, should something like this work?
>> https://www.thinkpenguin.com/gnu-linux/usb-30-expresscard-34mm
>>
>>
> I bought it and it does not work. Only if I insert it before starting the
> computer, then I can assign it to a VM with no errors.
>
> But when I start the VM to which it is assigned, it does not start with
> the error:
>
> libvirtError: End of file while reading data: Input/output error
>
> This is most likely a bug in the Qubes Manager
>
> 
> line: if ret == -1: raise libvirtError ('virDomainIsActive() failed', 
> dom=self)
> func: isActive
> line no.: 1338
> file: /usr/lib64/python2.7/site-packages/libvirt.py
> 
> line: if libvirt_domain.isActive():
> func: get_power_state
> line no.: 878
> file: /usr/lib64/python2.7/site-packages/qubes/modules/000QubesVm.py
> 
> line: state = vm.get_power_state()
> func: update_table
> line no.: 698
> file: /usr/lib64/python2.7/site-packages/qubesmanager/main.py
>
>
> I got similar problems with other express card USB controllers, so this
> seems a Qubes bug
>
> best
> Fran
>

I also paste here some lines from Dom0 log, but it does not seem relevant,
because the PCI device that I assigned had address 04:00.0, not 00:id.


(XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input
to Xen)
(XEN) Freed 292kB init memory.
(XEN) [VT-D] It's risky to assign :00:1d.0 with shared RMRR at da2ba000
for Dom3.
(XEN) [VT-D] It's risky to assign :00:1a.0 with shared RMRR at da2ba000
for Dom3.

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


[qubes-users] USB keyboard with trackpad and trackpoint recognized as mouse

2016-08-06 Thread kototamo
Hi,

I have a USB keyboard with an integrated trackpad and trackpoint. When 
connecting it Qubes if sys-usb can execute Qubes.InputMouse. 

How can I get it recognized as a keyboard + mouse?

thanks in advance.

-- 
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/9b90b2db-1c40-428b-b13f-d973f8fc53e4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: i3wm tiling window manager - is qubes-manager supposed to work?

2016-08-06 Thread kototamo
I had the same problem but after killing the qube-manager that was in the 
background and restarting it it worked. Also after reboot it works. 

Hope this helps.

-- 
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/40b632dc-0f3e-4e3b-a515-b0640018ccf0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] howto add untrusted repository to appVM (without using seperate template)

2016-08-06 Thread Andrew David Wong
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-08-06 18:05, emilcronja...@gmail.com wrote:
> Hi there,
> 
> How do I add an outside/untrusted repository to an app-vm based on the 
> standard template, *without* changing the whole template? And/or how do I, 
> after succeding, install a program from the outside source in the appVM
> and make the program survive reboot?
> 
> I guess this is a general question, although my problem is concerned with
> the VoIP-program Jtisi: they are not included in neither Fedora or Debian
> repos, and I would not like to add their "untrusted" repo only to the appVM
> wich would actually run the program. (I know I could create a standalone
> VM, but I prefer not to use 3 GB of space to run just one program :)).
> 
> SO: How to solve this? (Without jepoardizing my template-VM)
> 
> Best regards, E
> 
> PS: Why oh why is there no voip-client with zrtp-support in the
> fedora/debian repos?!
> 

You could do this by installing the program to some place in the AppVM that
survives reboot (e.g., the AppVM's home/ directory). Besides that, I can't
think of any way to satisfy all of your desiderata simultaneously. (You could
clone the TemplateVM, but you said you didn't want to create a StandaloneVM
because it would take up too much disk space, and a cloned TemplateVM would
take up roughly the same amount.)

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

iQIcBAEBCgAGBQJXppCLAAoJENtN07w5UDAwNbwQALclKJQwipRfeP/fPsNtRwiz
R/ujnQmz+rEulQFw0t+tjcIONCGVzxGfSkM3A7Ud1N6oWm8s51mV/kLjn/AD/NIe
69ZPb/gCXVKmyoGpaFmvYxVasUlTXBibVntz1M4pptmUe/34WW8zvF29etByjWhf
o8nKfzacchKQRpsbzh1hZp1EjWmIc7x58KFF4UBNX4yU1jH4zls6q+FzxaVeNfQi
t2HYndN83/9U0UqJxFqmTStz8phHv8EqqqvUmAX8UXyuQfBtdSWTqLX/bzTx57RR
wopdgj1p3Q4wzkLnjMkIaj5Z7ElJMz1g37dmg+W4Ixd89jkTicnXbvlnccgsc5d1
IPaYUvH547OqOXYFSrif+iNAD2z0dyWHZX81lqA2uPlJJLrPn+5XRA7RNCNVzP2D
KGE4ljUrqApxbfYMRzeNQH2ryQ/6uaxGy0Fv0y++/aQ0tSfhuXLv6IhnAZO204h5
fY4Y+lMBjYG8sNeUm4NRGLvnl72ZCuS4GRhru6oAEq/DWBUPtxXY9qIhAS3fUric
8Nk9vxhkqCYqfXd2IQCBoQ5teKAjJnPdtS+hCBQzWGuLsa1vleH9+L+vw84PO7u+
CFpuIGlri86aZyupAomnnDjFrL6yUvZdcNz/X1D+ni0s9zzW6jN5EjT7ndBQ528s
6nlh5jWh4zeZYtyeG5Je
=wXOr
-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/f58e9c48-8c2d-4a08-b1f1-95e3f94afea0%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.


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

2016-08-06 Thread donoban
It sounds like I've sent wrong log, I will check it.

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/9573A104-6995-4B36-8C35-643B3B7B8191%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Enable copr in fedora

2016-08-06 Thread Andrew David Wong
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-08-06 08:35, Herbies wrote:
> Hi, I'm trying to enable copr  in fedora-23, but I got this error.
> 
> Curl error (56): Failure when receiving data from the peer for 
> https://copr.fedorainfracloud.org/coprs/stuff/fedora-23/ [Received HTTP 
> code 403 from proxy after CONNECT]
> 
> 
> Template is connected to sys-firewall, and I have enabled all the 
> port/protocol. I have also commented the yum.conf so I have disabled the 
> update proxy but the error is always the same.
> 
> 
> Please could you help troubleshooting this?
> 
> Thanks you
> 

Are you sure you whitelisted all the correct ports/protocols? Perhaps you
should try allowing all access for N minutes instead?

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

iQIcBAEBCgAGBQJXpozLAAoJENtN07w5UDAw4dkQAM46RfJFqyJrIBeXktcHIya9
dwdVZUuG1UYo6e0Y0QQMmMWPfghSZIO7wnMG38iIcPW2r1Yhfb3BkxG+AAkD9/MI
pb50YQL7hLCoWTmAVpyx+ccEhDsrAMf68ajGiqKEn70GYGFiJV5Q/oS89/60leM/
zGr3neGgtPPLkVd5DTVbjO920jap+iQeMbwtrRDyjM0Zdav0xJMgit0LkWzvmRZt
auvaxsK6xR9PW3furOMXDzVozeg4EJIgQPwl50qarFGN7+K/9Qgvx44U7LHfFIOJ
U2+C36IMsLBwnWIWHyEsngKr71IQO8n/5+u4Uz7FXe0ZbC2EqACWPSUpENC7csiF
0XvBe9LKBDXDn7r4hTwsmZLlyM9qXMeqeCC2woeJuTuEGcitGLpNnd4MysKQ9QkY
umOK3KtLDZh8gWoHf0ZGMvr7B9Cfd80PPjn70fFnLsji1nNpSdqEKucJ3A7WRt/+
Pcr1RaRvgR+z/zLZhbIHUWIGnRSbC+tKgaJy+gVcq7diuFZgE4qduPr1NMBBEL4J
vl4Znuaiuq13a68LtHHmh2l0deuBCfZp46ejOt8pzYAaPl2JQcquu7NZ8ZIbDs/x
nMXTOogx6vAs61NqM1hgGiG0yTRg/YOpFVnUVs5PxOhRETRIwJayMbk2oXoy/2M/
S5t0VjNpP1uRzUb+ommy
=tWhV
-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/24dba6ac-00f2-de97-546f-5c49c2f6aad5%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] New laptop for Qubes V4

2016-08-06 Thread eldorado

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


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

2016-08-06 Thread Stephen Moreno

On 08/02/2016 09:55 PM, Marek Marczykowski-Górecki wrote:

>
> I think it doesn't really matter from security point of view. Either
> legacy or UEFI BIOS can contain bugs fatal to the system security.
>
> On the other hand, many UEFI BIOSes contains bugs affecting Qubes OS.
> Legacy BIOSes also have bugs, but those are much older and already have
> workarounds in Xen/Linux.
> In addition, Anti Evil Maid (which can detect some firmware
> modifications) isn't compatible with UEFI.
> In short: choose legacy BIOS (or at least a BIOS with legacy boot mode),
> for better Qubes OS support.
>
> - --
> Best Regards,
> Marek Marczykowski-Górecki
> Invisible Things Lab
>

Hi Marek,

Thanks for your reply.

After some further research it looks like my choice for an AM3 board is 
either:

older 760G chipset with legacy BIOS but no IOMMU
OR
newer 970 chipset with IOMMU but also a UEFI BIOS

I would be really interested in your views regarding this choice. Which 
option would you go for?
(I will need to use bluetooth with this system, in case that sways you 
towards a board with IOMMU.)


Regards,

Stephen

--
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/f71160f2-9b67-62fa-044c-027a859d028c%40mail.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] howto add untrusted repository to appVM (without using seperate template)

2016-08-06 Thread emilcronjager
Hi there,

How do I add an outside/untrusted repository to an app-vm based on the standard 
template, *without* changing the whole template? And/or how do I, after 
succeding, install a program from the outside source in the appVM and make the 
program survive reboot?

I guess this is a general question, although my problem is concerned with the 
VoIP-program Jtisi: they are not included in neither Fedora or Debian repos, 
and I would not like to add their "untrusted" repo only to the appVM wich would 
actually run the program. (I know I could create a standalone VM, but I prefer 
not to use 3 GB of space to run just one program :)). 

SO: How to solve this? (Without jepoardizing my template-VM)

Best regards,
E

PS: Why oh why is there no voip-client with zrtp-support in the fedora/debian 
repos?! 

-- 
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/3b093ed9-480a-49e0-8964-639fb9c95a4b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Error: failed to syncronize cache

2016-08-06 Thread Andrew David Wong
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-08-06 14:15, katerim...@sigaint.org wrote:
> Hello I want to do some upgrade to fedora VM but when I run update vm
> system or sudo dnf upgrade in terminal, shows up this message: Error:
> failed to syncronize cache for repo 'qubes-vm-r3..1-current'
> 
> Thank you
> 

I run into this message frequently when updating templates. I assume it's the
result of a bad Tor exit node (or circuit). Waiting a while then trying again
usually fixes it. If you don't want to wait for a new circuit to be selected
automatically (happens every 10 minutes), you can use tor-arm in sys-whonix to
request a new identity (press "n"), then try again.

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

iQIcBAEBCgAGBQJXpo6fAAoJENtN07w5UDAwJeYQAIw52FNOwTxlqhdbwBjaeyjy
KN27sdcWBinbQbdjJLzZJF2J6Cep7ktmcGkkZCDr5xKkL75IwdupX+Dzc4G3buVw
/ekKiBEE/+C7RrAwnfic/foS+txDJt+jge/fxkyM6tk7GpYw8hMjRxprFNL5OGrf
uW4yVCaEgLnsndRMOGmwyEYB40ziHk8PDQ+O1xaGtI4pflJE7suj48Oz94vgBNm0
IBONVmFzH+KZdt1moIs3V/8s2PNGfKAIkdMZNSNYcscIEVrZKqzxYWsPL3rJ5TvA
WSmC2cE3t7RPjMVYjCxnFAC0XlqTiXA4eGLW0cMFG3nA62aUaMEFTS5NfbLUPpbQ
l7cNLosOMho2eKbLXnkSSnhEdO+Mn8ZjK4bpur6Kl96amAqwD3usd9d5axEWRVn+
48SX/tAv8MU+jBWwnzv6k+WPvBn8y9dwk8onOfgfBO3nh5HHh2/iUu3OgygIqhtC
n/vcCawzkOAB+On7kvl1QhA4WYCLekIjI17n88VBI2HGJHhjGjw01yEII+M52sWj
NrsS7wbQVirMkj11EfN/pHu942F1gHm8TvqcR932kkmqsI7mD/saIech+oEbNdPy
IOnWAMclNy0RktGTSQul+7J7muDVY1R3A0RBgmgphvn+Lnsd2woUVvUWHUqFRNXu
fmsv+fEy+e6DjM0qZAqz
=cUGa
-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/b45f1688-f7c3-7f4f-72a0-578a4ae07941%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.


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

2016-08-06 Thread Marek Marczykowski-Górecki
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Sat, Aug 06, 2016 at 09:10:36PM +0200, donoban wrote:
> On Fri, 5 Aug 2016 20:27:03 +0200
> Marek Marczykowski-Górecki  wrote:
> 
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA256
> > 
> > On Wed, Aug 03, 2016 at 09:35:45AM +0200, donoban wrote:
> > > On 08/02/2016 10:57 PM, Marek Marczykowski-Górecki wrote:
> > > > 
> > > > Could you paste also list of packages in dom0 (rpm -qa)? This
> > > > should allow me to reproduce the problem.
> > > > 
> > > > 
> > > 
> > > Yes Marek! Here is it:
> > > https://paste.debian.net/786712
> > > 
> > > The only think that I did on both install was installing Xfce after
> > > the default KDE install (or maybe xfce was already installed?), I am
> > > not sure.
> > > 
> > > I hope it helps.
> > 
> > I've added additional step to the instruction[1] for Debian-based
> > UpdateVM:
> > 
> > If you are using Debian-based VM as UpdateVM (sys-firewall by
> > default), you need to download few more packages manually, but do not
> > install them yet:
> > 
> > sudo qubes-dom0-update systemd-compat-libs perl-libwww-perl
> > perl-Term-ANSIColor perl-Term-Cap gdk-pixbuf2-xlib speexdsp
> > qubes-mgmt-salt-admin-tools
> > (...)
> > Transaction Summary
> > ===
> > Install 15 Packages (+ 31 Dependent packages)
> > Upgrade  4 Packages (+200 Dependent packages)
> > 
> > Total download size: 173 M
> > Is this ok [y/d/N]: n
> > Exiting on user command
> > Your transaction was saved, rerun it with:
> >   yum load-transaction /tmp/yum_save_tx.
> > 
> > Please let me know if that helps.
> > 
> > [1] https://www.qubes-os.org/doc/upgrade-to-r3.2/
> > 
> 
> 
> It didn't :(
> 
> I've attacehd current log.

This log looks like VM upgrade, not dom0 (which original issue was
about). Also it looks like a template from Qubes 3.0 (qubes-core-agent
3.0.14, qubes-gui-agent 3.0.14), not 3.1 nor 3.2. Keep in mind that
direct 3.0 -> 3.2 upgrade is not supported. While it may work in some
cases, it is safer to upgrade first to 3.1, then to 3.2. 

This particular issue looks like a bug in dependencies which was present
some time ago. Should be fixed by "apt-get dist-upgrade" instead of
"apt-get upgrade".

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

iQEcBAEBCAAGBQJXpkKyAAoJENuP0xzK19csEjYH/0hf2IY3t/1rVquJIUoetx9r
irUdxwERJ9T5hJqhkM4K2+gleYgQisvn92p7A+TFeJ1vBocsyU4e4yg63VFskIxn
1SdbGFXHq21kvLpuJkEbCuMZ7kiH1+eIahKM6Pc+Q1jsDOCYc7V85nJLFp5EGi5J
zz/3p1z1wZw8/HB2Zd4pLeEwlV6LoYusx7hvFHvpHdNLS7h3YIVNDmvWiK5idyRv
9jNlTOeqq2vcjdQxCapsVErtJ97642ctM3Stt3ru4dBLFQHwjodf5SXBPw4MGkBX
5DeNcQEfDv5VQNj58YBdOwN2ppC0kHlZ+/6202q2MW58jd0ALy7NQAWQBb4ABZ0=
=ojus
-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/20160806200401.GZ32095%40mail-itl.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Error: failed to syncronize cache

2016-08-06 Thread katerimmel
Hello
I want to do some upgrade to fedora VM but when I run update vm system or
sudo dnf upgrade in terminal, shows up this message:
Error: failed to syncronize cache for repo 'qubes-vm-r3..1-current'

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/9ebec6e194a78a6f69e56eeeb02fde0e.webmail%40localhost.
For more options, visit https://groups.google.com/d/optout.


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

2016-08-06 Thread donoban
On Fri, 5 Aug 2016 20:27:03 +0200
Marek Marczykowski-Górecki  wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> On Wed, Aug 03, 2016 at 09:35:45AM +0200, donoban wrote:
> > On 08/02/2016 10:57 PM, Marek Marczykowski-Górecki wrote:
> > > 
> > > Could you paste also list of packages in dom0 (rpm -qa)? This
> > > should allow me to reproduce the problem.
> > > 
> > > 
> > 
> > Yes Marek! Here is it:
> > https://paste.debian.net/786712
> > 
> > The only think that I did on both install was installing Xfce after
> > the default KDE install (or maybe xfce was already installed?), I am
> > not sure.
> > 
> > I hope it helps.
> 
> I've added additional step to the instruction[1] for Debian-based
> UpdateVM:
> 
> If you are using Debian-based VM as UpdateVM (sys-firewall by
> default), you need to download few more packages manually, but do not
> install them yet:
> 
> sudo qubes-dom0-update systemd-compat-libs perl-libwww-perl
> perl-Term-ANSIColor perl-Term-Cap gdk-pixbuf2-xlib speexdsp
> qubes-mgmt-salt-admin-tools
> (...)
> Transaction Summary
> ===
> Install 15 Packages (+ 31 Dependent packages)
> Upgrade  4 Packages (+200 Dependent packages)
> 
> Total download size: 173 M
> Is this ok [y/d/N]: n
> Exiting on user command
> Your transaction was saved, rerun it with:
>   yum load-transaction /tmp/yum_save_tx.
> 
> Please let me know if that helps.
> 
> [1] https://www.qubes-os.org/doc/upgrade-to-r3.2/
> 


It didn't :(

I've attacehd current log.

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


log.tar.gz
Description: application/gzip