https://bugs.kde.org/show_bug.cgi?id=431921
Fabian Vogt <fab...@ritter-vogt.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|WAITINGFORINFO |---
Assignee|kdepim-b...@kde.org |plasma-b...@kde.org
Ever confirmed|0 |1
Product|kmail2 |Breeze
Version|5.15.3 |unspecified
Component|general |QStyle
Status|NEEDSINFO |CONFIRMED
CC| |fab...@ritter-vogt.de,
| |noaha...@gmail.com
--- Comment #9 from Fabian Vogt <fab...@ritter-vogt.de> ---
Inspecting with GammaRay shows that this is the Breeze SplitterProxy. It has
visible=true, which means that it for some reason didn't hide properly.
Using gdb, it shows that _splitter is null, so the underlying handle was
deleted before the SplitterProxy was cleared. clearSplitter() has "if(
!_splitter ) return;", so once it's in that state it never hides itself again.
I'm wondering which handle it is which got deleted, but this should be
relatively simple to fix in any case by also clearing if _splitter is null. It
might need a new variable to track whether the proxy is currently active, but
isVisible() might suffice.
I can make a MR, but to be able to test it I'd have to know what SplitterProxy
is actually for, it's not obvious... The issue is also not easy to reproduce.
--
You are receiving this mail because:
You are watching all bug changes.
