Script dialog's Add button freezes (OBS 25.0.8 64-bit)

[metal450]

I'm running OBS 25.0.8 64-bit (the most recent version) on Kubuntu 20.04 (KDE Plasma 5.18.5, Qt 5.12.8, Kernel 5.4.42). It was installed via the official repo, ppa:obsproject/obs-studio.

Anytime I click the "Add" button in the "Script" dialog, the UI freezes & needs to be force-terminated. All I do is:
1. Launch
2. Tools->Scripts.
3. In the Script dialog, click "+."
4. The background of the button lightens as if it's being pressed, but nothing else happens. Attempting to close the Scripts dialog now produces "Application obs is not responding," & has to be terminated.

To me this seems pretty clearly like a bug, but I've tried reporting it twice on their github & the developer just instantly closes it & makes some very dismissive comment. Last time he told me "github is not for support," and that if I want support with my issue, I should post on the forum.

Is this not a bug? Launch, access one menu, & it instantly crashes?

 

[Tuna]

You have installed the Linux browser plugin. And the bug lies in that component and is known. And it is actually left out of the official PPA for that exact reason. So I have no idea why you would have it installed other than a left over from a previous install or if you have installed it manually.

 

[metal450]

Yep, I have installed the browser plugin. So is it not possible to have both the browser plugin and scripts? Or you have to remove the browser plugin, add scripts, then re-add the browser plugin each time?

 

[metal450]

Nevermind, I got it. Remove the browser plugin, add the script, re-add the browser plugin & it works. Thanks.

Kinda surprising the developer on github didn't know about it if it's a known bug, but 4 weeks of trying, glad to have a solution :)

 

[Tuna]

Basically the browser plugin interferes with all GUI dialogs if you are unlucky.

Don't be too upset that your tickets get closed on the tracker. They really try to focus on code/development there. they get flooded with support requests daily - so they can sound a bit harsh because they try to be strict.

Use use the forums or discord for support. If people are confident it is a real bug one can move it to the tracker with some detailed report/explaination.

 

[metal450]

Understood, but for what it's worth, I'm very active on github and have worked with developers on dozens of projects. I'm also the author of a free/open-source project myself, which while not as big as this, has had tens of thousands of users that I personally support. It still doesn't seem necessary to instantly close every ticket with a short/dismissive comment.

(I reported this crash for the first time a month ago. They told me to "use the official repo" & closed the ticket. I said the behavior is the same. They told me to update my post to follow their template - it had all the identical information, I just didn't use their formatted headers precisely. I reformatted the same content into their requested headers. They never replied again. So a month later I opened another ticket. They said "Update to the most recent version" and closed it. I already was using the most recent version. They told me to go post on the forum. Note that none of their replies actually even addressed the issue.)

In any case, thank you for the reply - I'm glad to have it figured out, & I've definitely learned my lesson: even if I find something that seems like an obvious bug (like a crash), don't report it to them on their bug tracker :P