GNOME Bugzilla – Bug 610482
problems triggered when I open the laptop lid
Last modified: 2010-10-13 17:41:45 UTC
The problems I have are minor, and are not present if gnome-settings-daemon is not running.
They come every time I open the laptop lid (of course after having closed it, no matter for how long)
1) the first bulk of keypresses lag some seconds (no matter when I hit the keys, it can also be 1 minute after I opened the lid) then the keyboard goes back to normal work
2) some panel icons (apparently all applets) suddenly disappear and reappear (like a flahs). This does not always happen
3) I see a notification that says: "Could not switch the monitor configuration / could not set the configuration for CRTC 64" (this only if I not disable kernel mode setting in my intel x4500hd)
the monitor notification is another problem, because only one of my 2 laptops exposes it, but the other 2 bugs are present in both.
They are an HP and a DELL both with intel graphics, if that matters
*** Bug 612285 has been marked as a duplicate of this bug. ***
Created attachment 157762 [details] [review]
Fix xrandr erroring out on warped g-s-d fn-F7 timestamps
See https://bugs.launchpad.net/gnome-settings-daemon/+bug/484186 for a more details.
Is this fix about "could not switch the monitor configuration" or others issues?
It fixes issue #3 on your list. It does not fix the keypress refresh lag. I don't know exactly why, but it seems that xrandr events are propagated until a key is pressed. That's like an X issue though.
Do you suggest opening a bug in X?
I suppose it wouldn't hurt. This issue could be coming from anywhere X and below, including the kernel drivers, but X would be a good place to start.
What exactly should I write in the bug description?
I would summarize the symptoms (#1 and #2 in your description here), and state that it seems to be a delayed xrandr notification event that doesn't fire until the first key press.
the change described there has been tested by ubuntu users and seems to work correctly
"there" being X.org? So NOTGNOME?
Unfortunately, this bug report got littered with some superfluous information about a secondary X.org bug. However, the "Could not switch the monitor configuration / could not set the configuration for CRTC 64" bug is an issue with gnome-settings-daemon. The attached patch resolves this issue.
Ok. Federico, care to take a look?
For insterested people, here we have the Xorg bug about symptoms 1 and 2
The bug didn't receive any attention yet
For reference, here are Chase's comments from the Ubuntu bug:
--- comment 12
The libxrandr2 function XRRSetCrtcConfig (called from gnome-settings-daemon through libgnome-desktop) is called twice when I open the lid on my laptop. The second call has an older timestamp value, and thus the xorg xserver is returning RRSetConfigInvalidTime. Now we need to figure out why it's called twice like this.
--- comment 13
Gnome-settings-daemon is receiving two input events in a very short amount of time from the kernel. The input events are basically fn-F7, or "change my display output configuration". Unfortunately, these events are coming in reverse order, so the timestamps go backwards. The input timestamps are fed to the xserver, which evaluates the first just fine, and then errors out on the second due to the timestamp warping. What we need to do is either:
a. Have g-s-d detect warped timestamps and refuse to continue
b. Have g-s-d detect warped timestamps and set a the timestamp to the previous + 1
I'm testing out a. right first since it's the cleaner approach. I don't think there will be any issues with it, but you never know. I'll test out b. if a. has issues.
Pushed with some stylistic changes as c114f0ca3da756725996bfa2111b2cc4e1982d92 in master and d5e0550961e337a8ce08e41534bd26f7daab79be in gnome-2-30.
This does not include a fix for the first 2 sympthoms, right?
(In reply to comment #18)
> This does not include a fix for the first 2 sympthoms, right?
*** Bug 597682 has been marked as a duplicate of this bug. ***