Closed davidedmundson closed 2 years ago
In future would you consider adding some "namespace Bismuth" everywhere. It'll save me some time upstream if we can spot 3rd parties earlier
In future would you consider adding some "namespace Bismuth" everywhere. It'll save me some time upstream if we can spot 3rd parties earlier
Yeah, sure. But the decoration code was already in a Bismuth namespace, wasn't it?
In future would you consider adding some "namespace Bismuth" everywhere. It'll save me some time upstream if we can spot 3rd parties earlier
Yeah, sure. But the decoration code was already in a Bismuth namespace, wasn't it?
Ah maybe. Bismuth wasn't in the backtrace we had, but maybe the lambda got inlined.
Thanks
@gikari I have a similar issue but it does not need Bismuth enabled, just the Window Decoration bismuth has to be enabled. Would this fix that or is it a separate issue?
@gikari I have a similar issue but it does not need Bismuth enabled, just the Window Decoration bismuth has to be enabled. Would this fix that or is it a separate issue?
Yes.
@gikari I have a similar issue but it does not need Bismuth enabled, just the Window Decoration bismuth has to be enabled. Would this fix that or is it a separate issue?
Yes.
I applied the changes. Seems to fix it. Thanks.
Summary
We had a downstream report: https://bugs.kde.org/show_bug.cgi?id=455810
Crash is caused by
we want
the sharedptr can outlive this class, therefore it needs scoping.
Steps to Reproduce
see above
Expected behavior
see above
Screenshots
No response
Bismuth version
any
KDE Plasma version
5.25.
The platform KWin is running on
X11
Additional context
No response