[kwin] [Bug 475629] Crash in scripting engine when using Bismuth
https://bugs.kde.org/show_bug.cgi?id=475629 David Edmundson changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #22 from David Edmundson --- Lets track that as: 470759 We haven't seen any duplicates of the original bug, so lets close this -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475629] Crash in scripting engine when using Bismuth
https://bugs.kde.org/show_bug.cgi?id=475629 z...@proton.me changed: What|Removed |Added CC||z...@proton.me --- Comment #21 from z...@proton.me --- same happening here, back on 5.27 I had occasional crashes of my wayland session when using bismuth. I'm now using the polonium script on plasma 6.0.1 and the same issue is present except moving any window with the script active almost always immediately crashes the session. I suspect this has a similar root cause. Operating System: Arch Linux KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.9-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 16 × 12th Gen Intel® Core™ i5-12600K Memory: 31.1 GiB of RAM Graphics Processor: AMD Radeon RX 6700 XT Manufacturer: Gigabyte Technology Co., Ltd. Product Name: Z690 GAMING X DDR4 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475629] Crash in scripting engine when using Bismuth
https://bugs.kde.org/show_bug.cgi?id=475629 owl-from-hogva...@protonmail.com changed: What|Removed |Added CC||owl-from-hogvarts@protonmai ||l.com --- Comment #20 from owl-from-hogva...@protonmail.com --- Have similar issue. Also have bismuth installed 樂 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475629] Crash in scripting engine when using Bismuth
https://bugs.kde.org/show_bug.cgi?id=475629 --- Comment #19 from Hanabishi --- Just want to say that 5.15.12 still triggers the same crash. kwin_wayland[897]: segfault at 230 ip 7f58b774f0d6 sp 701a9f40 error 6 in libQt5Qml.so.5.15.12[7f58b76a7000+281000] likely on CPU 15 (core 7, socket 0) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475629] Crash in scripting engine when using Bismuth
https://bugs.kde.org/show_bug.cgi?id=475629 --- Comment #18 from Dmitrii Chermnykh --- Got crash with polonium and custom tiles, should I open a new report for that? #0 0x7f7a656c6278 in KWin::CustomTile::setRelativeGeometry(QRectF const&) (this=0x555f41fea270, geom=) at /usr/src/debug/kwin/kwin-5.27.9/src/tiles/customtile.cpp:146 #1 0x7f7a656c5127 in KWin::CustomTile::remove() (this=0x555f41a1afb0) at /usr/src/debug/kwin/kwin-5.27.9/src/tiles/customtile.cpp:278 #2 0x7f7a656c9f43 in KWin::CustomTile::qt_metacall(QMetaObject::Call, int, void**) (this=0x555f41a1afb0, _c=QMetaObject::InvokeMetaMethod, _id=3, _a=0x7ffd92b39230) at /usr/src/debug/kwin/build/src/kwin_autogen/include/moc_customtile.cpp:185 #3 0x7f7a64a7ce04 in QQmlObjectOrGadget::metacall(QMetaObject::Call, int, void**) const (this=0x7ffd92b39480, type=QMetaObject::InvokeMetaMethod, index=, argv=) at /usr/src/debug/qt5-declarative/qtdeclarative/src/qml/qml/qqmlobjectorgadget.cpp:51 #4 0x7f7a6497e006 in CallMethod (callType=QMetaObject::InvokeMetaMethod, callArgs=0x7f7a4c08a8f8, engine=0x555f4112f5f0, argTypes=0x0, argCount=0, returnType=43, index=, object=...) at /usr/src/debug/qt5-declarative/qtdeclarative/src/qml/jsruntime/qv4qobjectwrapper.cpp:1303 #5 CallPrecise(QQmlObjectOrGadget const&, QQmlPropertyData const&, QV4::ExecutionEngine*, QV4::CallData*, QMetaObject::Call) (object=..., data=..., engine=engine@entry=0x555f4112f5f0, callArgs=callArgs@entry=0x7f7a4c08a8f8, callType=callType@entry=QMetaObject::InvokeMetaMethod) at /usr/src/debug/qt5-declarative/qtdeclarative/src/qml/jsruntime/qv4qobjectwrapper.cpp:1557 #6 0x7f7a64980036 in QV4::QObjectMethod::callInternal(QV4::Value const*, QV4::Value const*, int) const (this=, thisObject=0x7f7a4c08a888, argv=, argc=0) at /usr/src/debug/qt5-declarative/qtdeclarative/src/qml/jsruntime/qv4qobjectwrapper.cpp:2115 #7 0x7f7a649a2c4e in QV4::FunctionObject::call(QV4::Value const*, QV4::Value const*, int) const (argc=0, argv=0x7f7a4c08a818, thisObject=0x7f7a4c08a888, this=0x7ffd92b395c8) at /usr/src/debug/qt5-declarative/qtdeclarative/src/qml/jsruntime/qv4functionobject_p.h:202 #8 QV4::Runtime::CallPropertyLookup::call(QV4::ExecutionEngine*, QV4::Value const&, unsigned int, QV4::Value*, int) (engine=0x555f4112f5f0, base=..., index=, argv=0x7f7a4c08a818, argc=0) at /usr/src/debug/qt5-declarative/qtdeclarative/src/qml/jsruntime/qv4runtime.cpp:1460 #9 0x7f7a33f97341 in () #10 0x7ffd92b39800 in () #11 0x in () -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475629] Crash in scripting engine when using Bismuth
https://bugs.kde.org/show_bug.cgi?id=475629 ja...@perfectshuffle.co.uk changed: What|Removed |Added CC||ja...@perfectshuffle.co.uk --- Comment #17 from ja...@perfectshuffle.co.uk --- *** Bug 476709 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475629] Crash in scripting engine when using Bismuth
https://bugs.kde.org/show_bug.cgi?id=475629 --- Comment #16 from Jakub --- Update: After four days with the latest Plasma packages but Qt5 packages downgraded to version 5.15.10, I have not experienced a single KWin crash even with Bismuth active, in contrast to 2-3 crashes per day with Qt5 version 5.15.11. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475629] Crash in scripting engine when using Bismuth
https://bugs.kde.org/show_bug.cgi?id=475629 --- Comment #15 from David Edmundson --- Even if Bismuth itself isn't used, a crash a script currently hits is a path a future script could hit. So we need to try to reproduce and follow up. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475629] Crash in scripting engine when using Bismuth
https://bugs.kde.org/show_bug.cgi?id=475629 --- Comment #14 from Hanabishi --- (In reply to Nate Graham from comment #12) > Isn't Bismuth dead now? I thought Polonium was meant to be its replacement. Yes, it is effectively abandoned. Polonium still lacks some functionality for me, though I do switched to it currently. The scripts work kinda dirty anyway and always will be. I hope Plasma will continue to improve native tiling so that we don't need them anymore. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475629] Crash in scripting engine when using Bismuth
https://bugs.kde.org/show_bug.cgi?id=475629 --- Comment #13 from Jakub --- Unfortunately Polonium does not support layouts that I use with Bismuth, and Bismuth still works fine for me even with the latest version of KWin. Yesterday I downgraded Qt5 packages to version 5.15.10, and didn’t experience any crash so far either. Operating System: Arch Linux KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.112.0 Qt Version: 5.15.10 List of qt5-* package versions: qt5-base 5.15.10+kde+r165-1 qt5-declarative 5.15.10+kde+r31-1 qt5-graphicaleffects 5.15.10-1 qt5-imageformats 5.15.11+kde+r12-1 qt5-location 5.15.10+kde+r5-1 qt5-multimedia 5.15.10+kde+r3-1 qt5-networkauth 5.15.10-1 qt5-quickcontrols 5.15.10-1 qt5-quickcontrols2 5.15.10+kde+r6-1 qt5-script 5.15.15-2 qt5-sensors 5.15.10-1 qt5-speech 5.15.10+kde+r1-1 qt5-svg 5.15.10+kde+r8-1 qt5-tools 5.15.10+kde+r3-2 qt5-translations 5.15.10-1 qt5-wayland 5.15.10+kde+r62-1 qt5-webchannel 5.15.10+kde+r3-1 qt5-webengine 5.15.15-2 qt5-webview 5.15.10-1 qt5-x11extras 5.15.10-1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475629] Crash in scripting engine when using Bismuth
https://bugs.kde.org/show_bug.cgi?id=475629 Nate Graham changed: What|Removed |Added Summary|Crash in scripting engine |Crash in scripting engine ||when using Bismuth --- Comment #12 from Nate Graham --- Isn't Bismuth dead now? I thought Polonium was meant to be its replacement. -- You are receiving this mail because: You are watching all bug changes.
