From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 51477] bad/missing graphics with NV11 / GeForce 2MX/MX400
Date: Sun, 02 Sep 2012 01:56:36 +0000 [thread overview]
Message-ID: <bug-51477-8800-xcxvCIMVVX@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-51477-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=51477
--- Comment #12 from György Balló <ballogy@freestart.hu> 2012-09-02 01:56:36 UTC ---
I have an NV17 [GeForce4 MX 440] card, and I have similar rendering issues.
The issues are started for me after this commit (the new libdrm port):
http://cgit.freedesktop.org/nouveau/xf86-video-nouveau/commit/?id=e70d801ae9287eab5e82f4d467dc8cd4be1b31a8
So I think the problem is in this commit or in the new libdrm.
The graphics corruption, what I experienced sometimes:
- Missing icons in Nautilus.
- The toolbar in Nautilus and the tabs in Firefox are shown brighter than it
should be.
- The text in GNOME Terminal is shown in other color than it should be.
These problems are usually disappear, when I move the mouse over the elements
or move the application's window.
I'm using GNOME 3 fallback mode.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
next prev parent reply other threads:[~2012-09-02 1:56 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-27 6:22 [Bug 51477] New: bad/missing graphics with NV11 / GeForce 2MX/MX400 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-51477-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2012-06-27 6:23 ` [Bug 51477] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-27 6:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-27 6:27 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-27 6:29 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-27 6:33 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-27 22:21 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-28 12:02 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-28 15:22 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-28 15:33 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-28 23:18 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-29 7:50 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-29 8:23 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-09-02 1:56 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2012-11-05 14:14 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-01 17:06 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-06-17 14:15 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-08 6:43 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-12 20:11 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-12 20:12 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-12-10 17:57 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-05 7:23 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-04-08 19:30 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-04-11 10:41 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-04-12 17:17 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-08-10 5:12 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-08-10 6:29 ` [Bug 51477] [NV10, NV20] bad/missing graphics, usually alpha-related bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-08-10 15:08 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-08-21 22:11 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-08 18:11 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-08 18:12 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-09 17:37 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-09 17: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-51477-8800-xcxvCIMVVX@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.