Open TricksterSam opened 2 months ago
Oh wow, that's definitely strange, thanks for reporting!
Are you installing plugdata through the OBS repository, or by downloading binaries?
It seems like plugdata (for some reason) doesn't have permissions to write to one of it's own configuration files. There is one settings file that JUCE creates to store some window and audio settings, located at ~/.config/plugdata.settings, have you deleted that one as well?
Also, does this also happen with the plugin version of plugdata?
I was using the deb binary and then switched to see if apt would work. I installed pludata-full so I would have the VST plugin also.
I deleted .config/plugdata.settings and .config/plugdata/ and then attempted to launch plugdata. It still doesn't display anything.
At one point the VST plugin would load but not display a GUI. Now, it isn't loading at all. I'm going to have to check the paths again. Will do that later.
I created a test user and they can open PlugData properly. Seems like it must be something in my /home/ folder. Are there any other files that might cause problems? If PlugData is sharing a path to Pd externals, could there be something going wrong there?
After updates and restarts and ignoring it. It now works, but I needed to enable the system title bar in order to move the window around. Wish I had a better report to provide.
After updates and restarts and ignoring it. It now works, but I needed to enable the system title bar in order to move the window around. Wish I had a better report to provide.
Are you using Wayland or X11?
X11
Wednesday, plugdata 0.8.3 crashed in PopOS 22.04 LTS. When I tried to reopen it, a process started and the icon displayed in Dash to Panel, but no window displayed. When I clicked on the icon, it would show a minimize and restore animation but there still was no window. Right-click>Quit got rid of the icon but a process persisted.
I tried reinstalling and hunting down every configuration file I could delete, but nothing changed this behavior.
I then tried launching plugdata with sudo and it worked. It seems I've either found a bug or got some kind of bad permissions settings somewhere. What could be affecting this?
Here are the errors I get from running plugdata without su.
`JUCE Assertion failure in juce_ValueTree.cpp:770
JUCE Assertion failure in juce_ValueTree.cpp:770
JUCE Assertion failure in juce_ValueTree.cpp:770
JUCE Assertion failure in juce_ValueTree.cpp:770
JUCE Assertion failure in juce_ValueTree.cpp:770
JUCE Assertion failure in juce_ValueTree.cpp:770
JUCE Assertion failure in juce_ValueTree.cpp:770
JUCE Assertion failure in juce_ValueTree.cpp:770
JUCE Assertion failure in juce_ValueTree.cpp:770
JUCE Assertion failure in juce_ValueTree.cpp:770
JUCE Assertion failure in juce_ValueTree.cpp:770
JUCE Assertion failure in juce_ValueTree.cpp:770
JUCE Assertion failure in juce_ValueTree.cpp:770
JUCE Assertion failure in juce_ValueTree.cpp:770
JUCE Assertion failure in juce_ValueTree.cpp:770
JUCE Assertion failure in juce_ValueTree.cpp:770
JUCE Assertion failure in juce_ValueTree.cpp:770
JUCE Assertion failure in juce_ValueTree.cpp:770
JUCE Assertion failure in juce_ValueTree.cpp:770
JUCE Assertion failure in juce_ValueTree.cpp:770
JUCE Assertion failure in juce_ValueTree.cpp:770
JUCE Assertion failure in juce_ValueTree.cpp:770
JUCE Assertion failure in juce_ValueTree.cpp:770
JUCE Assertion failure in juce_ValueTree.cpp:770
JUCE Assertion failure in juce_ValueTree.cpp:770
JUCE Assertion failure in juce_ValueTree.cpp:770
JUCE Assertion failure in juce_ValueTree.cpp:770
JUCE Assertion failure in juce_ValueTree.cpp:770
JUCE Assertion failure in juce_ValueTree.cpp:770
JUCE Assertion failure in juce_ValueTree.cpp:770
JUCE Assertion failure in juce_ValueTree.cpp:770
JUCE Assertion failure in juce_ValueTree.cpp:770
JUCE Assertion failure in juce_ValueTree.cpp:918
JUCE Assertion failure in juce_ValueTree.cpp:918
JUCE Assertion failure in juce_ValueTree.cpp:918
JUCE Assertion failure in juce_ValueTree.cpp:918
JUCE Assertion failure in juce_ValueTree.cpp:918
JUCE Assertion failure in juce_ValueTree.cpp:918
JUCE Assertion failure in juce_ValueTree.cpp:918
JUCE Assertion failure in juce_ValueTree.cpp:918
JUCE Assertion failure in juce_ValueTree.cpp:918
JUCE Assertion failure in juce_ValueTree.cpp:918
JUCE Assertion failure in juce_ValueTree.cpp:918
JUCE Assertion failure in juce_ValueTree.cpp:918
JUCE Assertion failure in juce_ValueTree.cpp:918
JUCE Assertion failure in juce_ValueTree.cpp:918
JUCE Assertion failure in juce_ValueTree.cpp:918
JUCE Assertion failure in juce_ValueTree.cpp:770
JUCE Assertion failure in juce_ValueTree.cpp:770
JUCE Assertion failure in juce_ValueTree.cpp:683
JUCE Assertion failure in juce_ValueTree.cpp:670
JUCE Assertion failure in juce_ValueTree.cpp:918
JUCE Assertion failure in juce_ValueTree.cpp:770
JUCE Assertion failure in juce_LookAndFeel.cpp:85
JUCE Assertion failure in FileSystemWatcher.cxx:383
JUCE Assertion failure in juce_LookAndFeel.cpp:85
JUCE Assertion failure in juce_ValueTree.cpp:918
JUCE Assertion failure in juce_ValueTree.cpp:770
JUCE Assertion failure in juce_LookAndFeel.cpp:85
JUCE Assertion failure in juce_LookAndFeel.cpp:85
JUCE Assertion failure in juce_LookAndFeel.cpp:85
JUCE Assertion failure in juce_LookAndFeel.cpp:85
JUCE Assertion failure in juce_LookAndFeel.cpp:85
JUCE Assertion failure in juce_LookAndFeel.cpp:85
JUCE Assertion failure in juce_LookAndFeel.cpp:85
JUCE Assertion failure in juce_LookAndFeel.cpp:85
JUCE Assertion failure in juce_LookAndFeel.cpp:85
JUCE Assertion failure in juce_LookAndFeel.cpp:85
JUCE Assertion failure in juce_ResizableWindow.cpp:244
JUCE Assertion failure in juce_ResizableWindow.cpp:245
JUCE Assertion failure in juce_ResizableWindow.cpp:244
JUCE Assertion failure in juce_ResizableWindow.cpp:245
JUCE Assertion failure in juce_LookAndFeel.cpp:85 `