From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 53391] nouveau: wrong display output order
Date: Sat, 9 Feb 2013 22:09:53 +0000 (UTC) [thread overview]
Message-ID: <20130209220953.5073011FE9A@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-53391-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=53391
--- Comment #7 from Stijn Tintel <stijn+bugs@linux-ipv6.be> 2013-02-09 22:09:53 ---
The 2nd patch seems to give the same behaviour as the 1st patch. And I do not
entirely agree it is only a cosmetic issue.
With nvidia.ko, I use an Xorg.conf just with the Device section to have X use
the proprietary driver. There are no screen or serverlayout sections, and I let
kwin configure my monitors. With nouveau, I use no Xorg.conf at all, because X
autodetects the nouveau driver. The difference with the nouveau driver is that
even when I save the monitor layout in the KDE settings, when I log out and
back in, the settings are forgotten. I would call that a KDE/kwin bug, but this
does not happen with the proprietary driver.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2013-02-09 22:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-03 18:20 [Bug 53391] New: nouveau: wrong display output order bugzilla-daemon
2013-02-03 18:22 ` [Bug 53391] " bugzilla-daemon
2013-02-09 16:46 ` bugzilla-daemon
2013-02-09 17:43 ` bugzilla-daemon
2013-02-09 17:59 ` bugzilla-daemon
2013-02-09 19:00 ` bugzilla-daemon
2013-02-09 20:11 ` bugzilla-daemon
2013-02-09 22:09 ` bugzilla-daemon [this message]
2013-02-09 22:37 ` bugzilla-daemon
2013-02-11 22:12 ` bugzilla-daemon
2013-02-12 12:54 ` bugzilla-daemon
2013-02-12 21:36 ` bugzilla-daemon
2013-02-13 0:53 ` bugzilla-daemon
2021-12-08 9:47 ` bugzilla-daemon
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=20130209220953.5073011FE9A@bugzilla.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).