Bug#765341: more information

[Martin Steghöfer]

Hi Klaumi!

Thank you for reporting the issue(s)!

I have to admit that I'm a bit lost in your tale. Am I right that what 
you are reporting are the following 3 issues?

1. "assert !ms_clipboard failed in wxClipboardSync" in various occasions:
a) When opening a certain project (all project in which you had applied 
LV2 plugins before?)
b) When playing the current selection
2. Small buttons in the project recovery dialog
3. Segmentation fault on applying LV2 plugins

Regarding 1: I am unable to reproduce this with any of my projects, 
neither by doing (a) nor (b). Maybe you could share a project that 
triggers the failure?

Regarding 2: I've observed this. It's a bug of wxWidgets 3.0.x. I've 
filed it in the wxWidget upstream tracker, but it doesn't seem to 
receive much attention:
http://trac.wxwidgets.org/ticket/16440
Maybe you can report being affected by that problem, too, so they raise 
its priority. If they don't fix it, we have to place some kind of 
workaround in Audacity.

Regarding 3: I was able to reproduce that crash in Debian unstable. 
However, I could not reproduce it in Ubuntu (using the exact same 
audacity package with wxWidgets 3.0), which I found weird. Maybe there 
is something more to it than Audacity's problems. I'm looking into that.

Cheers,
Martin



El 16/10/14 a les 13:36, Klaumi Klingsporn ha escrit:
> So, from my point of view as petty user, it would be better to link
> audacity against the old library for jessie. I know about the
> wxWidgets-transition, but the old version works works, upstream is
> working on the transition to wxwidgets 3.0 as well, why pressure the
> transition at this point?

I don't think wx2.8 will be around in Jessie. For example, there are 
many, many packages that were designed to run with FFmpeg, but in Debian 
they have to be ported to libav. For wxWidgets 2.8 it's much less 
serious, most packages have made the transition cleanly some time ago, 
it's really only Audacity that still has slight problems with wx3.0 - 
which is mainly because the transition was completely ignored during 
several months. Also, the transition isn't really "pressured" (as you 
say), the corresponding bug was opened 5 months ago.

So for now, let's try to get those issues fixed as soon as possible!