Hello, I just want to inform you that this problem still exists on kernel 3.18 (linux-image-3.18.0-trunk-amd64). Thus it's safe to say this is most likely X or even GNOME bug.
Please inform me if you have any additional ideas on how to isolate the origin of this problem. Or if you want me to do any additional debugging. Looking forward to your reply, Adnan
