Re: [qubes-users] Tip: How to speed up QubesOS shutdown

2017-03-18 Thread Jean-Philippe Ouellet
On Tue, Mar 14, 2017 at 7:11 PM, haaber  wrote:
> I dont't have any e820 pci device as far as I know, but shutdown is
> definitely a problem. xfce shuts down, and then I have a black screen
> with a blinking cursor, and, afaik unless I brutally remove electricity.
> No clue if this is related to Grzesiek's problem ... Bernhard

e820 does not refer to a device, but rather a table containing memory
layout information provided by the bios [1].

[1]: 
http://wiki.osdev.org/Detecting_Memory_(x86)#BIOS_Function:_INT_0x15.2C_EAX_.3D_0xE820

-- 
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/CABQWM_Bq0vh2s_z1i%3D2HWNv2Pn7QFvp_KZ9FbJwXd5J6%2ByV6hg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Can't start my StandaloneVM anymore

2017-03-18 Thread cooloutac
On Saturday, March 18, 2017 at 7:35:54 PM UTC-4, Andrew David Wong wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> On 2017-03-17 14:10, Unman wrote:
> > On Fri, Mar 17, 2017 at 10:49:04AM -0700, cooloutac wrote:
> >> On Friday, March 17, 2017 at 1:48:27 PM UTC-4, cooloutac wrote:
> >>> On Friday, March 17, 2017 at 1:17:10 PM UTC-4, Unman wrote:
>  On Fri, Mar 17, 2017 at 04:38:17PM +, faber wrote:
> > I have a Debian-9 StandaloneVM that I recently am unable to start it.
> > The only thing I've done, before getting stuck there, was removing
> > libreoffice (all packages), jack, mutt and icedove, nothing special.
> >
> > logs from /var/log/xen/console/guest-dev.log:
> >
> > https://share.riseup.net/#jt9PHXk7pbpDkz0ZKmwy7g
> >
> >
> > If you need anything else, please let me know!
> 
>  If you start it using qvm-start what error do you see?
>  Once you have started it can you attah to the console from dom0 using
>  (as root) xl console  ?
> >>>
> >>> ya and if you can do that check apt log.  I kill my debian system all the 
> >>> time removing or installing packages.  I blindly click yes and don't 
> >>> realize its asking me if it can kill my system by removing desktop haha.
> >>>
> >>> after reading about how when updating a template you could accidentally 
> >>> click yes to a not verified key I had to tell my family to make sure they 
> >>> read for that specific thing especially before hitting y. (this has 
> >>> nothing to do with your issue sorry)
> >>
> >> and when that happens you just keep trying till it gets a valid key.
> >>
> > 
> > I hope this was a joke.
> > I have no sense of humour - do NOT do this.
> > It's a common situation and you will find many answers with a simple
> > search.
> > 
> 
> I'm unclear about the disagreement here. I understood cooloutac as saying:
> 
> Sometimes, apt-get may download a package with an invalid signature.
> In that case, you should not install the invalidly signed package.
> Instead, you should re-download the package (and let apt-get re-check
> the signature), e.g., after a period of time, from a different server,
> or via a different connection, until you get a validly signed package,
> and only then proceed with installing that package.
> 
> If that's what cooloutac meant, then I'm not sure I see the problem
> with that approach. Isn't that what we *should* do in that situation?
> 
> P.S. - Let's keep the discussion civil and productive, please.
> 
> - -- 
> Andrew David Wong (Axon)
> Community Manager, Qubes OS
> https://www.qubes-os.org
> -BEGIN PGP SIGNATURE-
> 
> iQIcBAEBCgAGBQJYzcRHAAoJENtN07w5UDAwv38P/idMKPQlh+1hqJmlPwQJJHVq
> TjXSUJnS3AL2kX9WGmAbID1cPl3SxHG8ElDWbU5CxnJ7CdgffIV4CRqBcxo/z75H
> 6ggMHBKQuZXTUzKTU8IObHwy2A2wTo6RYNYsVO93GFiPsRGQnrXOYxcQ2jFhvZsM
> Hsih4Eg60Rbv/pbagWcooVfKDhMrqMHR+tnBBJzcXEwwgqVl2vhCcvzeL/ZeYfAN
> Z1nCenv42AQ601hKIDkD8+CgbXzCxAPtQQ7vXHAYq9W8UL/nWRzSbT3L5ih2Z7JW
> NUoNJ3NmMXPj11uf7EnZb+NY1mA70njdCQ0HdxiXB6iAZVQ8fJ0Fz6juyFie6RyP
> murVctv1Btgz6FR5clKfS9tIFxZJ2bTtPtFNTeiOZInDqIyJLr662Ji/i8Qql6b2
> aTfk0PxSWiDhXeyyBy6NuCckDRvUWyb0FNXJBLNUTzNR8zAuAuR+/jnwTdT+Q/YY
> v9Ja6LoqH3s7nfluxi4Zm4TInd/I7XkehYdikm+O4D9re4haoPJkYGfiMzc+g6qH
> vDMbGWttj7Tc0wQbmItbb31Nr1/R13wAfST9XMXQS0pav9zOS6J3yOy0Lu8aiQyU
> vcB2lP2cQon5capDrP8fatb4mEpRORdBwJ5tv+N2Tqq3tshzxaxJ6AhgzPDHUJmu
> punfqhmLEuvp2TodREZT
> =xrUX
> -END PGP SIGNATURE-

