From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 12665] Option RandR12 breaks X.org
Date: Wed, 3 Oct 2007 10:31:58 -0700 (PDT) [thread overview]
Message-ID: <20071003173158.D855213006F@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-12665-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
http://bugs.freedesktop.org/show_bug.cgi?id=12665
------- Comment #4 from madman2003-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org 2007-10-03 10:34 PST -------
This is strange, for a few days (up to 28 september) crtc's (kind of a router
for screens) were forced to a specific number. The problem is that for some
reason CRTC1 is picked as first one, the hardware won't allow this and the
infrastructure doesn't allow me to block this. then come back up. Are you sure
your date is not older than 30 september? Please retry current git and if it's
still problematic,
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2007-10-03 17:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-03 17:14 [Bug 12665] New: Option RandR12 breaks X.org bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-12665-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2007-10-03 17:15 ` [Bug 12665] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2007-10-03 17:15 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2007-10-03 17:15 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2007-10-03 17:31 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2007-10-03 18:17 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2007-10-03 18:30 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-08-24 19:28 ` 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=20071003173158.D855213006F@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.