Bug 466649 - [Activity Pager] Panel activity switcher text sometimes disappears
Summary: [Activity Pager] Panel activity switcher text sometimes disappears
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: Pager widget (show other bugs)
Version: 5.27.8
Platform: Other Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-03-01 11:19 UTC by Erik Quaeghebeur
Modified: 2024-08-17 12:21 UTC (History)
6 users (show)

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


Attachments
Screenshot showing invisible text in panel activity switcher (9.63 KB, image/png)
2023-03-01 11:19 UTC, Erik Quaeghebeur
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Erik Quaeghebeur 2023-03-01 11:19:50 UTC
Created attachment 156865 [details]
Screenshot showing invisible text in panel activity switcher

SUMMARY
I found myself without activity names in the panel activity switcher (not the one at the side of the screen, but the plasmoid one with a list of activity names one can put in the panel). Namely, all text was gone, while the highlight of the current activity was still there and while one could still click the (invisible) activity names to switch (please see attached screenshot). Removing and readding the plasmoid fixed it for me for now.

The only atypical thing is that before I had used a projector as an additional screen for a while.

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.26.5
KDE Frameworks Version:  5.102.0
Qt Version: 5.15.8
Comment 1 Nate Graham 2023-04-11 20:41:09 UTC
*** This bug has been marked as a duplicate of bug 445828 ***
Comment 2 Erik Quaeghebeur 2023-04-12 04:51:43 UTC
(In reply to Nate Graham from comment #1)
> 
> *** This bug has been marked as a duplicate of bug 445828 ***

I very much doubt this is a duplicate of the linked report. What made you decide it is?
Comment 3 Nate Graham 2023-04-13 16:56:37 UTC
Similar symptoms as Bug 445828. Does the text re-appear when the panel is made taller? If not, then I was wrong and it's something else.
Comment 4 Erik Quaeghebeur 2023-04-13 20:06:00 UTC
(In reply to Nate Graham from comment #3)
> Similar symptoms as Bug 445828. Does the text re-appear when the panel is
> made taller? If not, then I was wrong and it's something else.

I cannot reproduce it myself. It sometimes happens. However, it was not related to panel height changes and the text became invisible, but could still be clicked, which is different from the other report.
Comment 5 Nate Graham 2023-04-14 13:38:58 UTC
Ok, probably a different issue then.
Comment 6 Nate Graham 2023-04-14 13:39:48 UTC
...But you say you can't reproduce it now? Is this after upgrading to a new Plasma version, or is it magically working now with no obvious changes to the system?
Comment 7 Erik Quaeghebeur 2023-04-14 14:22:09 UTC
(In reply to Nate Graham from comment #6)
> ...But you say you can't reproduce it now? Is this after upgrading to a new
> Plasma version, or is it magically working now with no obvious changes to
> the system?
No Plasma update in the meantime. However, my laptop finds itself in so many different setups (two different setups with an extra display, connecting to projectors, etc.) that it is hard to reproduce the situations that may trigger bugs like these.
Comment 8 Nate Graham 2023-04-17 14:25:54 UTC
Ok, thanks. If you do manage to find a way to reproduce it, please don't hesitate to mention it here.
Comment 9 TraceyC 2024-08-09 20:25:41 UTC
(In reply to Erik Quaeghebeur from comment #7)
> No Plasma update in the meantime. However, my laptop finds itself in so many
> different setups (two different setups with an extra display, connecting to
> projectors, etc.) that it is hard to reproduce the situations that may
> trigger bugs like these.

Just following up on this report. Were you ever able to reproduce the problem?
Comment 10 Erik Quaeghebeur 2024-08-17 12:21:53 UTC
(In reply to TraceyC from comment #9)
> Just following up on this report. Were you ever able to reproduce the
> problem?

No. Likely, it was fixed somehow in the meantime. So it now works for me as it should.