I'm sorry Andrew.

-- 
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/3bd19088-0566-41ac-bbb7-b2fb1afa0c6b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Can't start my StandaloneVM anymore

2017-03-18 Thread Andrew David Wong
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2017-03-17 14:10, Unman wrote:
> On Fri, Mar 17, 2017 at 10:49:04AM -0700, cooloutac wrote:
>> On Friday, March 17, 2017 at 1:48:27 PM UTC-4, cooloutac wrote:
>>> On Friday, March 17, 2017 at 1:17:10 PM UTC-4, Unman wrote:
 On Fri, Mar 17, 2017 at 04:38:17PM +, faber wrote:
> I have a Debian-9 StandaloneVM that I recently am unable to start it.
> The only thing I've done, before getting stuck there, was removing
> libreoffice (all packages), jack, mutt and icedove, nothing special.
>
> logs from /var/log/xen/console/guest-dev.log:
>
> https://share.riseup.net/#jt9PHXk7pbpDkz0ZKmwy7g
>
>
> If you need anything else, please let me know!

 If you start it using qvm-start what error do you see?
 Once you have started it can you attah to the console from dom0 using
 (as root) xl console  ?
>>>
>>> ya and if you can do that check apt log.  I kill my debian system all the 
>>> time removing or installing packages.  I blindly click yes and don't 
>>> realize its asking me if it can kill my system by removing desktop haha.
>>>
>>> after reading about how when updating a template you could accidentally 
>>> click yes to a not verified key I had to tell my family to make sure they 
>>> read for that specific thing especially before hitting y. (this has nothing 
>>> to do with your issue sorry)
>>
>> and when that happens you just keep trying till it gets a valid key.
>>
> 
> I hope this was a joke.
> I have no sense of humour - do NOT do this.
> It's a common situation and you will find many answers with a simple
> search.
> 

I'm unclear about the disagreement here. I understood cooloutac as saying:

Sometimes, apt-get may download a package with an invalid signature.
In that case, you should not install the invalidly signed package.
Instead, you should re-download the package (and let apt-get re-check
the signature), e.g., after a period of time, from a different server,
or via a different connection, until you get a validly signed package,
and only then proceed with installing that package.

If that's what cooloutac meant, then I'm not sure I see the problem
with that approach. Isn't that what we *should* do in that situation?

P.S. - Let's keep the discussion civil and productive, please.

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

iQIcBAEBCgAGBQJYzcRHAAoJENtN07w5UDAwv38P/idMKPQlh+1hqJmlPwQJJHVq
TjXSUJnS3AL2kX9WGmAbID1cPl3SxHG8ElDWbU5CxnJ7CdgffIV4CRqBcxo/z75H
6ggMHBKQuZXTUzKTU8IObHwy2A2wTo6RYNYsVO93GFiPsRGQnrXOYxcQ2jFhvZsM
Hsih4Eg60Rbv/pbagWcooVfKDhMrqMHR+tnBBJzcXEwwgqVl2vhCcvzeL/ZeYfAN
Z1nCenv42AQ601hKIDkD8+CgbXzCxAPtQQ7vXHAYq9W8UL/nWRzSbT3L5ih2Z7JW
NUoNJ3NmMXPj11uf7EnZb+NY1mA70njdCQ0HdxiXB6iAZVQ8fJ0Fz6juyFie6RyP
murVctv1Btgz6FR5clKfS9tIFxZJ2bTtPtFNTeiOZInDqIyJLr662Ji/i8Qql6b2
aTfk0PxSWiDhXeyyBy6NuCckDRvUWyb0FNXJBLNUTzNR8zAuAuR+/jnwTdT+Q/YY
v9Ja6LoqH3s7nfluxi4Zm4TInd/I7XkehYdikm+O4D9re4haoPJkYGfiMzc+g6qH
vDMbGWttj7Tc0wQbmItbb31Nr1/R13wAfST9XMXQS0pav9zOS6J3yOy0Lu8aiQyU
vcB2lP2cQon5capDrP8fatb4mEpRORdBwJ5tv+N2Tqq3tshzxaxJ6AhgzPDHUJmu
punfqhmLEuvp2TodREZT
=xrUX
-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/79d67fad-7d94-dd2e-0a38-7df99697717e%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Can't start my StandaloneVM anymore

2017-03-18 Thread cooloutac
On Saturday, March 18, 2017 at 2:50:51 PM UTC-4, Holger Levsen wrote:
> On Sat, Mar 18, 2017 at 11:14:07AM -0700, cooloutac wrote:
> > On Saturday, March 18, 2017 at 2:11:50 PM UTC-4, cooloutac wrote:
> > >  I'm starting to think you're the joke.
> > Instead of arrogantly telling someone to do a simple search if you are too 
> > lazy to give a solution.  Do  everyone a favor and keep your fucking mouth 
> > shut!
> 
> instead of attacking people on the list, please read 
> https://www.qubes-os.org/code-of-conduct/
> 
> thanks.
> 
> 
> -- 
> cheers,
>   Holger

Well if this is gonna turn into the typical linux help channel with arrogant 
assholes insulting people askikng questions.  Good Luck  to Qubes...

-- 
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/63996b5f-b7fa-4d5f-b26c-a34e6bac98df%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] HCL - FUJITSU-D3410_B1 Mainboard

