From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 79756] [Radeon] Resizing Steam windows freezes Xorg
Date: Thu, 12 Jun 2014 10:28:57 +0000 [thread overview]
Message-ID: <bug-79756-502-UewsqWYpe9@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-79756-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 665 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=79756
--- Comment #8 from Marti Raudsepp <marti@juffo.org> ---
(In reply to comment #7)
> That's the standalone glamor tree. I mean glamor from the current xserver
> Git tree.
Can/should I build glamor separately or should just build the whole xorg-server
from git?
> Anyway, I think the attached backtrace can only happen if Steam uses GLX
> indirect rendering (current versions of Steam present a warning dialog on
> startup when that's the case).
Yeah, I'm aware there are some ABI issues on Arch Linux with Steam's bundled
libgcc_s.so.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1536 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 prev parent reply other threads:[~2014-06-12 10:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-06 23:59 [Bug 79756] New: [Radeon] Resizing Steam windows freezes Xorg bugzilla-daemon
2014-06-07 0:00 ` [Bug 79756] " bugzilla-daemon
2014-06-07 0:01 ` bugzilla-daemon
2014-06-07 10:36 ` bugzilla-daemon
2014-06-07 10:42 ` bugzilla-daemon
2014-06-09 7:30 ` bugzilla-daemon
2014-06-11 19:38 ` bugzilla-daemon
2014-06-12 6:50 ` bugzilla-daemon
2014-06-12 10:28 ` bugzilla-daemon [this message]
2014-06-12 17:45 ` bugzilla-daemon
2014-06-13 5:48 ` bugzilla-daemon
2016-02-14 4:47 ` bugzilla-daemon
2016-02-15 2:38 ` 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-79756-502-UewsqWYpe9@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.