When trying to start Audacity on the newest Tumblweed snapshot both the Packman repos version and repo-oss’s version throw this error. any ideas how to fix?
:Fatal Error: Mismatch between the program and library build versions detected.The library used 2.8 (no debug,Unicode,compiler with C++ ABI 1008,STL containers,compatible with 2.6),
and your program used 2.8 (no debug,Unicode,compiler with C++ ABI 1009,STL containers,compatible with 2.6).
Aborted
Tumbleweed question should go to the tumbleweed section.
Just a guess is the one repos has not caught up to the other and you have mixed version of things.
The price of living on the cutting edge
I had this problem. You can install the one from packman-multimedia repo (or the all of packman repo), should be the one at “Version: 2.1.1-98.1” (see YaST Software - versions tab - you can install from there). It works here.
Thank you. not sure why zypper dup didn’t update it though… i will call it a fluke though.
Will be moved to Tumbleweed, … (for the benifit of others) and is CLOSED for the moment.
Moved from Multimedia and open again.
Welcome. Exactly, ithe faulty oss version installed on update even though I have packman repos at higher priority (lower num’s). There will be a reason, but hey life’s too short and it flukes rarely. 
Audacity’s mess returned with today’s snapshot update (for me this updated yesterday’s snapshot and today’s in one go). A zypper dup would have produced a vendor change packman –> tumbleweed oss and a downgraded Audacity version possibly to fix the previous problem, so I did “zypper up” to avoid that vendor change.
However packman’s version then failed to open with the above fatal error! So I ran “zypper dup” to install Tumbleweed’s oss version. Starting by terminal, Audacity opened with a load of error messages (not fatal)! Tried to load mp3 file, and as expected it failed with a not-built-for-that-type message.
I decided to re-install packman’s Audacity using YaST as before. Surprisingly it opened i.e. no fatal message. Loading mp3 file and playback worked fine.
It’s irritating but not something I use daily, so I’m not in a hurry to do research and analysis of the issue.