plugdata doesn't load in the example host

[edwloef]

When trying to load plugdata in the example host (cargo r -- -b /usr/lib/clap/plugdata.clap) it fails to show the plugin GUI:

os error at /home/edwin/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/winit-0.30.12/src/platform_impl/linux/x11/window.rs:533: Xlib error: X error: BadAtom (invalid Atom parameter) (code: 5, request code: 18, minor code: 0)

Every other plugin I've tested works, I've verified this happens on two separate machines, and I'm also encountering this issue in my own host implementation. plugdata.clap loads fine in REAPER, so I can't tell to what degree the plugin is at fault.

[prokopyl]

That's weird, I can't reproduce this on my end (using PlugData 0.9.2 on Fedora Linux 43).

From your error message I'm assuming you're using a Linux-based OS, but which one/distro are you using specifically, and with which PlugData version?

[edwloef]

I'm on on PlugData 0.9.2 on Arch Linux. In Sway with Xwayland it gives the error message when trying to open the window, in XFCE with X11 it gives the error message when trying to close the window.

In Sway with Xwayland I've minimized it to calling create and then opening a window, embedding the plugin isn't even necessary to trigger the issue. Calling create after having opened the window works around it, but of course that isn't a real solution because you then don't know how large the window should be before opening it.

[prokopyl]

I'm having a hard time to reproduce this still, short of installing a new Arch VM to add Sway and XFCE and try it on there (which is most likely what I'm gonna do anyway if this issue persists).

Clack itself is completely ignores everything related to the UI and windowing system, so unless it's not passing the handle correctly, it's most likely something in the host implementation. And since you mention reproducing this in both your own host and clack-host-cpal, I strongly suspect it's something that is related to how winit does things (it is the one raising the error after all).

Maybe a winit update helps things? But if not a winit debugging session is probably gonna be necessary.

[edwloef]

Alrighty, I'll open a pr to "fix" the example host once I figure out wtf is going on. Could totally just be my setup though, I have no clue.