2017-03-18 Thread Marcus Dilger
i3-6100 / 16GB Ram / SSD / Multi-Monitor

Actual no Problems occurred.

-- 
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/b9fea9b8-2bf2-49c0-bbe5-1c1ca8bfaa92%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Qubes-HCL-FUJITSU-D3410_B1-20170318-231218.yml
Description: Binary data


[qubes-users] Re: HCL - DELL Precision Workstation T7400

2017-03-18 Thread ludwig jaffe
TPM is "present"
but hw report does not put this into file.



On Sat, Mar 18, 2017 at 5:37 PM, ludwig jaffe 
wrote:

> So having Bios A11 and the most recent Qubes-OS3.2 the problem at
> https://groups.google.com/d/msg/qubes-users/gjsM2FShN3A/t8XF6MSRAQAJ
> is resolved.
>
> My box runs fine with 2 xeons E5440@2.83 GHz and 40GB RAM  (max 64GB)
> possible
> without riser boards
>
> I use only 1 of two possible monitors at the moment.
>
> To fight against noise of a turbo jet starting install i8k
> and have the following in
> /etc/rc.local
>
> i8kfan speed 1 1
>
> this sets the speed of cpu and chassis fan to lower speed.
>
> Also one can disable the big fan that sits on the RAM modules. By
> unplugging.
> The box will scream at boot-up about "compromised" thermal solution,
> but one can press F1 and boot.
> The RAM has its own heat sink and the other fans will blow enough I guess.
>
> So at least my box did not die of over temperaure.
>
> Have fun.
>
>
>
>
> On Sat, Mar 18, 2017 at 4:56 PM, ludwig jaffe 
> wrote:
>
>> here the edited version, forget to fill fixme.
>>
>>
>>
>> On Sat, Mar 18, 2017 at 4:50 PM, ludwig jaffe 
>> wrote:
>>
>>> BIOS A11  04/30/2012  (newest version)
>>>
>>> BIOS A02 had problems with IOMMU
>>>
>>> ---
>>> So update that beast to A11 using T7400A11.exe
>>> and an usb stick booting freedos without drivers.
>>>
>>> Have fun!
>>>
>>>
>>> Ludwig
>>>
>>>
>>
>

-- 
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/CAP7JdrKX3QR%3DX2BisAWRK9WJ1PgA1nyVdvrLzbTm1v%2Bg8Y1pmw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: HCL - DELL Precision Workstation T7400

2017-03-18 Thread ludwig jaffe
So having Bios A11 and the most recent Qubes-OS3.2 the problem at
https://groups.google.com/d/msg/qubes-users/gjsM2FShN3A/t8XF6MSRAQAJ
is resolved.

My box runs fine with 2 xeons E5440@2.83 GHz and 40GB RAM  (max 64GB)
possible
without riser boards

I use only 1 of two possible monitors at the moment.

To fight against noise of a turbo jet starting install i8k
and have the following in
/etc/rc.local

i8kfan speed 1 1

this sets the speed of cpu and chassis fan to lower speed.

Also one can disable the big fan that sits on the RAM modules. By
unplugging.
The box will scream at boot-up about "compromised" thermal solution,
but one can press F1 and boot.
The RAM has its own heat sink and the other fans will blow enough I guess.

So at least my box did not die of over temperaure.

Have fun.




On Sat, Mar 18, 2017 at 4:56 PM, ludwig jaffe 
wrote:

> here the edited version, forget to fill fixme.
>
>
>
> On Sat, Mar 18, 2017 at 4:50 PM, ludwig jaffe 
> wrote:
>
>> BIOS A11  04/30/2012  (newest version)
>>
>> BIOS A02 had problems with IOMMU
>>
>> ---
>> So update that beast to A11 using T7400A11.exe
>> and an usb stick booting freedos without drivers.
>>
>> Have fun!
>>
>>
>> Ludwig
>>
>>
>

-- 
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/CAP7JdrJn8CS4ap-zUCcaMQSLw3PEETkmJ9z6jf%3D%2Bj32JCqLwXg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: HCL - DELL Precision Workstation T7400

2017-03-18 Thread ludwig jaffe
here the edited version, forget to fill fixme.



On Sat, Mar 18, 2017 at 4:50 PM, ludwig jaffe <ludwig.ja...@gmail.com>
wrote:

> BIOS A11  04/30/2012  (newest version)
>
> BIOS A02 had problems with IOMMU
>
> ---
> So update that beast to A11 using T7400A11.exe
> and an usb stick booting freedos without drivers.
>
> Have fun!
>
>
> Ludwig
>
>

-- 
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/CAP7JdrKCG00kkAqf%2BwqEG%3Dc3uufFFKrw5q%2BXOsywMrsmMr9xXw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Qubes-HCL-Dell_Inc_-Precision_WorkStation_T7400__-20170318-164205_edit.yml
Description: application/yaml


[qubes-users] HCL - DELL Precision Workstation T7400

2017-03-18 Thread ludwig jaffe
BIOS A11  04/30/2012  (newest version)

BIOS A02 had problems with IOMMU

---
So update that beast to A11 using T7400A11.exe
and an usb stick booting freedos without drivers.

Have fun!


Ludwig

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


Qubes-HCL-Dell_Inc_-Precision_WorkStation_T7400__-20170318-161105.yml
Description: application/yaml


Qubes-HCL-Dell_Inc_-Precision_WorkStation_T7400__-20170318-161105.yml
Description: application/yaml


