Description of problem: Using latest Ardour on Fedora, it works until you click a plugin, then most of the UI goes unresponsive. See thread over there - https://discourse.ardour.org/t/ui-partly-frozen/111870/2 Other users have reported it it says. Version-Release number of selected component (if applicable): How reproducible: Very Steps to Reproduce: 1. Open new window with Ardour plugin, or new Brave browser Window 2. Close it 3. Try and use some UI controls in the main window Actual results: The widgets don't respond Expected results: The widgets do respond Additional info:
Wayland is just a protocol specification in XML and the low-level C library that deals with the protocol. This issue here is a bug not with the protocol itself but with either your compositor, desktop environment's implementation of the Wayland protocol and surrounding functionality, or Xwayland. Moving to Xwayland for now,m but please provide a full bug report and not just a link to tan external discourse link, I am not willing to follow discussion on various media, let's keep the information centralized in bugzilla.
Sorry for logging it in the wrong place. Pretty sure I just hit this bug again on Brave browser. Opened a new browser window by mistake. Closed it and went back to the main window, then the button to create a new tab didn't work.
Just tested it again with Brave, and it does seem to be happen each time. The Ardour plugins must create a new window when they pop up in a similar way. Interestingly, I can open a new email window, close that, and Betterbird keeps working. Maybe that's a clue.
Sorry what I am after are the exact steps to reproduce the issue with Ardour (the original issued), typically: Steps to Reproduce: 1. 2. 3.
To be honest, Brave is probably an easier test case. Probably Chrome as well on which its based. As above. However ... 1. Open Ardour session 2. Drop on LSP EQ plugin 3. Double click to open plug in window 4. UI for plugin, and Ardour in the backgroud responds fine 5. Close plugin window 6. Main UI window now doesn't respond fully, most buttons don't work, but keyboard shortcuts do 7. Kill Ardour, reload, and it works again fine Hopefully that about covers it?
Unfortunately, I can't reproduce (I cannot even find that LSP EQ plugin in Arbour's menu). Also opened a new window dozens of times in the Brave browser to no avail either. To rule out an issue with the window manager itself (assuming you're running GNOME Shell as a Wayland compositor. i.e. the default on Fedora Workstation), there are a couple of things you can try: 1. Disable all extensions in GNOME Shell and see if that helps 2. Try to reproduce with another Wayland desktop such as KDE Plasma Wayland for example
Very weird, I've managed to reproduce it having logged in to Gnome in X mode. I also turned off all plugins and managed to get it to do it. LSP plugins have to be installed separately. lsp-plugins.x86_64 1.2.22-1.fc42 copr:copr.fedorainfracloud.org:ycollet:audinux
(In reply to gareth foster from comment #7) > Very weird, I've managed to reproduce it having logged in to Gnome in X > mode. […] right, that would rule out something specifically in Xwayland then. That leaves us with either GNOME Shell or the application itself. If the issue is the same with Brave as well, that means something in GNOME Shell, or rather mutter.
Hi mate, logged in with X org and tried new window in Brave, and it did it again there. If I see anything else do it, I'll flag it up. Wonder if the LSP plugins and Brave use the same UI toolkit or something.
Any chance that you could try to reproduce in another desktop, not GNOME then?
Tried to install that new COSMIC DE, also ran updates as the instructions, noticed it pulled through a Mutter update. Reboot. No COSMIC DE choice on the greeter. Tested this again anyway in GNOME. I now can't make it do it. Seemingly its fixed, and COSMIC DE had failed to install without me noticing, as I now can't remove it. It must have been the Mutter update? I'll do some further work in Ardour and come back here if it stuffs it again. Otherwise, happy days I suppose.
I was thinking more of KDE tbh. Thing is, the X11 support in Wayland relies on Xwayland, which is an Xserver, but also the X11 window manager which is part of the Wayland compositor. Writing an X11 window manager may look easy and simple on the surface, but the devil is always in the details, and X11 window managers play a crucial role in how the X11 applications behave so I prefer to test with long, tested and proven X11 window managers with Wayland desktops such as GNOME or KDE (not that the other -newer- Wayland compositors are "bad" in any way, it's just that they are more Wayland oriented and do not necessarily carry the years of development of the X11 window manager that the two others have).
I did plenty of noodling around with Ardour last night, and it didn't do it again. Also somebody on the Ardour forum thread has piped up saying it was a Mutter bug and has been reverted in Fedora. Sorry if I've messed anyone around on here with this.
No worries, and indeed, that looks like a mutter bug (possibly the window tracker regression that got fixed in 48.3-2). Closing this bug then.