Re: [qubes-users] issues in 3.2

2016-07-07 Thread Drew White
On Friday, 8 July 2016 09:50:21 UTC+10, Iestyn Best  wrote:
> On Thursday, July 7, 2016 at 11:00:45 AM UTC+10, Drew White wrote:
> > On Thursday, 7 July 2016 00:57:06 UTC+10, Andrew David Wong  wrote:
> > > I'm not a coder, so I don't know. If you know the task to be an easy
> > > one, why not help us out by contributing the patch yourself?
> > 
> > If I was to make a patch for it, it would involve me fixing all the bugs in 
> > it, basically rewriting the whole thing by going through line by line of 
> > the whole code to find where things are going wrong.
> > 
> > Since you have already been talking about rewriting the whole thing anyway, 
> > I don't see the point in doing that.
> > 
> > I personally have already altered things that are annoyances in the qvm 
> > tools and other things to fix what I find to be very very very annoying, 
> > and which are things that if I couldn't change, I wouldn't be using Qubes, 
> > yet I was told they couldn't be changed because other things worked off it, 
> > and yet those things with exactly the same change made, worked fine. one 
> > line of code in tools after one area changed in one tool. Took me 5 minutes 
> > to make the change, but made everything so much cleaner in the menu system. 
> > The next thing is the Windows Main Menu reader, and fixing that up.
> 
> Hi Drew,
> 
> Glad to see you are getting Qubes to work the way you like/need.
> 
> Just curious, have you provided patches to the Qubes team with those changes?
> 
> I would be interested in seeing if your fixes could come through in the main 
> release.
> 
> Regards,
> Iestyn Best

No, I have not provided them because I was told it would never be changed, and 
they would not  change it because they had things that worked using the way it 
was. So they will not change it no matter what, because I proposed it to them 
before.

I'll be happy to provide the small things that I have done to change things for 
more easy menu, but in 3.2 we need the real menu back, not that THING they call 
a menu that isn't.

-- 
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/1409eef0-4922-45cd-9c64-1771cdd55b2b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] issues in 3.2

2016-07-05 Thread Drew White
On Tuesday, 5 July 2016 19:41:53 UTC+10, Andrew David Wong  wrote:
> We agree that this is confusing from a UX perspective, and we are
> working on it:
> 
> https://github.com/QubesOS/qubes-issues/issues/1382


Question... Why is it from so long ago and nothing has happenned about it?

Is it really that hard to alter a tiny tiny tiny bit of code?

-- 
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/0e5ea0ec-88b2-472d-8e0d-4969f9207d4b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] issues in 3.2

2016-07-05 Thread Andrew David Wong
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-07-05 00:22, Drew White wrote:
>>> 5. Can't even "Run command in VM" on dom0
>> 
>> Can you elaborate? How are you trying to do that, and what (if 
>> anything) is happening instead of the expected behavior?
>> 
>> 
> I mean it doesn't have that option, it's disabled.
> 

Oh, I see. You mean in Qubes Manager, when you right-click on dom0,
the entry for "Run command in VM" is grayed out (along with almost
every other entry), yes?

That is normal, intended behavior. The intended way to run a command
in dom0 is simply to open a terminal in dom0.

We agree that this is confusing from a UX perspective, and we are
working on it:

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

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

