Thu, 21 Mar 2024 07:10:58 +0900 Masaru Nomiya <nomiya@lake.dti.ne.jp> :
Hello,
In the Message;
Subject : Re: Solved!, but.... (Was: Re: Audacity VS 'locale'?) Message-ID : <20240320075838.04acbf8a6cc95191be268827@trixtar.org> Date & Time: Wed, 20 Mar 2024 07:58:38 -0400
[BTF] == bent fender <slowroller@trixtar.org> has written:
BTF> Wed, 20 Mar 2024 12:33:11 +0900
MN> > Please show the message when you start audacity in the terminal.
BTF> There is no mesage and no audacity, sometimes a microsecond BTF> flash of the audacity splash-screen near the very end of the launch BTF> attempt and that is all.
Ah, I UNDERSTAND!
If you had written about this phenomenon, you could have solved it earlier.
If I had known about it maybe. I remember seeing that Audacity alert sometime in the past 12 months, AND my reaction would have been to 'Continue' and not enable bad plugs. I may be overqualified to be a dev but I ain't stupid :-) As noted earlier I did try to do a fresh TW install on my desktop to see if Audacity would work on it like it did on th elaptop fresh-TW hours earlier. *The entire TW install failed* (a first for me): https://paste.opensuse.org/pastes/fb23086139a5 I could do a fscheck with a fix but don't know if that'd be the best prospect of saving 1-1/2 hour of my time put into the install.
Anyway, you've got a plugin issue. That is, Audacity loads plugins at startup, but some of them are faulty and stop launch.
The solution is this;
$ rm -rf ~/.audacity-data
Someone (maybe you) had suggested that one before and it didn't work then or now. Carlos' "audacity --test" produces a splashflash and no Audacity or anything else. I also renamed these to no effect (just get a splashflash): .config/audacity/pluginsettings.cfg .config/audacity/pluginregistry.cfg