issues in 3.2

[Drew White]

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.

2. No desktop

3. No taskpar/panels

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

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

6. Has window borders and titles that are too wasteful.

7. Can't change fonts via interface, can't alter appearance to be functional.

[Drew White]

At least I can run things using the alternate consoles in the GUI.

Even though it's a waste of time when you use 5 monitors, it's at least working.... I guess....

[Drew White]

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

Well, at least I have a workaround for this. But it still needs a menu system. 

[Drew White]

KDE crashes EVERY TIME I change the RAM of a guest.

[Drew White]

X is broken.

The upgrade to new version of KDE has destroyed all functionality.

X crashes every 2 seconds.

Kill it, and it just shows login screen, and it's run as ROOT instead of as the user.

[Drew White]

Qubes 3.2 = broken qubes.

I'll list the rest in time, no need to overload you with the bugs.

I wish it was at least tested before it came out to the public though.

[cubit]

2. Jul 2016 08:02 by drew....@gmail.com:

I'll list the rest in time, no need to overload you with the bugs.

Now would be a good time. If you don't make the bugs know they may not be found until after 3.2 is released.

 

I wish it was at least tested before it came out to the public though.

3.2 is only a release candidate at the moment, it is not for public use.

https://en.wikipedia.org/wiki/Software_release_life_cycle#Release_candidate

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

[Andrew David Wong]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

3.2-rc1 is a release candidate. The purpose of having a release
candidate is to test the release. It's available to the public so that
any members of the public who wish to test it may do so. If you do not
wish to test it, you should not do so.

Also, please note the warning on the download page immediately above
the R3.2-rc1 download links:

"This is a testing release. We appreciate your desire to help us test
Qubes. However, we recommend you use a current and supported release
for daily use."

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

iQIcBAEBCgAGBQJXd8iWAAoJENtN07w5UDAwLJQP/0IeneeFDC9HuieomKwehvlM
DGg6wyrJwWI+2yqIeDmIqfxLFikUF8tTYciCdzirBcHKoH8o5znWuZ8J6AoCyHyN
MGpbp1Xrh5RaV5FUG6h8Yn+bhgOHR9I0Hs9T7YpQn7WEBrPzKb1D4ggEaItTHB9X
UFzPwDYHD64Mn8vPo4g9x/UVoetUxmlKyCwt289UvGQgq+W7vaJMYdhesOsYHdHv
LLxrk9s7Z7ODUFlz3+5i3SsIieo0GQLj2JU85/NFau5QpnJkiBZoa8n7jfB0jDSw
JaqNFIw/qF1OaInMnVynjzLjFOYv7vstqZHgtHtbrquViLd/KHCeSK46bffsEF03
O8QSnBc+zdae5ppFrDfdh3LY1p33akTLp7EvOvcX9yerGOhz2+8/5gu3lS+C1XDV
S9c739zFhUNa/qh2ReDbcbP/malEvpXC5SOAhuWkKMy85i6dKm8bcxH0tjDQt6fH
E2RHn7URbCascE05HqlfQW6Ggg7PROKqqdlngUO4kRxdhMR75yh28wYvP6o2oddK
LgHtYvqbGMknB+7L++dqgLX4g1EmWjBaeEmQMQ70dNRav736IBUv5IaMrqsdRs1d
zfjxDGTCVRwoOqSiDe8D66lGbyu9w0OwPvesJb8wyMTJapVkzjq8qU8yWic571Kd
B/RWG5Go1a34yQ/uFfVB
=sEBX
-----END PGP SIGNATURE-----

[Drew White]

hi folks,

Thanks for the info, I thought it was already a release because it was already now out there and available.

On Saturday, 2 July 2016 23:53:47 UTC+10, Andrew David Wong wrote:

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

No problem, and excellent. 

 

> 2. No desktop 3. No taskpar/panels

Sounds like this is already being tracked here:

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

This bug is only a small one, I don't think it's really a big bug at all.

Is it the normal way to set it to text login before starting X?

Or is there something else that needs to happen?

 

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

Yes, incorrect terminology, I apologise, didn't know how else to explain it, but it's explained in the bug tracking.

 

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

 

[Drew White]

On Saturday, 2 July 2016 23:58:56 UTC+10, Andrew David Wong wrote:

3.2-rc1 is a release candidate. The purpose of having a release
candidate is to test the release. It's available to the public so that
any members of the public who wish to test it may do so. If you do not
wish to test it, you should not do so.

Also, please note the warning on the download page immediately above
the R3.2-rc1 download links:

"This is a testing release. We appreciate your desire to help us test
Qubes. However, we recommend you use a current and supported release
for daily use."

