Bug 1376102 - After screen lock (not laptop suspend) the screen is blank with only mouse cursor moving. Can't recover.
Summary: After screen lock (not laptop suspend) the screen is blank with only mouse cu...
Keywords:
Status: CLOSED DUPLICATE of bug 1376364
Alias: None
Product: Fedora
Classification: Fedora
Component: plasma-desktop
Version: 24
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: KDE SIG
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-14 16:49 UTC by Eric M
Modified: 2016-09-16 13:10 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-16 13:10:30 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
output of "rpm -qa --last | tac" (300.84 KB, text/plain)
2016-09-14 16:49 UTC, Eric M
no flags Details

Description Eric M 2016-09-14 16:49:42 UTC
Created attachment 1200913 [details]
output of  "rpm -qa --last | tac"

Description of problem:

Manually choosing screen lock results in the screen going black with only the mouse cursor moving. There is no dialog box for re-entering password to unlock. Either reboot, or have a key sequence to restart X server.

The problem showed up after updates released on 13 September 2016. I assume this may have something to do with plasma, since there were a lot of plasma updates on that day.

Version-Release number of selected component (if applicable):



How reproducible:
Every time.

Steps to Reproduce:
1. Choose "lock screen" from menu.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Eric M 2016-09-15 20:29:21 UTC
I can also function key over to a text terminal and issue "loginctl unlock-sessions" to unlock.

Comment 2 redhat-bugs2eran 2016-09-16 02:37:23 UTC
Same problem here, on Fedora 24, appeared after a dnf update around the same time.

When this happened, I could recover by switching to a textual virtual console (Ctrl-Alt-F2), running "loginctl unlock-sessions" and then switching back (Ctrl-Alt-F1).

The problem went away after deleting the file $HOME/.config/kscreenlockerrc . The old content of that file was as follows:
===
[$Version]
update_info=kscreenlocker.upd:0.1-autolock

[Daemon]
LockGrace=10
Timeout=15

[Greeter]
Theme=org.fedoraproject.fedora.twenty.two
===

With that old kscreenlockerrc, journalctl showed the following error when locking:

kscreenlocker_greet[1234]: No metadata file in the package, expected it at: "/usr/share/plasma/look-and-feel/org.fedoraproject.fedora.twenty.two/"

This Fedora 24 box was upgraded from 22 and then 23.

Comment 3 Rex Dieter 2016-09-16 06:59:35 UTC
I think I see the problem then, yeah, we recently removed support for the old (now EOL) fedora.twenty.two theme

We'll have to handle the case that users may still have references to it.

Comment 4 Rex Dieter 2016-09-16 13:10:30 UTC

*** This bug has been marked as a duplicate of bug 1376364 ***


Note You need to log in before you can comment on or make changes to this bug.