From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 16148] New: primary display is borked with RandR12 enabled
Date: Thu, 29 May 2008 05:22:23 -0700 (PDT) [thread overview]
Message-ID: <bug-16148-8800@http.bugs.freedesktop.org/> (raw)
http://bugs.freedesktop.org/show_bug.cgi?id=16148
Summary: primary display is borked with RandR12 enabled
Product: xorg
Version: unspecified
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
ReportedBy: khadgaray-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Created an attachment (id=16807)
--> (http://bugs.freedesktop.org/attachment.cgi?id=16807)
Xorg log
Primary (laptop's) display is borked, when RandR12 option is enabled.
Additionally, when using DVI conector the secondary display also starts acting
weird ( rainbow coloured checkboxes).
Version-Release number of selected component (if applicable):
kernel-2.6.25-14.fc9.i686
xorg-x11-drv-nouveau-0.0.10-2.20080408git0991281.fc9.i386
How reproducible:
always
Steps to Reproduce:
1. Enable RandR12 option
2. Enable dual-head using gnome-display-properties
3. Display goes crazy
Actual results:
Crazy psychedelic coloured display
Expected results:
Sane boring functional display
Additional info:
xorg log attached
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2008-05-29 12:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-29 12:22 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-16148-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2008-05-29 12:23 ` [Bug 16148] primary display is borked with RandR12 enabled bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-05-29 12:39 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-05-29 12:41 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-08-17 17:29 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-08-18 9:24 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-08-18 14:26 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-09-02 13:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-09-02 13:11 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-09-14 17:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-05 18:49 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-07-23 23:42 ` 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-16148-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.