Bug 1397900 - transparent lock screen on multiple/single screens with blank screensaver theme
Summary: transparent lock screen on multiple/single screens with blank screensaver theme
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: mate-screensaver
Version: 27
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Wolfgang Ulbrich
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1398831 1401346 1408531 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-23 14:15 UTC by Jozef Mlich
Modified: 2018-09-02 05:56 UTC (History)
13 users (show)

Fixed In Version: mate-screensaver-1.16.0-2.fc25 mate-screensaver-1.20.1-2.fc27 mate-screensaver-1.20.1-2.fc28
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-09-02 04:49:17 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
test of screensaver (1.48 MB, image/png)
2016-11-23 14:15 UTC, Jozef Mlich
no flags Details
screenshot-locked (1.81 MB, image/png)
2016-11-23 14:16 UTC, Jozef Mlich
no flags Details
screenshot-floating-mate (322.92 KB, image/png)
2016-11-24 08:32 UTC, Jozef Mlich
no flags Details
screenshot-after-wake (446.97 KB, image/jpeg)
2016-12-01 14:31 UTC, Jozef Mlich
no flags Details

Description Jozef Mlich 2016-11-23 14:15:25 UTC
Created attachment 1223262 [details]
test of screensaver

After update to Fedora 25 blank screensaver is not working correctly. After locking (using hotkey ctrl-alt-l) I can see content of window (e.g. terminal, evolution). See screenshots.

I am not sure how to provide additional informations

Comment 1 Jozef Mlich 2016-11-23 14:16:27 UTC
Created attachment 1223263 [details]
screenshot-locked

Comment 2 Wolfgang Ulbrich 2016-11-23 17:40:53 UTC
Ohh, i do not use a second monitor so i never saw that.
What happens if you use another screensaver theme?

Comment 3 Wolfgang Ulbrich 2016-11-23 17:44:48 UTC
Btw. How much monitors are you using, 2 or 3 ?

Comment 4 Jozef Mlich 2016-11-24 08:32:19 UTC
I am using 3 monitors. With 'floating mate' screensaver it is working as expected. The 'blank screen' screensaver is broken. See attached screenshot

Comment 5 Jozef Mlich 2016-11-24 08:32:42 UTC
Created attachment 1223625 [details]
screenshot-floating-mate

Comment 6 Wolfgang Ulbrich 2016-11-26 18:10:30 UTC
*** Bug 1398831 has been marked as a duplicate of this bug. ***

Comment 7 Wolfgang Ulbrich 2016-11-26 18:12:17 UTC
It happens also with one monitor :-/

Comment 8 Jozef Mlich 2016-12-01 14:31:16 UTC
Created attachment 1226836 [details]
screenshot-after-wake

Additionally, it shows white screen after wake up on second and third screen. Currently I am using 'floating mate' screensaver.

Comment 9 Jozef Mlich 2016-12-02 13:38:38 UTC
Here is link to upstream bug tracking:
https://github.com/mate-desktop/mate-screensaver/issues/103

Comment 10 Wolfgang Ulbrich 2016-12-05 06:45:32 UTC
*** Bug 1401346 has been marked as a duplicate of this bug. ***

Comment 11 Chris Halsall 2016-12-12 05:30:49 UTC
To further report on this bug, I can also report that under F25 the "Blank screen" Screensaver doesn't actually blank the screen.  Once the time-out is reached the screens fade down to black, but then bounce back to display the screens.

Four possibly important points:

1. The screens don't just display what was showing when the "Blank screen" screensaver kicks in, but display all updates to the screens.  For example, live updates from "tail -f /var/log/error" shells.

2. Once there is any user input, the one screen which happened to have the mouse pointer within it is covered with the authentication challenge -- the other screens remain exposed and continue to update with whatever was being displayed (this is on a three monitor configuration).

