[krunner] [Bug 484904] New: krunner is placed on weird places when activated
https://bugs.kde.org/show_bug.cgi?id=484904 Bug ID: 484904 Summary: krunner is placed on weird places when activated Classification: Plasma Product: krunner Version: 6.0.2 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: jirisl...@gmail.com CC: alexander.loh...@gmx.de, natalie_clar...@yahoo.de Target Milestone: --- SUMMARY If I press Alt+f2, krunner is activated. But it is activated on the current screen (depending on mouse position). And it is shown on random places like top-right corner, bottom-left corner, seeming center of the screen and so on. STEPS TO REPRODUCE 1. press Alt+f2 OBSERVED RESULT krunner is placed somewhere. EXPECTED RESULT krunner should be placed on top-center as it used to with plasma 5 (this is new in plasma 6). SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240326 KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.1-3.gd922afa-default (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 PRO 7840U w/ Radeon 780M Graphics Memory: 58.4 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 21K6S0A006 System Version: ThinkPad P14s Gen 4 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484903] New: Windows are not shown after unplugging external monitor
https://bugs.kde.org/show_bug.cgi?id=484903 Bug ID: 484903 Summary: Windows are not shown after unplugging external monitor Classification: Plasma Product: kwin Version: 6.0.2 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: jirisl...@gmail.com Target Milestone: --- SUMMARY When I unplug an external monitor where I have konsoles open, the konsoles look like they are still on the second monitor. That is, I can activate/minimize them through the task panel, but they are not shown anywhere. This is new in plasma 6. It used to work fine with 5. Also for example Thunderbird is moved to the primary monitor properly. STEPS TO REPRODUCE 1. Plug in external monitor and let it extend the workspace (i.e. not clone) 2. Move there some konsoles 3. Unplug the monitor OBSERVED RESULT konsoles are not visible. EXPECTED RESULT konsole should be visible. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240326 KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.1-3.gd922afa-default (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 PRO 7840U w/ Radeon 780M Graphics Memory: 58.4 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 21K6S0A006 System Version: ThinkPad P14s Gen 4 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 476036] content of the terminal is misrendered/missing a part
https://bugs.kde.org/show_bug.cgi?id=476036 Jiri Slaby changed: What|Removed |Added Version|23.08.1 |24.02.0 --- Comment #2 from Jiri Slaby --- Still happens with konsole-24.02.0-1.1.x86_64. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 476037] external monitor disabled temporarily upon DPMS on, resulting in misposition of vertically maximized windows
https://bugs.kde.org/show_bug.cgi?id=476037 Jiri Slaby changed: What|Removed |Added Resolution|NOT A BUG |--- Status|RESOLVED|REOPENED Summary|external monitor disabled |external monitor disabled |temporarily upon DPMS on|temporarily upon DPMS on, ||resulting in misposition of ||vertically maximized ||windows Ever confirmed|0 |1 --- Comment #3 from Jiri Slaby --- (In reply to Zamundaaa from comment #2) > No, that was about not unnecessarily turning displays back on. If a display > temporarily pretends it's disconnected after waking up, that's not a problem > we can fix. Reported against amdgpu then: https://gitlab.freedesktop.org/drm/amd/-/issues/2958 > All we can do is to restore the state when the display gets > recognized again, and it sounds like that's working correctly. Mostly ;). Vertically maximized windows are misplaced. Should I create a separate bug or can we continue here? That is: 1) I have a window which is on (0,-1) (left bottom) on the external monitor. 2) I vertically maximize that 3) dpms off 4) dpms on 5) the window is moved to internal monitor at (0,-1) 6) external monitor resumes 7) the window is correctly moved to external monitor, but wrongly to (1536,-1) Note the x position of the window corresponds to the bottom display. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476037] New: external monitor disabled temporarily upon DPMS on
https://bugs.kde.org/show_bug.cgi?id=476037 Bug ID: 476037 Summary: external monitor disabled temporarily upon DPMS on Classification: Plasma Product: plasmashell Version: 5.27.8 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Session Management Assignee: plasma-b...@kde.org Reporter: jirisl...@gmail.com Target Milestone: 1.0 SUMMARY If both monitors: > Output: 1 eDP-1 enabled connected priority 1 Panel Modes: 0:1920x1200@60*! > 1:1920x1200@50 2:1920x1200@48 3:1920x1080@60 4:1600x1200@60 5:1680x1050@60 > 6:1280x1024@60 7:1440x900@60 8:1280x800@60 9:1280x720@60 10:1024x768@60 > 11:800x600@60 12:640x480@60 13:1600x1200@60 14:1280x1024@60 15:1024x768@60 > 16:1920x1200@60 17:1280x800@60 18:1920x1080@60 19:1600x900@60 20:1368x768@60 > 21:1280x720@60 Geometry: 489,1440 1536x960 Scale: 1.25 Rotation: 1 Overscan: > 0 Vrr: Automatic RgbRange: unknown > Output: 2 DP-7 enabled connected priority 2 DisplayPort Modes: > 0:3840x2160@60*! 1:3840x2160@60 2:3840x2160@60 3:3840x2160@50 4:3840x2160@30 > 5:3840x2160@30 6:3840x2160@30 7:2560x1440@60 8:1920x1080@60 9:1920x1080@60 > 10:1920x1080@60 11:1920x1080@50 12:1920x1080@50 13:1680x1050@60 > 14:1600x900@60 15:1280x1024@75 16:1280x1024@60 17:1440x900@60 18:1280x800@60 > 19:1152x864@75 20:1280x720@60 21:1280x720@60 22:1280x720@60 23:1280x720@50 > 24:1024x768@75 25:1024x768@70 26:1024x768@60 27:832x624@75 28:800x600@75 > 29:800x600@72 30:800x600@60 31:800x600@56 32:720x576@50 33:720x480@60 > 34:720x480@60 35:640x480@75 36:640x480@73 37:640x480@67 38:640x480@60 > 39:640x480@60 40:720x400@70 41:1600x1200@60 42:1280x1024@60 43:1024x768@60 > 44:2560x1600@60 45:1920x1200@60 46:1280x800@60 47:3840x2160@60 > 48:3200x1800@60 49:2880x1620@60 50:2560x1440@60 51:1920x1080@60 > 52:1600x900@60 53:1368x768@60 54:1280x720@60 Geometry: 0,0 2560x1440 Scale: > 1.5 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown go to DPMS off due to inactivity, waking DP-7 up takes so long, that windows are moved to eDP-1 temporarily for a second or two. Then again, all windows are restored to DP-7. STEPS TO REPRODUCE 1. be inactive 2. monitors go to sleep 3. move mouse 4. internal monitor on eDP-1 resumes quickly 5. windows from original DP-7 are moved to eDP-1 6. monitor on DP-7 resumes only now 7. windows are restored to DP-7 OBSERVED RESULT windows are moved back and forth EXPECTED RESULT it is wait for the monitor to appear. Maybe to low timeout is set? SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20231022 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 Kernel Version: 6.5.9-rc1-1.ga138c10-default (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 PRO 6850U with Radeon Graphics Memory: 29.9 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 21CRS0K83K System Version: ThinkPad T14s Gen 3 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 476036] content of the terminal is misrendered/missing a part
https://bugs.kde.org/show_bug.cgi?id=476036 --- Comment #1 from Jiri Slaby --- (In reply to Jiri Slaby from comment #0) > STEPS TO REPRODUCE > 1. switch from one desktop to another > 2. maybe vertical maximization and restore to original size is needed > before, I don't know for sure Thinking about it, this is likely related/needed: When monitors go to dpms off (after inactivity), it takes so long for the DP-7 output to come up, so that plasma "forgets" the output temporarily and moves all windows to eDP. After a second or two, all is moved back to place on DP-7. And this likely causes the problem -- the window is then distorted. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 476036] New: content of the terminal is misrendered/missing a part
https://bugs.kde.org/show_bug.cgi?id=476036 Bug ID: 476036 Summary: content of the terminal is misrendered/missing a part Classification: Applications Product: konsole Version: 23.08.1 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: jirisl...@gmail.com Target Milestone: --- Created attachment 162526 --> https://bugs.kde.org/attachment.cgi?id=162526=edit konsole misrendered SUMMARY I have a multimonitor setup on wayland: > $ kscreen-doctor -o > Output: 1 eDP-1 enabled connected priority 1 Panel Modes: 0:1920x1200@60*! > 1:1920x1200@50 2:1920x1200@48 3:1920x1080@60 4:1600x1200@60 5:1680x1050@60 > 6:1280x1024@60 7:1440x900@60 8:1280x800@60 9:1280x720@60 10:1024x768@60 > 11:800x600@60 12:640x480@60 13:1600x1200@60 14:1280x1024@60 15:1024x768@60 > 16:1920x1200@60 17:1280x800@60 18:1920x1080@60 19:1600x900@60 20:1368x768@60 > 21:1280x720@60 Geometry: 489,1440 1536x960 Scale: 1.25 Rotation: 1 Overscan: > 0 Vrr: Automatic RgbRange: unknown > Output: 2 DP-7 enabled connected priority 2 DisplayPort Modes: > 0:3840x2160@60*! 1:3840x2160@60 2:3840x2160@60 3:3840x2160@50 4:3840x2160@30 > 5:3840x2160@30 6:3840x2160@30 7:2560x1440@60 8:1920x1080@60 9:1920x1080@60 > 10:1920x1080@60 11:1920x1080@50 12:1920x1080@50 13:1680x1050@60 > 14:1600x900@60 15:1280x1024@75 16:1280x1024@60 17:1440x900@60 18:1280x800@60 > 19:1152x864@75 20:1280x720@60 21:1280x720@60 22:1280x720@60 23:1280x720@50 > 24:1024x768@75 25:1024x768@70 26:1024x768@60 27:832x624@75 28:800x600@75 > 29:800x600@72 30:800x600@60 31:800x600@56 32:720x576@50 33:720x480@60 > 34:720x480@60 35:640x480@75 36:640x480@73 37:640x480@67 38:640x480@60 > 39:640x480@60 40:720x400@70 41:1600x1200@60 42:1280x1024@60 43:1024x768@60 > 44:2560x1600@60 45:1920x1200@60 46:1280x800@60 47:3840x2160@60 > 48:3200x1800@60 49:2880x1620@60 50:2560x1440@60 51:1920x1080@60 > 52:1600x900@60 53:1368x768@60 54:1280x720@60 Geometry: 0,0 2560x1440 Scale: > 1.5 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown (mind the scales) I have konsoles on this DP-7 monitor. STEPS TO REPRODUCE 1. switch from one desktop to another 2. maybe vertical maximization and restore to original size is needed before, I don't know for sure OBSERVED RESULT Sometimes, one of the konsoles is misrendered. See the attachment. It looks like scaled down by 1.2 -- from 1093 px (the window) to 910 (the rendered content). EXPECTED RESULT Proper rendering. Is this konsole's fault? Or is it perhaps some plasma component? SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20231022 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Kernel Version: 6.5.7-9.g4e7c99b-default (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 PRO 6850U with Radeon Graphics Memory: 29.9 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 21CRS0K83K System Version: ThinkPad T14s Gen 3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465872] Plasma keeps crashing
https://bugs.kde.org/show_bug.cgi?id=465872 Jiri Slaby changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DOWNSTREAM URL||https://bugzilla.suse.com/s ||how_bug.cgi?id=1208188 --- Comment #25 from Jiri Slaby --- (In reply to Jiri Slaby from comment #23) > Maybe we should continue in downstream (openSUSE miscompilation) or upstream > (qt bug). Resolved downstream by dropping non-sse2 builds of qt libraries (which are apparently broken), see the downstream bug. https://bugzilla.suse.com/show_bug.cgi?id=1208188 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465872] Plasma keeps crashing
https://bugs.kde.org/show_bug.cgi?id=465872 --- Comment #23 from Jiri Slaby --- (In reply to Jiri Slaby from comment #22) > Ah, because it's not ep at that location -- 0xb706dff0 is code, not data: So: ExecutionEngine::setQmlEngine(this=0xb59250) sets m_qmlEngine to 0xb7b73c virtualGet that=0x9fbc0820 eng=0xb59250 qeng=0xb7208f08 I.e. ExecutionEngine is created by new(), 0xb7b73c is set as m_qmlEngine. Nothing else sets m_qmlEngine during runtime and then it crashes. At that point, the engine is still the one created earlier (0xb59250), but its m_qmlEngine is suddenly 0xb7208f08 (a pointer to the code). This really looks like a memory corruption. Note that when I set up a breakpoint in ExecutionEngine::setQmlEngine, the issue doesn't occur. So it is likely racy on the top of the above. (I wanted to add a "watch" to ExecutionEngine::m_qmlEngine there to see who overwrites that. Maybe we should continue in downstream (openSUSE miscompilation) or upstream (qt bug). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465872] Plasma keeps crashing
https://bugs.kde.org/show_bug.cgi?id=465872
--- Comment #22 from Jiri Slaby ---
(In reply to Jiri Slaby from comment #21)
> ep is corrupted:
> 1639if (QQmlEngine *qmlEngine = that->engine()->qmlEngine()) {
> 1640QQmlEnginePrivate *ep = QQmlEnginePrivate::get(qmlEngine);
> 1641if (ep && ep->propertyCapture) {
> 1642qDebug() << __func__ << ep << ep->propertyCapture;
> 1643ep->propertyCapture->captureProperty(that->object(), -1,
> role->index, /*doNotify=*/ false);
> 1644}
> 1645}
>
> This prints:
> virtualGet 0xb706dff0 0x8dc35e5b
...
> Many values/pointers are 0x8dc35e5b or -1879038348/0x90002674 or
> 0xc483ffe0/-997982240 or their combination. That is obviously bogus.
Ah, because it's not ep at that location -- 0xb706dff0 is code, not data:
> (gdb) x/24x 0xb706dff0
> 0xb706dff0 <_ZN20QQmlDelayedCallQueue11qt_metacastEPKc>:0x39e85356
> 0x81ffe0f8 0x1a1265c3 0x04ec8300
> 0xb706e000 <_ZN20QQmlDelayedCallQueue11qt_metacastEPKc+16>: 0x1424748b
> 0x4074f685 0x8d08ec83 0xed9c9483
> 0xb706e010 <_ZN20QQmlDelayedCallQueue11qt_metacastEPKc+32>: 0xe85650ff
> 0xffe076c8 0x8910c483 0x24448bc2
> 0xb706e020 <_ZN20QQmlDelayedCallQueue11qt_metacastEPKc+48>: 0x75d28510
> 0x04c4830b 0x8dc35e5b 0x90002674
> 0xb706e030 <_ZN20QQmlDelayedCallQueue11qt_metacastEPKc+64>: 0x5608ec83
> 0x5756e850 0xc483ffe0 0x04c48310
> 0xb706e040 <_ZN20QQmlDelayedCallQueue11qt_metacastEPKc+80>: 0x8dc35e5b
> 0x90002674 0xd9ebc031 0x0026748d
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 465872] Plasma keeps crashing
https://bugs.kde.org/show_bug.cgi?id=465872
--- Comment #21 from Jiri Slaby ---
(In reply to Hans Brage from comment #0)
> #7 0xb442e75c in QV4::ModelObject::virtualGet(QV4::Managed const*,
> QV4::PropertyKey, QV4::Value const*, bool*) (m=0xa15c0820, id=...,
> receiver=0xa15c0820, hasProperty=0x0) at
> /usr/src/debug/qtdeclarative-everywhere-src-5.15.8+kde22/src/qmlmodels/
> qqmllistmodel.cpp:1639
ep is corrupted:
1639if (QQmlEngine *qmlEngine = that->engine()->qmlEngine()) {
1640QQmlEnginePrivate *ep = QQmlEnginePrivate::get(qmlEngine);
1641if (ep && ep->propertyCapture) {
1642qDebug() << __func__ << ep << ep->propertyCapture;
1643ep->propertyCapture->captureProperty(that->object(), -1,
role->index, /*doNotify=*/ false);
1644}
1645}
This prints:
virtualGet 0xb706dff0 0x8dc35e5b
So:
> (gdb) p *(QQmlEnginePrivate *)0xb706dff0
> $3 = { = { = { =
> {_vptr.QObjectData = 0x39e85356, q_ptr = 0x81ffe0f8, parent = 0x1a1265c3,
> children = {> = {}, {p = {
> static shared_null = {ref = {atomic = {_q_value =
> std::atomic = { -1 }}}, alloc = 0, begin = 0, end = 0, array = {0x0}}, d
> = 0x4ec8300}, d = 0x4ec8300}}, isWidget = 1, blockSig = 1, wasDeleted = 0,
> isDeletingChildren = 1, sendChildEvents = 0, receiveChildEvents = 0,
> isWindow = 0, deleteLaterCalled = 1, unused = 1320052, postedEvents =
> 1081407109, metaObject = 0x8d08ec83}, extraData = 0xed9c9483,
> threadData = {> = {_q_value =
> std::atomic = { 0xe85650ff }}, }, connections
> = {> = {
> _q_value = std::atomic = {
> 0xffe076c8 }}, }, {currentChildBeingDeleted = 0x8910c483,
> declarativeData = 0x8910c483},
> sharedRefcount =
> {> = {_q_value =
> std::atomic = { 0x24448bc2 }}, data fields>}},
> mutex = { = { = {d_ptr = {_q_value =
> std::atomic = { 0x75d28510 }}}, }, fields>}, uiLanguage = {d = 0x4c4830b}},
> static baseModulesUninitialized = false, propertyCapture = 0x8dc35e5b,
> jsExpressionGuardPool = {d = 0x90002674}, rootContext = 0x5608ec83, profiler
> = 0x5756e850, outputWarningsToMsgLog = 224, cleanup = 0x4c48310,
> erroredBindings = 0x8dc35e5b, inProgressCreations = -1879038348,
> workerScriptEngine = 0xd9ebc031, baseUrl = {d = 0x26748d},
> activeObjectCreator = 0x53565755, networkAccessManager = 0xe0f7d7e8,
> networkAccessManagerFactory = 0x3c381ff, imageProviders = {{d = 0x83001a12,
> e = 0x83001a12}}, urlInterceptor = 0x748b0cec, scarceResourcesRefCount =
> 2089493540, importDatabase = {
> qmldirCache = { = {}, data = {buckets =
> 0xf6852024, numBuckets = -326927756, size = 1417907464, numBits = -4460},
> newedNodes = 0xe85650fd, nodePool = 0xffe07660},
> filePluginPath = {> = {> =
> {}, {p = {static shared_null = {ref = {atomic = {_q_value =
> std::atomic = { -1 }}}, alloc = 0, begin = 0, end = 0,
> array = {0x0}}, d = 0x8510c483}, d = 0x8510c483}}, fields>}, fileImportPath = {> =
> {> = {}, {p = {static
> shared_null = {ref = {
> atomic = {_q_value = std::atomic = { -1 }}}, alloc = 0,
> begin = 0, end = 0, array = {0x0}}, d = 0x833174c0}, d = 0x833174c0}}, data fields>}, qmlDirFilesForWhichPluginsHaveBeenLoaded = {
> q_hash = {{d = 0x838d08ec, e = 0x838d08ec}}}, initializedPlugins =
> {q_hash = {{d = 0xffeee270, e = 0xffeee270}}}, engine = 0x49e85650},
> typeLoader = {m_engine = 0x83ffe076, m_thread = 0xc08510c4,
> m_mutex = @0xec831774, m_profiler = {d = 0x94838d08}, m_networkReplies =
> {{d = 0x50ffeee2, e = 0x50ffeee2}}, m_typeCache = {{d = 0x7632e856, e =
> 0x7632e856}}, m_typeCacheTrimThreshold = -997982240,
> m_scriptCache = {{d = 0x75c08510, e = 0x75c08510}}, m_qmldirCache = {{d =
> 0x86f8d13, e = 0x86f8d13}}, m_importDirCache = {f = 0x890cc483, l =
> 0x5f5e5be8, hash = {{
> d = 0xb68dc35d , e =
> 0xb68dc35d }}, mx = 0, total =
> 1443425411},
> m_importQmlDirCache = { = {}, data =
> {buckets = 0x56bee857, numBuckets = -997982240, size = 214205200, numBits =
> -14967}, newedNodes = 0x5d5f5ee8, nodePool = 0x26b48dc3}},
> offlineStoragePath = {d = 0x0}, uniqueId = 3438013745, incubatorList =
> {__first = 0x26748d}, incubatorCount = 69485707, incubationController =
> 0x30440c7, static qml_debugging_enabled = false,
> networkAccessManagerMutex = { = {d_ptr = {_q_value =
> std::atomic = { 0xc300 }}}, },
> singletonInstances = {{d = 0x26748d, e = 0x26748d}}, cachedValueTypeInstances
> = {{
> d = 0x89565755, e = 0x89565755}}, m_compositeTypes = {{d = 0x25e853c6,
> e = 0x25e853c6}}, static s_designerMode = false, toDeleteInEngineThread =
> {_first = 0x81ffe0f7, _last = 0x1a1151c3, _flag = 0,
> _count = 376848768}}
Many values/pointers are 0x8dc35e5b or -1879038348/0x90002674 or
0xc483ffe0/-997982240 or their combination. That is obviously bogus.
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 465872] Plasma keeps crashing
https://bugs.kde.org/show_bug.cgi?id=465872 --- Comment #20 from Jiri Slaby --- Created attachment 156860 --> https://bugs.kde.org/attachment.cgi?id=156860=edit valgrind of plasmashell > Invalid read of size 4 >at 0x5686376: UnknownInlinedFun (qqmljavascriptexpression_p.h:230) >by 0x5686376: QQmlPropertyCapture::captureProperty(QObject*, int, int, > bool) (qqmljavascriptexpression.cpp:281) >by 0x831975B: QV4::ModelObject::virtualGet(QV4::Managed const*, > QV4::PropertyKey, QV4::Value const*, bool*) (qqmllistmodel.cpp:1639) >by 0x551C680: UnknownInlinedFun (qv4object_p.h:308) >by 0x551C680: QV4::Lookup::getterFallback(QV4::Lookup*, > QV4::ExecutionEngine*, QV4::Value const&) (qv4lookup.cpp:231) >by 0x8314B38: QV4::ModelObject::virtualResolveLookupGetter(QV4::Object > const*, QV4::ExecutionEngine*, QV4::Lookup*) (qqmllistmodel.cpp:1650) >by 0x551D78D: QV4::Lookup::getterGeneric(QV4::Lookup*, > QV4::ExecutionEngine*, QV4::Value const&) (qv4lookup.cpp:144) >by 0x558F20B: QV4::Moth::VME::interpret(QV4::CppStackFrame*, > QV4::ExecutionEngine*, char const*) (qv4vme_moth.cpp:641) >by 0x5592E3B: UnknownInlinedFun (qv4vme_moth.cpp:466) >by 0x5592E3B: QV4::Moth::VME::exec(QV4::CppStackFrame*, > QV4::ExecutionEngine*) (qv4vme_moth.cpp:430) >by 0x553DCFD: QV4::ArrowFunction::virtualCall(QV4::FunctionObject const*, > QV4::Value const*, QV4::Value const*, int) (qv4functionobject.cpp:528) >by 0x55A43E9: UnknownInlinedFun (qv4functionobject_p.h:202) >by 0x55A43E9: > QV4::Runtime::CallQmlContextPropertyLookup::call(QV4::ExecutionEngine*, > unsigned int, QV4::Value*, int) (qv4runtime.cpp:1366) >by 0x5590E13: QV4::Moth::VME::interpret(QV4::CppStackFrame*, > QV4::ExecutionEngine*, char const*) (qv4vme_moth.cpp:787) >by 0x5592E3B: UnknownInlinedFun (qv4vme_moth.cpp:466) >by 0x5592E3B: QV4::Moth::VME::exec(QV4::CppStackFrame*, > QV4::ExecutionEngine*) (qv4vme_moth.cpp:430) >by 0x553DCFD: QV4::ArrowFunction::virtualCall(QV4::FunctionObject const*, > QV4::Value const*, QV4::Value const*, int) (qv4functionobject.cpp:528) > Address 0x8dc35e63 is not stack'd, malloc'd or (recently) free'd So it's apparently not even use after free. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465872] Plasma keeps crashing
https://bugs.kde.org/show_bug.cgi?id=465872 Jiri Slaby changed: What|Removed |Added CC||jirisl...@gmail.com --- Comment #19 from Jiri Slaby --- For me, it works until I update (only) this: glibc 2.36-9.2 -> 2.37-1.4 glibc-devel2.36-9.2 -> 2.37-1.4 glibc-extra2.36-9.2 -> 2.37-1.4 glibc-locale 2.36-9.2 -> 2.37-1.4 glibc-locale-base 2.36-9.2 -> 2.37-1.4 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 463462] custom shortcuts menu empty, no way to add new custom shortcuts
https://bugs.kde.org/show_bug.cgi?id=463462 Jiri Slaby changed: What|Removed |Added CC||jirisl...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 310677] running KDE apps does not work after some time
https://bugs.kde.org/show_bug.cgi?id=310677 Jiri Slaby changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #6 from Jiri Slaby --- I don't even remember this, so this is likely fixed long time ago. -- You are receiving this mail because: You are watching all bug changes.
[kmix] [Bug 363139] osd is displayed very small sometimes
https://bugs.kde.org/show_bug.cgi?id=363139 Jiri Slaby changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #4 from Jiri Slaby --- I haven't seen it for years likely. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 452758] Valgrind does not read properly DWARF5 as generated by Clang14
https://bugs.kde.org/show_bug.cgi?id=452758 Jiri Slaby changed: What|Removed |Added CC||jirisl...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452247] Window is placed on wrong screen after monitors power on
https://bugs.kde.org/show_bug.cgi?id=452247 --- Comment #4 from Jiri Slaby --- (In reply to Nate Graham from comment #2) > If it affects non-KDE apps and Window Rules don't fix it, it's not an issue > with the X11-specific code to position windows, as that only affects certain > KDE windows and hasn't changed in a while and it's in the Frameworks release > cycle anyway. +1 as happens both to all windows, incl. xterm (Xwayland) and konsole (wayland). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452254] New: Window switch "their" monitor after unplug+replug (maybe regression of 5.24)
https://bugs.kde.org/show_bug.cgi?id=452254 Bug ID: 452254 Summary: Window switch "their" monitor after unplug+replug (maybe regression of 5.24) Product: kwin Version: 5.24.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: jirisl...@gmail.com Target Milestone: --- This is maybe a dup of bug 452247? SUMMARY When I unplug an external monitor connected via Thunderbolt and replug it, all windows switch "their" monitor. I.e. if a window was on the laptop monitor, it is now on the external one and vice versa. STEPS TO REPRODUCE 1. plug in an external monitor 2. move some windows there 3. unplug + replug OBSERVED RESULT The windows are on the opposite monitors. EXPECTED RESULT The window's monitor should be preserved. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20220402 KDE Plasma Version: 5.24.0 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.2 Kernel Version: 5.16.9-3.gdedbf20-default (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i7-6600U CPU @ 2.60GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 520 ADDITIONAL INFORMATION This happens likely since 5.24. I did not see this before. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449773] Conditional jump or move depends on uninitialised value in KWin::DrmPipeline::checkTestBuffer
https://bugs.kde.org/show_bug.cgi?id=449773 Bug 449773 depends on bug 445894, which changed state. Bug 445894 Summary: Crash in KWin::DrmOutput::updateCursor -> malloc(): unsorted double linked list corrupted https://bugs.kde.org/show_bug.cgi?id=445894 What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446101] Crash in KWin::DrmPipeline::setCursor
https://bugs.kde.org/show_bug.cgi?id=446101 Bug 446101 depends on bug 445894, which changed state. Bug 445894 Summary: Crash in KWin::DrmOutput::updateCursor -> malloc(): unsorted double linked list corrupted https://bugs.kde.org/show_bug.cgi?id=445894 What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445894] Crash in KWin::DrmOutput::updateCursor -> malloc(): unsorted double linked list corrupted
https://bugs.kde.org/show_bug.cgi?id=445894 Jiri Slaby changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #26 from Jiri Slaby --- In any way, the original issue is resolved. Let's track the other one in bug 449773. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449773] New: Conditional jump or move depends on uninitialised value in KWin::DrmPipeline::checkTestBuffer
https://bugs.kde.org/show_bug.cgi?id=449773
Bug ID: 449773
Summary: Conditional jump or move depends on uninitialised
value in KWin::DrmPipeline::checkTestBuffer
Product: kwin
Version: 5.24.0
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: platform-drm
Assignee: kwin-bugs-n...@kde.org
Reporter: jirisl...@gmail.com
CC: kwin-bugs-n...@kde.org, n...@kde.org,
xaver.h...@gmail.com
Depends on: 445894
Blocks: 446101
Target Milestone: ---
+++ This bug was initially created as a clone of Bug #445894 +++
> Conditional jump or move depends on uninitialised value(s)
>at 0xCD2EBCF:
> KWin::DrmPipeline::checkTestBuffer()::{lambda(QSharedPointer
> const&)#1}::operator()(QSharedPointer const&) const
> (drm_pipeline.cpp:306)
>by 0xCD2EDA3: KWin::DrmPipeline::checkTestBuffer() (drm_pipeline.cpp:318)
>by 0xCD2F41E:
> KWin::DrmPipeline::commitPipelinesAtomic(QVector const&,
> KWin::DrmPipeline::CommitMode, QVector const&)
> (drm_pipeline.cpp:131)
>by 0xCD26BA8: KWin::DrmGpu::testPipelines() (drm_gpu.cpp:427)
>by 0xCD29E27:
> KWin::DrmGpu::checkCrtcAssignment(QVector,
> QVector) (drm_gpu.cpp:365)
>by 0xCD29E27:
> KWin::DrmGpu::checkCrtcAssignment(QVector,
> QVector) (drm_gpu.cpp:365)
>by 0xCD3B298: UnknownInlinedFun (drm_gpu.cpp:398)
>by 0xCD3B298: UnknownInlinedFun (drm_gpu.cpp:396)
>by 0xCD3B298:
> KWin::DrmGpu::testPendingConfiguration(KWin::DrmGpu::TestMode) [clone
> .constprop.0] (drm_gpu.cpp:403)
>by 0xCD14B43: KWin::DrmBackend::updateOutputs() (drm_gpu.cpp:309)
>by 0xCD16F0C: KWin::DrmBackend::handleUdevEvent() (drm_backend.cpp:237)
>by 0x6FC54F2: UnknownInlinedFun (qobjectdefs_impl.h:398)
>by 0x6FC54F2: void doActivate(QObject*, int, void**)
> (qobject.cpp:3886)
>by 0x6FC88CE: QSocketNotifier::activated(QSocketDescriptor,
> QSocketNotifier::Type, QSocketNotifier::QPrivateSignal)
> (moc_qsocketnotifier.cpp:178)
>by 0x6FC90CA: QSocketNotifier::event(QEvent*) (qsocketnotifier.cpp:302)
> Uninitialised value was created by a stack allocation
>at 0xCD329F0: QtPrivate::QSlotObject (KWin::EglGbmBackend::*)(KWin::DrmAbstractOutput*),
> QtPrivate::List, void>::impl(int,
> QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) (qobjectdefs_impl.h:411)
(In reply to Vlad Zahorodnii from bug 445894 comment #23)
> > So it's the pointer returned by backend->drmFormat(m_output);
>
> drmFormat() returns an integer. can you add a default member initializer for
> GbmFormat::drmFormat, i.e.
>
> struct GbmFormat
> {
> uint32_t drmFormat = 0;
Sure, this makes it go away.
SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 2027
KDE Plasma Version: 5.23.2
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2
Kernel Version: 5.15.2-1.g26a203b-default (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i7-6600U CPU @ 2.60GHz
Memory: 15.3 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 520
Referenced Bugs:
https://bugs.kde.org/show_bug.cgi?id=445894
[Bug 445894] Crash in KWin::DrmOutput::updateCursor -> malloc(): unsorted
double linked list corrupted
https://bugs.kde.org/show_bug.cgi?id=446101
[Bug 446101] Crash in KWin::DrmPipeline::setCursor
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 445894] Crash in KWin::DrmOutput::updateCursor -> malloc(): unsorted double linked list corrupted
https://bugs.kde.org/show_bug.cgi?id=445894 Jiri Slaby changed: What|Removed |Added Blocks||449773 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=449773 [Bug 449773] Conditional jump or move depends on uninitialised value in KWin::DrmPipeline::checkTestBuffer -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446101] Crash in KWin::DrmPipeline::setCursor
https://bugs.kde.org/show_bug.cgi?id=446101 Jiri Slaby changed: What|Removed |Added Depends on||449773 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=449773 [Bug 449773] Conditional jump or move depends on uninitialised value in KWin::DrmPipeline::checkTestBuffer -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445894] Crash in KWin::DrmOutput::updateCursor -> malloc(): unsorted double linked list corrupted
https://bugs.kde.org/show_bug.cgi?id=445894
--- Comment #24 from Jiri Slaby ---
(In reply to Vlad Zahorodnii from comment #23)
> > So it's the pointer returned by backend->drmFormat(m_output);
>
> drmFormat() returns an integer. can you add a default member initializer for
> GbmFormat::drmFormat, i.e.
>
> struct GbmFormat
> {
> uint32_t drmFormat = 0;
Sure, this makes it go away.
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 445894] Crash in KWin::DrmOutput::updateCursor -> malloc(): unsorted double linked list corrupted
https://bugs.kde.org/show_bug.cgi?id=445894
--- Comment #22 from Jiri Slaby ---
Finding out the culprit in the == operand:
> 305 const auto = [this, backend, ](const
> QSharedPointer ){
> 306 const auto = supportedModifiers(buf->format());
> 307 if (backend) {
> 308 auto fmt1 = buf->format();
> 309 auto fmt2 = backend->drmFormat(m_output);
> 310 qDebug() << "fmt1" << fmt1;
> 311 qDebug() << "fmt2" << fmt2;
> 312 if (fmt1 == fmt2)
> 313 if (mods.isEmpty() ||
> mods.contains(buf->modifier()))
> 314 if (buf->size() == bufferSize())
> 315 buffer = buf;
> 316 }
> 317 };
> by 0x6EA3B87: ~QDebug (qdebug.cpp:154)
> by 0xCD2EC41:
> KWin::DrmPipeline::checkTestBuffer()::{lambda(QSharedPointer
> const&)#1}::operator()(QSharedPointer const&) const
> (drm_pipeline.cpp:311)
So it's the pointer returned by backend->drmFormat(m_output);
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 445894] Crash in KWin::DrmOutput::updateCursor -> malloc(): unsorted double linked list corrupted
https://bugs.kde.org/show_bug.cgi?id=445894
--- Comment #21 from Jiri Slaby ---
(In reply to Vlad Zahorodnii from comment #20)
> Not sure what valgrind doesn't like, I don't see issues with that code right
> off the bat.
I reorganized the conditions to one per line:
> 303 const auto = [this, backend, ](const
> QSharedPointer ){
> 304 const auto = supportedModifiers(buf->format());
> 305 if (backend)
> 306 if (buf->format() == backend->drmFormat(m_output))
> 307 if (mods.isEmpty() ||
> mods.contains(buf->modifier()))
> 308 if (buf->size() == bufferSize())
> 309 buffer = buf;
> 310 };
And added --track-origins=yes to valgrind (the last 2 lines are new):
> Conditional jump or move depends on uninitialised value(s)
>at 0xCD2EBCF:
> KWin::DrmPipeline::checkTestBuffer()::{lambda(QSharedPointer
> const&)#1}::operator()(QSharedPointer const&) const
> (drm_pipeline.cpp:306)
>by 0xCD2EDA3: KWin::DrmPipeline::checkTestBuffer() (drm_pipeline.cpp:318)
>by 0xCD2F41E:
> KWin::DrmPipeline::commitPipelinesAtomic(QVector const&,
> KWin::DrmPipeline::CommitMode, QVector const&)
> (drm_pipeline.cpp:131)
>by 0xCD26BA8: KWin::DrmGpu::testPipelines() (drm_gpu.cpp:427)
>by 0xCD29E27:
> KWin::DrmGpu::checkCrtcAssignment(QVector,
> QVector) (drm_gpu.cpp:365)
>by 0xCD29E27:
> KWin::DrmGpu::checkCrtcAssignment(QVector,
> QVector) (drm_gpu.cpp:365)
>by 0xCD3B298: UnknownInlinedFun (drm_gpu.cpp:398)
>by 0xCD3B298: UnknownInlinedFun (drm_gpu.cpp:396)
>by 0xCD3B298:
> KWin::DrmGpu::testPendingConfiguration(KWin::DrmGpu::TestMode) [clone
> .constprop.0] (drm_gpu.cpp:403)
>by 0xCD14B43: KWin::DrmBackend::updateOutputs() (drm_gpu.cpp:309)
>by 0xCD16F0C: KWin::DrmBackend::handleUdevEvent() (drm_backend.cpp:237)
>by 0x6FC54F2: UnknownInlinedFun (qobjectdefs_impl.h:398)
>by 0x6FC54F2: void doActivate(QObject*, int, void**)
> (qobject.cpp:3886)
>by 0x6FC88CE: QSocketNotifier::activated(QSocketDescriptor,
> QSocketNotifier::Type, QSocketNotifier::QPrivateSignal)
> (moc_qsocketnotifier.cpp:178)
>by 0x6FC90CA: QSocketNotifier::event(QEvent*) (qsocketnotifier.cpp:302)
> Uninitialised value was created by a stack allocation
>at 0xCD329F0: QtPrivate::QSlotObject (KWin::EglGbmBackend::*)(KWin::DrmAbstractOutput*),
> QtPrivate::List, void>::impl(int,
> QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) (qobjectdefs_impl.h:411)
Not sure if it tells you what is THE uninitialized object.
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 445894] Crash in KWin::DrmOutput::updateCursor -> malloc(): unsorted double linked list corrupted
https://bugs.kde.org/show_bug.cgi?id=445894 --- Comment #19 from Jiri Slaby --- *** Bug 446101 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446101] Crash in KWin::DrmPipeline::setCursor
https://bugs.kde.org/show_bug.cgi?id=446101 Jiri Slaby changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Jiri Slaby --- I believe, it's the same. *** This bug has been marked as a duplicate of bug 445894 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445894] Crash in KWin::DrmOutput::updateCursor -> malloc(): unsorted double linked list corrupted
https://bugs.kde.org/show_bug.cgi?id=445894
Jiri Slaby changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO |REPORTED
--- Comment #18 from Jiri Slaby ---
(In reply to Jiri Slaby from comment #16)
> (In reply to Vlad Zahorodnii from comment #15)
> > Can you confirm that this issue is gone in 5.24 beta?
>
> Waiting for beta to reach factory (a couple of days, I assume):
> https://build.opensuse.org/request/show/947521
OK, so I updated from KDE:Frameworks5. That means I am at v5.23.90 + some
patches. The crash seems to be gone, but I see this now:
> ==2431== Conditional jump or move depends on uninitialised value(s)
> ==2431==at 0xCD2C5FF:
> KWin::DrmPipeline::checkTestBuffer()::{lambda(QSharedPointer
> const&)#1}::operator()(QSharedPointer const&) const
> (drm_pipeline.cpp:302)
> ==2431==by 0xCD2C7E0: KWin::DrmPipeline::checkTestBuffer()
> (drm_pipeline.cpp:315)
> ==2431==by 0xCD2CCF8:
> KWin::DrmPipeline::commitPipelinesAtomic(QVector const&,
> KWin::DrmPipeline::CommitMode, QVector const&)
> (drm_pipeline.cpp:131)
> ==2431==by 0xCD249A8: KWin::DrmGpu::testPipelines() (drm_gpu.cpp:427)
> ==2431==by 0xCD26A67:
> KWin::DrmGpu::checkCrtcAssignment(QVector,
> QVector) (drm_gpu.cpp:365)
> ==2431==by 0xCD26A67:
> KWin::DrmGpu::checkCrtcAssignment(QVector,
> QVector) (drm_gpu.cpp:365)
> ==2431==by 0xCD39878: UnknownInlinedFun (drm_gpu.cpp:398)
> ==2431==by 0xCD39878: UnknownInlinedFun (drm_gpu.cpp:396)
> ==2431==by 0xCD39878:
> KWin::DrmGpu::testPendingConfiguration(KWin::DrmGpu::TestMode) [clone
> .constprop.0] (drm_gpu.cpp:403)
> ==2431==by 0xCD13573: KWin::DrmBackend::updateOutputs() (drm_gpu.cpp:309)
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 446101] Crash in KWin::DrmPipeline::setCursor
https://bugs.kde.org/show_bug.cgi?id=446101 Bug 446101 depends on bug 445894, which changed state. Bug 445894 Summary: Crash in KWin::DrmOutput::updateCursor -> malloc(): unsorted double linked list corrupted https://bugs.kde.org/show_bug.cgi?id=445894 What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445894] Crash in KWin::DrmOutput::updateCursor -> malloc(): unsorted double linked list corrupted
https://bugs.kde.org/show_bug.cgi?id=445894 --- Comment #17 from Jiri Slaby --- (In reply to Jiri Slaby from comment #14) > Anyway, if I do this in 5.23.5, it seems to fix the problem. Not completely, kwin still crashes, but elsewhere. Still memory corruption. Still waiting for 5.24 beta to reach factory. Just for completeness: > #5 0x7f8a202cbe3c in malloc_printerr (str=str@entry=0x7f8a203fd6d0 > "malloc(): smallbin double linked list corrupted") at malloc.c:5543 > #6 0x7f8a202cf28c in _int_malloc (av=av@entry=0x7f8a20434aa0 > , bytes=bytes@entry=129) at malloc.c:3797 > #7 0x7f8a202cf8aa in _int_realloc (av=av@entry=0x7f8a20434aa0 > , oldp=oldp@entry=0x55cf650a0900, oldsize=80, nb=144) at > malloc.c:4765 > #8 0x7f8a202d06db in __GI___libc_realloc (oldmem=0x55cf650a0910, > bytes=128) at malloc.c:3381 > #9 0x7f8a2097c2ac in reallocateData (options=8, allocSize= out>, header=0x55cf650a0910) at tools/qarraydata.cpp:183 > #10 QArrayData::reallocateUnaligned(QArrayData*, unsigned long, unsigned > long, QFlags) (data=0x55cf650a0910, > objectSize=objectSize@entry=2, capacity=52, options=...) at > tools/qarraydata.cpp:246 > #11 0x7f8a209f2352 in QTypedArrayData short>::reallocateUnaligned(QTypedArrayData*, unsigned long, > QFlags) (options=..., capacity=29, > data=) at > ../../include/QtCore/../../src/corelib/tools/qarraydata.h:228 > #12 QString::reallocData(unsigned int, bool) (this=0x7ffeea702398, alloc=29, > grow=) at text/qstring.cpp:2375 > #13 0x7f8a209f28c2 in QString::append(QString const&) > (this=this@entry=0x7ffeea702398, str=...) at text/qstring.cpp:2684 > #14 0x7f8a2096c0dd in qFormatLogMessage(QtMsgType, QMessageLogContext > const&, QString const&) (type=, context=, > str=) at global/qlogging.cpp:1414 > #15 0x7f8a2096cddf in stderr_message_handler (message=, > context=, type=) at global/qlogging.cpp:1742 > #16 qDefaultMessageHandler(QtMsgType, QMessageLogContext const&, QString > const&) (type=QtWarningMsg, context=..., message=...) at > global/qlogging.cpp:1786 > #17 0x7f8a20968a90 in qt_message_print(QtMsgType, QMessageLogContext > const&, QString const&) (msgType=QtWarningMsg, context=..., message=...) at > global/qlogging.cpp:1843 > #18 0x7f8a2096a00b in qt_message_output(QtMsgType, QMessageLogContext > const&, QString const&) (msgType=QtWarningMsg, context=..., message=...) at > global/qlogging.cpp:1924 > #19 0x7f8a20a6ab88 in QDebug::~QDebug() (this=0x7ffeea702490, > __in_chrg=) at io/qdebug.cpp:154 > #20 QDebug::~QDebug() (this=0x7ffeea702490, __in_chrg=) at > io/qdebug.cpp:148 > #21 0x7f8a1a14eab3 in KWin::printProps(KWin::DrmObject*) > (object=) at > /usr/src/debug/kwin5-5.23.5-6.1.x86_64/src/plugins/platforms/drm/drm_pipeline.cpp:621 > #22 0x7f8a1a152ef5 in KWin::DrmPipeline::printDebugInfo() const > (this=0x55cf644ee3b0) at > /usr/src/debug/kwin5-5.23.5-6.1.x86_64/src/plugins/platforms/drm/drm_pipeline.cpp:647 > #23 0x7f8a1a153428 in operator()() const > (__closure=__closure@entry=0x7ffeea702630) at > /usr/src/debug/kwin5-5.23.5-6.1.x86_64/src/plugins/platforms/drm/drm_pipeline.cpp:134 > #24 0x7f8a1a155cd4 in > KWin::DrmPipeline::commitPipelines(QVector const&, > KWin::DrmPipeline::CommitMode) (pipelines=..., > mode=KWin::DrmPipeline::CommitMode::Test) at > /usr/src/debug/kwin5-5.23.5-6.1.x86_64/src/plugins/platforms/drm/drm_pipeline.cpp:161 > #25 0x7f8a1a14d056 in > KWin::DrmGpu::commitCombination(QVector const&) > (pipelines=..., this=) at > /usr/src/debug/kwin5-5.23.5-6.1.x86_64/src/plugins/platforms/drm/drm_gpu.cpp:374 > #26 KWin::DrmGpu::findWorkingCombination(QVector const&, > QVector, QVector, > QVector const&) (this=, pipelines=..., > connectors=..., crtcs=..., planes=...) > at > /usr/src/debug/kwin5-5.23.5-6.1.x86_64/src/plugins/platforms/drm/drm_gpu.cpp:302 > #27 0x7f8a1a14de63 in operator()(KWin::DrmCrtc*, KWin::DrmPlane*) const > (__closure=__closure@entry=0x7ffeea7029b0, crtc=, > primaryPlane=) at > /usr/src/debug/kwin5-5.23.5-6.1.x86_64/src/plugins/platforms/drm/drm_gpu.cpp:331 > #28 0x7f8a1a14d655 in > KWin::DrmGpu::findWorkingCombination(QVector const&, > QVector, QVector, > QVector const&) (this=0x55cf631391e0, pipelines=..., > connectors=..., crtcs=..., planes=...) > at > /usr/src/debug/kwin5-5.23.5-6.1.x86_64/src/plugins/platforms/drm/drm_gpu.cpp:345 > #29 0x7f8a1a14de63 in operator()(KWin::DrmCrtc*, KWin::DrmPlane*) const > (__closure=__closure@entry=0x7ffeea702c60, crtc=, > primaryPlane=) at > /usr/src/debug/kwin5-5.23.5-6.1.x86_64/src/plugins/platforms/drm/drm_gpu.cpp:331 > #30 0x7f8a1a14d655 in &g
[kwin] [Bug 445894] Crash in KWin::DrmOutput::updateCursor -> malloc(): unsorted double linked list corrupted
https://bugs.kde.org/show_bug.cgi?id=445894 --- Comment #16 from Jiri Slaby --- (In reply to Vlad Zahorodnii from comment #15) > Can you confirm that this issue is gone in 5.24 beta? Waiting for beta to reach factory (a couple of days, I assume): https://build.opensuse.org/request/show/947521 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445894] Crash in KWin::DrmOutput::updateCursor -> malloc(): unsorted double linked list corrupted
https://bugs.kde.org/show_bug.cgi?id=445894 --- Comment #14 from Jiri Slaby --- Created attachment 145902 --> https://bugs.kde.org/attachment.cgi?id=145902=edit fix This DrmGpu::findWorkingCombination code is completely gone in master since: commit e2a0863843f92ab1f2f8d0c785a86570fc04d774 Author: Xaver Hugl Date: Tue Sep 28 10:29:56 2021 +0200 platforms/drm: more dynamic crtc assignment Anyway, if I do this in 5.23.5, it seems to fix the problem. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445894] Crash in KWin::DrmOutput::updateCursor -> malloc(): unsorted double linked list corrupted
https://bugs.kde.org/show_bug.cgi?id=445894 --- Comment #13 from Jiri Slaby --- Shouldn't the delete in DrmGpu::findWorkingCombination be preceded by allPipelines.removeLast() (or something like that)? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445894] Crash in KWin::DrmOutput::updateCursor -> malloc(): unsorted double linked list corrupted
https://bugs.kde.org/show_bug.cgi?id=445894
--- Comment #12 from Jiri Slaby ---
Created attachment 145901
--> https://bugs.kde.org/attachment.cgi?id=145901=edit
valgrind output
Looks promising (complete log attached):
> ==3522== Invalid read of size 1
> ==3522==at 0xCEAD79C:
> KWin::DrmPipeline::setCursor(QSharedPointer const&,
> QPoint const&) (drm_pipeline.cpp:324)
> ==3522==by 0xCE9AABE: KWin::DrmOutput::showCursor() (drm_output.cpp:108)
> ==3522==by 0xCE9ADFD:
> KWin::DrmOutput::updateTransform(KWin::AbstractOutput::Transform)
> (drm_output.cpp:323)
> ==3522==by 0xCE9692B: KWin::DrmBackend::updateOutputs() (drm_gpu.cpp:276)
> ==3522==by 0xCE990B8: KWin::DrmBackend::handleUdevEvent()
> (drm_backend.cpp:244)
> ==3522==by 0x6502422: UnknownInlinedFun (qobjectdefs_impl.h:398)
> ==3522==by 0x6502422: void doActivate(QObject*, int, void**)
> (qobject.cpp:3886)
> ==3522==by 0x65057FE: QSocketNotifier::activated(QSocketDescriptor,
> QSocketNotifier::Type, QSocketNotifier::QPrivateSignal)
> (moc_qsocketnotifier.cpp:178)
> ==3522==by 0x6505FFA: QSocketNotifier::event(QEvent*)
> (qsocketnotifier.cpp:302)
> ==3522==by 0x53CEA7E: QApplicationPrivate::notify_helper(QObject*,
> QEvent*) (qapplication.cpp:3632)
> ==3522==by 0x64CBDB9: QCoreApplication::notifyInternal2(QObject*,
> QEvent*) (qcoreapplication.cpp:1064)
> ==3522==by 0x652065A:
> QEventDispatcherUNIXPrivate::activateSocketNotifiers()
> (qeventdispatcher_unix.cpp:304)
> ==3522==by 0x6520ABA:
> QEventDispatcherUNIX::processEvents(QFlags)
> (qeventdispatcher_unix.cpp:511)
> ==3522== Address 0x1b65e4d0 is 112 bytes inside a block of size 136 free'd
> ==3522==at 0x484699B: operator delete(void*, unsigned long) (in
> /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
> ==3522==by 0xCEA9EEC:
> KWin::DrmGpu::findWorkingCombination(QVector const&,
> QVector, QVector,
> QVector const&)::{lambda(KWin::DrmCrtc*,
> KWin::DrmPlane*)#2}::operator()(KWin::DrmCrtc*, KWin::DrmPlane*) const
> (drm_gpu.cpp:333)
> ==3522==by 0xCEA970C:
> KWin::DrmGpu::findWorkingCombination(QVector const&,
> QVector, QVector,
> QVector const&) (drm_gpu.cpp:344)
> ==3522==by 0xCE96791: KWin::DrmBackend::updateOutputs() (drm_gpu.cpp:256)
> ==3522==by 0xCE990B8: KWin::DrmBackend::handleUdevEvent()
> (drm_backend.cpp:244)
> ==3522==by 0x6502422: UnknownInlinedFun (qobjectdefs_impl.h:398)
> ==3522==by 0x6502422: void doActivate(QObject*, int, void**)
> (qobject.cpp:3886)
> ==3522==by 0x65057FE: QSocketNotifier::activated(QSocketDescriptor,
> QSocketNotifier::Type, QSocketNotifier::QPrivateSignal)
> (moc_qsocketnotifier.cpp:178)
> ==3522==by 0x6505FFA: QSocketNotifier::event(QEvent*)
> (qsocketnotifier.cpp:302)
> ==3522==by 0x53CEA7E: QApplicationPrivate::notify_helper(QObject*,
> QEvent*) (qapplication.cpp:3632)
> ==3522==by 0x64CBDB9: QCoreApplication::notifyInternal2(QObject*,
> QEvent*) (qcoreapplication.cpp:1064)
> ==3522==by 0x652065A:
> QEventDispatcherUNIXPrivate::activateSocketNotifiers()
> (qeventdispatcher_unix.cpp:304)
> ==3522==by 0x6520ABA:
> QEventDispatcherUNIX::processEvents(QFlags)
> (qeventdispatcher_unix.cpp:511)
> ==3522== Block was alloc'd at
> ==3522==at 0x4843F2F: operator new(unsigned long) (in
> /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
> ==3522==by 0xCEA9C78:
> KWin::DrmGpu::findWorkingCombination(QVector const&,
> QVector, QVector,
> QVector const&)::{lambda(KWin::DrmCrtc*,
> KWin::DrmPlane*)#2}::operator()(KWin::DrmCrtc*, KWin::DrmPlane*) const
> (drm_gpu.cpp:324)
> ==3522==by 0xCEA970C:
> KWin::DrmGpu::findWorkingCombination(QVector const&,
> QVector, QVector,
> QVector const&) (drm_gpu.cpp:344)
> ==3522==by 0xCE96791: KWin::DrmBackend::updateOutputs() (drm_gpu.cpp:256)
> ==3522==by 0xCE990B8: KWin::DrmBackend::handleUdevEvent()
> (drm_backend.cpp:244)
> ==3522==by 0x6502422: UnknownInlinedFun (qobjectdefs_impl.h:398)
> ==3522==by 0x6502422: void doActivate(QObject*, int, void**)
> (qobject.cpp:3886)
> ==3522==by 0x65057FE: QSocketNotifier::activated(QSocketDescriptor,
> QSocketNotifier::Type, QSocketNotifier::QPrivateSignal)
> (moc_qsocketnotifier.cpp:178)
> ==3522==by 0x6505FFA: QSocketNotifier::event(QEvent*)
> (qsocketnotifier.cpp:302)
> ==3522==by 0x53CEA7E: QApplicationPrivate::notify_helper(QObject*,
> QEvent*) (qapplication.cpp:3632)
> ==3522==by 0x64CBDB9: QCoreApplication::notifyInternal2(QObject*,
> QEvent*) (qcoreapplication.cpp:1064)
> ==3522==by 0x652065A:
> QEventDispatcherUNIXPrivate::activateSocketNotifiers()
> (qeventdispatcher_unix.cpp:304)
> ==3522==by 0x6520ABA:
> QEventDispatcherUNIX::processEvents(QFlags)
> (qeventdispatcher_unix.cpp:511)
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 445894] Crash in KWin::DrmOutput::updateCursor -> malloc(): unsorted double linked list corrupted
https://bugs.kde.org/show_bug.cgi?id=445894 --- Comment #10 from Jiri Slaby --- (In reply to Vlad Zahorodnii from comment #9) > You can temporarily remove the capabilities by using setcap -r. When you're > done, sudo setcap CAP_SYS_NICE=+ep /path/to/kwin_wayland As I wrote, that quits after: > 26687 sched_setscheduler(0, SCHED_RR, 0x7ffd37879530) = -1 EPERM -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445894] Crash in KWin::DrmOutput::updateCursor -> malloc(): unsorted double linked list corrupted
https://bugs.kde.org/show_bug.cgi?id=445894 --- Comment #8 from Jiri Slaby --- (In reply to Vlad Zahorodnii from comment #7) > Most likely, kwin overwrites the data it shouldn't. It would be great if you > could run kwin with valgrind, but it can make the computer very unusable. You'd have to tell me how. kwin_wayland has cap_sys_nice=ep caps set. So if I wrap it by valgrind I get: > ==31896== > ==31896== Warning: Can't execute setuid/setgid/setcap executable: > /usr/bin/kwin_wayland > ==31896== Possible workaround: remove --trace-children=yes, if in effect > ==31896== > valgrind: /usr/bin/kwin_wayland: Permission denied If I unset those caps and create a wrapper: #!/bin/bash exec valgrind --log-file=/tmp/kwin_valgrind kwin_wayland.exe and set those caps to the wrapper (adding inheritance too): setcap cap_sys_nice=epi kwin_wayland It doesn't start. Changing valgrind to strace in that script shows, that it dies likely due to this: 26687 sched_setscheduler(0, SCHED_RR, 0x7ffd37879530) = -1 EPERM So the caps are not really inherited. Maybe ptrace() in valgrind/strace removes those caps. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445894] Crash in KWin::DrmOutput::updateCursor -> malloc(): unsorted double linked list corrupted
https://bugs.kde.org/show_bug.cgi?id=445894 Jiri Slaby changed: What|Removed |Added Version|5.23.3 |5.23.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428394] huge memory leak (Wayland session)
https://bugs.kde.org/show_bug.cgi?id=428394 --- Comment #13 from Jiri Slaby --- (In reply to Jiri Slaby from comment #12) > (In reply to David Edmundson from comment #11) > > *** Bug 441213 has been marked as a duplicate of this bug. *** > > FTR I'd say it's gone now. I didn't have to kill plasma for at least a month > (I don't even remember when I had to last time). plasma5-session-5.23.4-1.4.noarch I have. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428394] huge memory leak (Wayland session)
https://bugs.kde.org/show_bug.cgi?id=428394 --- Comment #12 from Jiri Slaby --- (In reply to David Edmundson from comment #11) > *** Bug 441213 has been marked as a duplicate of this bug. *** FTR I'd say it's gone now. I didn't have to kill plasma for at least a month (I don't even remember when I had to last time). -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 447872] konsole starts with Root Shell as default
https://bugs.kde.org/show_bug.cgi?id=447872 --- Comment #11 from Jiri Slaby --- (In reply to Ahmad Samir from comment #10) > (In reply to Axel Braun from comment #9) > > Same behaviour if you open a shell from dolphin with F4... > > Both use-cases use the same code, so it should be fixed for both of them. Confirmed. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 447872] konsole starts with Root Shell as default
https://bugs.kde.org/show_bug.cgi?id=447872
--- Comment #6 from Jiri Slaby ---
I believe you'll come up with sth like:
--- a/src/profile/ProfileManager.cpp
+++ b/src/profile/ProfileManager.cpp
@@ -211,7 +211,7 @@ void ProfileManager::loadAllProfiles(const QString
)
const QStringList = availableProfilePaths();
for (const QString : paths) {
Profile::Ptr profile = loadProfile(path);
-if (profile && !defaultProfileFileName.isEmpty() &&
path.endsWith(defaultProfileFileName)) {
+if (profile && !defaultProfileFileName.isEmpty() &&
QFileInfo(path).fileName() == defaultProfileFileName) {
_defaultProfile = profile;
}
}
--
You are receiving this mail because:
You are watching all bug changes.
[konsole] [Bug 447872] konsole starts with Root Shell as default
https://bugs.kde.org/show_bug.cgi?id=447872 --- Comment #5 from Jiri Slaby --- (In reply to Jiri Slaby from comment #4) > (In reply to Ahmad Samir from comment #3) > > I think I see what's causing this, I'll create an MR shortly. > > It's likely the endsWith... And Root Shell.profile vs Shell.profile -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 447872] konsole starts with Root Shell as default
https://bugs.kde.org/show_bug.cgi?id=447872 --- Comment #4 from Jiri Slaby --- (In reply to Ahmad Samir from comment #3) > I think I see what's causing this, I'll create an MR shortly. It's likely the endsWith... -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 447872] konsole starts with Root Shell as default
https://bugs.kde.org/show_bug.cgi?id=447872 --- Comment #2 from Jiri Slaby --- Bisected to: commit 50041fd02ee42cf2cd484f91869896419e09ef83 (HEAD) Author: Ahmad Samir Date: Wed Aug 11 13:38:12 2021 +0200 Simplify ProfileManager code Now all the profiles are loaded in the constructor; I didn't see any noticeable difference in loading times. Also all the profiles are loaded anyway because ProfileList calls ProfileManager::allProfiles() to populate the profiles menu ...etc. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 447872] konsole starts with Root Shell as default
https://bugs.kde.org/show_bug.cgi?id=447872 Jiri Slaby changed: What|Removed |Added CC||a.samir...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 447872] konsole starts with Root Shell as default
https://bugs.kde.org/show_bug.cgi?id=447872 --- Comment #1 from Jiri Slaby --- This opens the profile just fine. $ konsole --profile Shell It's just [Desktop Entry].DefaultProfile cannot be loaded somehow and Root Shell is used instead (and also set as the default). The same profile is mis-loaded in dolphin by F4. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 447872] New: konsole starts with Root Shell as default
https://bugs.kde.org/show_bug.cgi?id=447872 Bug ID: 447872 Summary: konsole starts with Root Shell as default Product: konsole Version: 21.12.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: jirisl...@gmail.com Target Milestone: --- SUMMARY Likely after update from 21.08.3 to 21.12.0, konsole starts with Root Shell profile as the default. STEPS TO REPRODUCE 1. run konsole 2. set some profile (not the Root Shell) as default 3. run konsole 4. the Root Shell is reset as default again OBSERVED RESULT In step 3, Root Shell is started EXPECTED RESULT The selected profile from step 2 should start. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20220101 KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.2 Kernel Version: 5.15.10-1.g85804f3-default (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i7-6600U CPU @ 2.60GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 520 ADDITIONAL INFORMATION $ grep ltProfile ~/.config/konsolerc DefaultProfile=Shell.profile $ cat /home/xslaby/.local/share/konsole/Shell.profile [Appearance] AntiAliasFonts=false ColorScheme=WhiteOnBlack DimmValue=43 Font=Misc Fixed,10,-1,5,57,0,0,0,0,0,SemiCondensed UseFontLineChararacters=true [Cursor Options] CursorShape=0 [General] DimWhenInactive=true InvertSelectionColors=true LocalTabTitleFormat=%d : %n (%w) Name=Shell Parent=FALLBACK/ TerminalColumns=80 TerminalRows=25 [Keyboard] KeyBindings=default [Scrolling] BlinkingCursorEnabled=false HistorySize=1 ScrollBarPosition=2 VerticalLine=true -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445894] Crash in KWin::DrmOutput::updateCursor -> malloc(): unsorted double linked list corrupted
https://bugs.kde.org/show_bug.cgi?id=445894 --- Comment #6 from Jiri Slaby --- (In reply to Zamundaaa from comment #5) > If you plug in and out without suspend, does that ever cause problems? Yes, sometimes -- still under KWin::DrmBackend::updateCursor() and further. Note that even if it doesn't crash, the secondary monitor output is always frozen after re-plug. I have to switch to a tty and back to have it redrawn (happens with suspend too). I don't even see a mouse pointer on that monitor otherwise. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445894] Crash in KWin::DrmOutput::updateCursor -> malloc(): unsorted double linked list corrupted
https://bugs.kde.org/show_bug.cgi?id=445894 --- Comment #4 from Jiri Slaby --- Today I encountered a little different crash: a bit different stack trace. But still a heap corruption and still KWin::DrmGpu::updateOutputs is common. > #5 0x7f9fea02fe8c in malloc_printerr (str=str@entry=0x7f9fea1616d0 > "malloc(): smallbin double linked list corrupted") at malloc.c:5543 > #6 0x7f9fea0332dc in _int_malloc (av=av@entry=0x7f9fea198aa0 > , bytes=bytes@entry=129) at malloc.c:3797 > #7 0x7f9fea0338fa in _int_realloc (av=av@entry=0x7f9fea198aa0 > , oldp=oldp@entry=0x55ac9a1aa920, oldsize=80, nb=144) at > malloc.c:4765 > #8 0x7f9fea03472b in __GI___libc_realloc (oldmem=0x55ac9a1aa930, > bytes=128) at malloc.c:3381 > #9 0x7f9fea6dd25c in reallocateData (options=8, allocSize= out>, header=0x55ac9a1aa930) at tools/qarraydata.cpp:183 > #10 QArrayData::reallocateUnaligned(QArrayData*, unsigned long, unsigned > long, QFlags) (data=0x55ac9a1aa930, > objectSize=objectSize@entry=2, capacity=52, options=...) at > tools/qarraydata.cpp:246 > #11 0x7f9fea7532f2 in QTypedArrayData short>::reallocateUnaligned(QTypedArrayData*, unsigned long, > QFlags) (options=..., capacity=25, > data=) at > ../../include/QtCore/../../src/corelib/tools/qarraydata.h:228 > #12 QString::reallocData(unsigned int, bool) (this=0x7ffd926347f8, alloc=25, > grow=) at text/qstring.cpp:2375 > #13 0x7f9fea753862 in QString::append(QString const&) > (this=this@entry=0x7ffd926347f8, str=...) at text/qstring.cpp:2684 > #14 0x7f9fea6cd0ad in qFormatLogMessage(QtMsgType, QMessageLogContext > const&, QString const&) (type=, context=, > str=) at global/qlogging.cpp:1414 > #15 0x7f9fea6cddaf in stderr_message_handler (message=, > context=, type=) at global/qlogging.cpp:1742 > #16 qDefaultMessageHandler(QtMsgType, QMessageLogContext const&, QString > const&) (type=QtWarningMsg, context=..., message=...) at > global/qlogging.cpp:1786 > #17 0x7f9fea6c9a60 in qt_message_print(QtMsgType, QMessageLogContext > const&, QString const&) (msgType=QtWarningMsg, context=..., message=...) at > global/qlogging.cpp:1843 > #18 0x7f9fea6cafdb in qt_message_output(QtMsgType, QMessageLogContext > const&, QString const&) (msgType=QtWarningMsg, context=..., message=...) at > global/qlogging.cpp:1924 > #19 0x7f9fea7cbaa8 in QDebug::~QDebug() (this=0x7ffd926348d8, > __in_chrg=) at io/qdebug.cpp:154 > #20 QDebug::~QDebug() (this=0x7ffd926348d8, __in_chrg=) at > io/qdebug.cpp:148 > #21 0x7f9fe3ef8282 in KWin::DrmPipeline::printDebugInfo() const > (this=0x55ac99e04190) at > /usr/src/debug/kwin5-5.23.3-1.1.x86_64/src/plugins/platforms/drm/drm_pipeline.cpp:634 > #22 0x7f9fe3ef8408 in operator()() const > (__closure=__closure@entry=0x7ffd926349f0) at > /usr/src/debug/kwin5-5.23.3-1.1.x86_64/src/plugins/platforms/drm/drm_pipeline.cpp:134 > #23 0x7f9fe3efacb4 in > KWin::DrmPipeline::commitPipelines(QVector const&, > KWin::DrmPipeline::CommitMode) (pipelines=..., > mode=KWin::DrmPipeline::CommitMode::Test) at > /usr/src/debug/kwin5-5.23.3-1.1.x86_64/src/plugins/platforms/drm/drm_pipeline.cpp:161 > #24 0x7f9fe3ef20f6 in > KWin::DrmGpu::commitCombination(QVector const&) > (pipelines=..., this=) at > /usr/src/debug/kwin5-5.23.3-1.1.x86_64/src/plugins/platforms/drm/drm_gpu.cpp:373 > #25 KWin::DrmGpu::findWorkingCombination(QVector const&, > QVector, QVector, > QVector const&) (this=, pipelines=..., > connectors=..., crtcs=..., planes=...) > at > /usr/src/debug/kwin5-5.23.3-1.1.x86_64/src/plugins/platforms/drm/drm_gpu.cpp:302 > #26 0x7f9fe3ef2e4d in operator()(KWin::DrmCrtc*, KWin::DrmPlane*) const > (__closure=__closure@entry=0x7ffd92634d70, crtc=0x55ac964765e0, > primaryPlane=) at > /usr/src/debug/kwin5-5.23.3-1.1.x86_64/src/plugins/platforms/drm/drm_gpu.cpp:331 > #27 0x7f9fe3ef26dd in > KWin::DrmGpu::findWorkingCombination(QVector const&, > QVector, QVector, > QVector const&) (this=0x55ac963d3870, pipelines=..., > connectors=..., crtcs=..., planes=...) > at > /usr/src/debug/kwin5-5.23.3-1.1.x86_64/src/plugins/platforms/drm/drm_gpu.cpp:344 > #28 0x7f9fe3ef2e4d in operator()(KWin::DrmCrtc*, KWin::DrmPlane*) const > (__closure=__closure@entry=0x7ffd92635020, crtc=0x55ac96475ee0, > primaryPlane=) at > /usr/src/debug/kwin5-5.23.3-1.1.x86_64/src/plugins/platforms/drm/drm_gpu.cpp:331 > #29 0x7f9fe3ef26dd in > KWin::DrmGpu::findWorkingCombination(QVector const&, > QVector, QVector, > QVector const&) (this=0x55ac963d3870, pipelines= out>, connectors=..., crtcs=..., planes=...) > at > /usr/src/debug/kwin5-5.23.3-1.1.x86_64/src/p
[kwin] [Bug 445894] Crash in KWin::DrmOutput::updateCursor -> malloc(): unsorted double linked list corrupted
https://bugs.kde.org/show_bug.cgi?id=445894 --- Comment #3 from Jiri Slaby --- Created attachment 144500 --> https://bugs.kde.org/attachment.cgi?id=144500=edit drm_info without TB -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445894] Crash in KWin::DrmOutput::updateCursor -> malloc(): unsorted double linked list corrupted
https://bugs.kde.org/show_bug.cgi?id=445894 --- Comment #2 from Jiri Slaby --- Created attachment 144499 --> https://bugs.kde.org/attachment.cgi?id=144499=edit drm_info with TB -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445894] Crash in KWin::DrmOutput::updateCursor -> malloc(): unsorted double linked list corrupted
https://bugs.kde.org/show_bug.cgi?id=445894 Jiri Slaby changed: What|Removed |Added Version|5.23.2 |5.23.3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445894] Crash in KWin::DrmOutput::updateCursor -> malloc(): unsorted double linked list corrupted
https://bugs.kde.org/show_bug.cgi?id=445894 Jiri Slaby changed: What|Removed |Added Blocks||446101 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=446101 [Bug 446101] Crash in KWin::DrmPipeline::setCursor -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446101] New: Crash in KWin::DrmPipeline::setCursor
https://bugs.kde.org/show_bug.cgi?id=446101 Bug ID: 446101 Summary: Crash in KWin::DrmPipeline::setCursor Product: kwin Version: 5.23.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: platform-drm Assignee: kwin-bugs-n...@kde.org Reporter: jirisl...@gmail.com CC: kwin-bugs-n...@kde.org, n...@kde.org Depends on: 445894 Target Milestone: --- Created attachment 143956 --> https://bugs.kde.org/attachment.cgi?id=143956=edit gdb's "bt full" of the crash +++ This bug was initially created as a clone of Bug #445894 +++ Maybe it's the same bug as I did exactly the same, but the backtrace is different. SUMMARY A crash occurred during resume from suspend. STEPS TO REPRODUCE 1. suspend notebook 2. connect thunderbolt with external monitor connected 3. resume notebook. 4. (rare) crash occurs OBSERVED RESULT > #0 0x7f52faaf2789 in > KWin::DrmPipeline::setCursor(QSharedPointer const&, > QPoint const&) (this=0x55a48387d990, buffer=..., hotspot=...) at > /usr/src/debug/kwin5-5.23.2-2.1.x86_64/src/plugins/platforms/drm/drm_pipeline.cpp:328 > > #1 0x7f52faadfa6f in KWin::DrmOutput::showCursor() (this=0x55a4838abe60) > at > /usr/src/debug/kwin5-5.23.2-2.1.x86_64/src/plugins/platforms/drm/drm_output.cpp:108 > > #2 0x7f52faadfd9e in > KWin::DrmOutput::updateTransform(KWin::AbstractOutput::Transform) > (this=0x55a4838abe60, transform=) at > /usr/src/debug/kwin5-5.23.2-2.1.x86_64/src/plugins/platforms/drm/drm_output.cpp:323 > > #3 0x7f52faadb8ec in KWin::DrmGpu::updateOutputs() (this= out>) at > /usr/src/debug/kwin5-5.23.2-2.1.x86_64/src/plugins/platforms/drm/drm_gpu.cpp:276 > #4 KWin::DrmBackend::updateOutputs() (this=) at > /usr/src/debug/kwin5-5.23.2-2.1.x86_64/src/plugins/platforms/drm/drm_backend.cpp:355 > #5 0x7f52faadd77a in KWin::DrmBackend::reactivate() > (this=0x55a481125c60) at > /usr/src/debug/kwin5-5.23.2-2.1.x86_64/src/plugins/platforms/drm/drm_backend.cpp:159 > #6 KWin::DrmBackend::reactivate() (this=0x55a481125c60) at > /usr/src/debug/kwin5-5.23.2-2.1.x86_64/src/plugins/platforms/drm/drm_backend.cpp:142 > #7 0x7f53013e3043 in QtPrivate::QSlotObjectBase::call(QObject*, void**) > (a=0x7fffb4a3f630, r=0x55a481125c60, this=0x55a48113e560) at > ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 > #8 doActivate(QObject*, int, void**) (sender=0x55a481121530, > signal_index=4, argv=0x7fffb4a3f630) at kernel/qobject.cpp:3886 > #9 0x7f53013dc50f in QMetaObject::activate(QObject*, QMetaObject const*, > int, void**) (sender=, m=m@entry=0x7f5302e25840 > , > local_signal_index=local_signal_index@entry=1, > argv=argv@entry=0x7fffb4a3f630) at kernel/qobject.cpp:3946 > #10 0x7f5302bc4a12 in KWin::Session::activeChanged(bool) (this= out>, _t1=) at > /usr/src/debug/kwin5-5.23.2-2.1.x86_64/build/src/kwin_autogen/EWIEGA46WW/moc_session.cpp:150 > #11 0x7f5302bd55ff in KWin::LogindSession::updateActive(bool) > (active=, this=0x55a481121530) at > /usr/src/debug/kwin5-5.23.2-2.1.x86_64/src/session_logind.cpp:303 > #12 KWin::LogindSession::handlePropertiesChanged(QString const&, > QMap const&) (interfaceName=, > properties=..., this=0x55a481121530) at > /usr/src/debug/kwin5-5.23.2-2.1.x86_64/src/session_logind.cpp:324 > #13 KWin::LogindSession::handlePropertiesChanged(QString const&, > QMap const&) (properties=..., interfaceName= out>, this=0x55a481121530) at > /usr/src/debug/kwin5-5.23.2-2.1.x86_64/src/session_logind.cpp:319 > #14 KWin::LogindSession::qt_static_metacall(QObject*, QMetaObject::Call, int, > void**) (_o=0x55a481121530, _id=, _a=, > _c=) at > /usr/src/debug/kwin5-5.23.2-2.1.x86_64/build/src/kwin_autogen/EWIEGA46WW/moc_session_logind.cpp:88 > #15 0x7f5302bc7c01 in KWin::LogindSession::qt_static_metacall(QObject*, > QMetaObject::Call, int, void**) (_a=0x7fffb4a3f7e0, _id=1, > _c=QMetaObject::InvokeMetaMethod, _o=0x55a481121530) at > /usr/src/debug/kwin5-5.23.2-2.1.x86_64/build/src/kwin_autogen/EWIEGA46WW/moc_session_logind.cpp:83 > #16 KWin::LogindSession::qt_metacall(QMetaObject::Call, int, void**) > (this=0x55a481121530, _c=QMetaObject::InvokeMetaMethod, _id=1, > _a=0x7fffb4a3f7e0) at > /usr/src/debug/kwin5-5.23.2-2.1.x86_64/build/src/kwin_autogen/EWIEGA46WW/moc_session_logind.cpp:125 > #17 0x7f5302e6069b in () at /lib64/libQt5DBus.so.5 > #18 0x7f53013d8fee in QObject::event(QEvent*) (this=0x55a481121530, > e=0x7f52f401b430) at kernel/qobject.cpp:1314 > #19 0x7f5302104a7f in QApplicationPrivate::notify_helper(QObject*, > QEvent*) (this=, receiver=0x55a481121530, e=0x7f52f401b430) at > kernel/qapplication.cpp:3632 > #20 0x7f53013ac9fa in QCoreApplication::notifyInternal2(QObject*, > QEvent*) (receiver=0x55a481121530, event=0x7f52f401b430) at > kernel/qcoreapplication.cpp:1064 > #21
[kwin] [Bug 445894] New: Crash in KWin::DrmOutput::updateCursor -> malloc(): unsorted double linked list corrupted
https://bugs.kde.org/show_bug.cgi?id=445894 Bug ID: 445894 Summary: Crash in KWin::DrmOutput::updateCursor -> malloc(): unsorted double linked list corrupted Product: kwin Version: 5.23.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: platform-drm Assignee: kwin-bugs-n...@kde.org Reporter: jirisl...@gmail.com Target Milestone: --- Created attachment 143823 --> https://bugs.kde.org/attachment.cgi?id=143823=edit gdb's "bt full" of the crash SUMMARY A crash occurred during resume from suspend. STEPS TO REPRODUCE 1. suspend notebook 2. connect thunderbolt with external monitor connected 3. resume notebook. 4. (rare) crash occurs OBSERVED RESULT > #0 __pthread_kill_implementation (threadid=, > signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 > #1 0x7f3b21bb28e3 in __pthread_kill_internal (signo=6, > threadid=) at pthread_kill.c:78 > #2 0x7f3b21b656f6 in __GI_raise (sig=sig@entry=6) at > ../sysdeps/posix/raise.c:26 > #3 0x7f3b21b4f845 in __GI_abort () at abort.c:100 > #4 0x7f3b21ba6a67 in __libc_message (action=action@entry=do_abort, > fmt=fmt@entry=0x7f3b21ce369f "%s\n") at ../sysdeps/posix/libc_fatal.c:155 > #5 0x7f3b21bbc86c in malloc_printerr (str=str@entry=0x7f3b21ce6788 > "malloc(): unsorted double linked list corrupted") at malloc.c:5543 > #6 0x7f3b21bbf89c in _int_malloc (av=av@entry=0x7f3b21d1daa0 > , bytes=bytes@entry=1040) at malloc.c:3897 > #7 0x7f3b21bc06d9 in __GI___libc_malloc (bytes=1040) at malloc.c:3216 > #8 0x7f3b21de296c in operator new(unsigned long) (sz=1040) at > ../../../../libstdc++-v3/libsupc++/new_op.cc:50 > #9 0x7f3b22b54262 in QRasterPaintEngine::createState(QPainterState*) > const () at /lib64/libQt5Gui.so.5 > #10 0x7f3b22b70c56 in QPainter::begin(QPaintDevice*) () at > /lib64/libQt5Gui.so.5 > #11 0x7f3b1bb717cb in KWin::DrmOutput::updateCursor() > (this=0x5596f79cc0d0) at > /usr/src/debug/kwin5-5.23.2-2.1.x86_64/src/plugins/platforms/drm/drm_output.cpp:150 > #12 0x7f3b1bb62527 in KWin::DrmBackend::updateCursor() > (this=0x5596f71d0210) at > /usr/src/debug/kwin5-5.23.2-2.1.x86_64/src/plugins/platforms/drm/drm_backend.cpp:571 > #13 0x7f3b1bb69071 in KWin::DrmBackend::handleUdevEvent() > (this=0x5596f71d0210) at > /usr/src/debug/kwin5-5.23.2-2.1.x86_64/src/plugins/platforms/drm/drm_backend.cpp:245 > #14 0x7f3b2246e043 in QtPrivate::QSlotObjectBase::call(QObject*, void**) > (a=0x7ffc38c73d50, r=0x5596f71d0210, this=0x5596f71db7a0) at > ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 > #15 doActivate(QObject*, int, void**) (sender=0x5596f71db4a0, > signal_index=3, argv=0x7ffc38c73d50) at kernel/qobject.cpp:3886 > #16 0x7f3b2246750f in QMetaObject::activate(QObject*, QMetaObject const*, > int, void**) (sender=sender@entry=0x5596f71db4a0, m=m@entry=0x7f3b2270dac0, > local_signal_index=local_signal_index@entry=0, > argv=argv@entry=0x7ffc38c73d50) at kernel/qobject.cpp:3946 > #17 0x7f3b2247141f in QSocketNotifier::activated(QSocketDescriptor, > QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) > (this=this@entry=0x5596f71db4a0, _t1=..., _t2=, _t3=...) at > .moc/moc_qsocketnotifier.cpp:178 > #18 0x7f3b22471c1b in QSocketNotifier::event(QEvent*) > (this=0x5596f71db4a0, e=0x7ffc38c73e70) at kernel/qsocketnotifier.cpp:302 > #19 0x7f3b2318fa7f in QApplicationPrivate::notify_helper(QObject*, > QEvent*) (this=, receiver=0x5596f71db4a0, e=0x7ffc38c73e70) at > kernel/qapplication.cpp:3632 > #20 0x7f3b224379fa in QCoreApplication::notifyInternal2(QObject*, > QEvent*) (receiver=0x5596f71db4a0, event=0x7ffc38c73e70) at > kernel/qcoreapplication.cpp:1064 > #21 0x7f3b2248c28b in > QEventDispatcherUNIXPrivate::activateSocketNotifiers() (this=0x5596f71755c0) > at kernel/qeventdispatcher_unix.cpp:304 > #22 0x7f3b2248c6eb in > QEventDispatcherUNIX::processEvents(QFlags) > (this=, flags=...) at kernel/qeventdispatcher_unix.cpp:511 > #23 0x5596f70ab39d in > QUnixEventDispatcherQPA::processEvents(QFlags) > (this=, flags=...) at qunixeventdispatcher.cpp:63 > #24 0x7f3b224363fb in > QEventLoop::exec(QFlags) > (this=this@entry=0x7ffc38c74000, flags=..., flags@entry=...) at > ../../include/QtCore/../../src/corelib/global/qflags.h:69 > #25 0x7f3b2243e6e0 in QCoreApplication::exec() () at > ../../include/QtCore/../../src/corelib/global/qflags.h:121 > #26 0x5596f704e625 in main(int, char**) (argc=, > argv=) at > /usr/src/debug/kwin5-5.23.2-2.1.x86_64/src/main_wayland.cpp:745 SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 2027 KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.15.2-1.g26a203b-default (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™
[frameworks-kio] [Bug 433993] Dolphin Crash when creating a folder in remote folder (kio-Gdrive, FTP)
https://bugs.kde.org/show_bug.cgi?id=433993 Jiri Slaby changed: What|Removed |Added CC||jirisl...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 444861] Dolphin crashed when I created a new folder in google drive using kio-gdrive
https://bugs.kde.org/show_bug.cgi?id=444861 Jiri Slaby changed: What|Removed |Added Resolution|--- |DUPLICATE CC||jirisl...@gmail.com Status|REPORTED|RESOLVED --- Comment #2 from Jiri Slaby --- *** This bug has been marked as a duplicate of bug 433993 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 433993] Dolphin Crash when creating a folder in remote folder (kio-Gdrive, FTP)
https://bugs.kde.org/show_bug.cgi?id=433993 Jiri Slaby changed: What|Removed |Added CC||alf...@gmail.com --- Comment #17 from Jiri Slaby --- *** Bug 444861 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 378152] The SemiCondensed Fixed font isn't handled correctly by Konsole
https://bugs.kde.org/show_bug.cgi?id=378152 --- Comment #12 from Jiri Slaby --- (In reply to Jiri Slaby from comment #7) > Confirmed. The qt fix doesn't help (obviously; but is a bug too). Commenting > out the line (patch attached) indeed helps. I actually need both changes in both libqt and konsole. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 378152] The SemiCondensed Fixed font isn't handled correctly by Konsole
https://bugs.kde.org/show_bug.cgi?id=378152 --- Comment #10 from Jiri Slaby --- (In reply to Ahmad Samir from comment #8) > Commenting out that line breaks the "draw intense colours in bold fonts" > option, very tricky stuff :) Sure, that's why the patch is marked as a workaround, not a fix :). (In reply to Ahmad Samir from comment #9) > A side point, it looks like semicondensed monospace fonts are a rare thing, > even Noto fonts, which have more weight/styles than any other font family > I've ever seen, doesn't have a semicondensed monospace font. Misc Fixed which I am using over a decade in xterm and which I wanted to teach konsole to use... One more thing: konsole picks /usr/share/fonts/misc/6x13-ISO8859-1.pcf.gz instead of /usr/share/fonts/misc/6x13.pcf.gz. I have to delete the former to have proper unicode support using the same font... -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 378152] The SemiCondensed Fixed font isn't handled correctly by Konsole
https://bugs.kde.org/show_bug.cgi?id=378152 --- Comment #7 from Jiri Slaby --- Created attachment 143440 --> https://bugs.kde.org/attachment.cgi?id=143440=edit workaround patch (In reply to Ahmad Samir from comment #6) > I am not sure it's the same issue as that upstream bug; the code in Konsole > sets the styleName to an empty string Confirmed. The qt fix doesn't help (obviously; but is a bug too). Commenting out the line (patch attached) indeed helps. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 378152] The SemiCondensed Fixed font isn't handled correctly by Konsole
https://bugs.kde.org/show_bug.cgi?id=378152 Jiri Slaby changed: What|Removed |Added URL||https://bugreports.qt.io/br ||owse/QTBUG-80952 --- Comment #5 from Jiri Slaby --- So this is already known: https://bugreports.qt.io/browse/QTBUG-80952 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 378152] The SemiCondensed Fixed font isn't handled correctly by Konsole
https://bugs.kde.org/show_bug.cgi?id=378152
--- Comment #4 from Jiri Slaby ---
It's because QFont::fromString(const QString ) doesn't OR the
QFont::resolve_mask with QFont::StyleNameResolved the same as
QFont::setStyleName(const QString ) does. So this is an upstream (Qt)
bug. Reproducer:
$ cat main.cpp
#include
#include
#include
#include
static void setLabelFont(QLabel , const QFont )
{
qDebug() << __func__ << font <<
"style" << font.style() << "stylename" << font.styleName()
<< "resolve" << QString::number(font.resolve(), 16);
label.setFont(font);
label.setText(font.toString());
}
int main(int argc, char *argv[])
{
QApplication a(argc, argv);
QDialog w;
QLabel label1(), label2();
QFont font1;
font1.fromString("Misc Fixed,10,-1,5,57,0,0,0,0,0,SemiCondensed");
auto font2 = font1;
#if 1
font2.resolve(font2.resolve() |
QFont::ResolveProperties::StyleNameResolved);
#else
font2.setStyleName("SemiCondensed");
#endif
setLabelFont(label1, font1);
setLabelFont(label2, font2);
w.show();
label2.move(0, label1.size().height() + 5);
w.resize(label1.size().width(), label2.pos().y() +
label2.size().height());
return a.exec();
}
$ cat Makefile
COMPONENTS=Qt5Core Qt5Gui Qt5Widgets
CXXFLAGS=$(shell pkg-config --cflags $(COMPONENTS)) -Wall -Og -g
LDLIBS=$(shell pkg-config --libs $(COMPONENTS)) -flto
all: main
Both labels are with the same font, the latter sets the resolve_mask and is
shown correctly.
--
You are receiving this mail because:
You are watching all bug changes.
[konsole] [Bug 378152] The SemiCondensed Fixed font isn't handled correctly by Konsole
https://bugs.kde.org/show_bug.cgi?id=378152 Jiri Slaby changed: What|Removed |Added Version|19.04.2 |21.08.2 CC||jirisl...@gmail.com --- Comment #3 from Jiri Slaby --- Still happens. For me on openSUSE with 21.08.2. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 441213] [wayland] plasmashell leaks a lot of memory
https://bugs.kde.org/show_bug.cgi?id=441213 Jiri Slaby changed: What|Removed |Added Summary|428394 |[wayland] plasmashell leaks ||a lot of memory -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 441213] New: 428394
https://bugs.kde.org/show_bug.cgi?id=441213 Bug ID: 441213 Summary: 428394 Product: plasmashell Version: 5.22.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic-performance Assignee: plasma-b...@kde.org Reporter: jirisl...@gmail.com Target Milestone: 1.0 SUMMARY After some uptime, plasmashell under wayland eats all the free memory here. This looks similar to bug 428394 (leak in intel's driver). STEPS TO REPRODUCE 1. use plasma 2. memory is filled up SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20210817 KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 Kernel Version: 5.13.1-1.gbebf622-default (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i7-6600U CPU @ 2.60GHz Memory: 15.1 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 520 ADDITIONAL INFORMATION heaptrack at: http://decibel.fi.muni.cz/~xslaby/n/heaptrack.plasmashell.20733.zst But it is somehow mangled. Heaptrack apparently doesn't support DWARF 5, I see a lot of: src/interpret/heaptrack_interpret.cpp:351 ERROR:Failed to create backtrace state for module /usr/lib64/qt5/plugins/platforms/libqwayland-generic.so: unrecognized DWARF version in .debug_info at 6 / Success (error code 0) > $ readelf --debug-dump=info > /usr/lib/debug/usr/lib64/qt5/plugins/platforms/libqwayland-generic.so-5.15.2+kde28-1.1.x86_64.debug > Contents of the .debug_info section: > ... > Compilation Unit @ offset 0x23: >Length:0x3960d (32-bit) >Version: 5 <--- >Unit Type: DW_UT_compile (1) >Abbrev Offset: 0x0 >Pointer Size: 8 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 440778] Crash when invoking send-keyboard-input shortcut in wayland
https://bugs.kde.org/show_bug.cgi?id=440778 --- Comment #8 from Jiri Slaby --- (In reply to Jiri Slaby from comment #7) > (In reply to David Redondo from comment #6) > > We probably should not be in this X code path at all on Wayland? > > That's what I think too -- if I am in a wayland window. It's likely that khotkeys (ShortcutsHandler::send_macro_key in particular) do not support wayland quite yet. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 440778] Crash when invoking send-keyboard-input shortcut in wayland
https://bugs.kde.org/show_bug.cgi?id=440778 --- Comment #7 from Jiri Slaby --- (In reply to David Redondo from comment #6) > We probably should not be in this X code path at all on Wayland? That's what I think too -- if I am in a wayland window. Not sure what should happen when in Xwayland window, but maybe libX11 should not be invoked too. In any way, both these scenario crash. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 440778] Crash when invoking send-keyboard-input shortcut in wayland
https://bugs.kde.org/show_bug.cgi?id=440778
--- Comment #5 from Jiri Slaby ---
(In reply to Nate Graham from comment #4)
> Feel free to submit a merge request to fix it!
If I only knew what the root cause is -- I only described the symptoms... The
Display is callocated (so zeroed) and lock_fns explicitly set to NULL in
OpenDisplay. lock_fns is then touched (Xmalloc-ed) only in _XInitDisplayLock.
Anyway, whole _XDisplay structure seems to be mangled:
> $4 = {ext_data = 0x7f169265d0a0 , free_funcs =
> 0x7f1692509d70, fd = 1, conn_checker = 0, proto_major_version = 904794160,
> proto_minor_version = 21891, vendor = 0x558335ee1100 "", resource_base =
> 4294967296, resource_mask = 94022033870896, resource_id = 0, resource_shift =
> 0,
> resource_alloc = 0x0, byte_order = 904802176, bitmap_unit = 21891,
> bitmap_pad = 0, bitmap_bit_order = 0, nformats = 0, pixmap_format = 0x0,
> vnumber = 0,
> release = 0, head = 0x3, tail = 0xf8, qlen = 256, last_request_read =
> 94022033919856, request = 0, last_req = 0x0, buffer = 0x0,
> bufptr = 0x1 , bufmax =
> 0x558335ee10e8 "\350\020\356\065\203U", max_request_size = 904794344,
> db = 0x558335ee1030, synchandler = 0x558335ee1100, display_name =
> 0x558335ee1100 "", default_screen = 904794160, nscreens = 21891, screens =
> 0x0,
> motion_buffer = 0, flags = 0, min_keycode = 0, max_keycode = 0, keysyms =
> 0x0, modifiermap = 0xdd, keysyms_per_keycode = 0, xdefaults = 0x0,
> scratch_buffer = 0x0, scratch_length = 0, ext_number = 0, ext_procs = 0x0,
> event_vec = {0xe1, 0x7f16903b4640, 0x558335f569e0, 0x640001,
> 0x7f16903b3c68,
> 0x7f1695fa7680 , 0x1, 0x0, 0x0, 0x0,
> 0x7f16903b3c68, 0x7f1695fa7680 , 0x1, 0x0, 0x0,
> 0x0,
> 0x7f16903b3c68, 0x7f1695fa7680 , 0x1, 0x0,
> 0x0, 0x0, 0x7f16903b3c68, 0x7f1695fa7680 , 0x1,
> 0x0,
> 0x0, 0x0, 0x21,
> 0x7f16925aa460
> wl_registry*, unsigned int, QString const&, unsigned int)>, 0x558335edacc0,
> 0x0, 0x31, 0x7f16959c1a00 , 0x558335ee0ed0, 0x5583357d3840
> , 0x0, 0x0, 0x31, 0x20001, 0x1,
> 0x558335ee1260, 0x0, 0x0, 0x31, 0x558335ed97e0, 0x0, 0x626b782f6769666e,
> 0x558335ee1200, 0x0, 0x31, 0x73782f656d6f682f, 0x6f632e2f7962616c,
> 0x626b782f6769666e, 0x0, 0x0, 0x31, 0x558335ee1310, 0x558335ed97a0,
> 0x558335ee1410, 0x0, 0x0, 0x41, 0x6168732f7273752f, 0x6c61636f6c2f6572,
> 0x5f434c2f73632f65, 0x534547415353454d, 0x6f6d2e6362696c2f, 0x0, 0x0,
> 0x41, 0x558335ee1370, 0x7f160001, 0x558335edba20, 0x5583363fd630, 0x0,
> 0x0,
> 0x0, 0x21, 0x558335edca90, 0x, 0x0, 0x21,
> 0x626b782f6374652f, 0x0, 0x62, 0x21, 0x558335eb2e40, 0x0, 0x0, 0x71,
> 0x270001, 0x28, 0x18,
> 0x5f00700077007a, 0x6d006900720070, 0x5f007900720061, 0x65006c00650073,
> 0x6f006900740063, 0x650064005f006e, 0x65006300690076, 0x6e0061006d005f,
> 0x72006500670061, 0x310076005f, 0x31, 0x558335f6d710, 0x400,
> 0x558335f4b830, 0x20001bd, 0x0, 0x31, 0x10001, 0x2, 0x18,
> 0xde78c2c00034, 0x30,
> 0x21, 0x31646f4d, 0x0, 0x0, 0x61, 0x7f1696190750 QObjectPrivate+16>, 0x558335eb5570, 0x0, 0x5583357d38f0
> ,
> 0x35ee1130, 0x0, 0x0}, wire_vec = {0x558335eb4ba0, 0x0, 0x0, 0x0, 0x21,
> 0x7f169265de18 ,
> 0x558335eec340, 0x0, 0x101, 0xc0001, 0xe, 0x18, 0x24, 0xa0060,
> 0x2c, 0xa0060, 0x74, 0xa0060, 0x558336020de0, 0x100a0, 0x18,
> 0xa0060, 0x0, 0x0, 0x48, 0xa0060, 0x58, 0xa0060, 0xc,
> 0xa0060, 0x0, 0x114, 0x0, 0xa0060, 0x50f00, 0x0, 0x558336020480,
> 0x558336011de0, 0x0, 0x13176, 0x101, 0xa0001, 0xe, 0x18, 0x0,
> 0xa0060, 0x558335f759b0, 0x100a0, 0xc, 0xa0060, 0x28, 0xa0060,
> 0x44, 0xa0060, 0x5c, 0xa0060, 0x78, 0xa0060, 0x0, 0x114,
> 0x90, 0xa0060, 0x0, 0x115, 0x224, 0xa0060, 0x240, 0x60060, 0x2ac,
> 0xa0060, 0x2c0, 0x60060, 0x21, 0x7f169265dfa0 QtWaylandClient::QWaylandShm+16>, 0x558335eec750, 0x558335eeca40, 0x31,
> 0x70001,
> 0x8, 0x18, 0x75006e0069006c, 0x6200660078, 0x111, 0xac0001,
> 0x7f1600e8, 0x18, 0x737265760007, 0x5006e6f69, 0x6775626564,
> 0x686372610007,
> 0x300716572, 0x3e00444949, 0x702d74712e67726f, 0x512e7463656a6f72,
> 0x50512e4150512e74, 0x496d726f6674616c, 0x697461726765746e,
> 0x726f746361466e6f,
> 0x61667265746e4979, 0x332e352e6563, 0x73616c630009, 0x656d614e73,
> 0x6e694c510019, 0x65746e4962467875, 0x506e6f6974617267, 0x42006e6967756c,
> 0x6174654d0008, 0x7f0061746144, 0x558335ed9688, 0x7fff8b1f4660,
> 0x558335eb4840, 0x7fff8b1f46d8, 0x0, 0x5583357d38c0 ,
> 0x5583357d38c0 , 0x5583357d38c0
> , 0x31, 0x558335ee2091, 0x0, 0x0, 0x558335ed9680,
> 0x558335ee19d0, 0x21,
> 0
[systemsettings] [Bug 440778] Crash when invoking send-keyboard-input shortcut in wayland
https://bugs.kde.org/show_bug.cgi?id=440778 --- Comment #3 from Jiri Slaby --- (In reply to Jiri Slaby from comment #2) > (gdb) p/x $rax > $5 = 0x31 Seems to be 0x31 every time. So no corruption, or a deterministic one. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 440778] Crash when invoking send-keyboard-input shortcut in wayland
https://bugs.kde.org/show_bug.cgi?id=440778 --- Comment #2 from Jiri Slaby --- (In reply to Jiri Slaby from comment #0) > > #3 0x7f550492bb3e in XQueryExtension > > (dpy=dpy@entry=0x5628d28aa030, name=name@entry=0x7f54fc12e019 > > "XInputExtension", major_opcode=major_opcode@entry=0x7ffd4d60744c, > > first_event=first_event@entry=0x7ffd4d607450, > > first_error=first_error@entry=0x7ffd4d607454) 0x7f550492bb36 <+102>: test %rax,%rax 0x7f550492bb39 <+105>: je 0x7f550492bb40 0x7f550492bb3b <+107>: mov%rbp,%rdi => 0x7f550492bb3e <+110>: call *(%rax) (gdb) p/x $rax $5 = 0x31 include/X11/Xlibint.h:#define LockDisplay(d) if ((d)->lock_fns) (*(d)->lock_fns->lock_display)(d) (gdb) p dpy->lock_fns $6 = (struct _XLockPtrs *) 0x31 Well, (d)->lock_fns is not NULL in that 'if', but is bogus, so it crashes. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 440778] Crash when invoking send-keyboard-input shortcut in wayland
https://bugs.kde.org/show_bug.cgi?id=440778 --- Comment #1 from Jiri Slaby --- (In reply to Jiri Slaby from comment #0) > It always used to work. Now I switched from X11 to wayland and kded5 crashes > in XQueryExtension: (No matter if I press it while in wayland or X11 window.) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 440778] Crash when invoking send-keyboard-input shortcut in wayland
https://bugs.kde.org/show_bug.cgi?id=440778 Jiri Slaby changed: What|Removed |Added Summary|Crash when invoking |Crash when invoking |send-keyboard-input |send-keyboard-input |shortcut|shortcut in wayland -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 440778] New: Crash when invoking send-keyboard-input shortcut
https://bugs.kde.org/show_bug.cgi?id=440778 Bug ID: 440778 Summary: Crash when invoking send-keyboard-input shortcut Product: frameworks-kded Version: 5.84.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: fa...@kde.org Reporter: jirisl...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY I have kded5 configured to output this key sequence when pressing ctrl+alt+shift+a: Shift+A:c:k:e:d:-:b:y:Shift+;:Space:Shift+J:i:r:i:Space:Shift+S:l:a:b:y:Space:<:j:i:r:i:s:l:a:b:y:Shift+@:k:e:r:n:e:l:.:o:r:g:Shift+> It always used to work. Now I switched from X11 to wayland and kded5 crashes in XQueryExtension: > #2 () at ../sysdeps/unix/sysv/linux/sigaction.c > #3 0x7f550492bb3e in XQueryExtension > (dpy=dpy@entry=0x5628d28aa030, name=name@entry=0x7f54fc12e019 > "XInputExtension", major_opcode=major_opcode@entry=0x7ffd4d60744c, > first_event=first_event@entry=0x7ffd4d607450, > first_error=first_error@entry=0x7ffd4d607454) > at /usr/src/debug/libX11-1.7.2-1.1.x86_64/src/QuExt.c:62 > #4 0x7f54fc12bd62 in get_xinput_base (dpy=0x5628d28aa030) at > /usr/src/debug/libXtst-1.2.3-2.4.x86_64/src/XTest.c:79 > #5 find_display (dpy=0x5628d28aa030) at > /usr/src/debug/libXtst-1.2.3-2.4.x86_64/src/XTest.c:83 > #6 find_display (dpy=0x5628d28aa030) at > /usr/src/debug/libXtst-1.2.3-2.4.x86_64/src/XTest.c:83 > #7 0x7f54fc12cf42 in XTestQueryExtension (dpy=0x5628d28aa030, > event_base_return=0x7ffd4d6074f8, error_base_return=0x7ffd4d6074fc, > major_return=0x7ffd4d607500, minor_return=0x7ffd4d607508) > at /usr/src/debug/libXtst-1.2.3-2.4.x86_64/src/XTest.c:101 > #8 0x7f54fc3e8bda in KHotKeys::xtest () at > /usr/src/debug/khotkeys5-5.22.4-1.1.x86_64/libkhotkeysprivate/shortcuts_handler.cpp:113 > #9 KHotKeys::xtest () at > /usr/src/debug/khotkeys5-5.22.4-1.1.x86_64/libkhotkeysprivate/shortcuts_handler.cpp:107 > #10 KHotKeys::ShortcutsHandler::send_macro_key(QKeySequence const&, unsigned > long) (key=, window_P=1, this=) at > /usr/src/debug/khotkeys5-5.22.4-1.1.x86_64/libkhotkeysprivate/shortcuts_handler.cpp:163 > #11 0x7f54fc3db406 in > KHotKeys::ShortcutsHandler::send_macro_key(QKeySequence const&, unsigned > long) (this=, window_P=1, key=...) at > /usr/src/debug/khotkeys5-5.22.4-1.1.x86_64/libkhotkeysprivate/shortcuts_handler.cpp:150 > #12 KHotKeys::KeyboardInputAction::execute() (this=0x5628d2a59a30) at > /usr/src/debug/khotkeys5-5.22.4-1.1.x86_64/libkhotkeysprivate/actions/keyboard_input_action.cpp:150 > #13 0x7f54fc3d41bd in KHotKeys::ActionData::execute() > (this=0x5628d2a597c0) at > /usr/src/debug/khotkeys5-5.22.4-1.1.x86_64/libkhotkeysprivate/action_data/action_data.cpp:93 > #14 0x7f5505376fe8 in doActivate(QObject*, int, void**) > (sender=0x5628d2a1f240, signal_index=4, argv=0x7ffd4d6077a0) at > kernel/qobject.cpp:3898 > #15 0x7f550537047f in QMetaObject::activate(QObject*, QMetaObject const*, > int, void**) > (sender=sender@entry=0x5628d2a1f240, m=m@entry=0x7f55066330a0 > , local_signal_index=local_signal_index@entry=1, > argv=argv@entry=0x7ffd4d6077a0) at kernel/qobject.cpp:3946 > #16 0x7f5506114182 in QAction::triggered(bool) > (this=this@entry=0x5628d2a1f240, _t1=) at > .moc/moc_qaction.cpp:376 > #17 0x7f5506116db4 in QAction::activate(QAction::ActionEvent) > (this=0x5628d2a1f240, event=) at kernel/qaction.cpp:1161 > #18 0x7f54fffeeacc in QAction::trigger() (this=0x5628d2a1f240) at > /usr/include/qt5/QtWidgets/qaction.h:187 > #19 KGlobalAccelPrivate::_k_invokeAction(QString const&, QString const&, long > long) (this=0x7ffd4d607810, componentUnique=..., actionUnique= out>, timestamp=0) > at /usr/src/debug/kglobalaccel-5.84.0-1.2.x86_64/src/kglobalaccel.cpp:453 > #20 0x7f5505376fb3 in QtPrivate::QSlotObjectBase::call(QObject*, void**) > (a=0x7ffd4d607970, r=0x7f552650 <(anonymous > namespace)::Q_QGS_s_instance::innerFunction()::holder>, this=0x5628d2d65650) > at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 > #21 doActivate(QObject*, int, void**) (sender=0x5628d2cfa1d0, > signal_index=3, argv=0x7ffd4d607970) at kernel/qobject.cpp:3886 > #22 0x7f550537047f in QMetaObject::activate(QObject*, QMetaObject const*, > int, void**) (sender=, m=, > local_signal_index=local_signal_index@entry=0, > argv=argv@entry=0x7ffd4d607970) at kernel/qobject.cpp:3946 > #23 0x7f54abf4 in > OrgKdeKglobalaccelComponentInterface::globalShortcutPressed(QString const&, > QString const&, long long) (_t3=, _t2=, > _t1=, this=) > at > /usr/src/debug/kglobalaccel-5.84.0-1.2.x86_64/build/src/kglobalaccel_component_interface.moc:227 > #24 OrgKdeKglobalaccelComponentInterface::qt_static_metacall(QObject*, > QMetaObject::Call, int, void**) (_o=_o@entry=0x5628d2cfa1d0, >
[kwin] [Bug 438789] kwin_wayland crashed in KWin::DrmGpu::updateOutputs while un/re-plugging monitor
https://bugs.kde.org/show_bug.cgi?id=438789 Jiri Slaby changed: What|Removed |Added Attachment #139952|text/x-log |text/plain mime type|| -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438789] kwin_wayland crashed in KWin::DrmGpu::updateOutputs while un/re-plugging monitor
https://bugs.kde.org/show_bug.cgi?id=438789 --- Comment #14 from Jiri Slaby --- (In reply to Zamundaaa from comment #13) > Thanks for all the information, was really helpful in pinning it down. Thanks, patched, waiting for no crashes :). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435751] Plasma crashes when click on night color widget
https://bugs.kde.org/show_bug.cgi?id=435751 --- Comment #6 from Jiri Slaby --- *** Bug 439325 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439325] crash while moving weston window
https://bugs.kde.org/show_bug.cgi?id=439325 Jiri Slaby changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Jiri Slaby --- Crashed again after pressed Start key quickly twice in a row. It's likely a dup of bug 435751, i.e.: https://gitlab.freedesktop.org/mesa/mesa/-/issues/4902 *** This bug has been marked as a duplicate of bug 435751 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435751] Plasma crashes when click on night color widget
https://bugs.kde.org/show_bug.cgi?id=435751 Jiri Slaby changed: What|Removed |Added CC||txemafi...@gmail.com --- Comment #5 from Jiri Slaby --- *** Bug 439270 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439270] Plasma crashed (and recovered) on Wayland while moving/adding/deleting plasmoids in panel
https://bugs.kde.org/show_bug.cgi?id=439270 Jiri Slaby changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #2 from Jiri Slaby --- Looks like a dup of that one. And it is gfx driver bug, likely: https://gitlab.freedesktop.org/mesa/mesa/-/issues/4902 *** This bug has been marked as a duplicate of bug 435751 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435751] Plasma crashes when click on night color widget
https://bugs.kde.org/show_bug.cgi?id=435751 Jiri Slaby changed: What|Removed |Added CC||jirisl...@gmail.com --- Comment #4 from Jiri Slaby --- I think this is: https://gitlab.freedesktop.org/mesa/mesa/-/issues/4902 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439270] Plasma crashed (and recovered) on Wayland while moving/adding/deleting plasmoids in panel
https://bugs.kde.org/show_bug.cgi?id=439270 Jiri Slaby changed: What|Removed |Added CC||jirisl...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438789] kwin_wayland crashed in KWin::DrmGpu::updateOutputs while un/re-plugging monitor
https://bugs.kde.org/show_bug.cgi?id=438789
--- Comment #10 from Jiri Slaby ---
(In reply to Jiri Slaby from comment #9)
> BTW I also applied the patch from bug 439208#c3, but kwin still crashes with
> the very same backtrace.
Just checked with the core file:
> (gdb) l DrmConnector::DrmConnector
> 25 if (m_conn) {
> 26 for (int i = 0; i < m_conn->count_encoders; ++i) {
> 27 m_encoders << m_conn->encoders[i];
> 28 }
> 29 } else {
> 30 qCWarning(KWIN_DRM) << "drmModeGetConnector failed!" <<
> strerror(errno);
> 31 }
> 32 }
> 33
> 34 DrmConnector::~DrmConnector() = default;
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 438789] kwin_wayland crashed in KWin::DrmGpu::updateOutputs while un/re-plugging monitor
https://bugs.kde.org/show_bug.cgi?id=438789 --- Comment #9 from Jiri Slaby --- (In reply to Zamundaaa from comment #8) > It seems like the logging rules aren't applied, did you add them? Ah, I am stupid. I am not using sddm for a couple of weeks as it doesn't start any session, so the log was old. I am using this from console: /usr/lib64/libexec/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland I assume the output is logged nowhere. Let me redirect the output to a file. > You can check if it worked with > echo $QT_LOGGING_RULES That's correctly set: $ echo $QT_LOGGING_RULES kwin_*.debug=true;kwin_libinput.debug=false BTW I also applied the patch from bug 439208#c3, but kwin still crashes with the very same backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438789] kwin_wayland crashed in KWin::DrmGpu::updateOutputs while un/re-plugging monitor
https://bugs.kde.org/show_bug.cgi?id=438789 Jiri Slaby changed: What|Removed |Added Attachment #139531|0 |1 is obsolete|| --- Comment #7 from Jiri Slaby --- Created attachment 139913 --> https://bugs.kde.org/attachment.cgi?id=139913=edit ~/.local/share/sddm/wayland-session.log (In reply to Zamundaaa from comment #3) > Could you also add > QT_LOGGING_RULES="kwin_*.debug=true;kwin_libinput.debug=false" > to /etc/environment, reboot and provide the same file again in the following > situations: ... > 3. with the crash I believe this is "3." log. Happened during unplug: > kwin_wayland_drm: failed to open drm device at "" And a lot of: > kwin_wayland_drm: drmModeAddFB2 and drmModeAddFB both failed! Nepřípustný > argument $ errno -l|grep 'Nepřípustný argument' EINVAL 22 Nepřípustný argument But those second messages are there even long before the crash. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439325] crash while moving weston window
https://bugs.kde.org/show_bug.cgi?id=439325 Jiri Slaby changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from Jiri Slaby --- (In reply to David Edmundson from comment #1) > So this was plasma in kwin, with a weston inside, and then plasma in the > outside kwin crashed? Exactly. I don't even know if running weston was necessary to trigged this. I was unable to reproduce so far. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439325] crash while moving weston window
https://bugs.kde.org/show_bug.cgi?id=439325 Jiri Slaby changed: What|Removed |Added Platform|Other |openSUSE RPMs -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439325] New: crash while moving weston window
https://bugs.kde.org/show_bug.cgi?id=439325 Bug ID: 439325 Summary: crash while moving weston window Product: plasmashell Version: 5.22.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: jirisl...@gmail.com Target Milestone: 1.0 Application: plasmashell (5.22.2) Qt Version: 5.15.2 Frameworks Version: 5.83.0 Operating System: Linux 5.13.0-1.g6ed423b-default x86_64 Windowing System: Wayland Drkonqi Version: 5.22.2 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Opened a weston nested compositor and moved with its window. Nothing else unusual. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [KCrash Handler] #4 0x7fa8c47ca91d in update_buffers (dri2_surf=dri2_surf@entry=0x7fa850004800) at ../src/egl/drivers/dri2/platform_wayland.c:670 #5 0x7fa8c47cb004 in image_get_buffers (driDrawable=, format=, stamp=, loaderPrivate=0x7fa850004800, buffer_mask=, buffers=0x7fa86153ce50) at ../src/egl/drivers/dri2/platform_wayland.c:805 #6 0x7fa8bfa86747 in brw_update_image_buffers (drawable=0x56273239bbd0, brw=0x56273bf55e40) at ../src/mesa/drivers/dri/i965/brw_context.c:1910 #7 brw_update_renderbuffers.isra.0 (drawable=0x56273239bbd0, context=, context=) at ../src/mesa/drivers/dri/i965/brw_context.c:1537 #8 0x7fa8bf16c9e6 in brw_prepare_render(brw_context*) (brw=0x56273bf55e40) at ../src/mesa/drivers/dri/i965/brw_context.c:1558 #9 0x7fa8bf157cc2 in brw_clear(gl_context*, GLbitfield) (ctx=0x56273bf55e40, mask=50) at ../src/mesa/drivers/dri/i965/brw_clear.c:255 #10 0x7fa8cb709f54 in QSGBatchRenderer::Renderer::renderBatches() (this=this@entry=0x7fa850006740) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.1.x86_64/src/quick/scenegraph/coreapi/qsgbatchrenderer.cpp:4042 #11 0x7fa8cb70a972 in QSGBatchRenderer::Renderer::render() (this=) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.1.x86_64/src/quick/scenegraph/coreapi/qsgbatchrenderer.cpp:4363 #12 0x7fa8cb6f1f60 in QSGRenderer::renderScene(QSGBindable const&) (bindable=, this=0x7fa850006740) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.1.x86_64/src/quick/scenegraph/coreapi/qsgrenderer.cpp:264 #13 QSGRenderer::renderScene(QSGBindable const&) (this=0x7fa850006740, bindable=) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.1.x86_64/src/quick/scenegraph/coreapi/qsgrenderer.cpp:220 #14 0x7fa8cb6f2433 in QSGRenderer::renderScene(unsigned int) (this=, fboId=) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.1.x86_64/src/quick/scenegraph/coreapi/qsgrenderer.cpp:212 #15 0x7fa8cb756e83 in QSGDefaultRenderContext::renderNextFrame(QSGRenderer*, unsigned int) (this=0x56271f1f8060, renderer=0x7fa850006740, fboId=) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.1.x86_64/src/quick/scenegraph/qsgdefaultrendercontext.cpp:228 #16 0x7fa8cb7c4c89 in QQuickWindowPrivate::renderSceneGraph(QSize const&, QSize const&) (this=0x56271f55e610, size=..., surfaceSize=...) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.1.x86_64/src/quick/items/qquickwindow.cpp:617 #17 0x7fa8cb76554d in QSGRenderThread::syncAndRender(QImage*) (this=0x5627256a77e0, grabImage=0x0) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.1.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:837 #18 0x7fa8cb765ef7 in QSGRenderThread::run() (this=0x5627256a77e0) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.1.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:1043 #19 0x7fa8c9ac9dd1 in QThreadPrivate::start(void*) (arg=0x5627256a77e0) at thread/qthread_unix.cpp:329 #20 0x7fa8c8ad8259 in start_thread (arg=0x7fa86153e640) at pthread_create.c:481 #21 0x7fa8c96ea2b3 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 17 (Thread 0x7fa863f50640 (LWP 13312) "plasmashell"): #1 0x7fa8a4da2824 in () at /usr/lib64/spa-0.2/support/libspa-support.so #2 0x7fa8a4d992e4 in () at /usr/lib64/spa-0.2/support/libspa-support.so #3 0x7fa8a4de7270 in () at /lib64/libpipewire-0.3.so.0 #4 0x7fa8c8ad8259 in start_thread (arg=0x7fa863f50640) at pthread_create.c:481 #5 0x7fa8c96ea2b3 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 16 (Thread 0x7fa89b7fe640 (LWP 12501) "QSGRenderThread"): #1 0x7fa8c8ae4a3f in __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x56271efc73c0, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at ../sysdeps/nptl/futex-internal.c:123 #2 0x7fa8c8ade280 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x56271efc7370, cond=0x56271efc7398) at pthread_cond_wait.c:504 #3
[kwin] [Bug 438789] kwin_wayland crashed in KWin::DrmGpu::updateOutputs while un/re-plugging monitor
https://bugs.kde.org/show_bug.cgi?id=438789 --- Comment #4 from Jiri Slaby --- (In reply to Zamundaaa from comment #3) > Hmm, there's a lot of (possibly unrelated) errors in that log before and > after the crash which suggest there's either another bug in KWin or a bug in > the graphics driver. FWIW, it sometimes crashes (with the same stack trace) also when I only unplug the connector. > I assume the thunderbolt dock has its own power supply? Yes. > Does it also work without it? I don't know, the dock powers the laptop (over thunderbolt). > And did you need to install a separate driver like DisplayLink > to get it to work? No, I don't even know about its existence. > Could you also add > QT_LOGGING_RULES="kwin_*.debug=true;kwin_libinput.debug=false" > to /etc/environment, reboot and provide the same file again in the following > situations: > 1. without any crash or unplug (to check for the other error) > 2. when you plug it out, wait for 10 seconds and plug it in again > 3. with the crash > > That should tell us whether or not it's on unplug or hotplug, and how much > time between the two events being processed by KWin passed. I set the env var and will restart the session later, but I answered the question I think. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438789] kwin_wayland crashed in KWin::DrmGpu::updateOutputs while un/re-plugging monitor
https://bugs.kde.org/show_bug.cgi?id=438789 --- Comment #2 from Jiri Slaby --- Created attachment 139531 --> https://bugs.kde.org/attachment.cgi?id=139531=edit ~/.local/share/sddm/wayland-session.log (In reply to Zamundaaa from comment #1) > Can you reproduce it again and then attach the resulting > ~/.local/share/sddm/wayland-session.log file? > > Does this only happen when you do it fast, or is there no crash if you first > unplug, wait for a bit and then replug? We had some electricity outages during the night and this happened again. They were like 1 s, so rather fast. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438789] New: kwin_wayland crashed in KWin::DrmGpu::updateOutputs while un/re-plugging monitor
https://bugs.kde.org/show_bug.cgi?id=438789
Bug ID: 438789
Summary: kwin_wayland crashed in KWin::DrmGpu::updateOutputs
while un/re-plugging monitor
Product: kwin
Version: 5.22.0
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: platform-drm
Assignee: kwin-bugs-n...@kde.org
Reporter: jirisl...@gmail.com
Target Milestone: ---
SUMMARY
When I unplugged and replugged an external monitor the following crash
occurred. I don't know if the unplug or replug caused this as I did it both in
one second or so.
> #0 qDeleteAll(KWin::DrmConnector* const*,
> KWin::DrmConnector* const*) (end=0x558831b810d0, begin=0x558831b810c8) at
> /usr/include/qt5/QtCore/qalgorithms.h:320
> #1 qDeleteAll >(QVector
> const&) (c=, c=...) at
> /usr/include/qt5/QtCore/qalgorithms.h:328
> #2 KWin::DrmGpu::updateOutputs() [clone .isra.0] (this=) at
> /usr/src/debug/kwin5-5.22.0-2.1.x86_64/src/plugins/platforms/drm/drm_gpu.cpp:308
> #3 0x7f3f56df8c2e in KWin::DrmBackend::updateOutputs()
> (this=0x5588308190a0) at
> /usr/src/debug/kwin5-5.22.0-2.1.x86_64/src/plugins/platforms/drm/drm_backend.cpp:328
> #4 KWin::DrmBackend::updateOutputs() (this=this@entry=0x5588308190a0) at
> /usr/src/debug/kwin5-5.22.0-2.1.x86_64/src/plugins/platforms/drm/drm_backend.cpp:320
> #5 0x7f3f56df9a1b in KWin::DrmBackend::handleUdevEvent()
> (this=0x5588308190a0) at
> /usr/src/debug/kwin5-5.22.0-2.1.x86_64/src/plugins/platforms/drm/drm_backend.cpp:230
> #6 0x7f3f5d3f40f3 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
> (a=0x7fff5456c7b0, r=0x5588308190a0, this=0x55883083ca90) at
> ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
> #7 doActivate(QObject*, int, void**) (sender=0x558830839290,
> signal_index=3, argv=0x7fff5456c7b0) at kernel/qobject.cpp:3886
> #8 0x7f3f5d3ed5bf in QMetaObject::activate(QObject*, QMetaObject const*,
> int, void**) (sender=sender@entry=0x558830839290, m=m@entry=0x7f3f5d6a0aa0,
> local_signal_index=local_signal_index@entry=0,
> argv=argv@entry=0x7fff5456c7b0) at kernel/qobject.cpp:3946
> #9 0x7f3f5d3f74bf in QSocketNotifier::activated(QSocketDescriptor,
> QSocketNotifier::Type, QSocketNotifier::QPrivateSignal)
> (this=this@entry=0x558830839290, _t1=..., _t2=, _t3=...) at
> .moc/moc_qsocketnotifier.cpp:178
> #10 0x7f3f5d3f7cbb in QSocketNotifier::event(QEvent*)
> (this=0x558830839290, e=0x7fff5456c8d0) at kernel/qsocketnotifier.cpp:302
> #11 0x7f3f5e2cda5f in QApplicationPrivate::notify_helper(QObject*,
> QEvent*) (this=, receiver=0x558830839290, e=0x7fff5456c8d0) at
> kernel/qapplication.cpp:3632
> #12 0x7f3f5d3bdaaa in QCoreApplication::notifyInternal2(QObject*,
> QEvent*) (receiver=0x558830839290, event=0x7fff5456c8d0) at
> kernel/qcoreapplication.cpp:1063
> #13 0x7f3f5d4124ab in
> QEventDispatcherUNIXPrivate::activateSocketNotifiers() (this=0x5588307c3a10)
> at kernel/qeventdispatcher_unix.cpp:304
> #14 0x7f3f5d41290b in
> QEventDispatcherUNIX::processEvents(QFlags)
> (this=, flags=...) at kernel/qeventdispatcher_unix.cpp:511
> #15 0x55882f39339d in
> QUnixEventDispatcherQPA::processEvents(QFlags)
> (this=, flags=...) at qunixeventdispatcher.cpp:63
> #16 0x7f3f5d3bc4bb in
> QEventLoop::exec(QFlags)
> (this=this@entry=0x7fff5456ca60, flags=..., flags@entry=...) at
> ../../include/QtCore/../../src/corelib/global/qflags.h:69
> #17 0x7f3f5d3c4790 in QCoreApplication::exec() () at
> ../../include/QtCore/../../src/corelib/global/qflags.h:121
> #18 0x55882f33626a in main(int, char**) (argc=,
> argv=) at
> /usr/src/debug/kwin5-5.22.0-2.1.x86_64/src/main_wayland.cpp:727
> (gdb) fram 2
> #2 KWin::DrmGpu::updateOutputs() [clone .isra.0] (this=) at
> /usr/src/debug/kwin5-5.22.0-2.1.x86_64/src/plugins/platforms/drm/drm_gpu.cpp:308
> 308 qDeleteAll(oldConnectors);
> (gdb) l
> 303
> 304 for(DrmOutput *removedOutput : removedOutputs) {
> 305 removeOutput(removedOutput);
> 306 }
> 307
> 308 qDeleteAll(oldConnectors);
> 309 qDeleteAll(oldCrtcs);
> 310 return true;
> 311 }
> 312
STEPS TO REPRODUCE
1. Unplug thunderbolt (behind which a monitor is connected)
2. Replug thunderbolt
3. boom
SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20210614
KDE Plasma Version: 5.22.0
KDE Frameworks Version: 5.82.0
Qt Version: 5.15.2
Kernel Version: 5.12.10-3.g332b26c-default (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i7-6600U CPU @ 2.60GHz
Memory: 15.1 GiB of RAM
Graphics Processor: Mesa DRI Intel® HD Graphics 520
ADDITIONAL INFORMATION
Running in wayland.
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 424272] Shift+click does not bring xterm to foreground
https://bugs.kde.org/show_bug.cgi?id=424272 Jiri Slaby changed: What|Removed |Added Status|RESOLVED|VERIFIED --- Comment #6 from Jiri Slaby --- Works for me. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 424271] Report with multiple versions is detected as spam
https://bugs.kde.org/show_bug.cgi?id=424271 Jiri Slaby changed: What|Removed |Added Summary|My report is detected as|Report with multiple |spam|versions is detected as ||spam -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 424271] My report is detected as spam
https://bugs.kde.org/show_bug.cgi?id=424271 --- Comment #6 from Jiri Slaby --- The original contained: 2020-05-12 07:46:52|install|kwin5|5X18X5-1X1 2020-06-15 09:53:22|install|kwin5|5X19X0-1X1 2020-07-13 07:56:32|install|kwin5|5X19X2-1X1 2020-07-14 09:30:02|install|kwin5|5X19X3-1X1 (If you think of X as .) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 424272] Shift+click does not bring xterm to foreground
https://bugs.kde.org/show_bug.cgi?id=424272 --- Comment #2 from Jiri Slaby --- (In reply to Jiri Slaby from comment #1) > My update history: Maybe this will work (replace X by .)? 2020-05-12 07:46:52|install|kwin5|5X18X5-1X1 2020-06-15 09:53:22|install|kwin5|5X19X0-1X1 2020-07-13 07:56:32|install|kwin5|5X19X2-1X1 2020-07-14 09:30:02|install|kwin5|5X19X3-1X1 -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 424271] My report is detected as spam
https://bugs.kde.org/show_bug.cgi?id=424271 --- Comment #5 from Jiri Slaby --- (In reply to Jiri Slaby from comment #4) > (In reply to Jiri Slaby from comment #3) > > 5X18X5 > > 5X19X0 > > 5X19X2 > > 5X19X3 > > OK, so 5.18.5? Separate versions work, but if you put several version on lines, it is considered as spam. I.e. replace those X with . and it is suddenly a spam. -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 424271] My report is detected as spam
https://bugs.kde.org/show_bug.cgi?id=424271 --- Comment #4 from Jiri Slaby --- (In reply to Jiri Slaby from comment #3) > 5X18X5 > 5X19X0 > 5X19X2 > 5X19X3 OK, so 5.18.5? -- You are receiving this mail because: You are watching all bug changes.
