[kde] [Bug 479891] Some text glyphs in QML software are mis-aligned or squished when using a fractional scale factor
https://bugs.kde.org/show_bug.cgi?id=479891 --- Comment #24 from Dāvis --- (In reply to Nate Graham from comment #23) > Apparently setting QT_SCALE_FACTOR_ROUNDING_POLICY=RoundPreferFloor in the > environment works around this. Indeed, that makes it look WAY better. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 473808] XDG Extended Attribute spec support
https://bugs.kde.org/show_bug.cgi?id=473808 Dāvis changed: What|Removed |Added CC||davis...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482780] Incorrect color gamut with HDR enabled
https://bugs.kde.org/show_bug.cgi?id=482780 --- Comment #16 from Dāvis --- I just tested Colorblindness Correction (in Window Management => Desktop Effects) and it doesn't work at all in HDR mode, I basically get nearly black screen (it's incredibly dim) so there definitively is some bug somewhere. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483038] Screen set to 60Hz but renders at 30FPS
https://bugs.kde.org/show_bug.cgi?id=483038 Dāvis changed: What|Removed |Added CC||davis...@gmail.com --- Comment #1 from Dāvis --- I just tested this with AMD Vega 64 using amdgpu driver and I don't have such issue. Works correctly in all refresh rates: 60 Hz, 72 Hz, 75 Hz, 85 Hz, 96 Hz, 100 Hz, 120 Hz, 144 Hz, 180 Hz. So this looks something specific to your setup/GPU/monitor. Maybe you can try different monitor and see if it makes any difference to rule that out. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482780] Incorrect color gamut with HDR enabled
https://bugs.kde.org/show_bug.cgi?id=482780 --- Comment #15 from Dāvis --- By the way another interesting thing regarding => https://webkit.org/blog-files/color-gamut/Webkit-logo-P3.png My phone's photo viewer does show logo in these modes: * Standard color mode is enabled (Contrast will remain constant) * Advanced => Original identify color gamut automatically through color calibration All other modes doesn't show it, not even P3 (Display all screen content in P3 color gamut) I tried other phones aswell and none of them could show it. Also Discord does show it on Linux and on my phone it does appear on Discord for few ms and then disappears. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482780] Incorrect color gamut with HDR enabled
https://bugs.kde.org/show_bug.cgi?id=482780 --- Comment #14 from Dāvis --- > (In reply to Dāvis from comment #1) > > Also for me that SDR Color Intensity slider doesn't work at all, it does > > nothing - no visual change between 0% and 100%. > That's bug 482809 > Unfortunately it's not, I tested that MR https://invent.kde.org/plasma/kwin/-/merge_requests/5397 but it didn't change anything. Slider still does nothing. > (In reply to Dāvis from comment #3) > > Ohh it looks like SDR Brightness calculation is wrong. Atleast for me if I > > set it to max 542 nits then I get correct saturation but screen is WAY too > > bright (it daylight can be fine but at night I don't want to be blinded :D) > > With HDR disabled I can set monitor's builtin brightness to 0% and colors > > are still saturated while screen being dim/non-bright. > > > > So I think KWin does brightness wrong, it probably needs to increase > > saturation when decreasing brightness to keep same ratio so that colors > > don't look washed out or something like that. > You're not entirely wrong, the perceived intensity of a color is tied to its > brightness, and that's much more noticeable when the color is less > saturated. I'm not sure yet if we should do anything about that in KWin > though. > I don't see why there couldn't be more configuration options. For example I have Android phone with HDR and there are a lot of settings that I can adjust. See attached screenshots (Android (MIUI) HDR/Color settings) of setting pages. Such settings might especially matter for people with various forms of color blindness and such. Also even for me if I have been seeing colors wrong my whole life I don't really care that now they are more "correct" if they look worse to me. I think perceived good looking colors can be subjective. Of course if I'm editing some video/photo then I do want most accurate colors but my issue is specifically about how application icons/colors looks like with HDR mode on. > (In reply to Dāvis from comment #4) > > No, it's not related to brightness, colors are just wrong, it's very > > noticeable when opening `htop` in Konsole and switching between HDR on and > > HDR off. The difference is so insane that HDR off looks WAY better and more > > "HDR" than with HDR on... Even with 542 nits those colors look washed out > > and not as "bright/colorful". > To some degree, that is expected. Without color management, wide color gamut > displays show very oversaturated colors, and if you get used to that, the > correct colors seem desaturated. > If that's actually what's happening for you though is hard do judge without > objective measurements. If you have access to a colorimeter, could you > measure what color gamut KWin actually outputs for sRGB apps? If you don't, > a visual comparison with a display close to sRGB (most laptops have that) > would also be useful. I don't have colorimeter and I don't really know what you mean but I took photos with my DSLR camera in 14-bit Adobe RGB where can compare HDR on vs off in exactly same settings: ISO 400, F/8, 1/50s Here: https://drive.google.com/drive/folders/1oMdpwjY0JUAtXfkVxVoKM1E-yuqppmrd?usp=drive_link They're unedited RAW so all information is there, you can open them with Gwenview and Darktable. There can clearly see that left side red image is more orange in HDR on but more bright red in off. Also in Konsole yellow and cyan is more intense with HDR off. That displayed red image is this so you can compare those photos with it => https://webkit.org/blog-files/color-gamut/Webkit-logo-P3.png (it's 16-bit color) While looking into this I found bunch of interesting things, most programs can't render that image but shows only red without that logo being visible. I tested Firefox, Chrome on both Linux and Windows and Edge aswell and none could show it. Gwenview also doesn't show it. But KolourPaint and mpv can show it. I also looked into HDR tests but I couldn't find any that would prove that HDR works... https://www.wide-gamut.com/test/image-hdr => says "It looks like your monitor or browser does not support HDR images :( The images below may not display correctly" - but maybe that test itself doesn't work rather than my HDR not working :D It doesn't work on my HDR phone either and here https://webkit.org/blog-files/color-gamut/comparison.html I see image/color difference even in SDR... I also tried looking at HDR movie with mpv but didn't see any difference either. I installed `vk-hdr-layer-kwin6-git` from AUR and used > ENABLE_HDR_WSI=1 mpv --vid=1 --aid=6 --vo=gpu-next --target-colorspace-hint > --gpu-api=vulkan --gpu-context=waylandvk MOVIE where MOVIE is > hevc (Main 10) (HDMV / 0x564D4448), yuv420p10le(tv, > bt2020nc/bt2020/smpte2084), 3840x2160 [SAR 1:1 DAR 16:9], 23.98 fps, 23.98 > tbr, 90k tbn -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482780] Incorrect color gamut with HDR enabled
https://bugs.kde.org/show_bug.cgi?id=482780 --- Comment #13 from Dāvis --- Created attachment 166912 --> https://bugs.kde.org/attachment.cgi?id=166912=edit Android (MIUI) HDR/Color settings -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482780] Incorrect color gamut with HDR enabled
https://bugs.kde.org/show_bug.cgi?id=482780 --- Comment #12 from Dāvis --- Created attachment 166911 --> https://bugs.kde.org/attachment.cgi?id=166911=edit Android (MIUI) HDR/Color settings -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482780] Incorrect color gamut with HDR enabled
https://bugs.kde.org/show_bug.cgi?id=482780 --- Comment #11 from Dāvis --- Created attachment 166910 --> https://bugs.kde.org/attachment.cgi?id=166910=edit Android (MIUI) HDR/Color settings -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482780] Incorrect color gamut with HDR enabled
https://bugs.kde.org/show_bug.cgi?id=482780 --- Comment #10 from Dāvis --- Created attachment 166909 --> https://bugs.kde.org/attachment.cgi?id=166909=edit Android (MIUI) HDR/Color settings -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482780] Incorrect color gamut with HDR enabled
https://bugs.kde.org/show_bug.cgi?id=482780 --- Comment #9 from Dāvis --- Created attachment 166908 --> https://bugs.kde.org/attachment.cgi?id=166908=edit Android (MIUI) HDR/Color settings -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482768] Plasmashell crashes in KScreen::WaylandConfig::setupRegistry() when I turn my monitor off and back on
https://bugs.kde.org/show_bug.cgi?id=482768 Dāvis changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=480835 --- Comment #3 from Dāvis --- Hmm this might be duplicated of https://bugs.kde.org/show_bug.cgi?id=480835 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 480835] plasmashell crashes in KScreen::WaylandConfig::setupRegistry() when monitor is turned off
https://bugs.kde.org/show_bug.cgi?id=480835 Dāvis changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=482768 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482768] Plasmashell crashes in KScreen::WaylandConfig::setupRegistry() when I turn my monitor off and back on
https://bugs.kde.org/show_bug.cgi?id=482768 Dāvis changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=464258 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464258] plasmashell crashed with the error The Wayland connection experienced a fatal error: Bad file descriptor
https://bugs.kde.org/show_bug.cgi?id=464258 Dāvis changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=482768 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482768] Plasmashell crashes in KScreen::WaylandConfig::setupRegistry() when I turn my monitor off and back on
https://bugs.kde.org/show_bug.cgi?id=482768 Dāvis changed: What|Removed |Added CC||davis...@gmail.com --- Comment #2 from Dāvis --- I also got this same crash but I didn't turn off my monitor. Maybe it went into power saving mode? in log I see > plasmashell[200110]: KPackageStructure of > KPluginMetaData(pluginId:"org.kde.graphsplasmoid", fileName: > "/usr/share/plasma/plasmoids/org.kde.graphsplasmoid/metadata.json") does not > match requested format "Plasma/Applet" > plasmashell[200110]: KPackageStructure of > KPluginMetaData(pluginId:"org.kde.plasma.kclock_1x2", fileName: > "/usr/share/plasma/plasmoids/org.kde.plasma.kclock_1x2/metadata.json") does > not match requested format "Plasma/Applet" > plasmashell[200110]: KPackageStructure of > KPluginMetaData(pluginId:"org.kde.plasma.kweather_1x4", fileName: > "/usr/share/plasma/plasmoids/org.kde.plasma.kweather_1x4/metadata.json") does > not match requested format "Plasma/Applet" > plasmashell[200110]: KPackageStructure of > KPluginMetaData(pluginId:"org.kde.merkuro.contact", fileName: > "/usr/share/plasma/plasmoids/org.kde.merkuro.contact/metadata.json") does not > match requested format "Plasma/Applet" > plasmashell[200110]: kf.coreaddons: The plugin > "/usr/lib/qt6/plugins/plasma/applets/plasma_applet_kweather_1x4.so" > explicitly states an Id in the embedded metadata, which is different from the > one derived from the filename The Id field from the KPlugin object in the > metadata should be removed > plasmashell[200110]: kscreen.kwayland: Connection to Wayland server timed out. > plasmashell[200110]: qt.core.qobject.connect: QObject::connect(QObject, > ConfigMonitor::Private): invalid nullptr parameter > plasmashell[200110]: KCrash: Application 'plasmashell' crashing... > crashRecursionCounter = 2 > systemd-coredump[200163]: [] Process 200110 (plasmashell) of user 1000 > dumped core. Note this looks very similar to https://bugs.kde.org/show_bug.cgi?id=464258 but message is different. Backtrace: Thread 18 (Thread 0x7ea495e006c0 (LWP 200136)): #0 0x7ea4b9aa5ebe in __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x0, op=393, expected=0, futex_word=0x5c8066e6a048) at futex-internal.c:57 #1 __futex_abstimed_wait_common (futex_word=futex_word@entry=0x5c8066e6a048, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0, cancel=cancel@entry=true) at futex-internal.c:87 #2 0x7ea4b9aa5f3f in __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x5c8066e6a048, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at futex-internal.c:139 #3 0x7ea4b9aa8750 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5c8066e69ff0, cond=0x5c8066e6a020) at pthread_cond_wait.c:503 #4 ___pthread_cond_wait (cond=0x5c8066e6a020, mutex=0x5c8066e69ff0) at pthread_cond_wait.c:618 #5 0x7ea4b048685c in cnd_wait () at ../mesa-24.0.2/src/c11/impl/threads_posix.c:135 #6 util_queue_thread_func () at ../mesa-24.0.2/src/util/u_queue.c:290 #7 0x7ea4b049e82c in impl_thrd_routine () at ../mesa-24.0.2/src/c11/impl/threads_posix.c:67 #8 0x7ea4b9aa955a in start_thread (arg=) at pthread_create.c:447 #9 0x7ea4b9b26a3c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78 Thread 17 (Thread 0x7ea497c006c0 (LWP 200133)): #0 0x7ea4b9aa5ebe in __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x0, op=393, expected=0, futex_word=0x5c8066e7e108) at futex-internal.c:57 #1 __futex_abstimed_wait_common (futex_word=futex_word@entry=0x5c8066e7e108, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0, cancel=cancel@entry=true) at futex-internal.c:87 #2 0x7ea4b9aa5f3f in __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x5c8066e7e108, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at futex-internal.c:139 #3 0x7ea4b9aa8750 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5c8066e7e0b0, cond=0x5c8066e7e0e0) at pthread_cond_wait.c:503 #4 ___pthread_cond_wait (cond=0x5c8066e7e0e0, mutex=0x5c8066e7e0b0) at pthread_cond_wait.c:618 #5 0x7ea4b048685c in cnd_wait () at ../mesa-24.0.2/src/c11/impl/threads_posix.c:135 #6 util_queue_thread_func () at ../mesa-24.0.2/src/util/u_queue.c:290 #7 0x7ea4b049e82c in impl_thrd_routine () at ../mesa-24.0.2/src/c11/impl/threads_posix.c:67 #8 0x7ea4b9aa955a in start_thread (arg=) at pthread_create.c:447 #9 0x7ea4b9b26a3
[konsole] [Bug 483149] Konsole's content doesn't update/is stuck/frozen
https://bugs.kde.org/show_bug.cgi?id=483149 --- Comment #1 from Dāvis --- By the way I figured out how to get it unstuck, if I resize Konsole's window with mouse then it gets unstuck and content renders/works again :) -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 483149] New: Konsole's content doesn't update/is stuck/frozen
https://bugs.kde.org/show_bug.cgi?id=483149 Bug ID: 483149 Summary: Konsole's content doesn't update/is stuck/frozen Classification: Applications Product: konsole Version: 24.02.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: davis...@gmail.com Target Milestone: --- SUMMARY I have Konsole with multiple tabs open where tab's content is frozen. That is if I switch between tabs - content doesn't get switched to new tab (and current tab doesn't react to keys) but only Konsole's window title name is changed. Hamburger menu still works but Konsole without content is useless... STEPS TO REPRODUCE No idea OBSERVED RESULT Tab's content is stuck/frozen. Can't switch to other tabs either. EXPECTED RESULT Tab's content to work - reacts to keys and switching to different tabs also updates content SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION backtrace of this stuck Konsole Thread 10 (Thread 0x756408c006c0 (LWP 43106) "konsol:traceq0"): #0 0x75644f4a5ebe in __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x0, op=393, expected=0, futex_word=0x59663503e238) at futex-internal.c:57 #1 __futex_abstimed_wait_common (futex_word=futex_word@entry=0x59663503e238, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0, cancel=cancel@entry=true) at futex-internal.c:87 #2 0x75644f4a5f3f in __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x59663503e238, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at futex-internal.c:139 #3 0x75644f4a8750 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x59663503e1e0, cond=0x59663503e210) at pthread_cond_wait.c:503 #4 ___pthread_cond_wait (cond=0x59663503e210, mutex=0x59663503e1e0) at pthread_cond_wait.c:618 #5 0x756415c8685c in cnd_wait () at ../mesa-24.0.2/src/c11/impl/threads_posix.c:135 #6 util_queue_thread_func () at ../mesa-24.0.2/src/util/u_queue.c:290 #7 0x756415c9e82c in impl_thrd_routine () at ../mesa-24.0.2/src/c11/impl/threads_posix.c:67 #8 0x75644f4a955a in start_thread (arg=) at pthread_create.c:447 #9 0x75644f526a3c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78 Thread 9 (Thread 0x75640a0006c0 (LWP 43105) "konsol:traceq0"): #0 0x75644f4a5ebe in __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x0, op=393, expected=0, futex_word=0x596634ec0598) at futex-internal.c:57 #1 __futex_abstimed_wait_common (futex_word=futex_word@entry=0x596634ec0598, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0, cancel=cancel@entry=true) at futex-internal.c:87 #2 0x75644f4a5f3f in __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x596634ec0598, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at futex-internal.c:139 #3 0x75644f4a8750 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x596634ec0540, cond=0x596634ec0570) at pthread_cond_wait.c:503 #4 ___pthread_cond_wait (cond=0x596634ec0570, mutex=0x596634ec0540) at pthread_cond_wait.c:618 #5 0x756415c8685c in cnd_wait () at ../mesa-24.0.2/src/c11/impl/threads_posix.c:135 #6 util_queue_thread_func () at ../mesa-24.0.2/src/util/u_queue.c:290 #7 0x756415c9e82c in impl_thrd_routine () at ../mesa-24.0.2/src/c11/impl/threads_posix.c:67 #8 0x75644f4a955a in start_thread (arg=) at pthread_create.c:447 #9 0x75644f526a3c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78 Thread 8 (Thread 0x75640aa006c0 (LWP 43104) "konsol:sh_opt0"): #0 0x75644f4a5ebe in __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x0, op=393, expected=0, futex_word=0x596634e0eb30) at futex-internal.c:57 #1 __futex_abstimed_wait_common (futex_word=futex_word@entry=0x596634e0eb30, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0, cancel=cancel@entry=true) at futex-internal.c:87 #2 0x75644f4a5f3f in __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x596634e0eb30, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at futex-internal.c:139 #3 0x75644f4a8750 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x596634e0ead8, cond=0x596634e0eb08) at pthread_cond_wait.c:503 #4 ___pthread_cond_wait (cond=0x596634e0eb08, mutex=0x596634e0ead8) at pthread_cond_wait.c:618 #5 0x756415c8685c in cnd_wait () at ../mesa-24.0.2/src/c11/impl/threads_posix.c:135 #6 util_queue_thread_func () at
[kmail2] [Bug 483141] New: KMail doesn't exit/froze/hung
https://bugs.kde.org/show_bug.cgi?id=483141 Bug ID: 483141 Summary: KMail doesn't exit/froze/hung Classification: Applications Product: kmail2 Version: 6.0.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: davis...@gmail.com Target Milestone: --- Created attachment 166893 --> https://bugs.kde.org/attachment.cgi?id=166893=edit backtrace of stuck KMail SUMMARY I have close to 300k emails (shows up like ~500k+) from GMail I'm trying to filter/move to local mailbox. In KMail I select "Apply All Filters" and then it slowly processes those - it's taking forever. Anyway issue is that KMail was using a lot of RAM (~6 GiB) and I was running low on free RAM so I did `pkill kmail`. While that did remove KMail from Plasma task panel the process still stayed stuck (using all that RAM) and didn't exit. STEPS TO REPRODUCE No idea OBSERVED RESULT KMail process stuck after issuing SIGTERM EXPECTED RESULT KMail to exit SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION I attached backtrace of this stuck running KMail. Here's the main thread: Thread 1 (Thread 0x7b18d0238100 (LWP 48119) "kmail"): #0 0x7b18e9d190bf in __GI___poll (fds=0x5b85fef1ade0, nfds=3, timeout=475) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7b18e5d932f6 in g_main_context_poll_unlocked (priority=2147483647, n_fds=3, fds=0x5b85fef1ade0, timeout=, context=0x7b18c8000ef0) at ../glib/glib/gmain.c:4653 #2 g_main_context_iterate_unlocked.isra.0 (context=context@entry=0x7b18c8000ef0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/glib/gmain.c:4344 #3 0x7b18e5d33162 in g_main_context_iteration (context=0x7b18c8000ef0, may_block=1) at ../glib/glib/gmain.c:4414 #4 0x7b18e91739c4 in QEventDispatcherGlib::processEvents (this=0x5b85fe9255d0, flags=...) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qeventdispatcher_glib.cpp:393 #5 0x7b18e8f43d6e in QEventLoop::processEvents (flags=..., this=0x7fff90a5ead0) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qeventloop.cpp:100 #6 QEventLoop::exec (this=0x7fff90a5ead0, flags=...) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qeventloop.cpp:182 #7 0x7b18e8f3c2b8 in QCoreApplication::exec () at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/global/qflags.h:74 #8 0x7b18e9ef0f0a in QApplication::exec () at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/widgets/kernel/qapplication.cpp:2574 #9 0x5b85fd0acc78 in main (argc=, argv=) at /usr/src/debug/kmail/kmail-24.02.0/src/main.cpp:174 It looks like it's stuck in event loop and haven't realized it should exit. this does nothing: > $ pkill -e --signal SIGTERM kmail > kmail killed (pid 48119) > $ cat /proc/48119/cmdline > /usr/bin/kmail-qwindowtitleKMail SIGKILL of course works. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 454363] No feedback when suspend to RAM is prevented due to background data transfer to USB device
https://bugs.kde.org/show_bug.cgi?id=454363 Dāvis changed: What|Removed |Added CC||davis...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 454363] No feedback when suspend to RAM is prevented due to background data transfer to USB device
https://bugs.kde.org/show_bug.cgi?id=454363 Dāvis changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=483107 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 483107] Plasma doesn't provide any feedback about progress of Suspend/Sleep
https://bugs.kde.org/show_bug.cgi?id=483107 Dāvis changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=454363 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 483107] New: Plasma doesn't provide any feedback about progress of Suspend/Sleep
https://bugs.kde.org/show_bug.cgi?id=483107 Bug ID: 483107 Summary: Plasma doesn't provide any feedback about progress of Suspend/Sleep Classification: Plasma Product: Powerdevil Version: 6.0.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: davis...@gmail.com CC: m...@ratijas.tk, natalie_clar...@yahoo.de Target Milestone: --- SUMMARY This is somewhat similar to https://bugs.kde.org/show_bug.cgi?id=454363 but in my case it was due to some IO problem. Basically currently Plasma doesn't provide any feedback after clicking "Sleep/Suspend" and it just appears that nothing happens/doesn't work/broken. There should be some way to indicate what is happening with my sleep/suspend and if there is error it should be displayed or user notified what he should do (like tell to check dmesg). Option to cancel in progress sleep/suspend would also be great! STEPS TO REPRODUCE Don't really know, I guess patching kernel to simulate failure could be one way... OBSERVED RESULT Clicking on "Sleep/Suspend" does nothing EXPECTED RESULT Show something about progress (or failure) of Sleep/Suspend. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Linux kernel 6.7.8 ADDITIONAL INFORMATION This is what systemd showed > systemctl suspend > Call to Suspend failed: There's already a shutdown or sleep operation in > progress After several minutes it did actually suspend but I had no idea it would. In dmesg can see hung task: [51914.351178] PM: suspend entry (deep) [52037.335042] Filesystems sync: 122.987 seconds [52037.348997] Freezing user space processes [52038.577747] Freezing user space processes completed (elapsed 1.228 seconds) [52038.577756] OOM killer disabled. [52038.577758] Freezing remaining freezable tasks [52058.581719] Freezing remaining freezable tasks failed after 20.004 seconds (0 tasks refusing to freeze, wq_busy=1): [52058.581727] Showing freezable workqueues that are still busy: [52058.581729] workqueue events_freezable: flags=0x4 [52058.581745] pwq 32: cpus=16 node=0 flags=0x0 nice=0 active=0/0 refcnt=2 [52058.581750] inactive: pci_pme_list_scan [52058.581757] workqueue events_freezable_power_: flags=0x86 [52058.581759] pwq 260: cpus=0-127 node=0 flags=0x4 nice=0 active=0/0 refcnt=2 [52058.581762] inactive: disk_events_workfn [52058.581766] pwq 260: cpus=0-127 node=0 flags=0x4 nice=0 active=0/0 refcnt=2 [52058.581770] inactive: disk_events_workfn [52058.581773] pwq 259: cpus=0-127 node=0 flags=0x4 nice=0 active=0/0 refcnt=2 [52058.581776] inactive: disk_events_workfn [52058.581780] pwq 260: cpus=0-127 node=0 flags=0x4 nice=0 active=0/0 refcnt=2 [52058.581782] inactive: disk_events_workfn [52058.581811] workqueue btrfs-endio-meta: flags=0xe [52058.581826] pwq 260: cpus=0-127 node=0 flags=0x4 nice=0 active=0/0 refcnt=2 [52058.581829] inactive: btrfs_end_bio_work [btrfs] [52058.581882] workqueue btrfs-endio-write: flags=0xe [52058.581898] pwq 257: cpus=0-127 node=0 flags=0x4 nice=0 active=0/0 refcnt=14 [52058.581901] inactive: 13*btrfs_work_helper [btrfs] [52058.581952] pwq 260: cpus=0-127 node=0 flags=0x4 nice=0 active=0/0 refcnt=2 [52058.581955] inactive: btrfs_work_helper [btrfs] [52058.582004] pwq 259: cpus=0-127 node=0 flags=0x4 nice=0 active=0/0 refcnt=10 [52058.582007] inactive: 9*btrfs_work_helper [btrfs] [52058.582059] workqueue btrfs_discard: flags=0xa0006 [52058.582062] pwq 256: cpus=0-127 flags=0x4 nice=0 active=0/0 refcnt=130 [52058.582064] inactive: btrfs_discard_workfn [btrfs] [52058.582112] workqueue btrfs-endio: flags=0xe [52058.582127] pwq 259: cpus=0-127 node=0 flags=0x4 nice=0 active=0/0 refcnt=8 [52058.582130] inactive: 7*btrfs_end_bio_work [btrfs] [52058.582172] pwq 259: cpus=0-127 node=0 flags=0x4 nice=0 active=0/0 refcnt=2 [52058.582175] inactive: btrfs_end_bio_work [btrfs] [52058.582216] pwq 259: cpus=0-127 node=0 flags=0x4 nice=0 active=0/0 refcnt=5 [52058.582219] inactive: 4*btrfs_end_bio_work [btrfs] [52058.582261] pwq 259: cpus=0-127 node=0 flags=0x4 nice=0 active=0/0 refcnt=11 [52058.582264] inactive: 10*btrfs_end_bio_work [btrfs] [52058.582309] workqueue btrfs-endio-meta: flags=0xe [52058.582324] pwq 259: cpus=0-127 node=0 flags=0x4 nice=0 active=0/0 refcnt=2 [52058.582327] inactive: btrfs_end_bio_work [btrfs] [52058.582373] workqueue btrfs-endio-write: flags=0xe [52058.582388] pwq 259: cpus=0-127 node=0 flags=0x4 nice=0 active=0/0 refcnt=4 [52058.582391] inactive: 3*btrfs_work_helper [btrfs] [52058.582440] pwq 259: cpus=0-127 node=0 flags=0x4 nice=0 active=0/0 refcnt=8 [52058.582443] inactive:
[kwin] [Bug 482774] Still tiny border shown even when set as "No Window Borders"
https://bugs.kde.org/show_bug.cgi?id=482774 --- Comment #6 from Dāvis --- (In reply to Nate Graham from comment #5) > The outline is only shown by the Breeze decoration. That's not true, see my previously attached screenshot "System settings border", that black outline comes from Plastik. But yeah it's not present for Oxygen for some reason I thought I saw it there too. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482780] Incorrect color gamut with HDR enabled
https://bugs.kde.org/show_bug.cgi?id=482780 --- Comment #4 from Dāvis --- No, it's not related to brightness, colors are just wrong, it's very noticeable when opening `htop` in Konsole and switching between HDR on and HDR off. The difference is so insane that HDR off looks WAY better and more "HDR" than with HDR on... Even with 542 nits those colors look washed out and not as "bright/colorful". So this basically means in current state HDR on setting is unusable as daily default. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482780] Incorrect color gamut with HDR enabled
https://bugs.kde.org/show_bug.cgi?id=482780 --- Comment #3 from Dāvis --- Ohh it looks like SDR Brightness calculation is wrong. Atleast for me if I set it to max 542 nits then I get correct saturation but screen is WAY too bright (it daylight can be fine but at night I don't want to be blinded :D) With HDR disabled I can set monitor's builtin brightness to 0% and colors are still saturated while screen being dim/non-bright. So I think KWin does brightness wrong, it probably needs to increase saturation when decreasing brightness to keep same ratio so that colors don't look washed out or something like that. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482780] Incorrect color gamut with HDR enabled
https://bugs.kde.org/show_bug.cgi?id=482780 --- Comment #2 from Dāvis --- Created attachment 166728 --> https://bugs.kde.org/attachment.cgi?id=166728=edit Photo example with HDR disabled -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482780] Incorrect color gamut with HDR enabled
https://bugs.kde.org/show_bug.cgi?id=482780 Dāvis changed: What|Removed |Added CC||davis...@gmail.com --- Comment #1 from Dāvis --- Created attachment 166726 --> https://bugs.kde.org/attachment.cgi?id=166726=edit HDR example with washed out colors I have very similar issue but I'm using AMD Vega 64 with Acer PREDATOR X34 monitor. When I set HDR mode in monitor settings and check "Enable HDR" in Display Configuration then all colors look washed out like missing saturation. This is most noticeable in System Setting icons on right side. When looking at photos/videos then it's not really that noticeable. YouTube videos look fine but it could be it's just not noticable due to not having a reference. Not sure if there is some test for this other than eyeballing :D I attached photos with HDR on and HDR off and while not that noticeable in photos you can kinda see it looks worse with HDR. For example put both images next to each other and look at wallpaper red cloud color at top. I'm using Display Port and linux kernel 6.7.8 so it shouldn't be this issue https://gitlab.freedesktop.org/drm/amd/-/issues/3079 which is claimed to be fixed. Also for me that SDR Color Intensity slider doesn't work at all, it does nothing - no visual change between 0% and 100%. I also tried mpv --target-prim=bt.709 but didn't see any difference either. Here's some info: > $ kscreen-doctor -o > Output: 1 DP-2 > enabled > connected > priority 1 > DisplayPort > Modes: 0:3440x1440@180*! 1:3440x1440@144 2:3440x1440@60 > 3:3840x2160@60 4:3840x2160@60 5:3840x2160@30 6:3840x2160@30 > 7:3840x2160@25 8:3840x2160@24 9:3840x2160@24 10:3440x1440@120 > 11:3440x1440@100 12:3440x1440@96 13:3440x1440@85 14:3440x1440@75 > 15:3440x1440@72 16:3440x1440@60 17:2560x1080@60 18:2560x1080@60 > 19:2560x1080@50 20:1920x1200@180 21:1920x1080@60 22:1920x1080@60 > 23:1920x1080@60 24:1920x1080@50 25:1920x1080@30 26:1920x1080@30 > 27:1920x1080@25 28:1920x1080@24 29:1920x1080@24 30:1600x1200@180 > 31:1680x1050@60 32:1280x1024@75 33:1280x1024@60 34:1440x900@60 > 35:1280x960@60 36:1280x800@60 37:1152x864@75 38:1280x720@60 > 39:1280x720@60 40:1280x720@60 41:1280x720@50 42:1024x768@75 > 43:1024x768@70 44:1024x768@60 45:832x624@75 46:800x600@75 47:800x600@72 > 48:800x600@60 49:800x600@56 50:720x576@50 51:720x576@50 52:720x480@60 > 53:720x480@60 54:720x480@60 55:720x480@60 56:640x480@75 57:640x480@73 > 58:640x480@67 59:640x480@60 60:640x480@60 61:640x480@60 62:720x400@70 > 63:1600x1200@60 64:1280x1024@60 65:1024x768@60 66:1920x1200@60 > 67:2560x1440@60 68:1920x1080@60 69:1600x900@60 70:1368x768@60 > 71:1280x720@60 > Geometry: 0,0 2294x960 > Scale: 1.5 > Rotation: 1 > Overscan: 0 > Vrr: Never > RgbRange: unknown > HDR: enabled > SDR brightness: 250 nits > SDR gamut wideness: 100% > Peak brightness: 542 nits > Max average brightness: 400 nits > Min brightness: 0 nits > Wide Color Gamut: enabled > ICC profile: none > # cat /sys/kernel/debug/dri/1/crtc-0/amdgpu_current_colorspace > BT2020_RGB > # cat /sys/kernel/debug/dri/1/crtc-0/amdgpu_current_bpc > Current: 8 > Block 0, Base EDID: > EDID Structure Version & Revision: 1.4 > Vendor & Product Identification: > Manufacturer: ACR > Model: 2223 > Serial Number: 277881511 > Made in: week 9 of 2021 > Basic Display Parameters & Features: > Digital display > Bits per primary color channel: 10 > DisplayPort interface > Maximum image size: 80 cm x 35 cm > Gamma: 2.20 > DPMS levels: Off > Supported color formats: RGB 4:4:4, YCrCb 4:4:4, YCrCb 4:2:2 > First detailed timing includes the native pixel format and preferred > refresh rate > Display is continuous frequency > Color Characteristics: > Red : 0.6884, 0.3095 > Green: 0.2578, 0.6699 > Blue : 0.1474, 0.0615 > White: 0.3134, 0.3291 > Block 1, CTA-861 Extension Block: > Revision: 3 > Underscans IT Video Formats by default > Basic audio support > Supports YCbCr 4:4:4 > Supports YCbCr 4:2:2 > Native detailed modes: 1 > Video Data Block: > ... > Colorimetry Data Block: > xvYCC601 > xvYCC709 > BT2020YCC > BT2020RGB > HDR Static Metadata Data Block: > Electro optical transfer functions: > Traditional gamma - SDR luminance range > SMPTE ST2084 >
[Powerdevil] [Bug 482077] powerdevil can pass -1 to KIdleTime::addIdleTimeout()
https://bugs.kde.org/show_bug.cgi?id=482077
--- Comment #55 from Dāvis ---
(In reply to Vlad Zahorodnii from comment #46)
> > It looks like some application is using
> > ext_idle_notifier_v1::get_idle_notification() with 4294967295ms as timeout
> > value, it's uint so this is kinda valid...
>
> can you apply the patch that I've attached to the bug report. it's going to
> be print the executable path and the pid of the offender
I built KWin with that patch but didn't notice any extra log entries, then
realized I didn't build debug build oops
Now with debug build I see same
> "" 3469 wants an idle notification with too big timeout 4294967295
where 3469 is `org_kde_powerdevil`
But I disagree that this is Powerdevil's bug. KWin should either respect this
and notify after ~50days or ignore it and potentially let application know this
in some way.
Powerdevil doing some stupid shit is just another bug - of course should be
fixed but that doesn't mean KWin shouldn't be fixed aswell because ANY
application can send garbage to it.
(In reply to Vlad Zahorodnii from comment #49)
>
> Hmm, can you attach gdb to powerdevil and add a breakpoint in
> KIdleTime::addIdleTimeout please?
Here
> #0 KIdleTime::addIdleTimeout (this=0x5e5e8b5506f0, msec=msec@entry=-1) at
> /usr/src/debug/kidletime/kidletime-6.0.0/src/kidletime.cpp:119
> #1 0x7092748f3cf4 in KIdleTime::addIdleTimeout
> (msec=std::chrono::duration = { -1ms }, this=) at
> /usr/include/c++/13.2.1/bits/chrono.h:587
> #2 PowerDevil::Core::registerActionTimeout (this=0x709258002470,
> action=, timeout=std::chrono::duration = { ms
> }) at /usr/src/debug/powerdevil/powerdevil-6.0.1/daemon/powerdevilcore.cpp:848
> #3 0x709273790ca9 in QtPrivate::QSlotObjectBase::call (a=0x7ffc048b8890,
> r=0x5e5e8b4ce400, this=0x5e5e8b4f9b10, this=, r= out>, a=) at
> /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qobjectdefs_impl.h:433
> #4 doActivate (sender=0x5e5e8b4b8a20, signal_index=6,
> argv=0x7ffc048b8890) at
> /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qobject.cpp:4039
> #5 0x70927490dbe7 in PowerDevil::PolicyAgent::screenLockerActiveChanged
> (this=, _t1=) at
> /usr/src/debug/powerdevil/build/daemon/powerdevilcore_autogen/include/moc_powerdevilpolicyagent.cpp:425
> #6 0x709274905115 in
> PowerDevil::PolicyAgent::onScreenLockerActiveChanged (this=0x5e5e8b4b8a20,
> active=true) at
> /usr/src/debug/powerdevil/powerdevil-6.0.1/daemon/powerdevilpolicyagent.cpp:577
> #7 0x709273790ca9 in QtPrivate::QSlotObjectBase::call (a=0x7ffc048b8ac0,
> r=0x5e5e8b4b8a20, this=0x5e5e8b5d9ce0, this=, r= out>, a=) at
> /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qobjectdefs_impl.h:433
> #8 doActivate (sender=0x5e5e8b5da460, signal_index=3,
> argv=0x7ffc048b8ac0) at
> /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qobject.cpp:4039
> #9 0x709274922bdb in OrgFreedesktopScreenSaverInterface::ActiveChanged
> (_t1=, this=) at
> /usr/src/debug/powerdevil/build/daemon/moc_screenlocker_interface.cpp:304
> #10 OrgFreedesktopScreenSaverInterface::qt_static_metacall
> (_o=_o@entry=0x5e5e8b5da460, _id=_id@entry=0, _a=_a@entry=0x7ffc048b8c88,
> _c=) at
> /usr/src/debug/powerdevil/build/daemon/moc_screenlocker_interface.cpp:235
> #11 0x7092749278b1 in
> OrgFreedesktopScreenSaverInterface::qt_static_metacall (_a=0x7ffc048b8c88,
> _id=0, _c=QMetaObject::InvokeMetaMethod, _o=0x5e5e8b5da460) at
> /usr/src/debug/powerdevil/build/daemon/moc_screenlocker_interface.cpp:229
> #12 OrgFreedesktopScreenSaverInterface::qt_metacall (this=0x5e5e8b5da460,
> _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7ffc048b8c88) at
> /usr/src/debug/powerdevil/build/daemon/moc_screenlocker_interface.cpp:290
> #13 0x7092745f70ce in QDBusConnectionPrivate::deliverCall
> (this=0x7092640016a0, object=0x5e5e8b5da460, msg=..., metaTypes= out>, slotIdx=6) at
> /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/dbus/qdbusintegrator.cpp:977
> #14 0x70927377c2c7 in QObject::event (this=0x5e5e8b5da460,
> e=0x709264031bc0) at
> /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qobject.cpp:1437
> #15 0x709273739818 in QCoreApplication::notifyInternal2
> (receiver=0x5e5e8b5da460, event=event@entry=0x709264031bc0) at
> /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qcoreapplication.cpp:1121
> #16 0x709273739b9b in QCoreApplication::sendEvent (event=0x709264031bc0,
> receiver=) at
> /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qcoreapplication.cpp:1539
> #17 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0,
> data=0x5e5e8b2ac900) at
> /u
[kwin] [Bug 482077] Journal is flooded with "QObject::startTimer: Timers cannot have negative intervals"
https://bugs.kde.org/show_bug.cgi?id=482077
--- Comment #44 from Dāvis ---
Hmm my backtrace is different than Jonathan's.
#0 KWin::IdleDetector::IdleDetector (this=0x55b8773c4220,
timeout=std::chrono::duration = { 4294967295ms }, parent=0x55b877124e50,
this=, timeout=std::chrono::duration = { ms },
parent=) at
/usr/src/debug/kwin/kwin-6.0.1/src/idledetector.cpp:13
#1 0x7d066e8580d6 in
KWin::IdleNotificationV1Interface::IdleNotificationV1Interface
(timeout=std::chrono::duration = { ms }, id=,
version=1, client=, this=0x55b877124e50) at
/usr/src/debug/kwin/kwin-6.0.1/src/wayland/idlenotify_v1.cpp:59
#2
KWin::IdleNotifyV1InterfacePrivate::ext_idle_notifier_v1_get_idle_notification
(this=, resource=, id=,
timeout=, seat=) at
/usr/src/debug/kwin/kwin-6.0.1/src/wayland/idlenotify_v1.cpp:53
#3 0x7d066a230596 in ffi_call_unix64 () at ../src/x86/unix64.S:104
#4 0x7d066a22d00e in ffi_call_int (cif=cif@entry=0x7ffd7e8cfa00,
fn=, rvalue=, avalue=,
closure=closure@entry=0x0) at ../src/x86/ffi64.c:673
#5 0x7d066a22fbd3 in ffi_call (cif=cif@entry=0x7ffd7e8cfa00, fn=, rvalue=rvalue@entry=0x0, avalue=avalue@entry=0x7ffd7e8cfad0) at
../src/x86/ffi64.c:710
#6 0x7d066db1bada in wl_closure_invoke
(closure=closure@entry=0x55b877c2f510, target=,
target@entry=0x55b876c7f520, opcode=opcode@entry=1, data=,
data@entry=0x55b876a3fa80, flags=2) at ../wayland-1.22.0/src/connection.c:1025
#7 0x7d066db20180 in wl_client_connection_data (fd=,
mask=, data=) at
../wayland-1.22.0/src/wayland-server.c:438
#8 0x7d066db1eae2 in wl_event_loop_dispatch (loop=0x55b875540920,
timeout=) at ../wayland-1.22.0/src/event-loop.c:1027
#9 0x7d066e848487 in KWin::Display::dispatchEvents (this=)
at /usr/src/debug/kwin/kwin-6.0.1/src/wayland/display.cpp:118
#10 0x7d066bf90ca9 in QtPrivate::QSlotObjectBase::call (a=0x7ffd7e8d0110,
r=0x55b875540670, this=0x55b875aa3330, this=, r=,
a=) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qobjectdefs_impl.h:433
#11 doActivate (sender=0x55b8758cb410, signal_index=3,
argv=0x7ffd7e8d0110) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qobject.cpp:4039
#12 0x7d066bf98530 in QSocketNotifier::activated (_t3=..., _t2=, _t1=..., this=0x55b8758cb410) at
/usr/src/debug/qt6-base/build/src/corelib/Core_autogen/include/moc_qsocketnotifier.cpp:231
#13 QSocketNotifier::event (this=0x55b8758cb410, e=) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qsocketnotifier.cpp:326
#14 0x7d066cef438b in QApplicationPrivate::notify_helper (this=, receiver=0x55b8758cb410, e=0x7ffd7e8d0210) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/widgets/kernel/qapplication.cpp:3296
#15 0x7d066bf39818 in QCoreApplication::notifyInternal2
(receiver=0x55b8758cb410, event=0x7ffd7e8d0210) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qcoreapplication.cpp:1121
#16 0x7d066c09e749 in QCoreApplication::sendEvent (event=0x7ffd7e8d0210,
receiver=) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qcoreapplication.cpp:1539
#17 QEventDispatcherUNIXPrivate::activateSocketNotifiers
(this=this@entry=0x55b8754712b0) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qeventdispatcher_unix.cpp:267
#18 0x7d066c09fbac in QEventDispatcherUNIX::processEvents (this=, flags=..., flags@entry=...) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qeventdispatcher_unix.cpp:476
#19 0x7d066c9b26e2 in QUnixEventDispatcherQPA::processEvents
(this=, flags=...) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/gui/platform/unix/qunixeventdispatcher.cpp:27
#20 0x7d066bf43d6e in QEventLoop::processEvents (flags=...,
this=0x7ffd7e8d03f0) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qeventloop.cpp:100
#21 QEventLoop::exec (this=0x7ffd7e8d03f0, flags=...) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qeventloop.cpp:182
#22 0x7d066bf3c2b8 in QCoreApplication::exec () at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/global/qflags.h:74
#23 0x7d066cef0f0a in QApplication::exec () at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/widgets/kernel/qapplication.cpp:2574
#24 0x55b8740b4dee in main (argc=, argv=) at
/usr/src/debug/kwin/kwin-6.0.1/src/main_wayland.cpp:609
It looks like some application is using
ext_idle_notifier_v1::get_idle_notification() with 4294967295ms as timeout
value, it's uint so this is kinda valid...
I don't know how to find out who is sending this message? But it seems like
assert() would be wrong for this case and KWin probably should just drop such
silly request.
Nothing special in my config:
$ cat ~/.config/powerdevilrc
[AC][Display]
TurnOffDisplayWhenIdle=false
[AC][SuspendAndShutdown]
AutoSuspendAction=0
[Battery][Display]
DisplayBrightness=60
UseProfileSpecificDisplayBrightness=true
$ cat ~/.config
[kwin] [Bug 482774] Still tiny border shown even when set as "No Window Borders"
https://bugs.kde.org/show_bug.cgi?id=482774 --- Comment #4 from Dāvis --- (In reply to Nate Graham from comment #3) > This isn't a border, it's an outline. You can turn it off in the Breeze > decoration config dialog. Awesome, thanks, that worked! It's in System Settings => Colors & Themes => Windows Decorations => Edit Breeze Theme (Icon) => Shadows and Outline => Outline intensity => Off I guess this is new feature? some people said it's not possible and some didn't like it aswell, see https://www.reddit.com/r/kde/comments/1133p4i/how_to_disable_window_outline_in_breeze/ Now for me this is all good but it seems if someone uses different decoration such as Oxygen or Plastik they still would have this issue since those don't have such setting. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482774] Still tiny border shown even when set as "No Window Borders"
https://bugs.kde.org/show_bug.cgi?id=482774 Dāvis changed: What|Removed |Added Attachment #166632|0 |1 is obsolete|| --- Comment #2 from Dāvis --- Created attachment 166634 --> https://bugs.kde.org/attachment.cgi?id=166634=edit Discord border -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482774] Still tiny border shown even when set as "No Window Borders"
https://bugs.kde.org/show_bug.cgi?id=482774 Dāvis changed: What|Removed |Added CC||davis...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482774] Still tiny border shown even when set as "No Window Borders"
https://bugs.kde.org/show_bug.cgi?id=482774 --- Comment #1 from Dāvis --- Created attachment 166632 --> https://bugs.kde.org/attachment.cgi?id=166632=edit Discord border -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482774] New: Still tiny border shown even when set as "No Window Borders"
https://bugs.kde.org/show_bug.cgi?id=482774 Bug ID: 482774 Summary: Still tiny border shown even when set as "No Window Borders" Classification: Plasma Product: kwin Version: 6.0.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: decorations Assignee: kwin-bugs-n...@kde.org Reporter: davis...@gmail.com Target Milestone: --- Created attachment 166631 --> https://bugs.kde.org/attachment.cgi?id=166631=edit System settings border SUMMARY I have set "No Window Borders" but I still see border around windows. STEPS TO REPRODUCE 1. Set Window Decoration with opposite border color of content to be easily visible such as Plastik 2. Set "No Window Borders" OBSERVED RESULT Seeing border even when "No Window Borders" is selected EXPECTED RESULT To not have any border at all SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION See attached screenshots. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482077] Journal is flooded with "QObject::startTimer: Timers cannot have negative intervals"
https://bugs.kde.org/show_bug.cgi?id=482077 --- Comment #21 from Dāvis --- Created attachment 166630 --> https://bugs.kde.org/attachment.cgi?id=166630=edit kwin_wayland (In reply to Jonathan Lopes from comment #16) > [...] > If I had enough time, I could try to plug a debugger on kwin_wayland to find > what is causing this problem. However, I have basically zero experience with > C++ debugging (although I can figure out with basic directions), so even if > I find some time to do it, I don't even know where to start. It's described in https://community.kde.org/KWin/Debugging#TL;DR_for_bug_reporters But I think "continue" there is wrong, atleast that didn't work for me, but this worked fine $ sudo -E gdb -pid (pidof kwin_wayland) -batch -ex "thread apply all backtrace" See attachment, but here's main thread: Thread 1 (Thread 0x758d15893a00 (LWP 1067690) "kwin_wayland"): #0 0x758d1a719616 in __GI_ppoll (fds=fds@entry=0x63fa9f7f1d40, nfds=nfds@entry=10, timeout=, timeout@entry=0x7ffc058d01b0, sigmask=sigmask@entry=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:42 #1 0x758d1ae98deb in ppoll (__ss=, __timeout=, __nfds=, __fds=) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qcore_unix.cpp:123 #2 qt_ppoll (timeout_ts=0x7ffc058d01b0, nfds=10, fds=0x63fa9f7f1d40) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qcore_unix.cpp:126 #3 qt_ppoll (timeout_ts=0x7ffc058d01b0, nfds=10, fds=0x63fa9f7f1d40) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qcore_unix.cpp:123 #4 qt_safe_poll (fds=0x63fa9f7f1d40, nfds=nfds@entry=10, timeout_ts=timeout_ts@entry=0x7ffc058d0260) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qcore_unix.cpp:158 #5 0x758d1ae9f65a in QEventDispatcherUNIX::processEvents (this=, flags=..., flags@entry=...) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/tools/qarraydatapointer.h:113 #6 0x758d1b7b26e2 in QUnixEventDispatcherQPA::processEvents (this=, flags=...) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/gui/platform/unix/qunixeventdispatcher.cpp:27 #7 0x758d1ad43d6e in QEventLoop::processEvents (flags=..., this=0x7ffc058d03b0) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qeventloop.cpp:100 #8 QEventLoop::exec (this=0x7ffc058d03b0, flags=...) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qeventloop.cpp:182 #9 0x758d1ad3c2b8 in QCoreApplication::exec () at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/global/qflags.h:74 #10 0x758d1bcf0f0a in QApplication::exec () at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/widgets/kernel/qapplication.cpp:2574 #11 0x63fa9c538dee in main (argc=, argv=) at /usr/src/debug/kwin/kwin-6.0.1/src/main_wayland.cpp:609 Currently for me this looks like one of the biggest issues for Plasma 6, because my today's journal size (just last ~7 hours) since I updated is already ~20 GiB (might be other log spam bugs aswell). And compare that with last 5 days (not counting today) when it's 26 GiB. So basically now in single day I generate more logs than previously in a week... `kwin_wayland` generates this warning at a rate of ~17 messages/second. Right now I have over 500k such entries in my journal while using Plasma 6 just for a day... -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 482746] New: Ugly text/font
https://bugs.kde.org/show_bug.cgi?id=482746 Bug ID: 482746 Summary: Ugly text/font Classification: Applications Product: NeoChat Version: 24.02.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: davis...@gmail.com CC: c...@carlschwan.eu Target Milestone: --- Created attachment 166613 --> https://bugs.kde.org/attachment.cgi?id=166613=edit NeoChat ugly text/font SUMMARY I'm on Arch Linux with Plasma 6, neochat 24.02.0, using Wayland with 150% scaling and text looks very ugly/bad. See attached screenshot and pay attention to letters like `e` and `s`. In System Settings I'm using Noto Sans 11pt font, but NeoChart is only application where it looks this bad. OBSERVED RESULT Ugly text EXPECTED RESULT Nice and pretty readable text SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 479721] Neochat can't be opened if it's set to minimize to tray at startup
https://bugs.kde.org/show_bug.cgi?id=479721 Dāvis changed: What|Removed |Added CC||davis...@gmail.com --- Comment #3 from Dāvis --- I'm also experiencing this bug on Arch Linux with Plasma 6, neochat 24.02.0 using Wayland Took me while to figure out why it stopped working but found this workaround: $ sed -i "s|MinimizeToSystemTrayOnStartup=true|MinimizeToSystemTrayOnStartup=false|" ~/.config/neochatrc Nothing interesting is shown in logs: qt.qml.typeresolution.cycle: Cyclic dependency detected between "qrc:/qt/qml/org/kde/desktop/private/TextFieldContextMenu.qml" and "qrc:/qt/qml/org/kde/desktop/MenuItem.qml" Reading access token from the keychain for xxx quotient.main: The library is built with end-to-end encryption (E2EE) qrc:/org/kde/neochat/qml/main.qml:250:9: QML RoomListPage: Created graphical object was not placed in the graphics scene. qrc:/org/kde/neochat/qml/RoomPage.qml:17:1: QML RoomPage: Created graphical object was not placed in the graphics scene. qrc:/org/kde/neochat/qml/RoomInformation.qml:133:13: QML ListSectionHeader: Binding loop detected for property "implicitWidth" qrc:/org/kde/neochat/qml/RoomInformation.qml:67:13: QML ListSectionHeader: Binding loop detected for property "implicitWidth" And backtrace: Thread 27 (Thread 0x7fffa6a006c0 (LWP 1050127) "QNetworkAccessM"): #0 0x74b190bf in __GI___poll (fds=0x7fff58001530, nfds=2, timeout=120171) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x72b6c2f6 in g_main_context_poll_unlocked (priority=2147483647, n_fds=2, fds=0x7fff58001530, timeout=, context=0x7fff58000c60) at ../glib/glib/gmain.c:4653 #2 g_main_context_iterate_unlocked.isra.0 (context=context@entry=0x7fff58000c60, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/glib/gmain.c:4344 #3 0x72b0c162 in g_main_context_iteration (context=0x7fff58000c60, may_block=1) at ../glib/glib/gmain.c:4414 #4 0x753739c4 in QEventDispatcherGlib::processEvents (this=0x7fff58000b70, flags=...) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qeventdispatcher_glib.cpp:393 #5 0x75143d6e in QEventLoop::processEvents (flags=..., this=0x7fffa69ffb50) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qeventloop.cpp:100 #6 QEventLoop::exec (this=0x7fffa69ffb50, flags=...) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qeventloop.cpp:182 #7 0x7522116f in QThread::exec (this=) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/thread/qthread.cpp:578 #8 QThread::run (this=) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/thread/qthread.cpp:699 #9 0x752a0bd3 in operator() (__closure=) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/thread/qthread_unix.cpp:324 #10 (anonymous namespace)::terminate_on_exception > (t=) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/thread/qthread_unix.cpp:260 #11 QThreadPrivate::start (arg=0x7fff5c016fc0) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/thread/qthread_unix.cpp:283 #12 0x74aa955a in start_thread (arg=) at pthread_create.c:447 #13 0x74b26a3c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78 Thread 26 (Thread 0x7fffa7e006c0 (LWP 1050126) "QQuickPixmapRea"): #0 0x74b190bf in __GI___poll (fds=0x5708d190, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x72b6c2f6 in g_main_context_poll_unlocked (priority=2147483647, n_fds=1, fds=0x5708d190, timeout=, context=0x7fff5c000c60) at ../glib/glib/gmain.c:4653 #2 g_main_context_iterate_unlocked.isra.0 (context=context@entry=0x7fff5c000c60, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/glib/gmain.c:4344 #3 0x72b0c162 in g_main_context_iteration (context=0x7fff5c000c60, may_block=1) at ../glib/glib/gmain.c:4414 #4 0x753739c4 in QEventDispatcherGlib::processEvents (this=0x7fff5c000b70, flags=...) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qeventdispatcher_glib.cpp:393 #5 0x75143d6e in QEventLoop::processEvents (flags=..., this=0x7fffa7dffaf0) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qeventloop.cpp:100 #6 QEventLoop::exec (this=0x7fffa7dffaf0, flags=...) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qeventloop.cpp:182 #7 0x7522106f in QThread::exec (this=this@entry=0x574b3910) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/global/qflags.h:74 #8 0x7770d0d3 in QQuickPixmapReader::run (this=0x574b3910) at /usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/quick/util/qquickpixmapcac
[kwin] [Bug 482077] Journal is flooded with "QObject::startTimer: Timers cannot have negative intervals"
https://bugs.kde.org/show_bug.cgi?id=482077 Dāvis changed: What|Removed |Added CC||davis...@gmail.com --- Comment #18 from Dāvis --- I'm also experiencing this issue on Arch Linux with Plasma 6, kwin 6.0.1. I don't have anything related to Razer. I have Logitech wireless mouse. -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 465977] New: ASSERT failure in Uils::exec: "Query failed:UNIQUE constraint failed: ResourceInfo.targettedResource
https://bugs.kde.org/show_bug.cgi?id=465977
Bug ID: 465977
Summary: ASSERT failure in Uils::exec: "Query failed:UNIQUE
constraint failed: ResourceInfo.targettedResource
Classification: Plasma
Product: kactivitymanagerd
Version: master
Platform: Archlinux
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: ivan.cu...@kde.org
Reporter: davis...@gmail.com
CC: plasma-b...@kde.org
Target Milestone: ---
SUMMARY
Hit this assert
```
org.kde.kactivities.resources: "INSERT INTO ResourceInfo( targettedResource,
title, autoTitle, mimetype, autoMimetype) VALUES ( :targettedResource, '' , 1
, '' , 1 )"
org.kde.kactivities.resources: QSqlError("1555", "Nevarēja saņemt rindu",
"UNIQUE constraint failed: ResourceInfo.targettedResource")
ASSERT failure in Uils::exec: "Query failed:UNIQUE constraint failed:
ResourceInfo.targettedResource Nevarēja saņemt rindu", file
/mnt/KDE/kactivitymanagerd/src/service/plugins/sqlite/Utils.h, line 54
```
```
#2 0x7f3a39a51ea8 in __GI_raise (sig=6) at ../sysdeps/posix/raise.c:26
#3 0x7f3a3b7d876e in KCrash::defaultCrashHandler (sig=6) at
/usr/src/debug/kcrash-git/kcrash/src/kcrash.cpp:597
#4
#5 __pthread_kill_implementation (threadid=,
signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
#6 0x7f3a39aa0953 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78
#7 0x7f3a39a51ea8 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#8 0x7f3a39a3b53d in __GI_abort () at abort.c:79
#9 0x7f3a3a0a41c7 in qAbort () at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.4.2/src/corelib/global/qglobal.cpp:3369
#10 0x7f3a3a0a449a in qt_message_fatal (message=...,
context=...) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.4.2/src/corelib/global/qlogging.cpp:1916
#11 QMessageLogger::fatal (this=this@entry=0x7fff18533f58,
msg=msg@entry=0x7f3a3a3bad58 "ASSERT failure in %s: \"%s\", file %s, line %d")
at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.4.2/src/corelib/global/qlogging.cpp:850
#12 0x7f3a3a0a4559 in qt_assert_x (where=where@entry=0x7f3a26d52fca
"Uils::exec", what=, file=file@entry=0x7f3a26d52a90
"/mnt/Dati/Git/KDE/kactivitymanagerd/src/service/plugins/sqlite/Utils.h",
line=line@entry=54) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.4.2/src/corelib/global/qglobal.cpp:3284
#13 0x7f3a26d2b80e in Utils::exec (eh=, query=...,
database=...) at
/mnt/Dati/Git/KDE/kactivitymanagerd/src/service/plugins/sqlite/Utils.h:54
#14 0x7f3a26d355d2 in Utils::exec (database=...,
value=..., variable=..., query=..., eh=Utils::FailOnError) at
/mnt/Dati/Git/KDE/kactivitymanagerd/src/service/plugins/sqlite/Utils.h:69
#15 StatsPlugin::insertResourceInfo (this=this@entry=0x561a80cec220, uri=...)
at
/mnt/Dati/Git/KDE/kactivitymanagerd/src/service/plugins/sqlite/StatsPlugin.cpp:239
#16 0x7f3a26d359df in StatsPlugin::saveResourceMimetype
(this=0x561a80cec220, uri=..., mimetype=..., autoMimetype=) at
/mnt/Dati/Git/KDE/kactivitymanagerd/src/service/plugins/sqlite/StatsPlugin.cpp:271
#17 0x7f3a3a16bd00 in QObject::event (this=0x561a80cec220,
e=0x561a80d00410) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.4.2/src/corelib/kernel/qobject.cpp:1378
#18 0x7f3a3b1759bc in QApplicationPrivate::notify_helper (this=, receiver=0x561a80cec220, e=0x561a80d00410) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.4.2/src/widgets/kernel/qapplication.cpp:3315
#19 0x7f3a3a12a258 in QCoreApplication::notifyInternal2
(receiver=0x561a80cec220, event=0x561a80d00410) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.4.2/src/corelib/kernel/qcoreapplication.cpp:1026
#20 0x7f3a3a12a42b in QCoreApplicationPrivate::sendPostedEvents
(receiver=0x0, event_type=0, data=0x561a80bb63a0) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.4.2/src/corelib/kernel/qcoreapplication.cpp:1804
#21 0x7f3a3a34f348 in postEventSourceDispatch (s=0x561a80bb7820) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.4.2/src/corelib/kernel/qeventdispatcher_glib.cpp:243
#22 0x7f3a3984782b in g_main_dispatch (context=0x7f3a30005040) at
../glib/glib/gmain.c:3454
#23 g_main_context_dispatch (context=0x7f3a30005040) at
../glib/glib/gmain.c:4172
#24 0x7f3a3989ecc9 in g_main_context_iterate.constprop.0
(context=0x7f3a30005040, block=1, dispatch=1, self=) at
../glib/glib/gmain.c:4248
#25 0x7f3a398460e2 in g_main_context_iteration (context=0x7f3a30005040,
may_block=1) at ../glib/glib/gmain.c:4313
#26 0x7f3a3a34d382 in QEventDispatcherGlib::processEvents
(this=0x561a80c111c0, flags=...) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.4.2/src/corelib/kernel/qeventdispatcher_glib.cpp:393
#27 0x7f3a3a135604 in QEventLoop::exec (this=0x7fff18534630, flags=...) at
[dolphin] [Bug 465357] Dolphin's UI freezes when stat() is slow
https://bugs.kde.org/show_bug.cgi?id=465357 Dāvis changed: What|Removed |Added CC||davis...@gmail.com --- Comment #7 from Dāvis --- (In reply to Andrew Gunnerson from comment #5) [...] > Since the UI is freezing despite the slow stat calls being on another > thread, I'm assuming there's a StatJob::exec()/KJob::exec() call somewhere > forcing the UI to wait for its completion. Unfortunately, I've had no luck > at all tracking down where the job came from. There are bunch of places that does IO. Eg. see https://invent.kde.org/system/dolphin/-/blob/master/src/kitemviews/kfileitemmodelrolesupdater.cpp#L1283 (`isDir()`) and https://invent.kde.org/system/dolphin/-/blob/master/src/kitemviews/kfileitemmodelrolesupdater.cpp#L837 (specifically `KFileMetaData::UserMetaData` there inside `KBalooRolesProvider::roleValues`) Things that are related to `KBalooRolesProvider` and `KFileMetaData` I'll be fixing with my multi-threaded implementation. Basically moving whole `KBalooRolesProvider` to a threadpool. Another refactoring I'm doing is that I'm removing it from Dolphin because we actually have 2 different implementations for this thing... -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 465357] Dolphin's UI freezes when stat() is slow
https://bugs.kde.org/show_bug.cgi?id=465357 --- Comment #6 from Dāvis --- By the way it's not even that unusual use case. I have both NFS and Samba mounts in `/etc/fstab` aswell. Several reasons :P And I have been doing this for like 10 years or so :D And KDE/Dolphin issue is not really about that but that it does IO in the main thread which should never be done there. Even if you try KDE on slow HDD you can see it clearly how laggy and slow everything is. The correct way to handle this would be to move all IO to different thread and make everything async. But that would be pretty significant change and I actually have been working on solving some parts of this. I hope to submit my patches in coming months. Specifically I'm implementing multi-threaded file metadata loading and some refactorings regarding that. Also this will require changes across few framework libraries. Basically I have 24-core CPU with 32 GB RAM so KDE/Dolphin should take full advantage of that. Currently for some things we're basically limited to 1 thread on Dolphin. If you take look at this publication https://www.researchgate.net/figure/NVMe-SSD-multithread-reading-throughput-for-4-kilobytes-blocks-and-up-to-256-threads_fig28_349520331 you can see that even on fast NVME drives if you add more threads you get more performance. For Dolphin this doesn't really matter since it's not really doing any serious IO work but it shows why using more than 1 thread can be worth it. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 464023] Stuck in KToolBarPrivate::init
https://bugs.kde.org/show_bug.cgi?id=464023 Dāvis changed: What|Removed |Added Summary|Deadlock in |Stuck in |KToolBarPrivate::init |KToolBarPrivate::init -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 464023] New: Deadlock in KToolBarPrivate::init
https://bugs.kde.org/show_bug.cgi?id=464023 Bug ID: 464023 Summary: Deadlock in KToolBarPrivate::init Classification: Frameworks and Libraries Product: frameworks-kxmlgui Version: 5.101.0 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: davis...@gmail.com Target Milestone: --- SUMMARY Got this weird deadlock for Konsole ``` Thread 7 (Thread 0x7fbfa5bfe6c0 (LWP 1889) "konsole:shlo0"): #0 0x7fbfb4e9c4b6 in ?? () from /usr/lib/libc.so.6 #1 0x7fbfb4e9ecd0 in pthread_cond_wait () from /usr/lib/libc.so.6 #2 0x7fbfa650c50e in ?? () from /usr/lib/dri/radeonsi_dri.so #3 0x7fbfa64bc89c in ?? () from /usr/lib/dri/radeonsi_dri.so #4 0x7fbfa650c43c in ?? () from /usr/lib/dri/radeonsi_dri.so #5 0x7fbfb4e9f8fd in ?? () from /usr/lib/libc.so.6 #6 0x7fbfb4f21a60 in ?? () from /usr/lib/libc.so.6 Thread 6 (Thread 0x7fbfa63ff6c0 (LWP 1888) "konsole:sh0"): #0 0x7fbfb4e9c4b6 in ?? () from /usr/lib/libc.so.6 #1 0x7fbfb4e9ecd0 in pthread_cond_wait () from /usr/lib/libc.so.6 #2 0x7fbfa650c50e in ?? () from /usr/lib/dri/radeonsi_dri.so #3 0x7fbfa64bc89c in ?? () from /usr/lib/dri/radeonsi_dri.so #4 0x7fbfa650c43c in ?? () from /usr/lib/dri/radeonsi_dri.so #5 0x7fbfb4e9f8fd in ?? () from /usr/lib/libc.so.6 #6 0x7fbfb4f21a60 in ?? () from /usr/lib/libc.so.6 Thread 5 (Thread 0x7fbfacaaa6c0 (LWP 1887) "konsole:disk$0"): #0 0x7fbfb4e9c4b6 in ?? () from /usr/lib/libc.so.6 #1 0x7fbfb4e9ecd0 in pthread_cond_wait () from /usr/lib/libc.so.6 #2 0x7fbfa650c50e in ?? () from /usr/lib/dri/radeonsi_dri.so #3 0x7fbfa64bc89c in ?? () from /usr/lib/dri/radeonsi_dri.so #4 0x7fbfa650c43c in ?? () from /usr/lib/dri/radeonsi_dri.so #5 0x7fbfb4e9f8fd in ?? () from /usr/lib/libc.so.6 #6 0x7fbfb4f21a60 in ?? () from /usr/lib/libc.so.6 Thread 4 (Thread 0x7fbfad3ec6c0 (LWP 1886) "konsole:cs0"): #0 0x7fbfb4e9c4b6 in ?? () from /usr/lib/libc.so.6 #1 0x7fbfb4e9ecd0 in pthread_cond_wait () from /usr/lib/libc.so.6 #2 0x7fbfa650c50e in ?? () from /usr/lib/dri/radeonsi_dri.so #3 0x7fbfa64bc89c in ?? () from /usr/lib/dri/radeonsi_dri.so #4 0x7fbfa650c43c in ?? () from /usr/lib/dri/radeonsi_dri.so #5 0x7fbfb4e9f8fd in ?? () from /usr/lib/libc.so.6 #6 0x7fbfb4f21a60 in ?? () from /usr/lib/libc.so.6 Thread 3 (Thread 0x7fbfae3976c0 (LWP 1885) "QXcbEventQueue"): #0 0x7fbfb4f140bf in poll () from /usr/lib/libc.so.6 #1 0x7fbfb32ed26b in ?? () from /usr/lib/libxcb.so.1 #2 0x7fbfb32eed1d in xcb_wait_for_event () from /usr/lib/libxcb.so.1 #3 0x7fbfaf1f5232 in ?? () from /usr/lib/libQt5XcbQpa.so.5 #4 0x7fbfb54e431a in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7fbfb4e9f8fd in ?? () from /usr/lib/libc.so.6 #6 0x7fbfb4f21a60 in ?? () from /usr/lib/libc.so.6 Thread 2 (Thread 0x7fbfaeb986c0 (LWP 1884) "QDBusConnection"): #0 0x7fbfb44cf6ec in ?? () from /usr/lib/libQt5DBus.so.5 #1 0x7fbfb1109c49 in ?? () from /usr/lib/libdbus-1.so.3 #2 0x7fbfb44d9bbd in ?? () from /usr/lib/libQt5DBus.so.5 #3 0x7fbfb56b0b76 in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5 #4 0x7fbfb568cf7c in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #5 0x7fbfb56d74d3 in QTimerInfoList::activateTimers() () from /usr/lib/libQt5Core.so.5 #6 0x7fbfb56d7b12 in ?? () from /usr/lib/libQt5Core.so.5 #7 0x7fbfb35df87b in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #8 0x7fbfb3636c89 in ?? () from /usr/lib/libglib-2.0.so.0 #9 0x7fbfb35de132 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #10 0x7fbfb56d7c8c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #11 0x7fbfb568574c in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #12 0x7fbfb54e724f in QThread::exec() () from /usr/lib/libQt5Core.so.5 #13 0x7fbfb44dbcba in ?? () from /usr/lib/libQt5DBus.so.5 #14 0x7fbfb54e431a in ?? () from /usr/lib/libQt5Core.so.5 #15 0x7fbfb4e9f8fd in ?? () from /usr/lib/libc.so.6 #16 0x7fbfb4f21a60 in ?? () from /usr/lib/libc.so.6 Thread 1 (Thread 0x7fbfaf824ac0 (LWP 1882) "konsole"): #0 0x7fbfb4f197fd in syscall () from /usr/lib/libc.so.6 #1 0x7fbfb54e057c in QSemaphore::acquire(int) () from /usr/lib/libQt5Core.so.5 #2 0x7fbfb56bdb94 in ?? () from /usr/lib/libQt5Core.so.5 #3 0x7fbfb44dceba in ?? () from /usr/lib/libQt5DBus.so.5 #4 0x7fbfb44d5250 in QDBusConnection::connect(QString const&, QString const&, QString const&, QString const&, QStringList const&, QString const&, QObject*, char const*) () from /usr/lib/libQt5DBus.so.5 #5 0x7fbfb44d535e in QDBusConnection::connect(QString const&, QString const&, QString const&,
[dolphin] [Bug 461574] Dolphin crashes if you seek a video multiple time on information panel
https://bugs.kde.org/show_bug.cgi?id=461574 Dāvis changed: What|Removed |Added CC||davis...@gmail.com --- Comment #1 from Dāvis --- Crash is inside `__strcmp_avx2`. Most likely your CPU doesn't support AVX instructions and seems KDE Neon is compiled assuming you have newer CPU -- 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/
[konsole] [Bug 454122] neofetch and right mouse button menu at the same time will cause a crash
https://bugs.kde.org/show_bug.cgi?id=454122 Dāvis changed: What|Removed |Added CC||davis...@gmail.com --- Comment #13 from Dāvis --- This is awesome! I had this same crash happen so often (not related to neofetch) and was really annoying me. ``` #5 0x7fd9fa75f104 in Konsole::ProcessInfo::isValid() const () from /usr/lib/libkonsoleprivate.so.1 #6 0x7fd9fa7f0da8 in Konsole::Session::getUrl() () from /usr/lib/libkonsoleprivate.so.1 #7 0x7fd9fa7f2e0f in Konsole::SessionController::url() const () from /usr/lib/libkonsoleprivate.so.1 #8 0x7fd9fa807191 in Konsole::SessionController::showDisplayContextMenu(QPoint const&) () from /usr/lib/libkonsoleprivate.so.1 #9 0x7fd9f9385381 in ?? () from /usr/lib/libQt5Core.so.5 #10 0x7fd9fa74f08a in Konsole::TerminalDisplay::configureRequest(QPoint const&) () from /usr/lib/libkonsoleprivate.so.1 #11 0x7fd9fa7c8c93 in Konsole::TerminalDisplay::mousePressEvent(QMouseEvent*) () from /usr/lib/libkonsoleprivate.so.1 #12 0x7fd9f9f1945b in QWidget::event(QEvent*) () from /usr/lib/libQt5Widgets.so.5 #13 0x7fd9f9ee2b1c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #14 0x7fd9f9ee8339 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #15 0x7fd9f9354b88 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #16 0x7fd9f9ee6337 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&,bool, bool) () from /usr/lib/libQt5Widgets.so.5 #17 0x7fd9f9f373b5 in ?? () from /usr/lib/libQt5Widgets.so.5 #18 0x7fd9f9f3915e in ?? () from /usr/lib/libQt5Widgets.so.5 #19 0x7fd9f9ee2b1c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #20 0x7fd9f9354b88 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #21 0x7fd9f984213c in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /usr/lib/libQt5Gui.so.5 #22 0x7fd9f982b985 in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /usr/lib/libQt5Gui.so.5 #23 0x7fd9f260b5f0 in ?? () from /usr/lib/libQt5XcbQpa.so.5 #24 0x7fd9f6ee581b in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #25 0x7fd9f6f3bec9 in ?? () from /usr/lib/libglib-2.0.so.0 #26 0x7fd9f6ee40d2 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #27 0x7fd9f939f50c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #28 0x7fd9f934d32c in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #29 0x7fd9f9357e59 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5 #30 0x55d8d537ab65 in ?? () #31 0x7fd9f8ccb290 in ?? () from /usr/lib/libc.so.6 #32 0x7fd9f8ccb34a in __libc_start_main () from /usr/lib/libc.so.6 #33 0x55d8d537b425 in ?? () ``` And now I wanted to look into it why it happens but turns out it's already fixed so I wasn't able to reproduce it anymore on latest git master :) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional
https://bugs.kde.org/show_bug.cgi?id=389191 --- Comment #37 from Dāvis --- (In reply to Nate Graham from comment #36) > (In reply to Dāvis from comment #35) > > Why this bug report is closed? It's still broken... > Please see > https://community.kde.org/Get_Involved/ > Issue_Reporting#Understand_what_the_resolution_statuses_mean > There's actually nothing written about "CLOSED UPSTREAM" state :P and also I would say it's bad idea to close issue if it's not resolved so it can be easier findable as people might think it doesn't apply to them and open new issues. Also I would say upstream needs to see how many people are impacted so everyone should be pointed there. > > If this is XWayland bug, then where's the link to upstream bug report? > In the URL field. That's a MR for potential fix, not bug report itself but sure. Also this affects many applications, here's issue for mpv https://github.com/mpv-player/mpv/issues/9443 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional
https://bugs.kde.org/show_bug.cgi?id=389191 Dāvis changed: What|Removed |Added CC||davis...@gmail.com Version|5.11.95 |git master --- Comment #35 from Dāvis --- Why this bug report is closed? It's still broken... If this is XWayland bug, then where's the link to upstream bug report? I've noticed that setting Wayland scaling breaks badly some games running under XWayland with Wine. I want to keep Wayland scaling (seems to be working fine at 150% for Wayland apps I use) but disable any scaling for XWayland because most apps work way better on X11 without any scaling than this broken scaling. This particular issue I just encountered isn't related to blurriness but window shaking/resizing and wrong resolution. It's hard to describe in words so watch this video demonstration https://youtu.be/AS9H8QrV5Ig Basically I've native Wayland resolution of 3440x1440 with 150% scaling and that causes XWayland to report incorrect resolution of 2288x960 which a lot of applications can't handle as they're used to standard resolutions so I think it would be very useful if we could force "regular" resolution to X11 clients. Also are there any workarounds for this other than disabling scaling altogether? by the way I'm using latest KWin git master and $ Xwayland -version The X.Org Foundation Xwayland Version 22.1.1 (12201001) X Protocol Version 11, Revision 0 $ wayland-info interface: 'wl_compositor', version: 4, name: 1 interface: 'zwp_tablet_manager_v2', version: 1, name: 2 interface: 'zwp_keyboard_shortcuts_inhibit_manager_v1', version: 1, name: 3 interface: 'xdg_wm_base',version: 4, name: 5 interface: 'zwlr_layer_shell_v1',version: 3, name: 6 interface: 'zxdg_decoration_manager_v1', version: 1, name: 7 interface: 'wp_viewporter', version: 1, name: 8 interface: 'wl_shm', version: 1, name: 9 formats: 'XB48'(0x38344258) 'AB48'(0x38344241) 'XB30'(0x30334258) 'AB30'(0x30334241) 'XR30'(0x30335258) 'AR30'(0x30335241) XRGB ARGB interface: 'wl_seat',version: 7, name: 10 name: capabilities: pointer keyboard touch keyboard repeat rate: 25 keyboard repeat delay: 660 interface: 'zwp_pointer_gestures_v1',version: 3, name: 11 interface: 'zwp_pointer_constraints_v1', version: 1, name: 12 interface: 'zwp_relative_pointer_manager_v1',version: 1, name: 13 interface: 'wl_data_device_manager', version: 3, name: 14 interface: 'zwlr_data_control_manager_v1', version: 2, name: 15 interface: 'zwp_primary_selection_device_manager_v1',version: 1, name: 16 interface: 'org_kde_kwin_idle', version: 1, name: 17 interface: 'zwp_idle_inhibit_manager_v1',version: 1, name: 18 interface: 'org_kde_plasma_shell', version: 6, name: 19 interface: 'org_kde_kwin_appmenu_manager', version: 1, name: 20 interface: 'org_kde_kwin_server_decoration_palette_manager', version: 1, name: 21 interface: 'org_kde_plasma_virtual_desktop_management', version: 2, name: 23 interface: 'org_kde_kwin_shadow_manager',version: 2, name: 25 interface: 'org_kde_kwin_dpms_manager', version: 1, name: 26 interface: 'org_kde_kwin_server_decoration_manager', version: 1, name: 27 interface: 'kde_output_management_v2', version: 2, name: 28 interface: 'kde_primary_output_v1', version: 1, name: 29 interface: 'zxdg_output_manager_v1', version: 3, name: 30 xdg_output_v1 output: 43 name: 'DP-1' description: 'Acer Technologies X34 GS/277881511' logical_x: 0, logical_y: 0 logical_width: 2293, logical_height: 960 interface: 'wl_subcompositor', version: 1, name: 31 interface: 'zxdg_exporter_v2', version: 1, name: 32 interface: 'zxdg_importer_v2', version: 1, name: 33 interface: 'xdg_activation_v1', version: 1, name: 36 interface: 'wp_drm_lease_device_v1', version: 1, name: 37 interface: 'wl_drm', version: 2, name: 40 interface: 'zwp_linux_dmabuf_v1',version: 4, name: 41 ... interface: 'kde_output_device_v2', version: 2, name: 42 interface: 'wl_output', version: 3, name: 43 x: 0, y: 0
[telepathy] [Bug 452011] krunner blocks UI when loading Telepathy contacts runner
https://bugs.kde.org/show_bug.cgi?id=452011 --- Comment #6 from Dāvis --- Okay, for now I just uninstalled telepathy runner. But it's very unfortunate issue because it might not be obvious at all why krunner freezes things and there could be other slow runners aswell. Many people can have them installed without realizing they would cause such issues. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 452011] krunner blocks UI
https://bugs.kde.org/show_bug.cgi?id=452011 --- Comment #2 from Dāvis --- (In reply to Nate Graham from comment #1) > This seems to be the culprit: > > #5 0x7fd4714fd9ac in QDBusInterface::QDBusInterface(QString const&, > QString const&, QString const&, QDBusConnection const&, QObject*) () at > /usr/lib/libQt5DBus.so.5 > #6 0x7fd35804e975 in KTp::GlobalPresence::GlobalPresence(QObject*) () > at /usr/lib/libKTpCommonInternals.so.9 > #7 0x7fd3ec84ddf0 in () at > /usr/lib/qt/plugins/kf5/krunner/krunner_ktp_contacts.so > #8 0x7fd3ec84f6c0 in () at > /usr/lib/qt/plugins/kf5/krunner/krunner_ktp_contacts.so > > Do you have KDE's telepathy software installed? Yeah, but I don't really use it. >From backtrace can see that KTP runner waits on QBus which obviously causes this slowdown, but that's just one potential culprit. I would say the real issue is that it blocks UI while loading runners at https://invent.kde.org/frameworks/krunner/-/blob/master/src/runnermanager.cpp#L968 which very likely is slow. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-krunner] [Bug 452011] krunner blocks UI
https://bugs.kde.org/show_bug.cgi?id=452011 Dāvis changed: What|Removed |Added CC||davis...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-krunner] [Bug 452011] New: krunner blocks UI
https://bugs.kde.org/show_bug.cgi?id=452011 Bug ID: 452011 Summary: krunner blocks UI Product: frameworks-krunner Version: 5.92.0 Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: alexander.loh...@gmx.de Reporter: davis...@gmail.com Target Milestone: --- SUMMARY krunner blocks UI which can be very annoying STEPS TO REPRODUCE Not exactly sure, but have something slow that krunner is trying to use and then first time you try to use krunner it will block whole UI for a while. Note that this is reproducible for both Plasma Desktop left side panel and top Alt+Space runner OBSERVED RESULT First time trying to search in krunner it will block whole UI. In case of plasmashell it blocks whole desktop/panels won't be responsive until it finishes. For me that can be like 10+ seconds. EXPECTED RESULT Don't block UI, show loading spinner and show results as soon as they come SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.24.3 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION It can be seen in this plasmashell backtrace ``` #0 0x7fd47046b15a in __futex_abstimed_wait_common () at /usr/lib/libc.so.6 #1 0x7fd47046d960 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libc.so.6 #2 0x7fd4708fccfc in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #3 0x7fd471527db9 in () at /usr/lib/libQt5DBus.so.5 #4 0x7fd4714f8b38 in () at /usr/lib/libQt5DBus.so.5 #5 0x7fd4714fd9ac in QDBusInterface::QDBusInterface(QString const&, QString const&, QString const&, QDBusConnection const&, QObject*) () at /usr/lib/libQt5DBus.so.5 #6 0x7fd35804e975 in KTp::GlobalPresence::GlobalPresence(QObject*) () at /usr/lib/libKTpCommonInternals.so.9 #7 0x7fd3ec84ddf0 in () at /usr/lib/qt/plugins/kf5/krunner/krunner_ktp_contacts.so #8 0x7fd3ec84f6c0 in () at /usr/lib/qt/plugins/kf5/krunner/krunner_ktp_contacts.so #9 0x7fd471413d95 in KPluginFactory::create(char const*, QWidget*, QObject*, QList const&, QString const&) (this=this@entry=0x55763a5b1bb0, iface=0x7fd3b4158990 "Plasma::AbstractRunner", parentWidget=parentWidget@entry=0x0, parent=parent@entry=0x7fd3484a75a0, args=..., keyword=...) at kcoreaddons/src/lib/plugin/kpluginfactory.cpp:232 #10 0x7fd3b41516e5 in KPluginFactory::create(QObject*, QList const&) (args=..., parent=0x7fd3484a75a0, this=0x55763a5b1bb0) at /usr/include/KF5/KCoreAddons/kpluginfactory.h:922 #11 KPluginFactory::instantiatePlugin(KPluginMetaData const&, QObject*, QList const&) (data=..., parent=0x7fd3484a75a0, args=...) at /usr/include/KF5/KCoreAddons/kpluginfactory.h:509 #12 0x7fd3b41526e7 in Plasma::RunnerManagerPrivate::loadInstalledRunner(KPluginMetaData const&) (this=this@entry=0x7fd45c016d80, pluginMetaData=...) at krunner/src/runnermanager.cpp:302 #13 0x7fd3b415474f in Plasma::RunnerManagerPrivate::loadRunners(QString const&) (this=0x7fd45c016d80, singleRunnerId=...) at krunner/src/runnermanager.cpp:210 #14 0x7fd3b414ea04 in Plasma::RunnerManager::launchQuery(QString const&, QString const&) (this=0x7fd3484a75a0, untrimmedTerm=, runnerName=...) at krunner/src/runnermanager.cpp:968 #15 0x7fd3b414ea9a in Plasma::RunnerManager::launchQuery(QString const&) (this=, term=) at krunner/src/runnermanager.cpp:942 #16 0x7fd470ace463 in () at /usr/lib/libQt5Core.so.5 #17 0x7fd470ad069f in QTimer::timeout(QTimer::QPrivateSignal) () at /usr/lib/libQt5Core.so.5 #18 0x7fd470ac1766 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #19 0x7fd47173d1c6 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #20 0x7fd470a9d5aa in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #21 0x7fd470ae8dd5 in QTimerInfoList::activateTimers() () at /usr/lib/libQt5Core.so.5 #22 0x7fd470ae93ba in () at /usr/lib/libQt5Core.so.5 #23 0x7fd46edf9163 in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #24 0x7fd46ee4f9e9 in () at /usr/lib/libglib-2.0.so.0 #25 0x7fd46edf66c5 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #26 0x7fd470ae957a in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #27 0x7fd470a9588b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #28 0x7fd470aa0fd7 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #29 0x557635d8e3f2 in main(int, char**) (argc=, argv=) at plasma-workspace/shell/main.cpp:243 ``` -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 386379] Dolphin scrolls faster in icon mode than other Qt/KDE software
https://bugs.kde.org/show_bug.cgi?id=386379 --- Comment #52 from Dāvis --- (In reply to Nate Graham from comment #51) > We just implemented the standard line-of-text-based scroll behavior for > Dolphin, making it consistent with everything else. The fact that scrolling > long distances with a mouse wheel is a pain in the neck is well known, and > it's why hardware makers have made mice with free-spinning wheels and Apple > implemented accelerating scrolling when turning a mouse wheel quickly. > > In other words, this problem is not specific to Dolphin and needs to be > fixed at a lower level. Personally I favor adding a scroll speed setting to > Libinput and implementing acceleration for very fast wheel movements. > > Those requests would need to be made in the Libinput project of course. If you would have read some earlier comments from here, you would find https://bugreports.qt.io/browse/QTBUG-73467 and https://gitlab.freedesktop.org/libinput/libinput/issues/185 where libinput is against implementing it and suggests it should be done in toolkits. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 414404] Sometimes akonadi_pop3_resource and akonadi_imap_resource crashes on exit
https://bugs.kde.org/show_bug.cgi?id=414404 Dāvis changed: What|Removed |Added CC||davis...@gmail.com Platform|Other |Archlinux Packages -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 414404] New: Sometimes akonadi_pop3_resource and akonadi_imap_resource crashes on exit
https://bugs.kde.org/show_bug.cgi?id=414404 Bug ID: 414404 Summary: Sometimes akonadi_pop3_resource and akonadi_imap_resource crashes on exit Product: Akonadi Version: 5.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: IMAP resource Assignee: kdepim-b...@kde.org Reporter: davis...@gmail.com Target Milestone: --- Did `akonadictl stop` which was followed by: org.kde.pim.akonadicontrol: ProcessControl: Application "/usr/bin/akonadi_imap_resource" stopped unexpectedly ( "Process crashed" ) org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_imap_resource' crashed. No restart! SOFTWARE/OS VERSIONS Arch Linux KDE Plasma Version: 5.17.3 KDE Frameworks Version: 5.64.0 Qt Version: 5.13.2 ADDITIONAL INFORMATION akonadi_imap_resource backtrace ``` #0 0x7f88d4a21569 in QSettings::setValue(QString const&, QVariant const&) () from /usr/lib/libQt5Core.so.5 #1 0x7f88d64bb900 in Akonadi::AgentBase::setOnline(bool) () from /usr/lib/libKF5AkonadiAgentBase.so.5 #2 0x5560435bf845 in ?? () #3 0x7f88d4ac7c20 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQt5Core.so.5 #4 0x55604359f0f7 in ?? () #5 0x5560435f017f in ?? () #6 0x5560435f1185 in ?? () #7 0x7f88d4ac7c20 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQt5Core.so.5 #8 0x7f88d5e6ba4d in KJob::result(KJob*, KJob::QPrivateSignal) () from /usr/lib/libKF5CoreAddons.so.5 #9 0x7f88d5e6c53c in KJob::finishJob(bool) () from /usr/lib/libKF5CoreAddons.so.5 #10 0x7f88d66a7de6 in KIMAP::Job::handleErrorReplies(KIMAP::Response const&) () from /usr/lib/libKF5IMAP.so.5 #11 0x7f88d66c63bc in KIMAP::SessionPrivate::responseReceived(KIMAP::Response const&) () from /usr/lib/libKF5IMAP.so.5 #12 0x7f88d4ac84fa in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5 #13 0x7f88d56124e5 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #14 0x7f88d561be11 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #15 0x7f88d4a9bd12 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #16 0x7f88d4a9ea89 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQt5Core.so.5 #17 0x7f88d4af4514 in ?? () from /usr/lib/libQt5Core.so.5 #18 0x7f88d2aa839e in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #19 0x7f88d2aaa1b1 in ?? () from /usr/lib/libglib-2.0.so.0 #20 0x7f88d2aaa1f1 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #21 0x7f88d4af3b13 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #22 0x7f88d4a9a83c in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #23 0x7f88d4aa2676 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5 #24 0x7f88d64cb0c2 in Akonadi::ResourceBase::init(Akonadi::ResourceBase&) () from /usr/lib/libKF5AkonadiAgentBase.so.5 #25 0x55604358b7a8 in ?? () #26 0x7f88d4467153 in __libc_start_main () from /usr/lib/libc.so.6 #27 0x5560435898ce in ?? () Dump of assembler code for function _ZN9QSettings8setValueERK7QStringRK8QVariant: 0x7f88d4a21560 <+0>: push r13 0x7f88d4a21562 <+2>: push r12 0x7f88d4a21564 <+4>: push rbp 0x7f88d4a21565 <+5>: subrsp,0x30 => 0x7f88d4a21569 <+9>: movrbp,QWORD PTR [rdi+0x8] 0x7f88d4a2156d <+13>:movrax,QWORD PTR fs:0x28 0x7f88d4a21576 <+22>:movQWORD PTR [rsp+0x28],rax 0x7f88d4a2157b <+27>:xoreax,eax 0x7f88d4a2157d <+29>:movrax,QWORD PTR [rsi] 0x7f88d4a21580 <+32>:moveax,DWORD PTR [rax+0x4] 0x7f88d4a21583 <+35>:test eax,eax 0x7f88d4a21585 <+37>:je 0x7f88d48a05fa 0x7f88d4a2158b <+43>:movr12,rsp 0x7f88d4a2158e <+46>:movr13,rdx 0x7f88d4a21591 <+49>:movrdx,rsi 0x7f88d4a21594 <+52>:movrsi,rbp 0x7f88d4a21597 <+55>:movrdi,r12 0x7f88d4a2159a <+58>:call 0x7f88d4a208e0 0x7f88d4a2159f <+63>:movrax,QWORD PTR [rbp+0x0] 0x7f88d4a215a3 <+67>:movrdx,r13 0x7f88d4a215a6 <+70>:movrsi,r12 0x7f88d4a215a9 <+73>:movrdi,rbp 0x7f88d4a215ac <+76>:call QWORD PTR [rax+0x18] 0x7f88d4a215af <+79>:movrdi,rbp 0x7f88d4a215b2 <+82>:call 0x7f88d4a209c0 0x7f88d4a215b7 <+87>:movrdi,r12 0x7f88d4a215ba <+90>:call 0x7f88d48bad70 0x7f88d4a215bf <+95>:movrax,QWORD PTR [rsp+0x28] 0x7f88d4a215c4 <+100>: xorrax,QWORD PTR fs:0x28 0x7f88d4a215cd <+109>: jne0x7f88d4a215d9 0x7f88d4a215cf
[dolphin] [Bug 386379] Dolphin scrolls faster in icon mode than other Qt/KDE software
https://bugs.kde.org/show_bug.cgi?id=386379 --- Comment #43 from Dāvis --- (In reply to Cqoicebordel from comment #42) > (In reply to Dāvis from comment #41) > > That's not possible if you use libinput, see bug #403842 > > Indeed, but is the bug present when using libinput ? > For me, the bug went away when upgrading to Kubuntu 18.10, which uses > libinput by default, I believe. > > So if it's only an evdev bug, that setting would be present ;) It is present even with libinput, you can test it yourself and you'll see that it's still there. In Dolphin set icon view, then zoom in to get biggest icon size possible and then do one tick of scroll wheel and see how much it scrolled. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 386379] Dolphin scrolls faster in icon mode than other Qt/KDE software
https://bugs.kde.org/show_bug.cgi?id=386379 --- Comment #41 from Dāvis --- (In reply to Cqoicebordel from comment #39) > I understood that. > > I was just referencing the comment of Nate Graham > > I think the height of a single line of text might make sense. If that's not > > fast enough by default, we could do two or three. I'll experiment. > > and wanted to point out that doing it hardcoded, by the height of a single > line wasn't needed, as the setting I mentioned gives the users the choice of > number of lines of text to scroll. That's not possible if you use libinput, see bug #403842 (In reply to Nate Graham from comment #36) > I think the height of a single line of text might make sense. If that's not > fast enough by default, we could do two or three. I'll experiment. I don't think that's good approach. I've now been thinking about this and I think scroll speed shouldn't be related to item size at all. For example even in details view where each item is a line of text I want smooth scrolling and don't want to scroll by whole row because I might have 72 font which would make that as a huge jump too. Scrolling should be in device independent pixels (so taking into account DPI) and it should be user controllable setting (https://bugreports.qt.io/browse/QTBUG-73467) Also by the way, Dolphin isn't only application which does it wrong, this issue is also present in File dialog. Relevant API: * https://doc.qt.io/qt-5/qabstractitemview.html#verticalScrollMode-prop * https://doc.qt.io/qt-5/qabstractslider.html#singleStep-prop It looks like if we don't set singleStep then Qt default will be used based on verticalScrollMode. So I think it always should be ScrollPerPixel with a good default scroll speed. Also might consider that it could be based on window's size. For example if I have huge window I can scroll faster because there's so much space so that I'll still see all items but if window's is very small then I might want to scroll a lot slower so items don't move out of window too quickly. -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 402882] Pointing Devices KCM
https://bugs.kde.org/show_bug.cgi?id=402882 --- Comment #8 from Dāvis --- (In reply to Nate Graham from comment #7) > (In reply to Dāvis from comment #6) > > But even that while looks nicer does provide a lot less configuration > > options than was possible with evdev. For example I can't configure mouse > > scrolling speed :( > That's a (legitimate) gripe about Libinput, not our configuration UI for it. Yeah I read about it: https://gitlab.freedesktop.org/libinput/libinput/issues/185 It needs to be implemented in Qt and Plasma needs to have configuration options. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 386379] Dolphin scrolls faster in icon mode than other Qt/KDE software
https://bugs.kde.org/show_bug.cgi?id=386379 --- Comment #33 from Dāvis --- Forgot to mention, using Dolphin 18.12.1 on ArchLinux with libinput KDE Frameworks 5.54.0 Qt 5.12.0 (built against 5.12.0) The xcb windowing system -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 386379] Dolphin scrolls faster in icon mode than other Qt/KDE software
https://bugs.kde.org/show_bug.cgi?id=386379 Dāvis changed: What|Removed |Added CC||davis...@gmail.com --- Comment #32 from Dāvis --- I'm also encountering this issue. I want to scroll half a row, but currently 1 mouse wheel scroll scrolls 2 rows of icons and there's no way to change it. -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 402882] Pointing Devices KCM
https://bugs.kde.org/show_bug.cgi?id=402882 Dāvis changed: What|Removed |Added CC||davis...@gmail.com --- Comment #6 from Dāvis --- I'm really sad about current situation on Plasma regarding mouse configuration while using libinput. This is what current Plasma KCM provides: https://i.imgur.com/EO2GR1N.png And this is how pointing-devices-kcm looks like https://i.imgur.com/9gmxTkq.png But even that while looks nicer does provide a lot less configuration options than was possible with evdev. For example I can't configure mouse scrolling speed :( -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355463] xembedsniproxy always crash when login
https://bugs.kde.org/show_bug.cgi?id=355463 Dāvis <davis...@gmail.com> changed: What|Removed |Added CC||davis...@gmail.com --- Comment #13 from Dāvis <davis...@gmail.com> --- I can confirm that still happens on Arch Linux with latest Plasma compiled from git master. Why patch haven't been submitted and merged? it really looks like it will fix this. I'll test this patch for a week and if I won't have crashes I'll submit it if no one else will have it by then. Crash looks like this xembedsniproxy[2320]: kde.xembedsniproxy: Scaling pixmap of window 16777276 "JavaEmbeddedFrame" from w*h 24 24 xembedsniproxy[2320]: ASSERT: "d" in file /usr/include/QtCore/qscopedpointer.h, line 112 #0 0x7f9730f1c5f8 in raise () from /usr/lib/libc.so.6 #1 0x7f9730f1da7a in abort () from /usr/lib/libc.so.6 #2 0x7f97317b38de in qt_message_fatal (context=..., message=) at /mnt/Qt/qtbase/src/corelib/global/qlogging.cpp:1606 #3 QMessageLogger::fatal (this=this@entry=0x7ffd6cbae290, msg=msg@entry=0x7f9731b85990 "ASSERT: \"%s\" in file %s, line %d") at /mnt/Qt/qtbase/src/corelib/global/qlogging.cpp:780 #4 0x7f97317a6b7b in qt_assert (assertion=assertion@entry=0x4137f3 "d", file=file@entry=0x4138b8 "/usr/include/QtCore/qscopedpointer.h", line=line@entry=112) at /mnt/Qt/qtbase/src/corelib/global/qglobal.cpp:3054 #5 0x004105c1 in QScopedPointer<xcb_get_geometry_reply_t, QScopedPointerDeleter >::operator-> (this=) at /usr/include/QtCore/qscopedpointer.h:112 #6 SNIProxy::getImageNonComposite (this=this@entry=0x91fdd0) at /mnt/KDE/kde/workspace/plasma-workspace/xembed-sni-proxy/sniproxy.cpp:247 #7 0x00410617 in SNIProxy::update (this=0x91fdd0) at /mnt/KDE/kde/workspace/plasma-workspace/xembed-sni-proxy/sniproxy.cpp:196 #8 0x0040d0f1 in FdoSelectionManager::nativeEventFilter (this=0x7ffd6cbaec10, eventType=..., message=, result=) at /mnt/KDE/kde/workspace/plasma-workspace/xembed-sni-proxy/fdoselectionmanager.cpp:140 #9 0x7f9731a79c8f in QAbstractEventDispatcher::filterNativeEvent (this=, eventType=..., message=message@entry=0x7f9720003cb0, result=result@entry=0x7ffd6cbae578) at /mnt/Qt/qtbase/src/corelib/kernel/qabstracteventdispatcher.cpp:460 #10 0x7f9728dc4719 in QXcbConnection::handleXcbEvent (this=this@entry=0x8466a0, event=event@entry=0x7f9720003cb0) at /mnt/Qt/qtbase/src/plugins/platforms/xcb/qxcbconnection.cpp:1065 #11 0x7f9728dc59f9 in QXcbConnection::processXcbEvents (this=0x8466a0) at /mnt/Qt/qtbase/src/plugins/platforms/xcb/qxcbconnection.cpp:1675 #12 0x7f9728e182cb in QXcbConnection::qt_static_metacall (_o=, _c=, _id=, _a=) at .moc/moc_qxcbconnection.cpp:187 #13 0x7f9731ab49bd in QMetaCallEvent::placeMetaCall (this=0x7f9720003c20, object=0x8466a0) at /mnt/Qt/qtbase/src/corelib/kernel/qobject.cpp:495 #14 0x7f9731abb459 in QObject::event (this=0x8466a0, e=) at /mnt/Qt/qtbase/src/corelib/kernel/qobject.cpp:1256 #15 0x7f9728dc6868 in QXcbConnection::event (this=, e=) at /mnt/Qt/qtbase/src/plugins/platforms/xcb/qxcbconnection.cpp:2268 #16 0x7f9731a7de43 in QCoreApplicationPrivate::notify_helper (receiver=receiver@entry=0x8466a0, event=event@entry=0x7f9720003c20) at /mnt/Qt/qtbase/src/corelib/kernel/qcoreapplication.cpp:1112 #17 0x7f9731a7deeb in doNotify (receiver=receiver@entry=0x8466a0, event=0x7f9720003c20) at /mnt/Qt/qtbase/src/corelib/kernel/qcoreapplication.cpp:1053 #18 0x7f9731a7e116 in QCoreApplication::notify (this=this@entry=0x7ffd6cbaebe0, receiver=receiver@entry=0x8466a0, event=) at /mnt/Qt/qtbase/src/corelib/kernel/qcoreapplication.cpp:1039 #19 0x7f973239dbd0 in QGuiApplication::notify (this=0x7ffd6cbaebe0, object=0x8466a0, event=) at /mnt/Qt/qtbase/src/gui/kernel/qguiapplication.cpp:1614 #20 0x7f9731a7e02a in QCoreApplication::notifyInternal2 (receiver=receiver@entry=0x8466a0, event=event@entry=0x7f9720003c20) at /mnt/Qt/qtbase/src/corelib/kernel/qcoreapplication.cpp:978 #21 0x7f9731a807f8 in QCoreApplication::sendEvent (event=0x7f9720003c20, receiver=0x8466a0) at ../../include/QtCore/../../../../../src/corelib/kernel/qcoreapplication.h:227 #22 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x83a690) at /mnt/Qt/qtbase/src/corelib/kernel/qcoreapplication.cpp:1613 #23 0x7f9731a80a60 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at /mnt/Qt/qtbase/src/corelib/kernel/qcoreapplication.cpp:1471 #24 0x7f9731afe27a in postEventSourceDispatch (s=0x8a4fd0) at /mnt/Qt/qtbase/src/corelib/kernel/qeventdispatcher_glib.cpp:270 #25 0x7f972d212dc7 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #26
[plasmashell] [Bug 348812] Crash in __strstr_sse2 after QSGRenderContext::initialize(QOpenGLContext*)
https://bugs.kde.org/show_bug.cgi?id=348812 --- Comment #31 from Dāvis <davis...@gmail.com> --- I submit a patch to Qt https://codereview.qt-project.org/144745 and with this patch it now crashes inside NVIDIA library so it seems to be GPU driver bug but not sure exactly how it's caused. -- You are receiving this mail because: You are watching all bug changes.