Re: [qubes-users] Tip: How to speed up QubesOS shutdown

2017-03-18 Thread haaber
>>> Have you tried the solution suggested here before of shutting down other
>>> vms first, then sys-usb and sys-net? Andrew, I think, posted a simple
>>> script that he uses. I suspect that that will have more impact with
>>> fewer consequences than this proposal, but user experience will be key
>>> here: comments ?
>>
>> Yes, I did try that, this is how I found out that on my system it is not 
>> possible to cleanly shut down VMs that hold PCI devices. If I try shutting 
>> down sys-net the VM Manager hangs for a few minutes, then the entire system 
>> stops responding then the machine gets killed, then VM manager throws an 
>> exception and then system becomes responsive again. After setting 
>> pci_e820_host to False I can cleanly shutdown sys-net and sys-usb just like 
>> any other VM.
>>
> 
> So that sounds very system specific. Why not put together a tip
> incorporating Andrew's script ( which will help on almost all
> machines), and then yours as a special case to be used where that
> doesnt help?

I dont't have any e820 pci device as far as I know, but shutdown is
definitely a problem. xfce shuts down, and then I have a black screen
with a blinking cursor, and, afaik unless I brutally remove electricity.
No clue if this is related to Grzesiek's problem ... 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/8452d566-22c1-ff28-aa86-93ad7c74b750%40web.de.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Can't start my StandaloneVM anymore

2017-03-18 Thread Holger Levsen
On Sat, Mar 18, 2017 at 11:14:07AM -0700, cooloutac wrote:
> On Saturday, March 18, 2017 at 2:11:50 PM UTC-4, cooloutac wrote:
> >  I'm starting to think you're the joke.
> Instead of arrogantly telling someone to do a simple search if you are too 
> lazy to give a solution.  Do  everyone a favor and keep your fucking mouth 
> shut!

instead of attacking people on the list, please read 
https://www.qubes-os.org/code-of-conduct/

thanks.


-- 
cheers,
Holger

-- 
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/20170318185044.GA6%40layer-acht.org.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Digital signature


[qubes-users] Re: Question to Mirage OS firewall users

2017-03-18 Thread Thomas Leonard
On Friday, February 24, 2017 at 1:16:55 PM UTC, Foppe de Haan wrote:
> On Tuesday, February 7, 2017 at 6:22:53 PM UTC+1, Thomas Leonard wrote:
> > On Tuesday, February 7, 2017 at 4:51:06 PM UTC, Foppe de Haan wrote:
> > > On Tuesday, February 7, 2017 at 5:24:58 PM UTC+1, Thomas Leonard wrote:
> > > > On Tuesday, February 7, 2017 at 3:55:30 PM UTC, Foppe de Haan wrote:
> > > > > Anyone else tried to use MirageOS i.c.w. a torrent client? I've 
> > > > > allocated 60mb ram, but it crashes within 2-8 hours here, which is 
> > > > > kind of disappointing.
> > > > 
> > > > Do the logs show an out-of-memory error when that happens? I haven't 
> > > > seen one for a long time now, but maybe torrents stress it more than 
> > > > usual.
> > > > 
> > > > If so, it could be https://github.com/yomimono/mirage-nat/issues/17 - 
> > > > there's a Mirage hackathon next month and I'm hoping to get some time 
> > > > to work on this there.
> > > 
> > > Yes. "Fatal error: out or memory. Mirage exiting with status 2"
> > 
> > By the way, what version of the firewall are you using?
> > If it's not qubes-mirage-firewall v0.2 then try upgrading first - there 
> > were lots of OOM problems in v0.1.
> > 
> > > That said, 2 minutes earlier the log notes that memory use was still only 
> > > at 16.7/38.2 MB.
> > 
> > The annoying thing about hashtables is the way they suddenly double in 
> > size. Since you're allocating 60 MB to the firewall (I only use 20 MB for 
> > mine), you could try adjusting the thresholds at these two lines:
> > 
> > https://github.com/talex5/qubes-mirage-firewall/blob/master/memory_pressure.ml#L41
> > https://github.com/talex5/qubes-mirage-firewall/blob/master/memory_pressure.ml#L47
> > 
> > Change the 0.9 (allow 90% of memory to be used) to 0.4 in both places. If 
> > the NAT table is the cause, that should make the problem go away.
> > 
> > > (Most of the log -- 90-95% -- consists of 'Failed to parse frame' 
> > > messages, btw.)
> > 
> > "Failed to parse frame" probably means it saw an ICMP (not TCP or UDP) 
> > packet and therefore didn't handle it. Another thing I'm hoping to fix 
> > soon... https://github.com/yomimono/mirage-nat/issues/15
> 
> It looks stable now (uptime 3-4 days since last reboot, whereas before it 
> only lasted ~8h max).

Thanks for the report! I've now made some updates to the firewall:

- It now uses an LRU-cache to drop old entries, rather than growing until it 
runs out of memory.

- ICMP queries (e.g. ping) and errors (e.g. Host unreachable) now work (they 
were dropped before).

- I've ported it to the new Mirage 3 release.

