After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 673370 - background-color colored rectangle, sometimes with window contents, overdrawn in primary monitor lock screen
background-color colored rectangle, sometimes with window contents, overdrawn...
Status: RESOLVED OBSOLETE
Product: gnome-screensaver
Classification: Deprecated
Component: general
3.4.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-screensaver maintainers
gnome-screensaver maintainers
Depends on:
Blocks:
 
 
Reported: 2012-04-02 14:57 UTC by Cosimo Cecchi
Modified: 2014-08-20 20:23 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
A little Gtk app which demonstrates the same bug. (482 bytes, text/plain)
2012-10-12 14:01 UTC, Will Thompson
Details

Description Cosimo Cecchi 2012-04-02 14:57:37 UTC
[ for lack of a better summary wording ]

I've seen this happening twice now, so it's worth a bug report

In a dual monitor configuration, when the screen is locked, I sometimes get a rectangle overdrawn over the primary screen; the rectangle has possibly the same color of what's specified in org.gnome.desktop.background primary-color (or a mix between that and the secondary-color), is placed at (0, 0) on the primary monitor and has the same size as the secondary monitor.

When it first happened, I managed to make it go away by changing the aforementioned gsetting, then could not reproduce it anymore. This morning I got it again. Unfortunately there's no error in ~/.xsession-errors when this happens.
Comment 1 Will Thompson 2012-10-12 13:40:06 UTC
I can reproduce this, but worse: it's possible to make window contents show up over the screensaver.

If a window pops up a dialog box (pinned to the window in the standard-ish GNOME 3 style) while the screen is locked, an area of the screen the same size as my laptop monitor appears at the top left of the combined screen area. If the window in question happens to be within that area, its contents are visible over the screensaver.

An easy way to reproduce it is with a web page which calls alert() after a timeout. See http://willthompson.co.uk/misc/screen-lock-bug/ for such a page, and http://willthompson.co.uk/misc/screen-lock-bug/screen-lock-bug.jpg for what I see by following those instructions.

If I undock my laptop, the problem doesn't occur.

I previously had my laptop to the left of the external monitor, and sometimes got a blob of wallpaper or window contents visible on the laptop screen over the screen lock: presumably this is because the top-left was on that screen.

I don't have a machine running Gnome 3.6 on hand, so I don't know if this still occurs there with the new screen-locking mechanism.
Comment 2 Will Thompson 2012-10-12 13:59:30 UTC
(In reply to comment #1)
> If a window pops up a dialog box (pinned to the window in the standard-ish
> GNOME 3 style) while the screen is locked, an area of the screen the same size
> as my laptop monitor appears at the top left of the combined screen area. If
> the window in question happens to be within that area, its contents are visible
> over the screensaver.

Note that it's the window which is revealed over the screen lock, not the dialog box pinned to it.

For the real-world example that made me look into this: Google Calendar pops up dialogs to remind you of appointments.

It's nothing to do with the browsers: I'll attach a simple Gtk app which demonstrates the same issue.
Comment 3 Will Thompson 2012-10-12 14:01:05 UTC
Created attachment 226325 [details]
A little Gtk app which demonstrates the same bug.


(Also, Matthias has tried the original web-page-based demo with Epiphany on 3.6, and the new screen locking doesn't have this issue.)
Comment 4 Ray Strode [halfline] 2012-10-15 22:32:14 UTC
Will, if you hit (from an unlocked screen) alt-f2, then type lg, then type enter, and then type:

Meta.disable_unredirect_for_screen(global.get_screen())

can you still reproduce?
Comment 5 Will Thompson 2012-10-19 08:16:08 UTC
(In reply to comment #4)
> Will, if you hit (from an unlocked screen) alt-f2, then type lg, then type
> enter, and then type:
> 
> Meta.disable_unredirect_for_screen(global.get_screen())
> 
> can you still reproduce?

No, that seems to make the issue go away. (And enable_unredirect_for_screen() brings it back.)
Comment 6 Ray Strode [halfline] 2012-10-19 15:29:28 UTC
okay, probably closely related to bug 677116
Comment 7 Samuel Wolf 2013-03-18 15:26:25 UTC
Hi,

is there a solution for the bug?
Debian Wheezy also affected :-(

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690669
Comment 8 Bastien Nocera 2014-08-20 20:23:53 UTC
The screen lock is now implemented directly in gnome-shell, not in
gnome-screensaver (as it was with older version of GNOME 3 and GNOME 2.x).

If the reported problems persists in recent versions of GNOME, please file a new bug against gnome-shell with the "lock-screen" component selected.

If your installation is an older version of GNOME that cannot be upgraded (such as an enterprise version), please use the appropriate support mechanism from your vendor, or your distribution instead.