iQIcBAEBCgAGBQJXe4DaAAoJENtN07w5UDAwSBcP/0mV9lG+DUkuI0QsJwMyZFHx
xckNoQJ5tVJy01D/ocfbPfMOJ85LFh8HLFnwWciMiobdm1EJfyQ/ITALpK7ndu2c
KNAQTYNhGvrhHuYhHX+sG7xOk1yrlC3+EoV8lAyyvGAsIfwoZps3HsebLubKEMld
yyuCQhyQYI1S2dlA9jcVgWyJKCU/yA/ZsnkGWlhTzq7MbYAdDmFtr4QetEKzTFis
NYhoznJq6xGzsQ5qzVJ1TE1k0InSlu++CW/BGltmyv6Aype9F80JH36vPYYMQe3P
HM2ssE3ECKNoNmWqFKFfaRxP5aZ03d9LLKIFdFniDdQUKXJHZV0QL0saUp2UR5lx
XdC+P8Gx0WlZOT+W4o6mrEhUfHOjR8SRNN8r0j1aoOyzzQ1a4Xhp+n3Xda/Mblpc
Tx46HsNiJTgk/5gCvwc2prFe/AmGv+taIz6bKWfoXzzCPC4tVSKjOZ06cOpidbRv
d6wv3sq0sPck4mZxs9hRUwZtGFRaBggFzfXAQ7mDg8TuFS6U2D2k8EHyxq5318tK
pfHdZ9DinbCFWz0Q6blD9qC0MTRpMUQ91kJa60i8LfIkZzV5MrwnEyG8ftdaOl71
Dg9TCsLC1ZAc+Xvy/3/U0ete6BZkWAv9dN2cmtwRx1u0XScEgJtA/XhiDROA0G+M
ZCtOwDK0LaC2GOfeiFBy
=M7t1
-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/f1ad0e96-7946-5ecc-8f78-83393465bfa2%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] issues in 3.2

2016-07-02 Thread Andrew David Wong
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-07-01 20:40, Drew White wrote:
> 
> 1. During initial configuration, if you don't create the NetVMs
> because you want to set everything yourself, it has error running a
> command because no matter what, it will try to run the command on
> the sys-net and sys-firewall.

Thanks. Tracking here:

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

> 2. No desktop 3. No taskpar/panels

Sounds like this is already being tracked here:

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

> 4. No terminal access, have to go to next window

Can you elaborate? I'm not sure what you mean. For example, is this
happening during the installer or on the desktop after installation?
What is "next window"?

> 5. Can't even "Run command in VM" on dom0

Can you elaborate? How are you trying to do that, and what (if
anything) is happening instead of the expected behavior?

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

iQIcBAEBCgAGBQJXd8deAAoJENtN07w5UDAw9WAP/0DFBakUaqtGwodA4LA2ZNyT
VdDGQjF8O2qe0u9MK7zhOlX3LZDsh+Mi6ZPajPwuTNo49rDQqHFKwozlbMExIhEU
/DcuayvsX1msDWE+OODsqDThvmERsDCFrbQTmxPlo+nePL5ZWRw408Tl3uihycQ4
lPQxCX+0OfkZ8yTn7dAclHZlIUokcAEPnv0MMYPtjTZhnIJmbSiA1aPsBkexmBdM
Rak/AEhJYH9UjW/quBS0YuFFvrRHNBlbAT0kQ1c5h5nwlaoGoCuzLfUAdQd6gXPx
ZTD4s2UB4v8vWeDiDsWgOeN8TD81QHCxesxBI09sJzkB2gzk2di4lcicLEVFfc42
8uYn361975VqvKSoYVF8k/hqels7iRFDPQyhSBUCOf8wK68q2jfWHwi5lKBh8scE
trx5q7H41Fx+xL2CZHSgY1ZaVMl49o7aHrqVmifsmqV50MIsM/45TZcUrxRkhQxD
94FNuIWrB6Kk8mrn5ZhSum4NTUkDIpIvNLYJnXjW+RSbazbGuuXAKXb/bxjKlvbz
EQqSSCiTCWkUei+RWD5MzBnq89eyXhQ5+amUl/LjliAilBlg4pznP/jjF7XfXNXZ
xhsbV1MhBMIBnPvMOLgvqPMRLPVIxP45rVeFyGutUOcEN/jyWs6ZrwAOQGP79UnL
/b6DXS4O4GZ6RvdAOcWc
=j+/7
-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/63f4e396-32d5-2a3a-7af7-1154cfa0ed0a%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.