There are quite a lot of changes, so I'd be happy to get reports about whether 
it works or not (I've just started running the new version on my laptop).

-- 
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/61f88c78-9442-435a-bed6-5f63e033bb6d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Can't start my StandaloneVM anymore

2017-03-18 Thread cooloutac
On Saturday, March 18, 2017 at 2:11:50 PM UTC-4, cooloutac wrote:
> On Friday, March 17, 2017 at 5:10:41 PM UTC-4, Unman wrote:
> > On Fri, Mar 17, 2017 at 10:49:04AM -0700, cooloutac wrote:
> > > On Friday, March 17, 2017 at 1:48:27 PM UTC-4, cooloutac wrote:
> > > > On Friday, March 17, 2017 at 1:17:10 PM UTC-4, Unman wrote:
> > > > > On Fri, Mar 17, 2017 at 04:38:17PM +, faber wrote:
> > > > > > I have a Debian-9 StandaloneVM that I recently am unable to start 
> > > > > > it.
> > > > > > The only thing I've done, before getting stuck there, was removing
> > > > > > libreoffice (all packages), jack, mutt and icedove, nothing special.
> > > > > > 
> > > > > > logs from /var/log/xen/console/guest-dev.log:
> > > > > > 
> > > > > > https://share.riseup.net/#jt9PHXk7pbpDkz0ZKmwy7g
> > > > > > 
> > > > > > 
> > > > > > If you need anything else, please let me know!
> > > > > 
> > > > > If you start it using qvm-start what error do you see?
> > > > > Once you have started it can you attah to the console from dom0 using
> > > > > (as root) xl console  ?
> > > > 
> > > > ya and if you can do that check apt log.  I kill my debian system all 
> > > > the time removing or installing packages.  I blindly click yes and 
> > > > don't realize its asking me if it can kill my system by removing 
> > > > desktop haha.
> > > > 
> > > > after reading about how when updating a template you could accidentally 
> > > > click yes to a not verified key I had to tell my family to make sure 
> > > > they read for that specific thing especially before hitting y. (this 
> > > > has nothing to do with your issue sorry)
> > > 
> > > and when that happens you just keep trying till it gets a valid key.
> > > 
> > 
> > I hope this was a joke.
> > I have no sense of humour - do NOT do this.
> > It's a common situation and you will find many answers with a simple
> > search.
> 
>  I'm starting to think you're the joke.

Instead of arrogantly telling someone to do a simple search if you are too lazy 
to give a solution.  Do  everyone a favor and keep your fucking mouth shut!

-- 
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/160c9760-2a12-4730-89ab-b28af7461622%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Can't start my StandaloneVM anymore

2017-03-18 Thread cooloutac
On Friday, March 17, 2017 at 5:10:41 PM UTC-4, Unman wrote:
> On Fri, Mar 17, 2017 at 10:49:04AM -0700, cooloutac wrote:
> > On Friday, March 17, 2017 at 1:48:27 PM UTC-4, cooloutac wrote:
> > > On Friday, March 17, 2017 at 1:17:10 PM UTC-4, Unman wrote:
> > > > On Fri, Mar 17, 2017 at 04:38:17PM +, faber wrote:
> > > > > I have a Debian-9 StandaloneVM that I recently am unable to start it.
> > > > > The only thing I've done, before getting stuck there, was removing
> > > > > libreoffice (all packages), jack, mutt and icedove, nothing special.
> > > > > 
> > > > > logs from /var/log/xen/console/guest-dev.log:
> > > > > 
> > > > > https://share.riseup.net/#jt9PHXk7pbpDkz0ZKmwy7g
> > > > > 
> > > > > 
> > > > > If you need anything else, please let me know!
> > > > 
> > > > If you start it using qvm-start what error do you see?
> > > > Once you have started it can you attah to the console from dom0 using
> > > > (as root) xl console  ?
> > > 
> > > ya and if you can do that check apt log.  I kill my debian system all the 
> > > time removing or installing packages.  I blindly click yes and don't 
> > > realize its asking me if it can kill my system by removing desktop haha.
> > > 
> > > after reading about how when updating a template you could accidentally 
> > > click yes to a not verified key I had to tell my family to make sure they 
> > > read for that specific thing especially before hitting y. (this has 
> > > nothing to do with your issue sorry)
> > 
> > and when that happens you just keep trying till it gets a valid key.
> > 
> 
> I hope this was a joke.
> I have no sense of humour - do NOT do this.
> It's a common situation and you will find many answers with a simple
> search.

 I'm starting to think you're the joke.  

-- 
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/a600e4a1-1c90-4803-9401-000c3e53a627%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] *.mov-Files with Intel-Grafic?

2017-03-18 Thread evo


Am 18.03.2017 um 17:18 schrieb Unman:
> On Sat, Mar 18, 2017 at 03:47:18PM +0100, evo wrote:
>> Hi!
>>
>> i tried to play mov-files on debian-8 template (with VLC) and it works
>> rather good, but just if i make a little window. If i go fullscreen it
>> doesn't work good at all.
>>
>> is it a problem of RAM or grafic-card? (i have 16GB RAM, but maby i
>> should give more to this VM) Initial memory is 2000 and max 4000.
>>
>> or is it a problem of grafic-card. i have 2 of them, intel and nvidia
>> K1000M. As i understood, i can not really use nvidia on qubes.
>>
>> can you play full-hd mov-files in qube-VMs?
>>
> 
> Yes is the answer, but I warrant it depends on your graphics and
> available memory, as you guess.
> You may find that you can resize the window to (almost) full screen
> without introducing choppiness, and that this works better than using
> the "full screen" mode. That's my experience.
> It's undoubtedly worth playing around to see what works best for you.
> 
> unman
> 

