From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 33887] New: nouveau causes graphic corruption were you cant do anything
Date: Thu, 3 Feb 2011 19:15:58 -0800 (PST) [thread overview]
Message-ID: <bug-33887-8800@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=33887
Summary: nouveau causes graphic corruption were you cant do
anything
Product: xorg
Version: 7.6
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: blocker
Priority: medium
Component: Driver/nouveau
AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
ReportedBy: oninekoze-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Created an attachment (id=42914)
--> (https://bugs.freedesktop.org/attachment.cgi?id=42914)
snapshot of graphic coruption
with ubuntu on an hp pavilion dv6605us(dv6500) and a GeForce 7150m / nForce
630M built in graphics theres so bad of graphic corruption where you can only
see the mouse correctly which is shown in the snapshot attachment
the only way to get past it is by disabling and/or completely removing nouveau
i have made a report to ubuntu's launchpad
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/711591
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-02-04 3:15 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-04 3:15 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-33887-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2011-02-04 13:59 ` [Bug 33887] nouveau causes graphic corruption were you cant do anything bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-05 6:53 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-05 7:00 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-05 9:32 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-05 13:26 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-05 13:46 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-05 14:13 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-05 14:30 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-05 14:32 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-05 14:43 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-05 21:18 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-05 21:43 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-05 22:07 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-06 11:24 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-06 12:12 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-06 14:29 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-06 20:37 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-06 21:36 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-06 22:29 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-06 23:45 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-07 4:14 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-07 5:20 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-07 10:29 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-07 10:36 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-07 10:41 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-08 5:12 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-08 5:23 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-09 15:30 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-09 15:37 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-09 15:39 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-09 16:19 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-11 7:53 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-11 10:43 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-14 18:17 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-22 11:05 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-22 11:12 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-04-30 21:29 ` 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-33887-8800@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.