How to file a helpful issue
The problem you're addressing (if any)
Even since 4.3 came out, there have been at least three or four separate bugs that completely broke qubes-global-config for me, on security-testing repos. Due to the release cadence of dom0 packages, it often took a couple of weeks or even over a month for the utility to start working.
QGC is a pretty important utility, so this has been highly annoying for using QubesOS to say the least. At this point, whenever I need to use QGC I feel like it's a 50/50 chance it's just not going to open after a random dom0 update broke it.
The solution you'd like
Somehow reduce the amount of times broken QGC packages are pushed to stable/sec-testing. Probably by writing more tests or perhaps by making it so that certain pages in QGC can error out and not load while keeping the rest working.
Completion criteria checklist
(This section is for developer use only. Please do not modify it.)
How to file a helpful issue
The problem you're addressing (if any)
Even since 4.3 came out, there have been at least three or four separate bugs that completely broke
qubes-global-configfor me, onsecurity-testingrepos. Due to the release cadence ofdom0packages, it often took a couple of weeks or even over a month for the utility to start working.QGC is a pretty important utility, so this has been highly annoying for using QubesOS to say the least. At this point, whenever I need to use QGC I feel like it's a 50/50 chance it's just not going to open after a random
dom0update broke it.The solution you'd like
Somehow reduce the amount of times broken QGC packages are pushed to stable/sec-testing. Probably by writing more tests or perhaps by making it so that certain pages in QGC can error out and not load while keeping the rest working.
Completion criteria checklist
(This section is for developer use only. Please do not modify it.)