From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 28658] New: [r300g] Occasional Compiz Crashes
Date: Mon, 21 Jun 2010 20:01:13 -0700 (PDT) [thread overview]
Message-ID: <bug-28658-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=28658
Summary: [r300g] Occasional Compiz Crashes
Product: Mesa
Version: git
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: Drivers/DRI/r300
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: ripps818@gmail.com
Created an attachment (id=36413)
--> (https://bugs.freedesktop.org/attachment.cgi?id=36413)
Compiz Backtrace
When using r300g gallium dri with radeon driver from the Xorg-Edgers PPA on
Ubuntu Maverick, Compiz occasionally crashes when starting a few programs.
For example, when I start gnome-mplayer, compiz crashes the moment it starts.
I've already confirmed that it's unrelated to mplayer itself. When mplayer is
run from a terminal or with another frontend (smplayer) it seems to work fine.
It's specifically something in the frontend gnome-mplayer that's triggering it.
I know that compiz has crashed several other times, but I've been unable to get
reliable crashes like I have with gnome-mplayer. Also, gnome-mplayer has some
transparency issues with the gtk-rgba in Maverick, but that might be unrelated.
I've attached a backtrace of compiz using gdb.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2010-06-22 3:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-22 3:01 bugzilla-daemon [this message]
2010-07-06 1:17 ` [Bug 28658] [Gallium/DRI] Occasional Compiz Crashes 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-28658-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox