OBS closes with no error reports in log when I click ANY button that browses files.

[Corbent]

Operating System Info

Other

Other OS

Arch Linux

OBS Studio Version

30.1.2

OBS Studio Version (Other)

No response

OBS Studio Log URL

https://obsproject.com/logs/MIsqlvBfBge3uSd5

OBS Studio Crash Log URL

No response

Expected Behavior

When I click a browse button (...) like inside "Remux Recordings" or the filepath for a media source it should open a dialog to browse files.

Current Behavior

When I click a browse button anywhere, OBS closes with no useful report in the logs.

Steps to Reproduce

1. Just click a browse files (...) button anywhere on the program. Plenty to choose.

...

Anything else we should know?

Guess it could be something external to OBS, yesterday it seemed to be working fine. The main difference is that today I tried to switch back to X11 because of that idiotic problem with the global hotkeys and it started happening, but now it also happens in wayland.

I have tried to delete the entire config folder (in fact this log I shared comes from a pristine installation of OBS), I have tried to reinstall both master branch and 30.1.2 of OBS, it's all the same.

It really is very annoying that the logs don't tell why in God's name it's closing.

[Corbent]

Something new. Tried running OBS straight on the console, instead of the App menu. When it closes I get the message:

zsh: segmentation fault (core dumped) ./obs

EDIT: Probably caused during recompilation of the source code?

[Fenrirthviti]

Please provide a gdb backtrace of the crash.

[tytan652]

22:48:02.303: OBS 30.1.0-196-gf60d6bcfe (linux)

You are not running OBS 30.1.2, but the master branch (196 commits to master since 30.1.0 when I write this).

[Corbent]

22:48:02.303: OBS 30.1.0-196-gf60d6bcfe (linux)

You are not running OBS 30.1.2, but the master branch (196 commits to master since 30.1.0 when I write this).

In the "anything else we should know" section I mentioned I tried both.

And here's the backtrace. First time using gdb so I hope this is what you are asking for:
https://pastebin.com/0u4NbRDE

[tytan652]

In the "anything else we should know" section I mentioned I tried both.

Log and given version were mismatching, but this is not a problem for this issue.

---

Looks like an issue more on the KDE Plasma (kwidgetsaddons) side 🤔 and since Plasma (Qt platform) doesn't use Portals outside of Flatpaks for the dialog.

Arch Linux GNOME works fine, the only difference that may matter is what handles the dialog.

[culebrasolida]

I'm also facing the same issue

[tytan652]

I forgot to say it explicitly, report the issue to KDE Plasma, if both release and master on Plasma cause the crash this is unlikely to be mainly OBS Studio fault.

[Corbent]

Got it. Thank you for your help.

[Corbent]

You were completely right! I downgraded kwidgetsaddons and the problem is solved! I need to learn to use this debugging tool because it would ahve saved like 3 invaluable hours of my life last night, I am on to stream tomorrow night.

[YanEx13]

Same problem in OBS Flatpak, in RHEL 9.4 KDE

[GuardianLiarus]

Facing the same issue wether it's flatpak or not, same for a friend on arch

We're both using KDE6

[Corbent]

As I mentioned, as a temporal workaround see if you can downgrade the kwidgetsaddons package.

6.1.0-1 on Arch works fine for me. I successfully made my first live stream last night. I am very happy.

[tytan652]

Messages indicating that you also encountered the issue are not helpful.

Nobody seems to have reported the issue to KDE and posted the link here, the issue will not get fixed if no Plasma user report the issue.

[Corbent]

I tried. But I don't even know where to file my report.

I went here:
https://invent.kde.org/frameworks/kwidgetsaddons/-/issues

Which is the source for kwidgetmodules, went to issues, but trying to create one requires KDE Identity which I don't have. So I suppose this is for internal use.

[GuardianLiarus]

I tried. But I don't even know where to file my report.

I went here: https://invent.kde.org/frameworks/kwidgetsaddons/-/issues

Which is the source for kwidgetmodules, went to issues, but trying to create one requires KDE Identity which I don't have. So I suppose this is for internal use.

I created an issue on the KDE bug report forms, with the help of OBS friends!: https://bugs.kde.org/show_bug.cgi?id=487247

[Corbent]

Thanks!

[tytan652]

I saw some of you showing that it happens in the Flatpak, which is weird since the Portal should be used and not kwidgetsaddons directly (so not the same issue/crash).

It makes me question if KDE stack is doing something wrong in a Flatpak context.

[Pointedstick]

Thanks for the KDE bug report. I can confirm that this is a regression in our code. We'll get right on it, and ship a bugfix release of the KWidgetsAddons framework once it's fixed.

So sorry for the breakage!

Folks wishing to be appraised of the progress of a fix can CC themselves on https://bugs.kde.org/show_bug.cgi?id=487247.

[GuardianLiarus]

Thanks for the KDE bug report. I can confirm that this is a regression in our code. We'll get right on it, and ship a bugfix release of the KWidgetsAddons framework once it's fixed.

So sorry for the breakage!

Folks wishing to be appraised of the progress of a fix can CC themselves on https://bugs.kde.org/show_bug.cgi?id=487247.

You're amazing at what you do, i just want you to know that, you took the time to check the issue on the kde bug report but also respond here as well, thank you so much!

[Pointedstick]

Thanks, you are very kind!

[tytan652]

This issue will be closed once a version of KWidgetsAddons with https://invent.kde.org/frameworks/kwidgetsaddons/-/commit/64fcc6fff124dd74e059b9271ba6693a2d561704 is released (e.g. 6.2.1 or 6.3.0).

[Pointedstick]

KWidgetsAddons 6.2.1 has been released now.

[tytan652]

Closing as a new version was released as stated above.

Normally it should not happen since it's a bugfix release but just in case:
If your distro doesn't plan to update KWidgetsAddons, fill a bug report on the distro bug tracker.

[ruineka]

I can confirm the system OBS package now works, but the flatpak still crashes the moment you attempt to import or export anything.

[Pointedstick]

Yes, the KDE Flatpak runtime needs to be updated to include the fix. That should be in progress too.

[ruineka]

Yes, the KDE Flatpak runtime needs to be updated to include the fix. That should be in progress too.

Thanks for the reply! It seems that runtime has been updated according to what I see here. So I suppose all that is left to be done is the flatpak for obs itself needs to be updated to target 6.7 and not 6.6.

[tytan652]

So I suppose all that is left to be done is the flatpak for obs itself needs to be updated to target 6.7 and not 6.6.

No, KDE should also update the 6.6 runtime. OBS has no plan and no reason to change the runtime since 6.6 is still supported.

Edit: https://invent.kde.org/packaging/flatpak-kde-runtime/-/tree/qt6.6 has the update

[ruineka]

So I suppose all that is left to be done is the flatpak for obs itself needs to be updated to target 6.7 and not 6.6.

No, KDE should also update the 6.6 runtime. OBS has no plan and no reason to change the runtime since 6.6 is still supported.

Edit: https://invent.kde.org/packaging/flatpak-kde-runtime/-/tree/qt6.6 has the update

I see this now too. That is strange because OBS still crashes and I don't see any updates when I run flatpak upgrade. Is there something I'm missing here? Sorry, I'm not all to familiar with the flatpak upgrade process.