[plasmashell] [Bug 450523] [Plasma][Wayland] Battery applet missing, restarting plasmashell throws segmentation fault
https://bugs.kde.org/show_bug.cgi?id=450523 --- Comment #1 from Mrcuve0 --- I can confirm this continues to happen with Plasma 5.24.1 too: Operating System: openSUSE Tumbleweed 20220218 KDE Plasma Version: 5.24.1 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.8-1-default (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-5200U CPU @ 2.20GHz Memory: 7,7 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 5500 Updates: This morning I started my laptop (cold boot) when battery powered, and again the battery applet was missing from my system tray. Restarting plasmashell from krunner however didn't throw any segmentation fault. Everything restarted successfully and the battery applet finally appeared (and updates correctly). So, the segmentation fault I reported early may bot be necessaritly linked to the battery applet missing. Some additional info: * I enabled "Show battery percentage on Icon"; * I don't have any lower and upper thresholds for battery recharging, as my system does not allow to; -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450523] New: [Plasma][Wayland] Battery applet missing, restarting plasmashell throws segmentation fault
https://bugs.kde.org/show_bug.cgi?id=450523
Bug ID: 450523
Summary: [Plasma][Wayland] Battery applet missing, restarting
plasmashell throws segmentation fault
Product: plasmashell
Version: 5.24.0
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: mrcuve0+...@posteo.net
CC: k...@davidedmundson.co.uk
Target Milestone: 1.0
Application: plasmashell (5.24.0)
Qt Version: 5.15.2
Frameworks Version: 5.90.0
Operating System: Linux 5.16.8-1-default x86_64
Windowing System: Wayland
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.24.0 [KCrashBackend]
-- Information about the crash:
- Unusual behavior I noticed:
The battery applet in the Plasmashell panel (system tray) disappears from time
to time, making it difficult to understand the remaining percentage. The
related entry is set to "always shown", changing it to "Shown when relevant"
does not solve the issue. I still have to find what causes it in order to
reproduce it. I noticed that, in some cases, the applet is missing even after a
cold boot (when powered on battery).
To solve the issue, I restart plasmashell using "plasmashell --replace &". The
panels restart and the battery applet appears, but the attached backtrace is
produced, and KDE Crash handler is invoked.
- Expected behavior:
If set to "Always shown", the battery applet in the system tray shoul always be
present.
If set to "Shown when relevant", it should be visible only when laptop is
battery powered.
The reporter is unsure if this crash is reproducible.
-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 0x7f72267a666a in wl_map_insert_at (data=, i=1761,
flags=1, map=) at ../src/wayland-util.c:249
#7 proxy_destroy (proxy=proxy@entry=0x5645aef2bb70) at
../src/wayland-client.c:503
#8 0x7f72267a7fcb in wl_proxy_destroy_caller_locks (proxy=0x5645aef2bb70)
at ../src/wayland-client.c:523
#9 wl_proxy_marshal_array_flags (proxy=proxy@entry=0x5645aef2bb70,
opcode=opcode@entry=0, interface=interface@entry=0x0, version=version@entry=1,
flags=flags@entry=1, args=args@entry=0x7fff91d468a0) at
../src/wayland-client.c:861
#10 0x7f72267a8abb in wl_proxy_marshal_flags (proxy=0x5645aef2bb70,
opcode=0, interface=0x0, version=1, flags=1) at ../src/wayland-client.c:784
#11 0x7f722685ca5e in wl_buffer_destroy (wl_buffer=0x5645aef2bb70) at
/usr/include/wayland/wayland-client-protocol.h:2017
#12 KWayland::Client::WaylandPointer::release
(this=0x5645ae1b3818) at
/usr/src/debug/kwayland-5.90.0-1.4.x86_64/src/client/wayland_pointer_p.h:44
#13 KWayland::Client::Buffer::Private::~Private (this=,
this=) at
/usr/src/debug/kwayland-5.90.0-1.4.x86_64/src/client/buffer.cpp:38
#14 QScopedPointerDeleter::cleanup
(pointer=0x5645ae1b3810) at /usr/include/qt5/QtCore/qscopedpointer.h:60
#15 QScopedPointerDeleter::cleanup
(pointer=0x5645ae1b3810) at /usr/include/qt5/QtCore/qscopedpointer.h:52
#16 QScopedPointer >::~QScopedPointer
(this=, this=) at
/usr/include/qt5/QtCore/qscopedpointer.h:107
#17 KWayland::Client::Buffer::~Buffer (this=, this=) at /usr/src/debug/kwayland-5.90.0-1.4.x86_64/src/client/buffer.cpp:58
#18 0x7f72268931c2 in
QtSharedPointer::CustomDeleter::execute (this=, this=) at /usr/include/qt5/QtCore/qsharedpointer_impl.h:187
#19
QtSharedPointer::ExternalRefCountWithCustomDeleter::deleter (self=) at
/usr/include/qt5/QtCore/qsharedpointer_impl.h:205
#20 0x7f7226898476 in QtSharedPointer::ExternalRefCountData::destroy
(this=0x5645ae6bf350) at /usr/include/qt5/QtCore/qsharedpointer_impl.h:149
#21 QSharedPointer::deref (dd=0x5645ae6bf350) at
/usr/include/qt5/QtCore/qsharedpointer_impl.h:458
#22 QSharedPointer::deref (dd=0x5645ae6bf350) at
/usr/include/qt5/QtCore/qsharedpointer_impl.h:454
#23 QSharedPointer::deref (this=0x5645af49d270) at
/usr/include/qt5/QtCore/qsharedpointer_impl.h:453
#24 QSharedPointer::~QSharedPointer (this=, this=) at
/usr/include/qt5/QtCore/qsharedpointer_impl.h:310
#25 QList >::node_destruct
(this=, to=0x5645aecb14f8, from=0x5645aecb14f8) at
/usr/include/qt5/QtCore/qlist.h:524
#26 QList >::dealloc(QListData::Data*)
[clone .isra.0] (data=0x5645aecb14e0, this=) at
/usr/include/qt5/QtCore/qlist.h:921
#27 0x7f7226888bd5 in QList
>::~QList (this=, this=) at
/usr/include/qt5/QtCore/qlist.h:871
#28 QList >::~QList (this=, this=) at /usr/include/qt5/QtCore/qlist.h:871
#29 QList >::operator= (other=...,
this=) at /usr/include/qt5/QtCore/qlist.h:167
#30 QList >::clear (this=) at /usr/include/qt5/QtCore/qlist.h:930
#31 KWayland::Client::ShmPool::release (this=this@entry=0x5645ae0c7490) at
/usr/src/debug/kwa
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 --- Comment #44 from Mrcuve0 --- Just to add additional information to my setup, some days ago I wanted to try OC my screens to 75Hz "for the lulz" following https://old.reddit.com/r/linux_gaming/comments/e339il/how_to_overclock_your_monitor_on_wayland/. Hence why you'll find 75Hz in the configs and logs. It probably does not have effects on the bug but, you know, sometimes "very unlikely" configs have an impact on what you are trying to debug and you find it only after hours of wasted time -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 --- Comment #43 from Mrcuve0 --- Created attachment 144960 --> https://bugs.kde.org/attachment.cgi?id=144960=edit Mrcuve0 - kscreen.log (.local/share/kscreen/) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 --- Comment #42 from Mrcuve0 --- Created attachment 144959 --> https://bugs.kde.org/attachment.cgi?id=144959=edit Mrcuve0 - kscreen_terminal.log -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 --- Comment #41 from Mrcuve0 --- I'm adding two different logs: * The first one `kscreen_terminal.log` is the one you asked (I'd like to understand why redirecting with tee or > didn't work with this particular command, anyway I copy pasted the stdout to this file :D). * The second one `kscreen.log` is the one produced by setting the .sh file in plasma-workspace/env like https://community.kde.org/Solid/Projects/ScreenManagement suggests. Hope both help. Anyway, I quickly searched for the string you mentioned and couldn't see it. It is also woth mentioning that both screens (e-DP1, my laptop's builtin, and DP-1 Dell U2419HC, my external one) were set to "automatic" before launching the command. However, DP-1 was clearly showing a "full-RGB" image. I tried to restart and disconnect DP-1 multiple times while having "automatic" in kscreen to force it to a visually "limited" scale but I couldn't. Also closing the laptop lid didn't change anything. It's interesting because some months ago (at least as soon as i got 5.23 on tumbleweed) these operations would have triggered the bug instantly (i.e. DP-1 would clearly show a "limited" image), now I cannot find a way to reproduce it sistematically (but I can guarantee you that I still have to manually launch kscreen just to set to "full" DP-1 from time to time) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 --- Comment #39 from Mrcuve0 --- Created attachment 144937 --> https://bugs.kde.org/attachment.cgi?id=144937=edit Mrcuve0 - kscreen folder -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444819] [Wayland] Plasmashell panel does not correctly display tooltips relying on translucency and blur when hovering from one applet to the other
https://bugs.kde.org/show_bug.cgi?id=444819 --- Comment #6 from Mrcuve0 --- Created attachment 143133 --> https://bugs.kde.org/attachment.cgi?id=143133=edit [System Tray] W/ Aritim-Light third party applets (and "pager" applet) sometime show contrast artifacts Contrast artifacts on third party applets like "Netspeed Widget" and "Advanced Radio Player". The background is way more gray than what it should be. Such artifacts also happens on "Pager" applet, when hovering on particular desktops. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444819] [Wayland] Plasmashell panel does not correctly display tooltips relying on translucency and blur when hovering from one applet to the other
https://bugs.kde.org/show_bug.cgi?id=444819 --- Comment #5 from Mrcuve0 --- Created attachment 143130 --> https://bugs.kde.org/attachment.cgi?id=143130=edit [System Tray] W/ Aritim-Light Plasma Theme, the clock tooltip displays a vertical offset -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444819] [Wayland] Plasmashell panel does not correctly display tooltips relying on translucency and blur when hovering from one applet to the other
https://bugs.kde.org/show_bug.cgi?id=444819 Mrcuve0 changed: What|Removed |Added Attachment #143127|[Aritim-Light][Icons-Only |[Breeze][Icons-Only Task filename|Task Manager]Blur missing |Manager]Blur missing on the |on the right side.png |right side.png Attachment #143127|[Icons-Only Task Manager] |[Icons-Only Task Manager] description|W/ Aritim-Light Plasma |W/ Breeze Plasma Theme, |Theme, blur is not applied |blur is not applied on the |on the rightmost side |rightmost side --- Comment #4 from Mrcuve0 --- Comment on attachment 143127 --> https://bugs.kde.org/attachment.cgi?id=143127 [Icons-Only Task Manager] W/ Breeze Plasma Theme, blur is not applied on the rightmost side EDIT: the screenshot refers to Breeze Plasma Theme, not Aritim-Light -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444819] [Wayland] Plasmashell panel does not correctly display tooltips relying on translucency and blur when hovering from one applet to the other
https://bugs.kde.org/show_bug.cgi?id=444819 Mrcuve0 changed: What|Removed |Added Attachment #143126|[Aritim-Light][KdeConnectAp |[Breeze][KdeConnectApplet]B filename|plet]Blur missing on the|lur missing on the bottom |bottom right corner.png |right corner.png Attachment #143126|W/ Aritim-Light Plasma |W/ Breeze Plasma Theme, description|Theme, blur is not applied |blur is not applied on the |on the rightmost side |rightmost side --- Comment #3 from Mrcuve0 --- Comment on attachment 143126 --> https://bugs.kde.org/attachment.cgi?id=143126 W/ Breeze Plasma Theme, blur is not applied on the rightmost side EDIT: the screenshot refers to Breeze Plasma Theme, not Aritim-Light -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444819] [Wayland] Plasmashell panel does not correctly display tooltips relying on translucency and blur when hovering from one applet to the other
https://bugs.kde.org/show_bug.cgi?id=444819 --- Comment #2 from Mrcuve0 --- Created attachment 143128 --> https://bugs.kde.org/attachment.cgi?id=143128=edit [Icons-Only Task Manager] W/ Aritim-Light Plasma Theme, blur is not applied on the right half of the tooltip -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444819] [Wayland] Plasmashell panel does not correctly display tooltips relying on translucency and blur when hovering from one applet to the other
https://bugs.kde.org/show_bug.cgi?id=444819 --- Comment #1 from Mrcuve0 --- Created attachment 143127 --> https://bugs.kde.org/attachment.cgi?id=143127=edit [Icons-Only Task Manager] W/ Aritim-Light Plasma Theme, blur is not applied on the rightmost side -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444819] New: [Wayland] Plasmashell panel does not correctly display tooltips relying on translucency and blur when hovering from one applet to the other
https://bugs.kde.org/show_bug.cgi?id=444819 Bug ID: 444819 Summary: [Wayland] Plasmashell panel does not correctly display tooltips relying on translucency and blur when hovering from one applet to the other Product: plasmashell Version: 5.23.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: mrcuve0+...@posteo.net Target Milestone: 1.0 Created attachment 143126 --> https://bugs.kde.org/attachment.cgi?id=143126=edit W/ Aritim-Light Plasma Theme, blur is not applied on the rightmost side SUMMARY On Wayland, whenever you move the mouse cursor from one applet to the other hovering over them, the tooltips displayed are not correctly rendered. Artifacts are in fact visible mostly on the right side of the tooltip, where translucency is applied but no blur. This is especially visible on PlasmaThemes heavily relying on transparency and blur, such as Aritim-Light-Rounded-Blur. Nevertheless, the problem is visible, although in a less extent, also with default Breeze Plasma Theme. I'm attaching some screenshots as example. I searched for similar issue but couldn't find anything, a part bug 422072 and clones, which I believe is deeply linked to the issue I'm reporting right now. I'm in fact experiencing that bug as well. I'm no KDE dev but I believe the freeze on 422072 is due to this incomplete rendering, once invoked multiple times hovering over the applets many times, with a culprit on the Digital Clock (and Event Calendar). I believe such artifacts may have been left unnoticed since on default Breeze PlasmaTheme it is quite difficult to notice them (but actually quite easy on Aritim-Light, which is a way less common Plasma Theme) STEPS TO REPRODUCE 1. Place the cursor on Icons-Only Task Manager or System Tray applets, wait until the hovering causes tooltips to be drawn; 2. Move your cursor to hover on different task icon/applets and notice some artifacts, especially on the right side of the tooltip, indicating the tooltip is not correctly rendered; 3. Install Aritim-Light-Rounded-Blur (or any other Plasma Theme relying on transparency and blur more than Breeze) and you should notice the artifacts way better OBSERVED RESULT Tooltips are drawn incorrectly, presenting graphical issue on their right side. EXPECTED RESULT Tooltips should be rendered correctly in their entireness. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20211031 KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.14-1-default (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-5200U CPU @ 2.20GHz Memory: 7,7 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 5500 ADDITIONAL INFORMATION This bug may be related, with way more drastical consequences, to bug 422072. It also may give devs further information and help them finding the cause, which may rely on the (bugged) rendering flow applied to tootltips -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 --- Comment #34 from Mrcuve0 --- I added "export QT_LOGGING_RULES="kwin_*.debug=true" as suggested, removed the log and rebooted to reach a clean state. I recorded 4 different logs for the 4 subsequent actions done: * 00a: shows the initial state of the log, the screen is on Automatic and no preference has been set yet * 00b: the log records the instant when I switch from Automatic to Full, before logout *** LOGOUT *** * 01a: shows the state after logout, the screen is back in Automatic mode * 01b: I switch again from Automatic to Full, the log records this action Points of Interest I noticed using diff: --> Comparison among 00b and 01a (logout happens in between): * Line 7: The properties of Crtc 60 change (why?) * Line 70: The properties of connector 77 change (why?) * Line 71: Connector 85 (crtc 60) goes from Automatic to Full * Line 74 and 75: The two hex addresses changes (IDs?) * Line 421 in 01a sets the RGB range to Automatic --> Comparison among 01a and 01b: * Line 522: the RGB range is set to Full --- I didn't find any "kwin_wayland_drm: Atomic test for (0) failed! Invalid argument" string in these logs, however we can find on line 4: "kwin_wayland_drm: Using Atomic Mode Setting on gpu "/dev/dri/card0" So I guess the error does not produce in my case (?) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 --- Comment #33 from Mrcuve0 --- Created attachment 142673 --> https://bugs.kde.org/attachment.cgi?id=142673=edit After logout, Automatic to Full After logout, I switch again from Automatic to Full, the logs records this action -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 --- Comment #32 from Mrcuve0 --- Created attachment 142672 --> https://bugs.kde.org/attachment.cgi?id=142672=edit After Logout The logs shows the state after logout/login -> the screen is back to Automatic RGB mode -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 --- Comment #31 from Mrcuve0 --- Created attachment 142671 --> https://bugs.kde.org/attachment.cgi?id=142671=edit Before Logout, Atuomatic -> Full The logs records the instant where I change RGB mode from Automatic to Full, before logging out -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442520] Display Configuration KCM fails to apply full RGB range
https://bugs.kde.org/show_bug.cgi?id=442520 --- Comment #30 from Mrcuve0 --- Created attachment 142670 --> https://bugs.kde.org/attachment.cgi?id=142670=edit Before Logout, initial state of the log Before Logout, the screen is already in Automatic RGB mode, initial state of the log -- You are receiving this mail because: You are watching all bug changes.
