Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1314386 - gnome-shell spams logs with Gdk-WARNING
Summary: gnome-shell spams logs with Gdk-WARNING
Keywords:
Status: CLOSED DUPLICATE of bug 1304681
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 24
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Owen Taylor
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-03 13:38 UTC by Jan Synacek
Modified: 2016-03-04 12:34 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-04 12:34:37 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Jan Synacek 2016-03-03 13:38:29 UTC 
Description of problem:
I'm getting massive spam into the logs (several times a second, all the time) from the gnome shell:

Mar 03 14:33:04 ntb-work org.gnome.Shell.desktop[7035]: (gnome-shell:7035): Gdk-WARNING **: gdk-frame-clock: layout continuously requested, giving up after 4 tries


Version-Release number of selected component (if applicable):
gnome-shell-3.19.90-1.fc24.x86_64


Steps to Reproduce:
1. journalctl -f
2. Observe.


Additional info:
I have a docked Lenovo T440s and an external monitor connected to the dock. When I switched the primary monitor from the Lenovo's built-in to the external one, gnome-shell crashed and keeps crashing whenever I try to set the display settings.
Comment 1 Jan Synacek 2016-03-03 13:41:34 UTC 
The spam happens even when using only the built-in display... But I noticed that it starts when I get a notification.
Comment 2 Florian Müllner 2016-03-04 12:34:37 UTC 

*** This bug has been marked as a duplicate of bug 1304681 ***
Note You need to log in before you can comment on or make changes to this bug.