It looks to me like the python-wxgtk and wxwidgets versioning is orthogonal, it's just chance they happen to be similar.
I did try doing a rebuild of the python-wxgtk source package (on my affected machine) to see if that would help, and it's the same behaviour. One thing I forgot to mention, this also affected the last build of 5.0, before 5.0.1. On 17/11/18 5:34 am, Seth Hillbrand wrote: > Am 2018-11-16 12:39, schrieb Carsten Schoenert: >> So downgrading is a bit difficult and right now before the soft freeze >> for Buster not the right way I think. > > That's a fair assessment. I believe the issue is mixing versions. So > an alternate solution is to upgrade both to the 3.0.4 version. I would > be curious to hear if there were issues when both are running on 3.0.4 > as I haven't had any issues in Buster related to this. > > -Seth
