Bug 348836

Summary: characters on lock screen missing after switching user session
Product: [Unmaintained] kscreenlocker Reporter: A. Fachat <afachat>
Component: generalAssignee: David Edmundson <kde>
Status: RESOLVED UPSTREAM    
Severity: minor CC: bshah, mgraesslin, wbauer1
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Kubuntu   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Display of missing characters on lock screen.

Description A. Fachat 2015-06-07 13:57:25 UTC 
When I switch the user session, and return back to the now locked old session, I get a garbled lock screen. It almost looks right - just some of the textual characters are missing. For example of the word "Sonntag" (sunday in German), the characters "onn" and "a" are missing. Also the submit button has no text displayed. What is being left out varies.

This is with the kubuntu KDE 5.3 backport (because 5.2 plasma was crashing all the time, much more than 5.3 still does), and switching user sessions in 5.2 didn't even work at all...

I can provide a screen shot if necessary.

Reproducible: Always

Steps to Reproduce:
1. KDE menu -> leave -> switch user
2. Switch back to original session with e.g. Ctrl-Alt-F7
3. The old session creates a lock screen that is shown

Actual Results:  
The lock screen is missing characters in the middle of some words

Expected Results:  
The lock screen should show correct words with all characters...
Comment 1 A. Fachat 2015-06-07 14:03:20 UTC 
Created attachment 93055 [details]
Display of missing characters on lock screen.
Comment 2 Wolfgang Bauer 2015-07-29 09:34:11 UTC 
The lock screen has nothing to do with kdm.

Reassigning to the correct component.

Although this rather looks like a graphics driver issue to me.
Comment 3 Martin Flöser 2015-12-15 17:20:13 UTC 
unfortunately this is a known issue in Qt in relation with the driver. [1], [2] 

I'm sorry there is not much we can do about it.

[1] https://bugreports.qt.io/browse/QTBUG-42386
[2] https://bugreports.qt.io/browse/QTBUG-36976