Summary: | k3b crashes on startup with SIGBUS when trying to load libwidevinecdm.so from local Firefox profile | ||
---|---|---|---|
Product: | [Applications] k3b | Reporter: | Aurélien COUDERC <coucouf> |
Component: | general | Assignee: | K3b Bugs <k3b-bugs-null> |
Status: | RESOLVED DOWNSTREAM | ||
Severity: | crash | CC: | aacid, michalm, trueg |
Priority: | NOR | ||
Version First Reported In: | 24.12.0 | ||
Target Milestone: | --- | ||
Platform: | Debian testing | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Aurélien COUDERC
2025-01-08 08:06:38 UTC
This is clearly not a k3b problem, we're not debian nor firefox nor webengine/chromium there's nothing we can do here. I suggest you add more debug symbols so you get debug info on libQt6WebEngineCore and possibly report a bug against the debian webengine package since it seems what may be at fault here (or the Qt6 webengine code upstream). Hmm, so k3b crashing on startup is not a k3b problem, oh well… I’ll try confirming with the original reporter if that happens with other webengine-enabled apps and get more symbols as you suggested. Thanks I don't understand why you are upset, there's literally nothing we can do in k3b code to fix this problem (other than not using qtwebengine). Do it is not a k3b bug. It also "works for me" so it points to either a bug in qtwebengine, or in how debian compiled qtwebengine, again nothing we can fix. For the record you were right that it has nothing to do with k3b specifically. The user had a corrupt widevine library in their browser config which caused the crash. It still looks very fragile to me and I’d be surprise if you cannot somehow attack that to inject random code into apps using qtwebengine. |