Version-Release number of selected component: firefox-20.0-1.fc18 Additional info: backtrace_rating: 4 cmdline: /usr/lib/firefox/firefox http://www.gnu.org/software/gnash/ crash_function: do_winsys_init executable: /usr/lib/firefox/firefox kernel: 3.8.9-200.fc18.i686.PAE uid: 1000 ureports_counter: 1 xsession_errors: Truncated backtrace: Thread no. 1 (10 frames) #0 do_winsys_init at radeon_drm_winsys.c:204 #1 radeon_drm_winsys_create at radeon_drm_winsys.c:582 #2 create_screen at target.c:12 #3 dri2_init_screen at dri2.c:807 #4 driCreateNewScreen at ../../../../src/mesa/drivers/dri/common/drisw_util.c:69 #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:1195
Created attachment 741214 [details] File: backtrace
Created attachment 741215 [details] File: cgroup
Created attachment 741216 [details] File: core_backtrace
Created attachment 741217 [details] File: dso_list
Created attachment 741218 [details] File: environ
Created attachment 741219 [details] File: limits
Created attachment 741220 [details] File: maps
Created attachment 741221 [details] File: open_fds
Created attachment 741222 [details] File: proc_pid_status
Created attachment 741223 [details] File: var_log_messages
Unfortunately, I don't recall what caused this problem. I think I was using Firefox over X11 (via SSH forwarding), but don't recall what I was doing at the time or even if I noticed the crash. The bug report tool popped up on the remote machine's display, and I didn't see it for several hours. I'll keep any eye out, though, and if anything more happens, will add to this report. reporter: libreport-2.1.4 backtrace_rating: 4 cmdline: /usr/lib64/firefox/firefox http://flowingdata.com/2013/06/07/rise-of-craft-beer/ crash_function: do_winsys_init executable: /usr/lib64/firefox/firefox kernel: 3.9.6-200.fc18.x86_64 package: firefox-21.0-3.fc18 reason: Process /usr/lib64/firefox/firefox was killed by signal 11 (SIGSEGV) runlevel: N 5 uid: 431
This is an automated bug update. Please reopen if you can reproduce the bug reliably and remove the [abrt] string from bug summary.
Hi Martin, It's still happening pretty reliably, almost always over X11 forwarding. Most recent occurrence was about 2:45 PM PDT today on version 22.0, installed from updates within the past week. I'd edit the bug as you requested (reopen and remove [abrt]), but Bugzilla doesn't seem to want me to do so. Chris
radeon_drm_winsys_create() ... sounds like the X driver problem.
Recently meet this issue too when ssh with X11 forwarding to a remote machine with firefox 22 opening. The bug report shows on the remote machine. Both the local and remote machine is 64bit. Seems like the package xorg-x11-drv-radeonhd is orphaned?
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.