-
-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GUI bugs on Manjaro (x11 related?) #1910
Comments
This is definitely a really bad idea as it will most certainly break your install. I don't use Arch btw, but I'm sure they will have some guidance on how best to remove/replace system packages. |
Yes. |
Could you try building plugdata from source? It's possible that there are some library incompatibilities since Arch is a rolling release (so it's possible that the packages we originally linked against have been updated), and you're using a variant of Arch. Paste this in your terminal and wait:
|
Ok i installed it that way (cmake --install) without any change. |
Hello,
i don't know whether this is caused by my OS or plugdata, but i'm having various problems with the GUI in the standalone and vst3 application (in Renoise), like copy and paste not working, objects being created in places where they're not supposed to (used to be somewhere far off the visible part of the canvas, now it's always at the left edge), sliders not updating their position, when the window is open but not in foreground, and the menu and right click menu not opening. Sometimes it crashes the DAW and sometimes objects don't work as they should (i think).
It's the same for plugin and standalone versions.
The Terminal shows various "JUCE Assertion failure in juce_Displays.cpp:..." sometimes
I have tried all the versions from the AUR with no difference and have copied the files from the arch release on https://github.com/plugdata-team/plugdata/releases/tag/v0.9.1 page into /usr/bin etc, which worked fine for a month, but after a recent system update it's returned to being buggy and it didn't work again this time...
If anyone had any clue what may be the cause it'd be great
The text was updated successfully, but these errors were encountered: