Hide Forgot
Description of problem: Got a crazy idea to enable 3D Desktop for a moment. Well crashed after several minutes while moving single window. Version-Release number of selected component (if applicable): 0:7.1-0.25.fc9 kernel 2.6.25 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: Program terminated with signal 6, Aborted. [New process 2760] #0 0x0000003a6cc32215 in raise (sig=<value optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 64 return INLINE_SYSCALL (tgkill, 3, pid, selftid, sig); Missing separate debuginfos, use: debuginfo-install audit.x86_64 dbus.x86_64 expat.x86_64 freetype.x86_64 libXau.x86_64 libXdmcp.x86_64 libXfont.x86_64 libcap.x86_64 libdrm.x86_64 libfontenc.x86_64 libpciaccess.x86_64 libselinux.x86_64 openssl.x86_64 pixman.x86_64 xorg-x11-drv-keyboard.x86_64 xorg-x11-drv-mouse.x86_64 zlib.x86_64 (gdb) bt #0 0x0000003a6cc32215 in raise (sig=<value optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #1 0x0000003a6cc33d83 in abort () at abort.c:88 #2 0x0000003a6cc2b039 in __assert_fail (assertion=<value optimized out>, file=<value optimized out>, line=<value optimized out>, function=<value optimized out>) at assert.c:78 #3 0x00007fe8d19d85c8 in evict_and_alloc_block (bo=0x20f0090) at ../common/dri_bufmgr_fake.c:498 #4 0x00007fe8d19d8733 in dri_fake_reloc_and_validate_buffer (bo=0x20f0090) at ../common/dri_bufmgr_fake.c:814 #5 0x00007fe8d19d8658 in dri_fake_reloc_and_validate_buffer (bo=0x253e210) at ../common/dri_bufmgr_fake.c:1010 #6 0x00007fe8d19d8658 in dri_fake_reloc_and_validate_buffer (bo=0x227cac0) at ../common/dri_bufmgr_fake.c:1010 #7 0x00007fe8d19d8658 in dri_fake_reloc_and_validate_buffer (bo=0x24b9cb0) at ../common/dri_bufmgr_fake.c:1010 #8 0x00007fe8d19d88ce in dri_fake_process_relocs (batch_buf=0x24b9cb0, count_p=0x7fffec01296c) at ../common/dri_bufmgr_fake.c:1049 #9 0x00007fe8d19d8f29 in _intel_batchbuffer_flush (batch=0x1684560, file=<value optimized out>, line=<value optimized out>) at intel_batchbuffer.c:134 #10 0x00007fe8d19dd778 in intelFinish (ctx=0xac8) at intel_context.c:372 #11 0x00007fe8e39611a4 in ?? () #12 0x0000000000000000 in ?? ()
Zdeňku, could we get /etc/X11/xorg.conf and /var/log/Xorg.*.log attached to this bug, please?
Created attachment 302993 [details] Xorg configuration
Created attachment 302994 [details] Xorg log file
Changing version to '9' as part of upcoming Fedora 9 GA. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This message is a reminder that Fedora 9 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 9. 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 '9'. 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 9'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 9 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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 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.