https://bugs.kde.org/show_bug.cgi?id=442321
Duncan <1i5t5.dun...@cox.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |1i5t5.dun...@cox.net
--- Comment #14 from Duncan <1i5t5.dun...@cox.net> ---
(In reply to zellox from comment #13)
> (In reply to Nate Graham from comment #12)
> > 99% sure this is Bug 429168.
> >
> > *** This bug has been marked as a duplicate of bug 429168 ***
>
> What makes you say that?
[as original reporter of the duped bug, hope this answers your question]
While the duped bugs don't seem to be identical (mine won't show running
windows at all, for instance, yours and some other dupes show running windows
normally but the theory seems to be that it's losing track of the running
instances so starts a new one if clicking on a pinned icon), I believe they're
being marked dupe on the theory that the investigation and fix for any of them
will be a sufficiently big change that the others will either be fixed with it,
or at minimum, change the situation sufficiently that closing them all together
and filing new bugs for any remaining buggy behavior would be the most
efficient way forward.
I actually expect these other "works intermittently" bugs (including this one)
to be fixed first, but with any luck that'll fix my bug too, and if not, it's
likely to at least point to a fix for mine. (I'm not a dev but can do the
occasional hack-patch, and as a live-git user, quite often commits fixing other
people's bugs are the pointer I need to allow me to do the hack-patch fixing
mine. Tho in this case it may actually simply point me at the component I seem
to be missing and I can either install it or decide it's not worth the hassle
and that I must continue using alternative solutions.)
--
You are receiving this mail because:
You are watching all bug changes.