hmmm... ok... what is about the nvidia-doc on the qubes page?
is it non realistic?

-- 
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/68e8c226-5d7a-1795-07a7-7216b6698e35%40aliaks.de.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Tip: How to speed up QubesOS shutdown

2017-03-18 Thread Grzegorz Chodzicki


On 03/18/2017 05:21 PM, Unman wrote:
> On Sat, Mar 18, 2017 at 08:59:29AM -0700, Grzesiek Chodzicki wrote:
>> W dniu sobota, 18 marca 2017 15:08:35 UTC+1 użytkownik Unman napisał:
>>> On Sat, Mar 18, 2017 at 03:41:49AM -0700, Grzesiek Chodzicki wrote:
 I've experienced this issue myself and I saw some people complaining about 
 it on the mailing list. Sometimes Qubes takes forever to poweroff.

 The issue is caused by the fact that for some unknown reason machines with 
 PCI devices attached take forever to shutdown and sometimes need to be 
 manually killed from within VM Manager. After manually killing them, the 
 system will shutdown normally.

 So, here's the fix:

 In Dom0 run qvm-prefs -s sys-net pci_e820_host false

 Repeat that for sys-usb and any other machine that holds a PCI device.

 Your system should shut down normally after this.

 No, I don't know how or why this works but I know that it solved the issue 
 on my machine. Explanation welcome. I'll add this to documentation once we 
 have a confirmation that this is 100% reproducible.

>>> I'd be reluctant to propose this as a tip as is, because it will almost
>>> certainly break networking for some users.
>>> We specifically set pci_e820 to address user problems. I don't know what
>>> the intersection is between those for whom this is a fix and those for
>>> whom shutdown is slow/doesn't happen.
>>>
>>> Have you tried the solution suggested here before of shutting down other
>>> vms first, then sys-usb and sys-net? Andrew, I think, posted a simple
>>> script that he uses. I suspect that that will have more impact with
>>> fewer consequences than this proposal, but user experience will be key
>>> here: comments ?
>> Yes, I did try that, this is how I found out that on my system it is not 
>> possible to cleanly shut down VMs that hold PCI devices. If I try shutting 
>> down sys-net the VM Manager hangs for a few minutes, then the entire system 
>> stops responding then the machine gets killed, then VM manager throws an 
>> exception and then system becomes responsive again. After setting 
>> pci_e820_host to False I can cleanly shutdown sys-net and sys-usb just like 
>> any other VM.
>>
> So that sounds very system specific. Why not put together a tip
> incorporating Andrew's script ( which will help on almost all
> machines), and then yours as a special case to be used where that
> doesnt help?
That's the point, I don't know whether this is specific to my machine
but I don't have another PC to test so I posted this here so other
people can try it and see if that alleviates 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/b4834e61-6e58-6a2a-a552-81e9509d007b%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Tip: How to speed up QubesOS shutdown

2017-03-18 Thread Unman
On Sat, Mar 18, 2017 at 08:59:29AM -0700, Grzesiek Chodzicki wrote:
> W dniu sobota, 18 marca 2017 15:08:35 UTC+1 użytkownik Unman napisał:
> > On Sat, Mar 18, 2017 at 03:41:49AM -0700, Grzesiek Chodzicki wrote:
> > > I've experienced this issue myself and I saw some people complaining 
> > > about it on the mailing list. Sometimes Qubes takes forever to poweroff.
> > > 
> > > The issue is caused by the fact that for some unknown reason machines 
> > > with PCI devices attached take forever to shutdown and sometimes need to 
> > > be manually killed from within VM Manager. After manually killing them, 
> > > the system will shutdown normally.
> > > 
> > > So, here's the fix:
> > > 
> > > In Dom0 run qvm-prefs -s sys-net pci_e820_host false
> > > 
> > > Repeat that for sys-usb and any other machine that holds a PCI device.
> > > 
> > > Your system should shut down normally after this.
> > > 
> > > No, I don't know how or why this works but I know that it solved the 
> > > issue on my machine. Explanation welcome. I'll add this to documentation 
> > > once we have a confirmation that this is 100% reproducible.
> > > 
> > 
> > I'd be reluctant to propose this as a tip as is, because it will almost
> > certainly break networking for some users.
> > We specifically set pci_e820 to address user problems. I don't know what
> > the intersection is between those for whom this is a fix and those for
> > whom shutdown is slow/doesn't happen.
> > 
> > Have you tried the solution suggested here before of shutting down other
> > vms first, then sys-usb and sys-net? Andrew, I think, posted a simple
> > script that he uses. I suspect that that will have more impact with
> > fewer consequences than this proposal, but user experience will be key
> > here: comments ?
> 
> Yes, I did try that, this is how I found out that on my system it is not 
> possible to cleanly shut down VMs that hold PCI devices. If I try shutting 
> down sys-net the VM Manager hangs for a few minutes, then the entire system 
> stops responding then the machine gets killed, then VM manager throws an 
> exception and then system becomes responsive again. After setting 
> pci_e820_host to False I can cleanly shutdown sys-net and sys-usb just like 
> any other VM.
> 

So that sounds very system specific. Why not put together a tip
incorporating Andrew's script ( which will help on almost all
machines), and then yours as a special case to be used where that
doesnt help?

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


Re: [qubes-users] *.mov-Files with Intel-Grafic?

