[Solved] Audacity menu stops working in MATE 20.3

[evilmrb]

I have spotted an issue that's causing me problems. I recently upgraded my MATE setup from 20.2 to 20.3.
If I open an mp3 file in Audacity, close it and choose not to save the project, from then on none of Audacity's menu options can be selected with the mouse. Clicking on any item does not result in the sub-menus being displayed. The keyboard shortcuts still work OK at this point. I have had some success in getting it working again by resizing the maximised window but otherwise I have to close Audacity by right-clicking the tab in the panel and clicking 'Close'.
This problem occurs with both the installed version 3.0.2 and an AppImage of 3.1.3.
I am virtually certain this problem didn't happen in 20.2 because I use Audacity such a lot.

Can anybody replicate this and suggest a way forward?

Mark B

[MikeNovember]

Hi,

Try Audacity 3.1.3 flatpak, it runs for me with 20.3 Mate:

Code: Select all

flatpak install org.audacityteam.Audacity

Regards,

MN

[evilmrb]

MikeNovember,

Thank you for your help and suggestion. I tried your idea but it did not fix the issue.

Mark B

[MikeNovember]

Hi,

Sorry for you. It DOES work correctly for me with Audacity 3.1.3 flatpak:
- I import an mp3 file from the file menu,
- once imported I close it without saving the project, from the file menu,
- after that the menus still works with mouse.

Regards,

MN

[evilmrb]

Hi,

I tried again using the old version 2.3.3 from the Mint repos. I have the problem with that too. I am mystified because I have been using Audacity on my entire music collection and never had this problem before the 20.3 upgrade. Also, since upgrading to 20.3 the panel at the bottom of the screen often vanishes and I'm unable to navigate my system. Can someone please advise me how to turn this into a bug report? I've signed up to github (and what a performance that was!) and I have no idea how to proceed.

Mark

[northcup]

Try Audacity 3.1.3 flatpak, it runs for me with 20.3 Mate:

Code: Select all

flatpak install org.audacityteam.Audacity

Thankyou for this hint. That solve my problems with AC!
greets Klaus

[all41]

Hi,

I tried again using the old version 2.3.3 from the Mint repos. I have the problem with that too. I am mystified because I have been using Audacity on my entire music collection and never had this problem before the 20.3 upgrade. Also, since upgrading to 20.3 the panel at the bottom of the screen often vanishes and I'm unable to navigate my system. Can someone please advise me how to turn this into a bug report? I've signed up to github (and what a performance that was!) and I have no idea how to proceed.

Mark

What Windows Manager are you using
Control Center/Desktop Settings/Windows.
Try temporarily changing to a different wm.

[evilmrb]

What Windows Manager are you using
Control Center/Desktop Settings/Windows.
Try temporarily changing to a different wm.

Bingo!

All41, you are a star. I was using Marco + Compositing. Every other option solves my issue with Audacity so I have switched to Marco + Compton as that seems to be the smoothest option on my setup.

Thank you so much for helping me and teaching me a new thing too.

Mark

[all41]

What Windows Manager are you using
Control Center/Desktop Settings/Windows.
Try temporarily changing to a different wm.

Bingo!

All41, you are a star. I was using Marco + Compositing. Every other option solves my issue with Audacity so I have switched to Marco + Compton as that seems to be the smoothest option on my setup.

Thank you so much for helping me and teaching me a new thing too.

Mark

That's good to here--you're welcome
Could you tell which wm was causing the issue please--
which were you using causing the Audacity issue.
Sometimes you can just temporarily chang wm, and when reverting back
the problem is gone. My guess--you were using Compiz wm

[evilmrb]

That's good to here--you're welcome
Could you tell which wm was causing the issue please--
which were you using causing the Audacity issue.
Sometimes you can just temporarily change wm, and when reverting back
the problem is gone. My guess--you were using Compiz wm

It was in my reply but it was Marco + Compositing that caused me the problem. Compiz was terrible on my machine. I just tried Marco + Compositing again and the problem returned. I will stick with Marco + Compton because that works well. Thanks again!

Mark

[all41]

It was in my reply

Yep. Sorry. Thanks for the info Mark.
Actually I will be picking up my new prescription glasses today.
I've had to rely on these cheap otc readers after a new pup destroyed my others