Bug 1317024 - Screensaver freezes
Screensaver freezes
Status: CLOSED EOL
Product: Fedora
Classification: Fedora
Component: gnome-shell (Show other bugs)
22
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Owen Taylor
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-03-11 12:55 EST by Aram Agajanian
Modified: 2016-07-19 14:46 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-07-19 14:46:01 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Aram Agajanian 2016-03-11 12:55:48 EST
Description of problem:
I ran some OS updates on Tuesday.  Since then, every evening the monitor has turned on (from powersave mode) and the screensaver is frozen.

I can still get to a virtual console by pressing the key combination C-A-F3.

I found the following lines in the logs from yesterday evening:

Mar 10 23:35:02 mycomputer.localdomain gnome-session[1566]: (gnome-shell:1584): GLib-GIO-CRITICAL **: g_dbus_connection_signal_unsubscribe: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
Mar 10 23:35:02 mycomputer.localdomain gnome-session[1566]: (gnome-shell:1584): GLib-GIO-CRITICAL **: g_dbus_connection_signal_unsubscribe: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
Mar 10 23:35:02 mycomputer.localdomain gnome-session[1566]: (gnome-shell:1584): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Mar 10 23:35:02 mycomputer.localdomain gnome-session[1566]: (gnome-shell:1584): GLib-GIO-CRITICAL **: g_dbus_connection_signal_unsubscribe: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
Mar 10 23:35:02 mycomputer.localdomain gnome-session[1566]: (gnome-shell:1584): GLib-GIO-CRITICAL **: g_dbus_connection_signal_unsubscribe: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
Mar 10 23:35:02 mycomputer.localdomain gnome-session[1566]: (gnome-shell:1584): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Mar 10 23:55:12 mycomputer.localdomain /usr/libexec/gdm-x-session[2208]: (WW) RADEON(0): radeon_dri2_flip_event_handler: Pageflip completion event has impossible msc 219456675 < target_msc 219456676
Mar 10 23:55:53 mycomputer.localdomain gnome-session[2312]: (gnome-settings-daemon:2399): GnomeDesktop-WARNING **: Failed to acquire idle monitor proxy: Timeout was reached
Mar 10 23:55:53 mycomputer.localdomain gnome-session[2312]: (gnome-settings-daemon:2399): GnomeDesktop-WARNING **: Error setting property 'PowerSaveMode' on interface org.gnome.Mutter.DisplayConfig: Timeout was reached (g-io-error-quark, 24)
Mar 11 00:00:00 mycomputer.localdomain gnome-session[2312]: (evolution-alarm-notify:2682): evolution-alarm-notify-WARNING **: alarm.c:253: Requested removal of nonexistent alarm!


Version-Release number of selected component (if applicable):
gnome-shell-3.16.4-1.fc22.x86_64
kernel-4.4.3-201.fc22.x86_64

How reproducible:
It has happened every evening for the last three nights.

Steps to Reproduce:
1.  Press the Super-L key combination to lock the UI.
2.  Go home.
3.  Come back next morning.

Actual results:
Monitor is on and screensaver is frozen.  The time displayed is sometime in the late evening.

Expected results:
The monitor should be in powersave mode and the screensaver should respond to the keyboard and mouse.
Comment 1 Fedora End Of Life 2016-07-19 14:46:01 EDT
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

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