Didn't see that, because I just went directly to the download area.

I went to www.qubes-os.org

Then followed the download link, it currently says 3.1

Then found the link to the FTP directory.

Used that, then downloaded.

Couldn't see anything for 3.2 there.

If I scroll down I can see it there for the download.

But due to the design of the website, it doesn't show everything

immediately, and I already knew how to get to the directory, so

I did.

Such as life. I know now, and will keep it in mind to check for the

future times I download and such. Thanks.

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

[Drew White]

On Tuesday, 5 July 2016 19:41:53 UTC+10, Andrew David Wong wrote:
> 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

From a UX perspective, it's a simple thing to fix.
All you have to do is enable it and have it operational.
the only other way to do it from KDE is to open the run widget.
But when you have a bug in KDE where you can't do anything and have no terminal access, the 'run command in' is most beneficial.

As for not having them showing, easy as, if that's what you want.

So many things I see that you all are talking about doing, I see so many flaws, and so many good things too.

In MOST cases, you need to build it in for both ways around. To have and not have. To include and exclude. To show and hide.

I'm a functional person, not a wanky interface person. I'd rather have the run as there, that way I can just use that instead of having to open a terminal.
I normally have 15 terminals open anyway. several in Dom0, several in the NetVM, and at LEAST 1 in every other guest that I'm running.

Sometimes takes me 5 minutes to find a terminal to run something in, or just to get to the desktop space to get access to a terminal.. I'd rather just click on the Qubes Manager, Right click on Dom0, then run as. Only because often the run widget doesn't function the way I want it to with many things.

The latest KDE isn't built for functionality, it's built for wankyness. that's my opinion from seeing it the way it is these days, in Qubes 3.2 at least.

Please remember this... "If it ain't broke don't fix it"

Qubes 3.1 still has a tonne of bugs that aren't fixed, and that's got a non RC version there in the downloads... Still with all the bugs...

Will 3.2 this time be fixed before moving on to a new version?
Will all the critical and important bugs that cause crashes be fixed before version 4 comes out?
Because there are still bugs in Qubes stemming from version 2.0 that are still there.

So I'm just curious.

WARNING: Don't misunderstand the way that all may sound. It's not actually sounding the way you may read it. Just because there is no vocals here means that things will be read the way the reader wishes to read it, and not be read the way it is intended to be read.

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

[Andrew David Wong]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 2016-07-05 06:01, Drew White wrote:
> 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?
>

Priorities, and the need to discuss and plan things before taking
action.

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

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?

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

iQIcBAEBCgAGBQJXfRwvAAoJENtN07w5UDAwB9gP/1LjjLL9/a3S3JUaV2JTTyp9
ii/QuqQLhDJTkesuMYofrqVCLWL23sUOhEk/9SJvsiVqL0owzETq9DVkWtAR5vgN
dc/iz1kPAjKkXPCt5lghyIkiLc2ybqtcFJHkXBNwjUX5v9/qvDntmoZYOLYwIKRn
LgGlFc3lXFry/IldUkdDM39XtYECOLyg/ieV1gtNzUzsUnO/IPWzRxNhWbxQHO/L
W+MKq8G/crQgBzj/DZ9lXWp1KPQM6QAmxrGjOZ11NHR1dEimvu8761mmiXbgzRhe
8Dne2LCmW4k0yLWewD8yh+wqJjKUsG4PPtFBz0Mnc0ST+eRMYTYlH3XHzUJKzV4p
i65PPF7WJpEGFT/+TbeV02Lm5A4edpQoN1Yb6bINaGNS5Ee9rk2UR3WaKnnHSnu5
8mvPOvVhcu2wTMSg4xHKVyc1r8GXRDf5U1iZz7+YHPu2uW/1lfXJX+oM/85etaW5
n4eRm1gToDJzjloNAah9ms8buPWmQa0bD89rXb5Wz4bH9yIenhzgqvPQw68M7pR7
ctTB3CtxaFoLHMS7vIwsrhzNsZ+qY5K0KQwAJG8U4y/Yayf6rG1wWuRAa7gsqE8i
WsF/nrudxze33mlkP5zOYwXCcUHTczfzO0DuyqS7LnWbl9whxrHLb3Nyje5SQ/2t
G1+pfrJ93aJOcONqrioQ
=ei53
-----END PGP SIGNATURE-----

[Eva Star]

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

It's not rational to lose developers time on new features at old QM,
because of new Qubes Manager required to be implemented from scratch.

[Drew White]

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.

[Iestyn Best]

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

[Drew White]

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.