Bug 406732 - Some digits of the clock are invisible on the screenlocker
Summary: Some digits of the clock are invisible on the screenlocker
Status: RESOLVED FIXED
Alias: None
Product: kscreenlocker
Classification: Plasma
Component: greeter (show other bugs)
Version: unspecified
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
: 406890 (view as bug list)
Depends on:
Blocks:
 
Reported: 2019-04-21 14:49 UTC by Pyroman
Modified: 2019-07-15 18:18 UTC (History)
7 users (show)

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

Attachments
Screen video capture (552.68 KB, video/mp4)
2019-04-21 14:49 UTC, Pyroman 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Pyroman 2019-04-21 14:49:18 UTC 
Created attachment 119544 [details]
Screen video capture

See screen captured video in the attachment.

libkscreenlocker5 version: 5.15.4-0xneon+18.04+bionic+build28
Comment 1 David Edmundson 2019-04-21 16:18:58 UTC 
nvidia after resume?
Comment 2 Pyroman 2019-04-21 16:24:59 UTC 
(In reply to David Edmundson from comment #1)
> nvidia after resume?

No, it's Intel builtin video. Suspend and hibernate not used on that machine.
Comment 3 Patrick Silva 2019-04-26 00:31:37 UTC 
*** Bug 406890 has been marked as a duplicate of this bug. ***
Comment 4 Patrick Silva 2019-04-26 11:23:01 UTC 
Requested info was already provided in comment 2.
Comment 5 Guo Yunhe 2019-05-21 09:02:51 UTC 
I am using Intel GPU and I also experienced once this issue after resume. I remember I installed some fonts, maybe that changed the font width.
Comment 6 Nate Graham 2019-07-13 17:35:33 UTC 
Can anyone reproduce this in Plasma 5.16?
Comment 7 Guo Yunhe 2019-07-13 20:30:36 UTC 
For several weeks, I haven't seen this problem in all my machines anymore.

Operating System: openSUSE Tumbleweed 20190708
KDE Plasma Version: 5.16.2
KDE Frameworks Version: 5.59.0
Qt Version: 5.13.0
Kernel Version: 5.1.16-1-default
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz
Memory: 31.2 GiB
Comment 8 Tore Havn 2019-07-13 22:13:07 UTC 
I only ever saw it once, and I have no clue how to reproduce, I'm afraid.

I assume it's okay, but one never knows...

I'm okay with closing this one, and rather open a new one later if the problem reappears.
Comment 9 Nate Graham 2019-07-15 18:00:44 UTC 
Phew!
Comment 10 Pyroman 2019-07-15 18:18:26 UTC 
After upgrading to 5.16 two weeks ago I didn't see this issue yet.