Bug 325741 - panel spacer has dark strands after a certain operation
Summary: panel spacer has dark strands after a certain operation
Status: RESOLVED UNMAINTAINED
Alias: None
Product: plasma4
Classification: Unmaintained
Component: panel (other bugs)
Version First Reported In: unspecified
Platform: unspecified Linux
: NOR minor
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-10-07 13:00 UTC by Scott
Modified: 2018-06-08 19:02 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Scott 2013-10-07 13:00:51 UTC
The 'spacer' item that can be added to Panels has dark strands on each
end(of the spacer item itself) after a certain operation.

If someone uses an 'icon-only Task Manager' widget on a panel, and tries to
add a 'Spacer', this 'Spacer' itself is the first one to have dark strands
on itself.

Here's the fun part, add Spacers to other Panels and they will start to have
dark strands too.

If one removes the 'Spacer' from the 'icon-only Task Manager' widget, then
all other Spacers that were created (after the 'icon-only tmanager' spacer)
would no longer as well have dark strands.

The 'spacers' created before adding a spacer to the icon-only task manager
were never affected.

Reproducible: Always




Not obvious to track down that this was the problem.   Solution to work around of course is can be undone without any freezes or crashes.. so it's a minor bug..
(the spacer can be easily removed fromt the icon-only taskmanager widget :)
^ it was accidentally added in the first place lol ;)
Comment 1 Nate Graham 2018-06-08 19:02:56 UTC
Hello!

This bug report was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this bug is already resolved in Plasma 5.

Accordingly, we hope you understand why we must close this bug report. If the issue described  here is still present in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting

If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging

Thanks for your understanding!

Nate Graham