Bug#933419: darkradiant: Please rebuild against wxWidgets GTK 3 package

[Scott Talbert]

On Tue, 30 Jul 2019, Tobias Frost wrote:

> (I guess more than 10 packages are affected, so I guess this qualifies
> as mass-bug-filing and should be discussed on devel as recommended in
> dev-rev §7.1. Would be great if you could follow this procedure. Another
> nice thing would be to add blocking indications to the transition bug,
> it makes a bit clearer and might help for peeking for fixes -- this is
> something I found useful when I did the libpng transition. Thanks for
> considering!)

We did discuss this on debian-devel back in November, although technically 
it appears that I didn't mention that we planned to do mass-bug-filing.

https://lists.debian.org/debian-devel/2018/11/msg00551.html

I'll look into adding the blocking indications to the tracking bug, but 
admittedly, I'm not very good with the BTS (and documentation isn't the 
best).

>> If everything seems to be working fine, that's probably all you need to do.
>>
>> There are a couple of known issues:
>> 1) If your package uses wxGLCanvas, this doesn't currently work when running
>> under Wayland.  As a workaround, you can force use of X.  See bug: [2]
>> 2) If your package uses graphics contexts, it may encounter a problem with
>> coordinate overflow.  See bug: [3]
>>
> FTR, darkradiant is also affected by #900678.

I'm not sure that we can afford to wait for a fix for #900678.  There is 
no movement upstream on that and it's more than just a fix - rather 
wxGLCanvas needs to be ported to something like EGL instead of GLX.  I can 
send you a patch that adds the workaround to use X for you to consider.

> It might be also affected by [3], how to test that?
> There is at least another issue: On my Tuxedo with a QHD+ display, one
> area in the windows is no longer using the whole area, but only a
> fraction of it. I see that also in slic3r and slic3r-prusa, but I did not
> test yet if it requires a QHD+ display to trigger the bug.

To be honest, I'm not sure how to test that one.  Perhaps we could ask the 
kicad developers.  They seem to have switched to the GTK 3 build at least 
on Fedora so perhaps they have figured it out.

Thanks,
Scott