From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 14394] New: [NV4B] Composite broken on 2nd head
Date: Tue, 5 Feb 2008 18:07:56 -0800 (PST) [thread overview]
Message-ID: <bug-14394-8800@http.bugs.freedesktop.org/> (raw)
http://bugs.freedesktop.org/show_bug.cgi?id=14394
Summary: [NV4B] Composite broken on 2nd head
Product: xorg
Version: git
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
ReportedBy: chalserogers-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Created an attachment (id=14164)
--> (http://bugs.freedesktop.org/attachment.cgi?id=14164)
Xorg log
When using metacity's composite manager, windows moved from my primary head
(LVDS) to the second head (DVI-D-0) do not appear at all. The mouse pointer
appears correctly, and the pointer changes depending on the contents of the
invisible window as normal (ie: a text-caret when over a textbox, etc).
This happened with the switch to metacity 2.21.8. One of the changes to the
compositor was to use the Composite Overlay Window. The kwin's compositor in
KDE4 also exhibits the same behaviour.
Composite works correctly when using xcompmgr, which leads me to suspect that
it's a problem with the COW on the second head.
--
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-02-06 2:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-06 2:07 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-14394-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2008-02-06 22:48 ` [Bug 14394] [NV4B] Composite broken on 2nd head bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-02-06 23:41 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-02-07 8:42 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-02-07 21:52 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-02-08 18:49 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-02-11 21:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-02-11 21:26 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-02-14 17:21 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-02-14 22:31 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-02-15 11:59 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-02-16 0:41 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-02-16 10:38 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-02-16 21:41 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-02-16 21:45 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-02-16 22:56 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-02-16 23:10 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-02-17 1:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-02-17 20:37 ` 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-14394-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.