3. After some lengthy time (I don't know exactly how long) all the monitors are actually blanked, and the screensaver behaves as expected -- one monitor displays the challenge while the others remain black.

4. I can also confirm that, for example, the "Floating MATE" screensaver behaves as expected: the screens' contents are hidden.  This issue seems to be solely with the "Blank screen" screensaver".

The reason I chose the "Blank screen" was I didn't want any compute being consumed by the screensaver, and it always worked as expected before this upgrade to F25.

I know this is an upstream bug (as noted by Jozef Mlich above), but I wanted to further document this here.

Regards.

Comment 12 David Mansfield 2016-12-13 14:21:22 UTC
As this is a security vulnerability I would think it should be taken a bit more seriously.  I think a more formal stance should be taken by Fedora / Red Hat  / MATE.

There is an unintended information disclosure issue here that is potentially significant. For example leaving sensitive document open on screen, lock and walk away.

Upstream issue has been open since September, so obviously not a priority for upstream, but Fedora at least needs to make a conscious decision regarding this.

Comment 13 Wolfgang Ulbrich 2016-12-24 19:25:27 UTC
*** Bug 1408531 has been marked as a duplicate of this bug. ***

Comment 14 Wolfgang Ulbrich 2016-12-24 19:35:17 UTC
(In reply to David Mansfield from comment #12)
> As this is a security vulnerability I would think it should be taken a bit
> more seriously.  I think a more formal stance should be taken by Fedora /
> Red Hat  / MATE.
> 
> There is an unintended information disclosure issue here that is potentially
> significant. For example leaving sensitive document open on screen, lock and
> walk away.
> 
> Upstream issue has been open since September, so obviously not a priority
> for upstream, but Fedora at least needs to make a conscious decision
> regarding this.
Maybe you think i am from Redhat :-)
I am not and i maintain Mate alone here in my limited free time.
Sorry, same package works well for f24 (mate gtk3).
There was a change for backgrounds by gtk+ upstream in last gtk3 version (3.22),
but i don't know to adjust mate-screensaver for myself for this change.
So we have to wait for a fix by Mate upstream.
Anyway, other screensaver themes are working which you can use for the moment.

Comment 15 Dennis W. Tokarski 2017-01-09 21:26:41 UTC
Hi, same experience here, but with a twist in the last week or so. Something in the stream of updates has changed the behavior.

The screensaver does not launch no matter which saver is selected. I used to just have an empty ~/Pictures directory and selected "Picture folder" as a way to get the same result as with "Blank screen". But now they all fail in the same way.

Logging in remotely with ssh and watching the process list when locking the screen shows that mate-screensaver does not launch the configured child process.

At this point, if you really really want a locked screensaver screen, you can:
  1) Launch manually from a terminal window, e.g., /usr/libexec/mate-screensaver/slideshow
  2) Hit F11 to maximize the window the screensaver is running in, and
  3) Type Ctrl-Alt-L to actually lock the screen

It gets the job done, but of course it's a nuisance. And you can't just have it happen with a timeout.

Comment 16 Don Swaner 2017-01-09 22:41:30 UTC
No recent change here, on a currently upgraded system.  Cosmos, pictures folder, and floating mate screensavers all work as expected - blank screen screensaver does not work, as described above.

