File browser window invisible on OBS 31.0.1 & linux mint 22.1

C

crayzcrinkle

Member
I have OBS Studio 31.0.1 (not flatpak)
Linux Mint 22.1
Basically there seems to be a bug or something, when trying to open a file browser window (specify image path, select sound/video source etc) the file browser window opens completely invisible. Spent ages with the OBS Discord helpers and they are convinced its a system issue, but if it was a system issue I think it would affect more than just one program. Theres no error in the OBS log, and the window can be ended from the task bar and then the rest of OBS is usable again.
Any other windows in OBS open fine, but the file browser one does not and the behavior does not exhibit in any other program.
Specs: 7900x, 96gb ram, NV 4080 Super
Linux mint uses cinnamon I think

Anyone know what to do? What to try?
If I can't solve this I may have to go back to crapdows 11!
 
Cassual54

Cassual54

New Member
I have the exact same issue. I'm not using Linux Mint, but EndeavourOS with the Cinnamon desktop (so Cinnamon could be the culprit).

I've been using the flatpak package of OBS for a long time without any issues, but the last update doesn't let me browse files when I try to add an image source or even export my settings. Downgrading to the previous version fixes the issue, but I hope I won't have to live in 30.2.3 forever.
 
A

am53n8

New Member
I think I found something?

The flatpak version and a clean install of mint both work, so narrowed it down to my install.
Found these 2 threads (https://forums.linuxmint.com/viewtopic.php?p=2562424&hilit=obs+studio#p2562424 & https://forums.linuxmint.com/viewtopic.php?t=439301) and managed to narrow it down to my user account. (it works fine both when launching as sudo or from a new user account)

This brings us to /home/<username>/.config/obs-studio. Made a backup and started deleting files to narrow it down more. After deleting user.ini and opening obs I can suddenly use the file browser again! Selected my scenes from scene collection and it still works. Select my old profile and... it's broken again. Restored the backup, create a new profile and it works! Switching to the old one breaks it again, while switching to the new one it's fine. This leads me to believe something in my profile is wrong, but I have yet to figure out what exactly.

Unfortunately both creating a new profile and deleting the user.ini results in having to change all settings, docks, etc again. Please keep this in mind before randomly trying things or blaming me. The browsing issue seems to be solved for me now.

Uninstalling obs also doesn't get rid of the .config folder, the same profile works fine in both 30.0.2 and 30.2.3

I wrote this entire thing down so someone can check my work and maybe it helps someone else. Also because at this point I do not believe the issue is Mint/Cinnamon. Is it obs? I don't know.

Good luck.
 
A

AaronD

Active Member
am53n8 said:
After deleting user.ini and opening obs I can suddenly use the file browser again!
Click to expand...
*.ini would be a text file, readable with countless text editors. Pretty much every graphical OS has a graphical one, and of course there's the classic command-line text editors like vim, emacs, and nano.

Anyway, since you've narrowed it down to that one file, the next step is to start messing with its contents...
Back it up, of course, but you already know that. :-)
 
Cassual54

Cassual54

New Member
I'm using the Flatpak version of OBS, and I noticed that using a fresh profile had the file browser working, looking for images and everything. The moment I signed in my YouTube account, it stopped working again. I could have something to do with that service integration, just based on my experience.
 
A

am53n8

New Member
Apologies it has been a while, other things got in the way. I did try looking into it a bit more, and ended up being able to break a fresh install in under 2 minutes. Logging into twitch and adding the twitch stats or stream info dock reliably broke it for me.

Anyway 31.0.2 and 31.0.3 are working fine, whatever the issue was it seems to be fixed now.
 
You must log in or register to reply here.
Top