Bug 480699 - compiz-fusion crash in r300_dri.so
compiz-fusion crash in r300_dri.so
Product: Fedora
Classification: Fedora
Component: mesa (Show other bugs)
x86_64 Linux
low Severity high
: ---
: ---
Assigned To: Adam Jackson
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2009-01-19 17:30 EST by tonglichn2000
Modified: 2015-03-30 09:38 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-06-28 07:07:29 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description tonglichn2000 2009-01-19 17:30:27 EST
Description of problem:

Running compiz-fusion causes the X server to crash.

Version-Release number of selected component (if applicable):

mesa-dri-drivers: version 7.3 x86_64, release 0.4.fc11

How reproducible:


Steps to Reproduce:
1. startx
2. start compiz-fusion
Actual results:

X server crashes w/ the following backtrace:

0: /usr/bin/X(xorg_backtrace+0x26) [0x4e95d6]
1: /usr/bin/X(xf86SigHandler+0x39) [0x47dc99]
2: /lib64/libc.so.6 [0x3f4ce32fe0]
3: /usr/lib64/dri/r300_dri.so [0x7f1a466be75f]
4: /usr/lib64/dri/r300_dri.so [0x7f1a466bef4a]
5: /usr/lib64/dri/r300_dri.so(r300EmitState+0xcc) [0x7f1a466be4b2]
6: /usr/lib64/dri/r300_dri.so(r300BeginBatch+0x6e) [0x7f1a466be530]
7: /usr/lib64/dri/r300_dri.so(r300EmitCacheFlush+0x27) [0x7f1a466d2edf]
8: /usr/lib64/dri/r300_dri.so [0x7f1a466c43c8]
9: /usr/lib64/dri/libdricore.so(_tnl_run_pipeline+0x119) [0x7f1a4639257f]
10: /usr/lib64/dri/r300_dri.so [0x7f1a466b9476]
11: /usr/lib64/dri/libdricore.so(_tnl_draw_prims+0x9c9) [0x7f1a46392fe9]
12: /usr/lib64/dri/libdricore.so [0x7f1a4638afbe]
13: /usr/lib64/xorg/modules/extensions//libglx.so [0x7f1a59e312bc]
14: /usr/lib64/xorg/modules/extensions//libglx.so [0x7f1a59e2b9d6]
15: /usr/lib64/xorg/modules/extensions//libglx.so [0x7f1a59e2fb72]
16: /usr/bin/X(Dispatch+0x364) [0x4473f4]
17: /usr/bin/X(main+0x3bd) [0x42cdcd]
18: /lib64/libc.so.6(__libc_start_main+0xe6) [0x3f4ce1e5c6]
19: /usr/bin/X [0x42c259]
Comment 1 Juha Tuomala 2009-02-26 13:48:34 EST
I get the same crash, 
0: /usr/bin/X(xorg_backtrace+0x26) [0x4e7b66]
1: /usr/bin/X(xf86SigHandler+0x39) [0x47d659]
2: /lib64/libc.so.6 [0x3875a32f90]
3: /usr/lib64/dri/r300_dri.so [0x5b40af7]
4: /usr/lib64/dri/r300_dri.so [0x5b4114a]
5: /usr/lib64/dri/r300_dri.so(r300EmitState+0x95) [0x5b408ba]
6: /usr/lib64/dri/r300_dri.so(r300BeginBatch+0x8a) [0x5b409bc]
7: /usr/lib64/dri/r300_dri.so [0x5b3b11e]
8: /usr/lib64/xorg/modules/extensions//libglx.so [0x9f5786]
9: /usr/lib64/xorg/modules/extensions//libglx.so [0x9f98f2]
10: /usr/bin/X(Dispatch+0x364) [0x4468d4]
11: /usr/bin/X(main+0x45d) [0x42cd1d]
12: /lib64/libc.so.6(__libc_start_main+0xe6) [0x3875a1e576]
13: /usr/bin/X [0x42c0f9]

Fatal server error:
Caught signal 11.  Server aborting


84:00.0 VGA compatible controller: ATI Technologies Inc R580 [Radeon X1900 XT] (Primary)
84:00.1 Display controller: ATI Technologies Inc R580 [Radeon X1900 XT] (Secondary)

(--) PCI:*(0@132:0:0) ATI Technologies Inc R580 [Radeon X1900 XT] (Primary) rev 0, Mem @ 0xd0000000/268435456, 0xc0700000/65536, I/O @ 0x00005000/256
, BIOS @ 0x????????/131072
(--) PCI: (0@132:0:1) ATI Technologies Inc R580 [Radeon X1900 XT] (Secondary) rev 0, Mem @ 0xc0710000/65536

I manage crash it just using KDE, i guess GL effects trigger it.
Comment 2 Juha Tuomala 2009-02-26 14:07:26 EST
How can i disable DRI then?

Section "Device"
        Identifier  "d0"
#       Driver      "radeonhd"
        Driver      "radeon"
#       Driver      "vesa"
        Option      "DRI"   "Off"

(**) RADEON(0): Option "DRI" "Off"
(II) RADEON(0): [DRI] installation complete
(II) GLX: Initialized DRI GL provider for screen 0

but it still crashes. radeon man page says that DRI off should do it.
Comment 3 Juha Tuomala 2009-02-27 05:10:24 EST
# rpm -e mesa-dri-drivers --nodeps

Allows me to stay on desktop without crashes without lobotomizing the whole system with yum remove. And now I feel dirty about that --nodeps.
Comment 4 Bug Zapper 2009-06-09 06:47:52 EDT
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
Comment 5 Matěj Cepl 2009-11-05 13:21:30 EST
Since this bugzilla report was filed, there have been several major updates in various components of the Xorg system, which may have resolved this issue. Users who have experienced this problem are encouraged to upgrade their system to the latest version of their packages. For packages from updates-testing repository you can use command

yum upgrade --enablerepo='*-updates-testing'

Alternatively, you can also try to test whether this bug is reproducible with the upcoming Fedora 12 distribution by downloading LiveMedia of F12 Beta available at http://alt.fedoraproject.org/pub/alt/nightly-composes/ . By using that you get all the latest packages without need to install anything on your computer. For more information on using LiveMedia take a look at https://fedoraproject.org/wiki/FedoraLiveCD .

Please, if you experience this problem on the up-to-date system, let us now in the comment for this bug, or whether the upgraded system works for you.

If you won't be able to reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.

[This is a bulk message for all open Fedora Rawhide Xorg-related bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.]
Comment 6 Matěj Cepl 2010-02-26 07:27:13 EST
Could you please reply to the previous question? If you won't reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.

[Note please, that this is machine generated comment for large amount of bugs; due to some technical issues, it is possible we've missed some of the responses -- it is happens, please, just a make a comment about that; that we will see. Thank you]
Comment 7 Bug Zapper 2010-04-27 08:45:43 EDT
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '11'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 11's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 11 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 8 Bug Zapper 2010-06-28 07:07:29 EDT
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.
Comment 9 tonglichn2000 2015-03-30 09:38:41 EDT
It's already closed and marked wontfix years ago. I don't understand why it's still sending me email with needinfo

Note You need to log in before you can comment on or make changes to this bug.