[kwin] [Bug 372305] Crash in ContrastEffect::uploadRegion
https://bugs.kde.org/show_bug.cgi?id=372305 --- Comment #5 from Dakota Sullivan --- Created attachment 113741 --> https://bugs.kde.org/attachment.cgi?id=113741=edit New crash information added by DrKonqi kwin_x11 (5.13.2) using Qt 5.11.0 - What I was doing when the application crashed: Switching back from tty1 to tty7 I am running KDE Neon on a Lenovo ThinkPad T470 laptop with NVIDIA GeForce 940MX hybrid graphics, with two external displays connected through a dock. This issue just started happening after upgrading xorg to the HWE version so that I could stop screen tearing. When I was running xorg 1.18 I didn't have any issues regardless of if the NVIDIA GPU was enabled or not. I'm also running the latest nvidia-390 display drivers. -- Backtrace (Reduced): #6 KWin::ContrastEffect::uploadRegion (this=this@entry=0x19c8550, map=@0x7ffdc02346a8: 0x7f2be05c56f0, region=...) at /workspace/build/effects/backgroundcontrast/contrast.cpp:281 #7 0x7f2c02c009a4 in KWin::ContrastEffect::uploadGeometry (this=this@entry=0x19c8550, vbo=vbo@entry=0x191a200, region=...) at /workspace/build/effects/backgroundcontrast/contrast.cpp:299 #8 0x7f2c02c01ea4 in KWin::ContrastEffect::doContrast (this=this@entry=0x19c8550, w=w@entry=0x226a940, shape=..., screen=..., opacity=1, screenProjection=...) at /workspace/build/effects/backgroundcontrast/contrast.cpp:442 #9 0x7f2c02c02929 in KWin::ContrastEffect::drawWindow (this=this@entry=0x19c8550, w=w@entry=0x226a940, mask=mask@entry=2, region=..., data=...) at /workspace/build/effects/backgroundcontrast/contrast.cpp:419 #10 0x7f2c05e9a16e in KWin::EffectsHandlerImpl::drawWindow (this=0x19c2e90, w=w@entry=0x226a940, mask=mask@entry=2, region=..., data=...) at /workspace/build/effects.cpp:456 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 372305] Crash in ContrastEffect::uploadRegion
https://bugs.kde.org/show_bug.cgi?id=372305 Dakota Sullivan changed: What|Removed |Added CC||dakota.sullivan@madwiremedi ||a.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 388684] Plasma crashes if screenshot notification disappears while drag-'n-dropping image
https://bugs.kde.org/show_bug.cgi?id=388684 --- Comment #8 from Dakota Sullivan <dakota.sulli...@madwiremedia.com> --- I did some more testing and it turns out I can only cause this when I have two or more System Tray plasmoids. I am guessing it has something to do with duplicate timers, but I am pretty new to KDE so I don't know how to fix this. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 388684] Plasma crashes if screenshot notification disappears while drag-'n-dropping image
https://bugs.kde.org/show_bug.cgi?id=388684 --- Comment #7 from Dakota Sullivan <dakota.sulli...@madwiremedia.com> --- Using the layout direction for debugging I can confirm that the "onContainsMouseChanged" and "onDraggingChanged" event handlers and "containsMouse" and "dragging" variables are working as far as I can tell. The issue seems to be something inside the notificationTimer where it doesn't stop properly. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 388684] Plasma crashes if screenshot notification disappears while drag-'n-dropping image
https://bugs.kde.org/show_bug.cgi?id=388684 --- Comment #5 from Dakota Sullivan <dakota.sulli...@madwiremedia.com> --- Something else to note is that the notification item disappears even while I have my mouse hovering on top of it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 388684] Plasma crashes if screenshot notification disappears while drag-'n-dropping image
https://bugs.kde.org/show_bug.cgi?id=388684 --- Comment #4 from Dakota Sullivan <dakota.sulli...@madwiremedia.com> --- That did not fix the issue. I was able to modify /usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationPopup.qml and change the layout direction after restarting Plasma, but applying your changes appeared to have no effect. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 388684] Plasma crashes if screenshot notification disappears while drag-'n-dropping image
https://bugs.kde.org/show_bug.cgi?id=388684 --- Comment #2 from Dakota Sullivan <dakota.sulli...@madwiremedia.com> --- I can trigger the crash without another notification showing up, but I am running three screens all which have notification widgets in their panels, and it doesn't matter which screen I drag from. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 388684] New: Plasma crashes if screenshot notification disappears while drag-'n-dropping image
https://bugs.kde.org/show_bug.cgi?id=388684 Bug ID: 388684 Summary: Plasma crashes if screenshot notification disappears while drag-'n-dropping image Product: plasmashell Version: 5.11.4 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: dakota.sulli...@madwiremedia.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.11.4) Qt Version: 5.9.3 Frameworks Version: 5.41.0 Operating System: Linux 4.10.0-42-generic x86_64 Distribution: KDE neon User Edition 5.11 -- Information about the crash: - What I was doing when the application crashed: I had just taken a screenshot and was trying to drag-and-drop the image from the notification into Slack, but apparently I took too long and the notification timed out and disappeared, along with Plasma. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f506d15a8c0 (LWP 2294))] Thread 8 (Thread 0x7f4f9cde8700 (LWP 3015)): #0 0x7f5067144e0c in roundToMillisecond (val=...) at kernel/qtimerinfo_unix.cpp:210 #1 QTimerInfoList::timerWait (this=0x7f4f98002cd0, tm=...) at kernel/qtimerinfo_unix.cpp:405 #2 0x7f506714643e in timerSourcePrepareHelper (timeout=0x7f4f9cde7af4, src=) at kernel/qeventdispatcher_glib.cpp:132 #3 timerSourcePrepare (source=, timeout=0x7f4f9cde7af4) at kernel/qeventdispatcher_glib.cpp:165 #4 0x7f50616e491d in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f50616e52bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f50616e549c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f50671466cb in QEventDispatcherGlib::processEvents (this=0x7f4f980008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #8 0x7f50670eee2a in QEventLoop::exec (this=this@entry=0x7f4f9cde7cc0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #9 0x7f5066f178f4 in QThread::exec (this=) at thread/qthread.cpp:515 #10 0x7f4f9f2c6517 in KCupsConnection::run() () from /usr/lib/x86_64-linux-gnu/libkcupslib.so #11 0x7f5066f1c709 in QThreadPrivate::start (arg=0x56b3e70) at thread/qthread_unix.cpp:368 #12 0x7f5065dc36ba in start_thread (arg=0x7f4f9cde8700) at pthread_create.c:333 #13 0x7f506682b3dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 7 (Thread 0x7f4fb340a700 (LWP 2566)): #0 0x7f506681f70d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f50616e538c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f50616e549c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f50671466cb in QEventDispatcherGlib::processEvents (this=0x7f4fac0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f50670eee2a in QEventLoop::exec (this=this@entry=0x7f4fb3409c90, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f5066f178f4 in QThread::exec (this=this@entry=0x2b02eb0) at thread/qthread.cpp:515 #6 0x7f506ac0e046 in QQuickPixmapReader::run (this=0x2b02eb0) at util/qquickpixmapcache.cpp:868 #7 0x7f5066f1c709 in QThreadPrivate::start (arg=0x2b02eb0) at thread/qthread_unix.cpp:368 #8 0x7f5065dc36ba in start_thread (arg=0x7f4fb340a700) at pthread_create.c:333 #9 0x7f506682b3dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7f503e7a0700 (LWP 2447)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f506c8c5d04 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7f506c8c5d49 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7f5065dc36ba in start_thread (arg=0x7f503e7a0700) at pthread_create.c:333 #4 0x7f506682b3dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7f504c972700 (LWP 2373)): #0 0x7f5061729a79 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f50616e5488 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f50671466cb in QEventDispatcherGlib::processEvents (this=0x7f50440008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #3 0x7f50670eee2a in QEventLoop::exec (this=this@entry=0x7f504c971ce0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #4 0x7f5066f178f4 in QThread::exec (this=) at thread/qthread.cpp:515 #5 0x7f506a06ed25 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7f5066f1c709 in QThreadPrivate::start (arg=0x21e5210) at thread/qthread_unix.cpp:368 #7
