From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 15758] Invisible mouse pointer on NV4E (C51)
Date: Tue, 29 Apr 2008 12:18:22 -0700 (PDT) [thread overview]
Message-ID: <20080429191822.6B06E130051@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-15758-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
http://bugs.freedesktop.org/show_bug.cgi?id=15758
--- Comment #1 from Stuart Bennett <sb476-KWPb1pKIrIJaa/9Udqfwiw@public.gmane.org> 2008-04-29 12:18:18 PST ---
I think this is most likely caused by the hardware issue fixed for nv in bug
7309. I'm not sure where the fix (delay) should go in nouveau however, since
simply delaying for a second each time the cursor is turned off is not an
option, as the hwcursor gets turned on and off many times during normal
operation.
--
Configure bugmail: http://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:[~2008-04-29 19:18 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-29 18:36 [Bug 15758] New: Invisible mouse pointer on NV4E (C51) bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-15758-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2008-04-29 19:18 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2008-06-15 17:31 ` [Bug 15758] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-06-16 13:11 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-12-31 19:57 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-01-03 3:51 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-01-22 12:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-01-22 23:57 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-01-23 21:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-01-26 19:33 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-01-26 19:35 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-07 20:30 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-07 20:32 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-07 23:36 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-08 9:18 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-08 12:23 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-08 14:04 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-04-04 22:48 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-04-05 9:18 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-04-07 10:12 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-02-24 5:12 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-02-24 6:50 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-02-24 11:38 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-06-23 13:22 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-06-23 14:26 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-06-23 14:53 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-08 4:45 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-08 4:56 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-19 8:08 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-19 16:05 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-08-26 10:15 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-11-19 8:02 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-25 16:47 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-25 19:35 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-20 1:16 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-04 11:05 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-05 6:26 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-22 22:29 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-23 7:59 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-24 0:53 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-24 6:56 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-24 14:32 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-24 16:33 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-25 17:34 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-25 17:50 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-09-19 15:22 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04 8:21 ` 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=20080429191822.6B06E130051@annarchy.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.