From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 42160] [NV4e] Mouse pointer disappears randomly after resuming from GNOME screensaver
Date: Tue, 25 Oct 2011 00:47:50 +0000 [thread overview]
Message-ID: <bug-42160-8800-AzRs31Luhl@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-42160-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=42160
--- Comment #4 from Ben Skeggs <skeggsb-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> 2011-10-24 17:47:50 PDT ---
(In reply to comment #3)
> If I remember correctly, the hardware cursor on NV4E is very sensitive/buggy.
>
> This commit in the nv driver from years ago might give you a lead:
> http://cgit.freedesktop.org/xorg/driver/xf86-video-nv/commit/?id=7f281be7e53ac274016a6af6b2b5dc6f8bddb810
Yes, the is the likely culprit. However, we can't just stick a 1 second sleep
in our cursor enable/disable function, that would be ridiculous. I suspect the
hw bug is somewhat more specific than that.
I attempted to ask NVIDIA for information on the cause a long time ago..
However, as expected, apparently this is far too secret to possibly reveal. I
don't have any of the effected hardware to tinker with it myself.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2011-10-25 0:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-24 12:57 [Bug 42160] New: [NV4e] Mouse pointer disappears randomly after resuming from GNOME screensaver bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-42160-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2011-10-24 12:58 ` [Bug 42160] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-10-24 12:59 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-10-24 18:22 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-10-24 18:22 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-10-24 18:22 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-10-24 19:47 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-10-25 0:47 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2011-10-26 16:57 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-19 16:40 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-42160-8800-AzRs31Luhl@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.