2017-03-18 Thread Unman
On Sat, Mar 18, 2017 at 03:47:18PM +0100, evo wrote:
> Hi!
> 
> i tried to play mov-files on debian-8 template (with VLC) and it works
> rather good, but just if i make a little window. If i go fullscreen it
> doesn't work good at all.
> 
> is it a problem of RAM or grafic-card? (i have 16GB RAM, but maby i
> should give more to this VM) Initial memory is 2000 and max 4000.
> 
> or is it a problem of grafic-card. i have 2 of them, intel and nvidia
> K1000M. As i understood, i can not really use nvidia on qubes.
> 
> can you play full-hd mov-files in qube-VMs?
> 

Yes is the answer, but I warrant it depends on your graphics and
available memory, as you guess.
You may find that you can resize the window to (almost) full screen
without introducing choppiness, and that this works better than using
the "full screen" mode. That's my experience.
It's undoubtedly worth playing around to see what works best for you.

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


[qubes-users] *.mov-Files with Intel-Grafic?

2017-03-18 Thread evo
Hi!

i tried to play mov-files on debian-8 template (with VLC) and it works
rather good, but just if i make a little window. If i go fullscreen it
doesn't work good at all.

is it a problem of RAM or grafic-card? (i have 16GB RAM, but maby i
should give more to this VM) Initial memory is 2000 and max 4000.

or is it a problem of grafic-card. i have 2 of them, intel and nvidia
K1000M. As i understood, i can not really use nvidia on qubes.

can you play full-hd mov-files in qube-VMs?

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


[qubes-users] Re: very frequent crashes (about every other hour)

2017-03-18 Thread Steffen Hartmann
Am Freitag, 17. März 2017 04:34:12 UTC+1 schrieb Drew White:
> On Monday, 13 March 2017 07:47:34 UTC+11, Steffen Hartmann  wrote:
> > Hello,
> > 
> > after installation and some weeks of using cubes 3.2 I'm still facing 
> > troubles with the system hanging comletly.
> > It starts with very delayed mouse and keyboard input - finally everything 
> > stops.
> > When looking with top in dom0 no obvious memory hungry tasks.
> > 
> > However I have to reboot or even stop the computer the hard way pulling the 
> > mains.
> > 
> > With my other OS's on the same computer no such troubles.
> > 
> > Where can I look into to trace down this problem?
> > 
> > I have a dell precision 5500 with 16 GB Ram an 3 VM running (sys-firewall, 
> > sys-net, fed23) and dom0 of course.
> > 
> > Everything is pretty much standard installation.
> > 
> > thank you
> 
> Hi Steffen,
> 
> You are using the almost EXACT SAME machine that I am. I have 24 GB RAM.
> I used to have the exact same problem before I reconfigured things to work 
> properly so that this did not happen.
> 
> FIRSTLY, upgrade to A16, there are bugs in A13 that should not be there.
> This fixes the frequent overloads and thus the lockups.
> 
> SECOND, disable screensaver, put it to blank screen.
> THIRD, whenever you are going away overnight, pause every guest that runs web 
> browsers, OR shut them down.
> 
> FOURTH, make sure you update the Qubes Manager to get rid of the Memory Leak 
> it has.
> 
> Currently I have been using most of my own things to replace the Qubes 
> Manager, thus utilising less RAM in Dom0, which also resolved numerous 
> locking issues.
> 
> I run Fedora 23 Templates, along with Debian 8, and numerous versions of 
> Windows along with other operating systems including Android.
> At times I have anywhere up to 20 Guests running at a time.
> 
> RARELY less than 8.



Hi,

I upgraded BIOS to A16 as suggested by Drew and now uptime is > 8 h without 
crash.

Thank you to all and I will keep you informed.

Steffen

-- 
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/43cae663-d824-47df-93b8-876c29d98946%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Tip: How to speed up QubesOS shutdown

2017-03-18 Thread Unman
On Sat, Mar 18, 2017 at 03:41:49AM -0700, Grzesiek Chodzicki wrote:
> I've experienced this issue myself and I saw some people complaining about it 
> on the mailing list. Sometimes Qubes takes forever to poweroff.
> 
> The issue is caused by the fact that for some unknown reason machines with 
> PCI devices attached take forever to shutdown and sometimes need to be 
> manually killed from within VM Manager. After manually killing them, the 
> system will shutdown normally.
> 
> So, here's the fix:
> 
> In Dom0 run qvm-prefs -s sys-net pci_e820_host false
> 
> Repeat that for sys-usb and any other machine that holds a PCI device.
> 
> Your system should shut down normally after this.
> 
> No, I don't know how or why this works but I know that it solved the issue on 
> my machine. Explanation welcome. I'll add this to documentation once we have 
> a confirmation that this is 100% reproducible.
> 

I'd be reluctant to propose this as a tip as is, because it will almost
certainly break networking for some users.
We specifically set pci_e820 to address user problems. I don't know what
the intersection is between those for whom this is a fix and those for
whom shutdown is slow/doesn't happen.

Have you tried the solution suggested here before of shutting down other
vms first, then sys-usb and sys-net? Andrew, I think, posted a simple
script that he uses. I suspect that that will have more impact with
fewer consequences than this proposal, but user experience will be key
here: comments ?

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


Re: [qubes-users] Re: Can't start my StandaloneVM anymore

