How do you want to handle ticket, bug tracking? Forum only?
Adding unsolved stuff to [url=https://www.whonix.org/wiki/Dev/Qubes]https://www.whonix.org/wiki/Dev/Qubes[/url]?
Use phabricator?
https://phabricator.whonix.org/tag/qubes/
Created the first one that I think that is quite important, but not so easy to implement.
forward randomness from /dev/random to VMs in Qubes:
https://phabricator.whonix.org/T31
check if the haveged entropy gathering daemon passes entropy tests in Qubes:
https://phabricator.whonix.org/T32
Important! I will get back to you on these.
Thanks Patrick! 
[quote=“Patrick, post:2, topic:769”]check if the haveged entropy gathering daemon passes entropy tests in Qubes:
https://phabricator.whonix.org/T32[/quote]
Please check my pastedump links. All tests were done inside the same Whonix-Workstation AppVM, based on nrgaways template.
Haveged off:
http://pastedump.eu/bTJwjRHX
http://pastedump.eu/lfzalBt8
http://pastedump.eu/gX0j3mvc
http://pastedump.eu/4rJEnrCj
Haveged on:
http://pastedump.eu/F7LKfUjn
http://pastedump.eu/nFacdE1x
http://pastedump.eu/fT0fJl6e
http://pastedump.eu/6DgREzsB
Thanks, Qubonix!
Since pastedump will purge sooner or later these results, it would be better to have them on the wiki. Could you add them please to either
I cannot comment on how bad the failed tests are. No idea if that’s serious or not at all. If you re-run them a few times, it could be that they’re all passed?
Whatever that would mean…
When we have them on the wiki, maybe WhonixQubes could contact haveged’s developer and ask for its view?
Great!
But how do you suppose how to track bugs generally?
What about having a topic “Qubes + Whonix: Bug Tracker” that is pinned and closed by default, that links to phabricator Qubes component? Similar to the other “Qubes + Whonix:” topics.
I mean, if we discuss all sorts of specific bugs as well as the bug tracker generally here, it’s going to get really too crowded/confusing in this thread.
[quote=“Patrick, post:5, topic:769”]Thanks, Qubonix!
Since pastedump will purge sooner or later these results, it would be better to have them on the wiki. Could you add them please to either
I cannot comment on how bad the failed tests are. No idea if that’s serious or not at all. If you re-run them a few times, it could be that they’re all passed?
Whatever that would mean…
When we have them on the wiki, maybe WhonixQubes could contact haveged’s developer and ask for its view?[/quote]
I have them set to purge after a month’s time, but yes, I can move them onto the wiki. I’ll put them in both sections, we can hash out where it belongs most after the fact.
If you constantly do tests, you will get between 0 <= x <= 2 for tests failed, at least in the 30+ tests that I did.
edit1: I will add it to the dev/entropy page, seeing as how I do not have permissions to create pages
edit2: I’ve submitted the update to the dev/entropy page, just waiting on authorization
edit3: I’m not used to wiki edits, so I’m not sure how to create a collapsible box. I have the test results saved as text files up until I figure it out.
Yeah. I get you. This one specific thread is obviously not a monolithic place for hashing out the details of individual Whonix Qubes bugs. Rather a meta-conversation about the concept of Whonix Qubes bug tracking, where you cited examples.
Are we exclusively talking about “bugs” or does this also include other formal “issues” as well, like proposed features, code and architecture development, etc? I’m guessing so, based on other issues I’m seeing on Whonix Phabricator. Would probably be best to use a more general name, like “Issue Tracker”, so as not to limit usage/thinking to just “bugs”.
I am for the idea of using the Whonix Phabricator system with the “Qubes” tag and other relevant tags.
I just “joined” the Qubes project/tag in Whonix Phabricator, so hopefully that will email me notifications when activities happen with the Qubes tag.
My only real concern is wanting to keep things accessible for others, like especially @nrgaway.
So it would be good to know what @nrgaway’s preferences are as well.
I guess I could also manually mirror issues between the Whonix Forum and Whonix Phabricator as well, for wider accessibility to others.
But, yeah, I am personally for using the same Phabricator issue tracker system as general Whonix OS.
Yeah. This makes sense to do something like this. I will implement.
Yes, not just bugs. Also features. So talking about “issues” or “tickets” makes more sense indeed.
E-mail notification works for me so we should be able to get it to work for everyone.
Test-wise created ⚓ T33 test phabricator notification - please check if you got notification.
[quote=“Patrick, post:10, topic:769”]E-mail notification works for me so we should be able to get it to work for everyone.
Test-wise created ⚓ T33 test phabricator notification - please check if you got notification.[/quote]
Did not get an email notification.
Checked my email address and account settings. All generally look good.
I did successfully get an email notification when I responded to the ticket.
Actually, I just noticed the “Qubes” project was not in a “Watched” state for me.
So the ticket was “Subscribed” but not “Watched”.
Checking “Watch” gave a prompt which said I should get email notifications now.
Hopefully this “Watch” status will now push email notifications to me now for the “Qubes” tag.
Regarding this…
Are public users able to create a Whonix Phabricator account and initiate a new ticket without hitting a moderation wall before this point of initiating a new ticket on a new account?
Created a new ticket:
https://phabricator.whonix.org/T34
Got notification for that?
Otherwise we got to figure out how. Should all be possible with the bug tracker. Just need to learn it. They got a support channel:
irc.freenode.net #phabricator
Anyone can sign up and post. No moderation queue. They should also be able to post new tickets, but it’s untested. Please create a new ticket for testing. When that user functionality is tested, i.e. from user’s perspective, I can promote you to admin so you can rename tickets, change status, close, whatever, etc.
[quote=“Patrick, post:13, topic:769”]Created a new ticket:
https://phabricator.whonix.org/T34
Got notification for that?[/quote]
Success. Yes. Got email notification.
Ok.
Tried to create a new ticket. Got the following error page after filling out form and clicking “Create Task” button.
https://phabricator.whonix.org/maniphest/task/create/
Unhandled Exception ("PhabricatorApplicationTransactionValidationException")Validation errors: - The selected edit policy excludes you. Choose a edit policy which allows you to edit the object.
Tried multiple times, with and without JavaScript. Same error occurred.
Confirmed.
Upstream issue:
maniphest lacks secure policy setting for creation of new tasks:
https://secure.phabricator.com/T6860
Relaxed policy. Normal, non-administrator should now be able to create new tickets. Please test.
Tried to create a new ticket again. Failed. Got the same exact error.
Unhandled Exception ("PhabricatorApplicationTransactionValidationException")Validation errors: - The selected edit policy excludes you. Choose a edit policy which allows you to edit the object.
Tweaked some more settings. Now I tested it myself. Should be definitively fixed by now.
Just noticed this topic 
Since qubes-whonix is its own package now; why not use github issues. That would make most sense to me.
Github didn’t scale for a distribution scale project (Whonix). Github doesn’t support roadmaps referencing tickets that are in different repositories/projects. Neither adding tickets to more than one roadmap is supported. Possibly you might want to split that package in future.
The two issues I’ve reported aren’t really issues with the qubes-whonix package itself. Rather Qubes specific issues, that upstream is not going to add to their tracker, but that I find still generally important for a security focused operating system:
There is no good solution for backup / restore. Github is proprietary service after all.
Since you both are doing most Whonix Qubes work, it’s up to you.
Failed again on creating new test ticket.
New error type:
https://phabricator.whonix.org/maniphest/task/create/
You Shall Not Pass: Maniphest You do not have permission to edit task projects. Users with the "Can Edit Task Projects" capability: Administrators can take this action.