From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 63933] New: Error in r300_set_framebuffer_state if use Dual-Head setup
Date: Thu, 25 Apr 2013 21:40:26 +0000 [thread overview]
Message-ID: <bug-63933-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1030 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=63933
Priority: medium
Bug ID: 63933
Assignee: dri-devel@lists.freedesktop.org
Summary: Error in r300_set_framebuffer_state if use Dual-Head
setup
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: victoraur.santos@gmail.com
Hardware: x86-64 (AMD64)
Status: NEW
Version: 9.1
Component: Drivers/DRI/r300
Product: Mesa
Created attachment 78488
--> https://bugs.freedesktop.org/attachment.cgi?id=78488&action=edit
Full log using compiz as gl-based wm
If try to start any WM that uses GL(Compiz, Gnome-shell, etc...) i get screen
completely stained and a lot of r300 error in .xsession-errors
Attached full log (using compiz)
Detail: if only one monitor is connected this error/bug doesn't occur and WM
GL-based start correctly.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2487 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2013-04-25 21:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-25 21:40 bugzilla-daemon [this message]
2013-04-25 21:47 ` [Bug 63933] Error in r300_set_framebuffer_state if use Dual-Head setup bugzilla-daemon
2013-04-26 21:57 ` bugzilla-daemon
2013-04-26 22:21 ` bugzilla-daemon
2013-04-26 22:25 ` bugzilla-daemon
2013-04-26 22:29 ` bugzilla-daemon
2013-04-26 22:32 ` 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=bug-63933-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.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 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.