Hide Forgot
Description of problem: Tried to tun XMBC and got this mesa tools crash. Version-Release number of selected component: glx-utils-8.1.0-3.fc18 Additional info: reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: glxinfo crash_function: do_winsys_init executable: /usr/bin/glxinfo kernel: 3.9.11-200.fc18.x86_64 runlevel: N 5 uid: 1000 xsession_errors: Truncated backtrace: Thread no. 1 (10 frames) #0 do_winsys_init at radeon_drm_winsys.c:212 #1 radeon_drm_winsys_create at radeon_drm_winsys.c:610 #2 create_screen at target.c:11 #3 dri2_init_screen at dri2.c:807 #4 driCreateNewScreen at ../../../../src/mesa/drivers/dri/common/drisw_util.c:70 #5 driswCreateScreen at drisw_glx.c:672 #6 AllocAndFetchScreenConfigs at glxext.c:758 #7 __glXInitialize at glxext.c:859 #9 GetGLXPrivScreenConfig at glxcmds.c:174 #11 glXChooseVisual at glxcmds.c:1197
Created attachment 791883 [details] File: backtrace
Created attachment 791884 [details] File: cgroup
Created attachment 791885 [details] File: core_backtrace
Created attachment 791886 [details] File: dso_list
Created attachment 791887 [details] File: environ
Created attachment 791888 [details] File: limits
Created attachment 791889 [details] File: maps
Created attachment 791890 [details] File: open_fds
Created attachment 791891 [details] File: proc_pid_status
Created attachment 791892 [details] File: var_log_messages
Couple seconds later firefox also experienced crash asociated with radeon drm: https://bugzilla.redhat.com/show_bug.cgi?id=957531
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 '18'. 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 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. 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.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.