Comment 17 Dennis W. Tokarski 2017-01-10 18:05:35 UTC
(In reply to Don Swaner from comment #16)
> No recent change here, on a currently upgraded system.  Cosmos, pictures
> folder, and floating mate screensavers all work as expected - blank screen
> screensaver does not work, as described above.

Arrrrrggghhh! It's intermittent. Grrrr.

I verified the broken behavior across all screensaver types yesterday not five minutes before posting. They hadn't been working for a week, across multiple updates, reboots, suspend and hibernation cycles.

And then yesterday evening when I saw your post, Don, I tried it again and everything worked as you describe! Well wtf. Nothing had intervened except a few hours in hibernation. After resume my experience matched your description.

And it was working this morning still, too. Then I picked up some updates, after which all screensavers were broken again. So I ran memtest a while, because this was pretty suggestive, but no problems found. I'll run it again overnight tonight.

Anyway, I've just done some suspend/hibernate/resume cycles, power-off-and-reboot, none of which made any difference. Still broken.

Dunno what more to say. I do hope when the devs find the blank-screen problem the fix applies to all the rest of this.

Comment 18 Wolfgang Ulbrich 2017-01-11 15:35:59 UTC
Upstream do not monitor Redhat Bugzilla.
If you want that someone fix it you need to post at
https://github.com/mate-desktop/mate-screensaver/issues/103
Repeating the same here does not help.
Sorry, i am not able to fix it.

Comment 19 Fedora Update System 2017-01-17 21:53:43 UTC
mate-screensaver-1.16.0-2.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2017-ea54cba2e2

Comment 20 Chris Halsall 2017-01-17 22:47:42 UTC
Just to put on the table, I found that all screen-savers stopped working after an update last week.

I'm growing tired of this.  Clearly Fedora doesn't take this issue, and many other issues, seriously.

My next workstation install will be Ubuntu based.

Goodbye.

Comment 21 Fedora Update System 2017-01-19 09:10:35 UTC
mate-screensaver-1.16.0-2.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-ea54cba2e2

Comment 22 Fedora Update System 2017-01-20 18:06:44 UTC
mate-screensaver-1.16.0-2.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.

Comment 23 James Boyle 2018-04-10 19:35:44 UTC
This issue seems to have recurred, except with an additional symptom.  Here is the new issue:

Do the following:
1. Have two display-port attached displays.  Login to MATE.
2. Press ctrl-alt-L or allow the screensaver timeout to lock the screen.

3.a. Bump the mouse or type a key on the keyboard before the displays have either been placed into power save mode or put to sleep:
< MATE presents the password prompt and the user's windows remain hidden until the password has been correctly entered. >

3.b. Bump the mouse or type a key on the keyboard after the displays have been put into power save mode, but before they have been put to sleep: 
< MATE presents the unlock with password prompt, but displays (doesn't hide) the windows of your desktop.  You cannot interact with the applications or windows until the password has been correctly entered, but the content is plainly visible as described by other users in this bug. >

3.c. Bump the mouse to type a key on the keyboard after the displays have been put to sleep:
< MATE blanks one display where the password dialog box would have been, the other is available for interaction WITHOUT having entered in the correct password.  New applications can be launched, all applications may be used with the same privilege level of the user who had previously logged in and foolishly believed that their desktop was locked.  To reiterate, any person may control the logged in user's system WITHOUT entering a password. >

Comment 24 Patrick Hemmer 2018-04-24 03:29:48 UTC
Also experiencing this on a brand new Fedora 27 system. The one difference for me is that it only happens on idle. If I use CTRL+ALT+L it locks fine. However if I leave the system idle, the desktop is completely visible, and only when you press a key or move the mouse does it hide the desktop and pop up the login dialog.

mate-screensaver-1.20.0-1.fc27.x86_64

Comment 25 Jan Kurik 2018-05-31 09:11:27 UTC
This bug is currently reported against a Fedora version which is already unsuported.
I am changing the version to '27', the latest supported release.

Please check whether this bug is still an issue on the '27' release.
If you find this bug not being applicable on this release, please close it.

Comment 26 James Boyle 2018-06-01 18:47:23 UTC
My report in comment #23, https://bugzilla.redhat.com/show_bug.cgi?id=1397900#c23, was a report about symptoms shown on a month old Fedora 27 installation, so I can confirm that this bug exists on Fedora 27.

Comment 27 Fedora Update System 2018-08-25 14:53:12 UTC
mate-screensaver-1.20.1-2.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-ab94a41797

Comment 28 Fedora Update System 2018-08-25 14:53:34 UTC
mate-screensaver-1.20.1-2.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-f4c88b2bb5

Comment 29 Fedora Update System 2018-08-25 19:59:23 UTC
mate-screensaver-1.20.1-2.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-ab94a41797

Comment 30 Fedora Update System 2018-08-25 22:37:50 UTC
mate-screensaver-1.20.1-2.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-f4c88b2bb5

Comment 31 Fedora Update System 2018-09-02 04:49:17 UTC
mate-screensaver-1.20.1-2.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.

Comment 32 Fedora Update System 2018-09-02 05:56:04 UTC
mate-screensaver-1.20.1-2.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.


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