Summary: | Lines from Mouse Mark effect are not captured in screenshot | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | saxn <saileshpoudel0> |
Component: | wayland-generic | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | albayenes, antonio.prcela, bachirgiga, kde, nate |
Priority: | NOR | Keywords: | wayland |
Version: | 5.25.4 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | https://invent.kde.org/plasma/kwin/commit/11f7387bad280bd0be50432fb1baf370db5f2a4f | Version Fixed In: | 5.26 |
Sentry Crash Report: |
Description
saxn
2022-08-08 17:40:19 UTC
Can confirm on Wayland. Works on X11 still not there in 5.26 ? Confirmed. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 Kernel Version: 5.18.19-3-MANJARO (64 bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz Memory: 15,5 GiB RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Produces: HP Product Name: HP ProBook 450 G6 A possibly relevant merge request was started @ https://invent.kde.org/plasma/kwin/-/merge_requests/2972 Git commit 14513ebcdaf6f8d790abe1f013a557b15ed4f413 by Vlad Zahorodnii. Committed on 19/09/2022 at 19:10. Pushed by vladz into branch 'master'. effects/mousemark: Specify effect chain position M +5 -0 src/effects/mousemark/mousemark.cpp M +1 -0 src/effects/mousemark/mousemark.h https://invent.kde.org/plasma/kwin/commit/14513ebcdaf6f8d790abe1f013a557b15ed4f413 Git commit 11f7387bad280bd0be50432fb1baf370db5f2a4f by Vlad Zahorodnii. Committed on 19/09/2022 at 19:26. Pushed by vladz into branch 'Plasma/5.26'. effects/mousemark: Specify effect chain position (cherry picked from commit 14513ebcdaf6f8d790abe1f013a557b15ed4f413) M +5 -0 src/effects/mousemark/mousemark.cpp M +1 -0 src/effects/mousemark/mousemark.h https://invent.kde.org/plasma/kwin/commit/11f7387bad280bd0be50432fb1baf370db5f2a4f *** Bug 460139 has been marked as a duplicate of this bug. *** |