[kwin] [Bug 460594] Plasma freeze happening since 5.26.0 update
https://bugs.kde.org/show_bug.cgi?id=460594 Oded Arbel changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #42 from Oded Arbel --- No, does not appear to be related. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460594] Plasma freeze happening since 5.26.0 update
https://bugs.kde.org/show_bug.cgi?id=460594 zyf0330 changed: What|Removed |Added Resolution|WORKSFORME |--- Status|RESOLVED|REPORTED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460594] Plasma freeze happening since 5.26.0 update
https://bugs.kde.org/show_bug.cgi?id=460594 zyf0330 changed: What|Removed |Added CC||zyf034...@gmail.com --- Comment #41 from zyf0330 --- https://bugs.kde.org/show_bug.cgi?id=466285 Is this a similar issue? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460594] Plasma freeze happening since 5.26.0 update
https://bugs.kde.org/show_bug.cgi?id=460594 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #40 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460594] Plasma freeze happening since 5.26.0 update
https://bugs.kde.org/show_bug.cgi?id=460594 g changed: What|Removed |Added CC||g.airia...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460594] Plasma freeze happening since 5.26.0 update
https://bugs.kde.org/show_bug.cgi?id=460594 --- Comment #39 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460594] Plasma freeze happening since 5.26.0 update
https://bugs.kde.org/show_bug.cgi?id=460594 Vlad Zahorodnii changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #38 from Vlad Zahorodnii --- This sounds like https://bugs.kde.org/show_bug.cgi?id=461316. If you can reproduce this bug, can you specify mesa version? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460594] Plasma freeze happening since 5.26.0 update
https://bugs.kde.org/show_bug.cgi?id=460594 --- Comment #37 from JC --- I updated my system to kde-frameworks v5.101.0 and kde-plasma (including kwin) v5.26.4. After 4 days, my system seems to be operating normally again. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460594] Plasma freeze happening since 5.26.0 update
https://bugs.kde.org/show_bug.cgi?id=460594 Dāvis changed: What|Removed |Added CC||davis...@gmail.com --- Comment #36 from Dāvis --- I have been experiencing exactly this same deadlock. I'm using Arch Linux with AMD Radeon Vega Mobile 8 GPU. It happens kinda rarely but still annoying. And it's definitely related with notifications (it freezes right after displaying some) but I don't remember which one in particular it was, maybe Discord. Also I might be remembering wrong but maybe when notification shows up and you mouseover somewhere it. For `plasmashell` ``` 0x7ffb1cb454b6 in ?? () from /usr/lib/libc.so.6 Thread 50 (Thread 0x7ff9b47f86c0 (LWP 829722) "QSGRenderThread"): #0 0x7ffb1cbbd0bf in poll () at /usr/lib/libc.so.6 #1 0x7ffb1f34d20b in () at /usr/lib/libxcb.so.1 #2 0x7ffb1f34f01b in xcb_wait_for_special_event () at /usr/lib/libxcb.so.1 #3 0x7ffb160e2de8 in glPrimitiveBoundingBox () at /usr/lib/libGLX_mesa.so.0 #4 0x7ffb160e3c54 in glPrimitiveBoundingBox () at /usr/lib/libGLX_mesa.so.0 #5 0x7ffb160e5801 in glPrimitiveBoundingBox () at /usr/lib/libGLX_mesa.so.0 #6 0x7ffb160e5b3b in glPrimitiveBoundingBox () at /usr/lib/libGLX_mesa.so.0 #7 0x7ffb146f5368 in () at /usr/lib/dri/radeonsi_dri.so #8 0x7ffb146f54b3 in () at /usr/lib/dri/radeonsi_dri.so #9 0x7ffb146f8575 in () at /usr/lib/dri/radeonsi_dri.so #10 0x7ffb147d019a in () at /usr/lib/dri/radeonsi_dri.so #11 0x7ffb147d0846 in () at /usr/lib/dri/radeonsi_dri.so #12 0x7ffb147aa166 in () at /usr/lib/dri/radeonsi_dri.so #13 0x7ffb14983efa in () at /usr/lib/dri/radeonsi_dri.so #14 0x7ffb1eb67b49 in QSGBatchRenderer::Renderer::renderBatches() () at /usr/lib/libQt5Quick.so.5 #15 0x7ffb1eb6c5d1 in QSGBatchRenderer::Renderer::render() () at /usr/lib/libQt5Quick.so.5 #16 0x7ffb1eb54085 in QSGRenderer::renderScene(QSGBindable const&) () at /usr/lib/libQt5Quick.so.5 #17 0x7ffb1eb54524 in QSGRenderer::renderScene(unsigned int) () at /usr/lib/libQt5Quick.so.5 #18 0x7ffb1ebad935 in QSGDefaultRenderContext::renderNextFrame(QSGRenderer*, unsigned int) () at /usr/lib/libQt5Quick.so.5 #19 0x7ffb1ec07e51 in QQuickWindowPrivate::renderSceneGraph(QSize const&, QSize const&) () at /usr/lib/libQt5Quick.so.5 #20 0x7ffb1ebb7f06 in () at /usr/lib/libQt5Quick.so.5 #21 0x7ffb1ebbce14 in () at /usr/lib/libQt5Quick.so.5 #22 0x7ffb1cfc42ba in () at /usr/lib/libQt5Core.so.5 #23 0x7ffb1cb488fd in () at /usr/lib/libc.so.6 #24 0x7ffb1cbcaa60 in () at /usr/lib/libc.so.6 Thread 49 (Thread 0x7ff9b4ff96c0 (LWP 829721) "plasmash:gdrv0"): #0 0x7ffb1cb454b6 in () at /usr/lib/libc.so.6 #1 0x7ffb1cb47cd0 in pthread_cond_wait () at /usr/lib/libc.so.6 #2 0x7ffb1475099e in () at /usr/lib/dri/radeonsi_dri.so #3 0x7ffb14703f8c in () at /usr/lib/dri/radeonsi_dri.so #4 0x7ffb147508cc in () at /usr/lib/dri/radeonsi_dri.so #5 0x7ffb1cb488fd in () at /usr/lib/libc.so.6 #6 0x7ffb1cbcaa60 in () at /usr/lib/libc.so.6 Thread 48 (Thread 0x7ff9b67fc6c0 (LWP 354694) "QSGRenderThread"): #0 0x7ffb1cb454b6 in () at /usr/lib/libc.so.6 #1 0x7ffb1cb47cd0 in pthread_cond_wait () at /usr/lib/libc.so.6 #2 0x7ffb1cfcb744 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #3 0x7ffb1ebbd203 in () at /usr/lib/libQt5Quick.so.5 #4 0x7ffb1cfc42ba in () at /usr/lib/libQt5Core.so.5 #5 0x7ffb1cb488fd in () at /usr/lib/libc.so.6 #6 0x7ffb1cbcaa60 in () at /usr/lib/libc.so.6 Thread 47 (Thread 0x7ff9b6ffd6c0 (LWP 354693) "plasmash:gdrv0"): #0 0x7ffb1cb454b6 in () at /usr/lib/libc.so.6 #1 0x7ffb1cb47cd0 in pthread_cond_wait () at /usr/lib/libc.so.6 #2 0x7ffb1475099e in () at /usr/lib/dri/radeonsi_dri.so #3 0x7ffb14703f8c in () at /usr/lib/dri/radeonsi_dri.so #4 0x7ffb147508cc in () at /usr/lib/dri/radeonsi_dri.so #5 0x7ffb1cb488fd in () at /usr/lib/libc.so.6 #6 0x7ffb1cbcaa60 in () at /usr/lib/libc.so.6 Thread 46 (Thread 0x7ffa1928c6c0 (LWP 248842) "threaded-ml"): #0 0x7ffb1cbbd0bf in poll () at /usr/lib/libc.so.6 #1 0x7ffac567b8c7 in () at /usr/lib/libpulse.so.0 #2 0x7ffac566546c in pa_mainloop_poll () at /usr/lib/libpulse.so.0 #3 0x7ffac566f42c in pa_mainloop_iterate () at /usr/lib/libpulse.so.0 #4 0x7ffac566f4e1 in pa_mainloop_run () at /usr/lib/libpulse.so.0 #5 0x7ffac567fc02 in () at /usr/lib/libpulse.so.0 #6 0x7ffac561bc47 in () at /usr/lib/pulseaudio/libpulsecommon-16.1.so #7 0x7ffb1cb488fd in () at /usr/lib/libc.so.6 #8 0x7ffb1cbcaa60 in () at /usr/lib/libc.so.6 Thread 45 (Thread 0x7ffa11ffb6c0 (LWP 224262) "plasmashel:sh1"): #0 0x7ffb1cb454b6 in () at /usr/lib/libc.so.6 #1 0x7ffb1cb47cd0 in pthread_cond_wait () at
[kwin] [Bug 460594] Plasma freeze happening since 5.26.0 update
https://bugs.kde.org/show_bug.cgi?id=460594 Søren Holm changed: What|Removed |Added CC||s...@sgh.dk -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460594] Plasma freeze happening since 5.26.0 update
https://bugs.kde.org/show_bug.cgi?id=460594 Kevin Funk changed: What|Removed |Added CC||kf...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460594] Plasma freeze happening since 5.26.0 update
https://bugs.kde.org/show_bug.cgi?id=460594 Charles Dennett changed: What|Removed |Added CC||cdenn...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460594] Plasma freeze happening since 5.26.0 update
https://bugs.kde.org/show_bug.cgi?id=460594 Rafael Nascimento changed: What|Removed |Added CC||rafaeln@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460594] Plasma freeze happening since 5.26.0 update
https://bugs.kde.org/show_bug.cgi?id=460594 Tobias C. Berner changed: What|Removed |Added CC||tcber...@freebsd.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460594] Plasma freeze happening since 5.26.0 update
https://bugs.kde.org/show_bug.cgi?id=460594 Sergio changed: What|Removed |Added CC||sergio.calleg...@gmail.com --- Comment #35 from Sergio --- Experiencing the same issue on Manjaro (see https://forum.manjaro.org/t/plasmashell-freezes/127677/2). Good news is that it is easy to check whether the issue is a freeze in plasmashell or another issue. Furthermore if the problem is a freeze in plasmashell it can be worked around without any data loss. 1. switch to a virtual console (e.g. CTRL+ALT+F2), login there, kill plasmashell (e.g. killall plasmashell); 2. go back to the graphics console (e.g. CTRL+ALT+F1), if the panel is now gone, then the problem was plasmashell *freezing*. 3. now it should be possible to get the runner (ALT+F2), restart plasmashell from there (e.g. plasmashell --replace). The above procedure lets all your applications survive. I am seeing the issue with X11 (on an Intel Haswell laptop with integrated Intel graphics), so this is definitely not a Wayland-related or Wayland specific problem. If I understand correctly, plasmashell uses a *cooperative* multitasking model for its widgets, so it is enough to have one widget freezing to get a complete plasmashell freeze, which makes freezes like this somehow easy to see, particularly if a non-official widget is used. The model has the advantage of being very lightweight, but clearly has some disadvantage. Is there any possibility to complement it with a watchdog, so that when the shell freezes after some time it is automatically restarted and one can get an indication of the last widget the execution thread was in at the freeze time? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460594] Plasma freeze happening since 5.26.0 update
https://bugs.kde.org/show_bug.cgi?id=460594 t3hd...@gmail.com changed: What|Removed |Added CC||t3hd...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460594] Plasma freeze happening since 5.26.0 update
https://bugs.kde.org/show_bug.cgi?id=460594 --- Comment #34 from JC --- (In reply to jcfisher from comment #33) > Could this possibly be related or the same issue as > https://bugs.kde.org/show_bug.cgi?id=457847? The symptoms seem similar if > not identical. Not sure, they mention having black rectangles. In my case I can see the content of all the windows, in fact I see all windows from all desktops, but no black rectangles. I've been trying to isolate the cause but so far no luck. Sometimes it happens when I get a notification, other times it happens when I switch windows with alt+tab and once it happened just by using the open file dialog (which shows a pop-up with the possible file names). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460594] Plasma freeze happening since 5.26.0 update
https://bugs.kde.org/show_bug.cgi?id=460594 --- Comment #33 from jcfis...@reality-overwritten.net --- Could this possibly be related or the same issue as https://bugs.kde.org/show_bug.cgi?id=457847? The symptoms seem similar if not identical. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460594] Plasma freeze happening since 5.26.0 update
https://bugs.kde.org/show_bug.cgi?id=460594 Jure Repinc changed: What|Removed |Added CC||j...@holodeck1.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460594] Plasma freeze happening since 5.26.0 update
https://bugs.kde.org/show_bug.cgi?id=460594 --- Comment #32 from JC --- (In reply to JC from comment #31) > My experience is similar to what Ricardo reported but my setup is slightly > different. This started happening around the upgrade to KWin 2.26.0: I meant KDE Plasma 5.26.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460594] Plasma freeze happening since 5.26.0 update
https://bugs.kde.org/show_bug.cgi?id=460594 --- Comment #31 from JC --- (In reply to Ricardo J. Barberis from comment #28) My experience is similar to what Ricardo reported but my setup is slightly different. This started happening around the upgrade to KWin 2.26.0: Operating System: Gentoo Linux 2.9 KDE Plasma Version: 5.26.3 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.5 Kernel Version: 5.19.8-gentoo (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-8086K CPU @ 4.00GHz Memory: 31.2 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460594] Plasma freeze happening since 5.26.0 update
https://bugs.kde.org/show_bug.cgi?id=460594 JC changed: What|Removed |Added CC||mg05182-...@yahoo.ca -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460594] Plasma freeze happening since 5.26.0 update
https://bugs.kde.org/show_bug.cgi?id=460594 --- Comment #30 from Ricardo J. Barberis --- (In reply to Nicolas Fella from comment #29) > From the responses so far I don't see any concrete explanation why Plasma > would cause this. This and similar problems reported by other people make me > suspect there might be something wrong with X11/Graphics drivers, but I > can't really prove it Indeed, I initially thought this was a kwin_x11 problem. Only after seeing these reports of Plasma freezing I noticed those. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460594] Plasma freeze happening since 5.26.0 update
https://bugs.kde.org/show_bug.cgi?id=460594 --- Comment #29 from Nicolas Fella --- >From the responses so far I don't see any concrete explanation why Plasma would cause this. This and similar problems reported by other people make me suspect there might be something wrong with X11/Graphics drivers, but I can't really prove it -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460594] Plasma freeze happening since 5.26.0 update
https://bugs.kde.org/show_bug.cgi?id=460594 --- Comment #28 from Ricardo J. Barberis --- (In reply to Bernhard Übelacker from comment #25) > So one data point might be the graphics driver, are all experiencing this > hang using an AMD graphics card? Nope, I'm on an Intel system, *but* I mostly experience kwin_x11 crashes (it actuallt dies without Dr. Konqui showing up and I have to start it via konsole/yakuake/krunner, whichever I can access at that moment) and only a few plasmashell freezes in between. I did notice that when kwin dies repeatedly, if I restart plasmashell it won't die again, at least for the rest of the day. Also, the crashes/freezes seem pretty random: sometimes while receiveing a notification or several, sometimes when I Shift+Del an emal in kmail (confirmation popup) and some other times kwin just dies without an obviuos (to me) trigger. Operating System: Slackware64 15.0+ (-current) KDE Plasma Version: 5.26.3 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.6 Kernel Version: 5.19.17 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i5-1035G1 CPU @ 1.00GHz Memory: 15.2 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics Manufacturer: LENOVO Product Name: 81YK System Version: IdeaPad 5 15IIL05 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460594] Plasma freeze happening since 5.26.0 update
https://bugs.kde.org/show_bug.cgi?id=460594 --- Comment #27 from quirinbrun...@t-online.de --- (In reply to Bernhard Übelacker from comment #25) > (In reply to Bernhard Übelacker from comment #24) > So one data point might be the graphics driver, are all experiencing this > hang using an AMD graphics card? I have a Ryzen 4800H as well. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460594] Plasma freeze happening since 5.26.0 update
https://bugs.kde.org/show_bug.cgi?id=460594 --- Comment #26 from hockeymikey --- > (In reply to Bernhard Übelacker from comment #25) Kinda, I'm using an 2021 Omen 15 with an AMD 4800H and a Nvidia 2060m. So I think the Radeon graphics is used for the built in display, but my external ones are ran through the Nvidia gpu. Hope that helped, I appreciate all your help. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460594] Plasma freeze happening since 5.26.0 update
https://bugs.kde.org/show_bug.cgi?id=460594 --- Comment #25 from Bernhard Übelacker --- (In reply to Bernhard Übelacker from comment #24) > Thread 1 in each process seem to be middle in some processing, plasmashell > waiting for some mutex, kwin_x11 for some xcb request. Tried to look a little further in plasmashell process. It looks like thread 1 is inside some QSGThreadedRenderLoop and is waiting to be woken by some other thread: Thread 1 (Thread 0x7fd89f10aa00 (LWP 1857)): ... #4 ___pthread_cond_wait (cond=0x7fd87006c068, mutex=0x7fd87006c040) at ./nptl/pthread_cond_wait.c:618 #5 0x7fd8a3cd199b in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x7fd87006c040) at thread/qwaitcondition_unix.cpp:146 #6 QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x7fd87008b428, deadline=...) at thread/qwaitcondition_unix.cpp:225 #7 0x7fd8a5a0b968 in QSGThreadedRenderLoop::polishAndSync(QSGThreadedRenderLoop::Window*, bool) (this=this@entry=0x7fd898007220, w=w@entry=0x7fd8980319a0, inExpose=inExpose@entry=true) at scenegraph/qsgthreadedrenderloop.cpp:1603 #8 0x7fd8a5a0cc23 in QSGThreadedRenderLoop::handleExposure(QQuickWindow*) (this=0x7fd898007220, window=) at scenegraph/qsgthreadedrenderloop.cpp:1374 ... https://sources.debian.org/src/qtdeclarative-opensource-src/5.15.6%2Bdfsg-2/src/quick/scenegraph/qsgthreadedrenderloop.cpp/#L1603 1603 w->thread->waitCondition.wait(>thread->mutex); https://sources.debian.org/src/qtdeclarative-opensource-src/5.15.6%2Bdfsg-2/src/quick/scenegraph/qsgthreadedrenderloop.cpp/#L1374 1374 polishAndSync(w, true); There are a few other threads executing below `QSGRenderThread::run()` and also waiting ... : ... #6 QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=this@entry=0x7fd870082768, mutex=mutex@entry=0x7fd870082760, deadline=...) at thread/qwaitcondition_unix.cpp:225 #7 0x7fd8a5a07c95 in QSGRenderThreadEventQueue::takeEvent(bool) (wait=true, this=0x7fd870082758) at scenegraph/qsgthreadedrenderloop.cpp:257 #8 QSGRenderThread::processEventsAndWaitForMore() (this=this@entry=0x7fd8700826c0) at scenegraph/qsgthreadedrenderloop.cpp:935 #9 0x7fd8a5a0a0c1 in QSGRenderThread::run() (this=0x7fd8700826c0) at scenegraph/qsgthreadedrenderloop.cpp:1052 ... But there is one thread that seems waiting in plasmashell process also for some xcb reply: (gdb) bt #0 0x7fd8a3b1afef in __GI___poll (fds=fds@entry=0x7fd72e7fa7a8, nfds=nfds@entry=1, timeout=timeout@entry=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fd8a61a4d12 in poll (__timeout=-1, __nfds=1, __fds=0x7fd72e7fa7a8) at /usr/include/x86_64-linux-gnu/bits/poll2.h:47 #2 _xcb_conn_wait (c=c@entry=0x56038ce45910, cond=cond@entry=0x7fd7180e71c8, vector=vector@entry=0x0, count=count@entry=0x0) at ../../src/xcb_conn.c:508 #3 0x7fd8a61a716a in xcb_wait_for_special_event (c=0x56038ce45910, se=0x7fd7180e71a0) at ../../src/xcb_in.c:806 #4 0x7fd89ddf1465 in dri3_wait_for_event_locked (draw=draw@entry=0x7fd7180f5798, full_sequence=full_sequence@entry=0x0) at ../src/loader/loader_dri3_helper.c:584 #5 0x7fd89ddf22a4 in dri3_find_back (draw=draw@entry=0x7fd7180f5798, prefer_a_different=) at ../src/loader/loader_dri3_helper.c:726 #6 0x7fd89ddf3da1 in dri3_get_buffer (format=format@entry=4099, buffer_type=buffer_type@entry=loader_dri3_buffer_back, draw=draw@entry=0x7fd7180f5798, driDrawable=) at ../src/loader/loader_dri3_helper.c:2030 #7 0x7fd89ddf40d3 in loader_dri3_get_buffers (driDrawable=, format=4099, stamp=0x7fd718088720, loaderPrivate=0x7fd7180f5798, buffer_mask=, buffers=0x7fd72e7fab00) at ../src/loader/loader_dri3_helper.c:2255 #8 0x7fd8966ae13f in dri_image_drawable_get_buffers (drawable=drawable@entry=0x7fd718088720, images=images@entry=0x7fd72e7fab00, statts=statts@entry=0x7fd71816ce78, statts_count=statts_count@entry=2) at ../src/gallium/frontends/dri/dri2.c:289 #9 0x7fd8966ae27f in dri2_allocate_textures (ctx=0x56038d312f10, drawable=0x7fd718088720, statts=0x7fd71816ce78, statts_count=2) at ../src/gallium/frontends/dri/dri2.c:458 #10 0x7fd8966b1265 in dri_st_framebuffer_validate (stctx=, stfbi=, statts=0x7fd71816ce78, count=2, out=0x7fd72e7face0) at ../src/gallium/frontends/dri/dri_drawable.c:82 #11 0x7fd896784d62 in st_framebuffer_validate (stfb=stfb@entry=0x7fd71816ca20, st=st@entry=0x56039097e4f0) at ../src/mesa/state_tracker/st_manager.c:238 #12 0x7fd896785405 in st_manager_validate_framebuffers (st=0x56039097e4f0) at ../src/mesa/state_tracker/st_manager.c:1333 #13 0x7fd89675f6ed in st_validate_state (st=st@entry=0x56039097e4f0, pipeline=pipeline@entry=ST_PIPELINE_CLEAR) at ../src/mesa/state_tracker/st_atom.c:231 #14 0x7fd896933314 in st_Clear (ctx=0x5603916d9e70, mask=50) at ../src/mesa/state_tracker/st_cb_clear.c:432 #15 0x7fd8a59af885 in QSGBatchRenderer::Renderer::renderBatches() (this=this@entry=0x7fd7180c23a0) at scenegraph/coreapi/qsgbatchrenderer.cpp:4022 #16 0x7fd8a59b0326 in
[kwin] [Bug 460594] Plasma freeze happening since 5.26.0 update
https://bugs.kde.org/show_bug.cgi?id=460594 Bernhard Übelacker changed: What|Removed |Added CC||bernha...@mailbox.org --- Comment #24 from Bernhard Übelacker --- Created attachment 153835 --> https://bugs.kde.org/attachment.cgi?id=153835=edit plasmashell_and_kwin_x11_thread-apply-bt.txt I notice also such a hang. I left today at 12:05 the system. When I came back at 13:45 the time was stuck at 12:15, and three notifications from kdeconnect where still visible. To me it looks like this hang is likely to happen if kdeconnect is producing multiple notifications fast in a row. I assume this is the case when I changed WLAN accesspoints in this time and my phone is connecting to the new acesspoint. I gathered core dumps of kwin_x11 and plasmashell. Attached is a `thread apply all bt`, but there are many threads in each and am not sure which one is supposed to do something. Most of them are waiting for something, but I cannot say for what. If wanted, I can add more debug symbols. Thread 1 in each process seem to be middle in some processing, plasmashell waiting for some mutex, kwin_x11 for some xcb request. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460594] Plasma freeze happening since 5.26.0 update
https://bugs.kde.org/show_bug.cgi?id=460594 --- Comment #23 from Dmitry Nezhevenko --- Created attachment 153743 --> https://bugs.kde.org/attachment.cgi?id=153743=edit call stack I also see this on 5.26.3 (debian unstable). It's laptop with Intel GPU (i7-10610U). It also happens mostly when notification is displayed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460594] Plasma freeze happening since 5.26.0 update
https://bugs.kde.org/show_bug.cgi?id=460594 Dmitry Nezhevenko changed: What|Removed |Added CC||d...@inhex.net -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460594] Plasma freeze happening since 5.26.0 update
https://bugs.kde.org/show_bug.cgi?id=460594 Oded Arbel changed: What|Removed |Added CC||o...@geek.co.il -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460594] Plasma freeze happening since 5.26.0 update
https://bugs.kde.org/show_bug.cgi?id=460594 tata...@gmail.com changed: What|Removed |Added CC||tata...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460594] Plasma freeze happening since 5.26.0 update
https://bugs.kde.org/show_bug.cgi?id=460594 quirinbrun...@t-online.de changed: What|Removed |Added CC||quirinbrun...@t-online.de -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460594] Plasma freeze happening since 5.26.0 update
https://bugs.kde.org/show_bug.cgi?id=460594 jcfis...@reality-overwritten.net changed: What|Removed |Added CC||jcfisher@reality-overwritte ||n.net -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460594] Plasma freeze happening since 5.26.0 update
https://bugs.kde.org/show_bug.cgi?id=460594
--- Comment #22 from Bailey ---
here is all plasmashell log
11/6/22 11:11 PMplasmashell
file:///usr/share/plasma/plasmoids/org.kde.plasma.mediacontroller/contents/ui/ExpandedRepresentation.qml:649:
TypeError: Value is undefined and could not be converted to an object
11/6/22 11:11 PMplasmashell
file:///usr/share/plasma/plasmoids/org.kde.plasma.mediacontroller/contents/ui/CompactRepresentation.qml:77:
TypeError: Cannot read property 'implicitWidth' of null
11/6/22 11:11 PMplasmashell
file:///usr/share/plasma/plasmoids/org.kde.plasma.mediacontroller/contents/ui/main.qml:56:
TypeError: Value is undefined and could not be converted to an object
11/6/22 11:11 PMplasmashell
file:///usr/share/plasma/plasmoids/org.kde.plasma.mediacontroller/contents/ui/main.qml:62:
TypeError: Value is undefined and could not be converted to an object
11/6/22 11:11 PMplasmashell
file:///usr/share/plasma/plasmoids/org.kde.plasma.mediacontroller/contents/ui/main.qml:70:
TypeError: Value is undefined and could not be converted to an object
11/6/22 11:11 PMplasmashell
file:///usr/share/plasma/plasmoids/org.kde.plasma.mediacontroller/contents/ui/main.qml:72:
TypeError: Value is undefined and could not be converted to an object
11/6/22 11:11 PMplasmashell
file:///usr/share/plasma/plasmoids/org.kde.plasma.mediacontroller/contents/ui/main.qml:283:
TypeError: Value is undefined and could not be converted to an object
11/6/22 11:11 PMplasmashell
file:///usr/share/plasma/plasmoids/org.kde.plasma.mediacontroller/contents/ui/main.qml:272:
TypeError: Value is undefined and could not be converted to an object
11/6/22 11:11 PMplasmashell
file:///usr/share/plasma/plasmoids/org.kde.plasma.mediacontroller/contents/ui/ExpandedRepresentation.qml:649:
TypeError: Value is undefined and could not be converted to an object
11/6/22 11:12 PMplasmashell Could not find the Plasmoid for
Plasma::FrameSvgItem(0x56045af9e440) QQmlContext(0x56045b977a60)
QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml")
11/6/22 11:12 PMplasmashell Could not find the Plasmoid for
Plasma::FrameSvgItem(0x56045af9e440) QQmlContext(0x56045b977a60)
QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml")
11/6/22 11:12 PMplasmashell
file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationItem.qml:221:21:
QML SelectableLabel: Binding loop detected for property "implicitWidth"
11/6/22 11:12 PMplasmashell
file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationItem.qml:221:21:
QML SelectableLabel: Binding loop detected for property "implicitWidth"
11/6/22 11:12 PMplasmashell
file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationItem.qml:221:21:
QML SelectableLabel: Binding loop detected for property "implicitHeight"
11/6/22 11:12 PMplasmashell
file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationItem.qml:221:21:
QML SelectableLabel: Binding loop detected for property "implicitWidth"
11/6/22 11:13 PMplasmashell Could not find the Plasmoid for
Plasma::FrameSvgItem(0x5604630ae5e0) QQmlContext(0x56045b977a60)
QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml")
11/6/22 11:13 PMplasmashell Could not find the Plasmoid for
Plasma::FrameSvgItem(0x5604630ae5e0) QQmlContext(0x56045b977a60)
QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml")
11/6/22 11:13 PMplasmashell
file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationItem.qml:221:21:
QML SelectableLabel: Binding loop detected for property "implicitWidth"
11/6/22 11:13 PMplasmashell
file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationItem.qml:221:21:
QML SelectableLabel: Binding loop detected for property "implicitWidth"
11/6/22 11:13 PMplasmashell
file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationItem.qml:221:21:
QML SelectableLabel: Binding loop detected for property "implicitHeight"
11/6/22 11:13 PMplasmashell
file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationItem.qml:221:21:
QML SelectableLabel: Binding loop detected for property "implicitWidth"
11/6/22 11:16 PMplasmashell Could not find the Plasmoid for
Plasma::FrameSvgItem(0x5604631dba80) QQmlContext(0x56045b977a60)
QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml")
11/6/22 11:16 PMplasmashell Could not find the Plasmoid for
[kwin] [Bug 460594] Plasma freeze happening since 5.26.0 update
https://bugs.kde.org/show_bug.cgi?id=460594 Bailey changed: What|Removed |Added CC||mundanedefoliat...@gmail.co ||m --- Comment #21 from Bailey --- same bug here archlinux 6.07-arch1-1 kde plasma version: 5.26.2 kde framework version: 5.99.0 qt version: 5.15.7 X11 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460594] Plasma freeze happening since 5.26.0 update
https://bugs.kde.org/show_bug.cgi?id=460594 dmb1372 changed: What|Removed |Added CC||aenigma1...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460594] Plasma freeze happening since 5.26.0 update
https://bugs.kde.org/show_bug.cgi?id=460594 --- Comment #20 from Timothy B --- It looks like my issue has already been reported in bug #457847, and I wasn't aware of that ticket's existence when I started getting those random screen freezes. Apologies in advance for polluting this bug ticket, and any updates regarding my issue will now appear in the linked bug ticket. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460594] Plasma freeze happening since 5.26.0 update
https://bugs.kde.org/show_bug.cgi?id=460594 k...@trummer.xyz changed: What|Removed |Added CC||k...@trummer.xyz -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460594] Plasma freeze happening since 5.26.0 update
https://bugs.kde.org/show_bug.cgi?id=460594 --- Comment #19 from mlchatnoir...@gmail.com --- (In reply to hockeymikey from comment #18) at least it shows it's not limited to one app, so likely a problem coming from KDE and not a specific app dispatching wrongly formatted notifications -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460594] Plasma freeze happening since 5.26.0 update
https://bugs.kde.org/show_bug.cgi?id=460594 --- Comment #18 from hockeymikey --- (In reply to mlchatnoir666 from comment #15) If I would have to guess (they are black so can't be sure), it's kde connect and a notification from my phone, which is snapchat probably. Or it could be teams or thunderbird. I don't think the emojis are causing issue or anything custom, but maybe it is. If it was must be some edge case. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460594] Plasma freeze happening since 5.26.0 update
https://bugs.kde.org/show_bug.cgi?id=460594 --- Comment #17 from Timothy B --- Link to core dump: https://drive.google.com/file/d/1tg25SXZi3O3li7LrI_LD7ZE-asbVsCmk/view?usp=sharing -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460594] Plasma freeze happening since 5.26.0 update
https://bugs.kde.org/show_bug.cgi?id=460594 --- Comment #16 from Timothy B --- Created attachment 153401 --> https://bugs.kde.org/attachment.cgi?id=153401=edit Journal logs and stack trace The random screen freeze just happened yet again right after invoking the Alt-Tab switcher. This time, I changed the switcher style to Compact, and I was able to generate a stack trace and core dump from the TTY with `pkill -ILL kwin_x11`. Quite interestingly the journal logs showed that my KWin restart global shortcut (Ctrl+Alt+Shift+K) is working, but apparently KWin didn't respond to SIGTERM while it froze. However, plasmashell did respond to my other global shortcut (Ctrl+Alt+Shift+Backspace) and restarted in the background, but the wallpaper became black after KWin restarted, so I had to restart it again with the same shortcut. The command for the KWin restart shortcut is currently `nohup sh -c "systemctl --user restart plasma-kwin_x11.service"`, but I will need to change that to make it kill KWin instead of terminating. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460594] Plasma freeze happening since 5.26.0 update
https://bugs.kde.org/show_bug.cgi?id=460594 --- Comment #15 from mlchatnoir...@gmail.com --- UPDATE: it seems like my crashes come from notifications as stated by hockeymikey, and for my case it's probably telegram (no crash since I turned off telegram's notifications). I suspect their custom emojis being the cause of this, but I'll need to investigate further, and I still can't tell whether the bug comes from QT/KDE not handling things or telegram dispatching unprocessable notifications. @hockeymickey since you seem to have the same bug as me, do you think you can guess which app causes them? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460594] Plasma freeze happening since 5.26.0 update
https://bugs.kde.org/show_bug.cgi?id=460594 Nicolas Fella changed: What|Removed |Added Summary|Plasma crash happening |Plasma freeze happening |since 5.26.0 update |since 5.26.0 update -- You are receiving this mail because: You are watching all bug changes.