2017-03-18 Thread Unman
On Sat, Mar 18, 2017 at 08:11:00AM +, faber wrote:
> Ok I've been able to log in, these are the last logs (I removed some
> other programs that I didn't remember before, like imagemagick, but I
> still don't think there is something wrong with it):
> https://share.riseup.net/#TaSVuYAJQCblXyFZc0z2aQ
> 
> unman:
> > log in as root, no password.
> > Then follow the advice an look at your apt logs - almost certainly you
> > have chosen to delete essential Qubes packages. Look in the apt logs >and
> > see exactly what you did. As you have root access you can  run any apt
> > tool to reinstall the missing packages.
> >
> > unman

Plesae don't top post.

I think that you will find that your decision to remove qubes-gui-agent
and qubes-core-agent may have something to do with your problems.

As you have root access to the qube you can reinstall these packages and
packages on which they depend (e.g imagemagick).

Two points:
First, the qube was starting, as you discovered from attaching to the
console. Almost everything about your initial post was misleading.

Second, exactly this problem has been covered before on the list. A
simple search would have enabled you to understand your problem and fix
it yourself. Just saying.

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


Re: [qubes-users] Is it really hard to autogenerate apropos data for all qubes utils ?

2017-03-18 Thread Unman
On Sat, Mar 18, 2017 at 03:32:54AM -0400, Jean-Philippe Ouellet wrote:
> Unman is correct.
> 
> Additionally, mandb index generation may be of lesser quality because
> our man pages are not actual man pages, but rather lifted from
> reStructuredText via pandoc, which generate raw *roff formatting
> macros rather than semantic mdoc (or even man(7)) ones. This is
> because reStructuredText inherently lacks such semantics, and pandoc
> does not attempt to heuristically assign any.
> 
> Example:
> NAME
> 
> qvm-block - list/set VM PCI devices.
> 
> Turns into:
> .TH "qvm\-block" "" "" "" ""
> .SH NAME
> .PP
> qvm\-block \- list/set VM PCI devices.
> 
> Instead of:
> .Sh NAME
> .Nm qvm-block
> .Nd list/set VM PCI devices

Although, of course, apropos seems to work perfectly with that utility as well.

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


[qubes-users] Re: Installing Qubes 3.2 on an Alienware

2017-03-18 Thread Grzesiek Chodzicki
W dniu sobota, 18 marca 2017 00:18:05 UTC+1 użytkownik Tristan Fleming napisał:
> Has anyone found a work around for Qubes on an Alienware 17 r4?
> 
> I just bought this laptop thinking that it would work with Qubes. So far, I 
> havent had any luck. It was a good excuse to buy a new laptop, though! ;)
> 
> 
> I bought the Alienware 17 r4
> 
> Intel(R) Core(TM) i7-7700HQ
> 8gb ram DDR4
> NVIDIA GeForce GTX 1060 with 6GB GDDR5 (problem numero uno)
> 
> 
> So, to the point, I have two problems. One is the GFX card. And the other is 
> UEFI. 
> 
> 
> Oh, and lest we forget the Qubes bugs. 
> 
> 
> I booted in Legacy mode, initial graphics GUI starts, Boot into basic 
> graphics mode; 
> 
> 
> Basic Graphics Mode FAILS 
> 
> 
> Txt based install has common bugs: "LUKS was not provided a pw" Cannot 
> partition, cannot install! 
> 
> 
> On the Hardware Compatibility List, it says Alienware works but without 
> sound. So, how did that person get Alienware to work!? 
> 
> 
> Any help is appreciated. My problems are common, but someone figured this 
> out, right?
> 
> 
> Thanks, crew!

Nvidia 10 series GPUs are not yet supported by nouveau driver. If possible 
disable it in UEFI (switch to Intel iGPU).

-- 
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/8a3e0619-85c7-4716-bf9f-4d018cd05a74%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Can't start my StandaloneVM anymore

2017-03-18 Thread faber
Ok I've been able to log in, these are the last logs (I removed some
other programs that I didn't remember before, like imagemagick, but I
still don't think there is something wrong with it):
https://share.riseup.net/#TaSVuYAJQCblXyFZc0z2aQ

unman:
> log in as root, no password.
> Then follow the advice an look at your apt logs - almost certainly you
> have chosen to delete essential Qubes packages. Look in the apt logs >and
> see exactly what you did. As you have root access you can  run any apt
> tool to reinstall the missing packages.
>
> 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/53bf66a2-ab38-ba57-bde3-036b3c6ac112%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Is it really hard to autogenerate apropos data for all qubes utils ?

2017-03-18 Thread Jean-Philippe Ouellet
Unman is correct.

Additionally, mandb index generation may be of lesser quality because
our man pages are not actual man pages, but rather lifted from
reStructuredText via pandoc, which generate raw *roff formatting
macros rather than semantic mdoc (or even man(7)) ones. This is
because reStructuredText inherently lacks such semantics, and pandoc
does not attempt to heuristically assign any.

Example:
NAME

qvm-block - list/set VM PCI devices.

Turns into:
.TH "qvm\-block" "" "" "" ""
.SH NAME
.PP
qvm\-block \- list/set VM PCI devices.

Instead of:
.Sh NAME
.Nm qvm-block
.Nd list/set VM PCI devices

-- 
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/CABQWM_DEZ56Pdsfnp-gav_AJuzmGPtrz3D80cQKMdE0%3DqiXAGw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.