On Wed, Jul 31, 2019 at 09:04:24AM +1200, Olly Betts wrote: > On Tue, Jul 30, 2019 at 01:57:08PM -0400, Scott Talbert wrote: > > 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). > > I've just run a "bts" command to mark all the open "please rebuild" bugs > as blocking the transition bug. > > > On Tue, 30 Jul 2019, Tobias Frost wrote: > > > 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.
That would be very welcome. > Although forcing X under GTK3 is a workaround, it's really no worse than > sticking with GTK2 - the GTK2 build only works because GTK2 doesn't > support Wayland directly at all, and so there use of X is implicitly > forced. Yes, I somewhat agree. However, it is a bad user experience when programs do segfault on wayland especially as this is now the default in Debian. So I fear it is not ready yet for prime time in Debian, but as we are early in the release cycle of bullseye that might change later, I guess. (For darkradiant, I like to wait a bit more to see how things evolve; see below for a second reason) A quick Thought: Would there be a possiblity to have at least an message printed out on wayland before crashing emitted from wxwidgets? like a warning "you are using GLCanvas under wayland, this app will crash!" The "fixes" in #900768:33 are merely workarounds IMHO. As it seems to be effort to make it properly, I think it is not really good to make dozens of packages carry around the workarounds as they will likely survive a proper fix later (as nobody tends to track such things later) BTW The other issue I mentioned is not related to wayland but to having a QHD+ display… I need to pinpoint that further and will then file a bug accordingly, however I'm not sure against which package. This is a regression which makes darkradiant* unusable, so I will need to postpone a fix for this bug, unfortunatly. * one have to expect that someone using darkradiant using a QHD+ or 4K display, because of the nature of darkadiant. -- tobi
