Description of problem: I'm not sure what's exactly causing the problem, but my machine crashes at least once a day. Not always but very often a few minutes after starting the machine at that day. Normally it's a really hard crash which looks like someone just pressed the reset button. Sometimes even the BIOS needs some autorecovery. Sometimes it just freezes. This is the first time ABRT was able catch the problem. (Might be something different of course...) It might have something to do with Firefox, since Firefox was always open everytime the machine crashed. However, I have almost always a browser window open, so it might have nothing to do with it, especially because it isn't a specific website or thing I do in the browser that's causing this. Sorry that I can't be more specific. Version-Release number of selected component: gnome-shell-3.4.1-6.fc17 Additional info: libreport version: 2.0.18 abrt_version: 2.0.18 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: gjs_g_arg_release_internal kernel: 3.7.3-101.fc17.x86_64 truncated backtrace: :Thread no. 1 (10 frames) : #6 gjs_g_arg_release_internal at gi/arg.c:2792 : #7 gjs_g_argument_release at gi/arg.c:3040 : #8 gjs_invoke_c_function at gi/function.c:993 : #9 function_call at gi/function.c:1245 : #10 CallJSNative at jscntxtinlines.h:701 : #11 js::Invoke at jsinterp.cpp:696 : #12 js::Interpret at jsinterp.cpp:4810 : #13 js::RunScript at jsinterp.cpp:653 : #14 js::Invoke at jsinterp.cpp:740 : #15 js_fun_apply at jsfun.cpp:2205
Created attachment 692731 [details] File: core_backtrace
Created attachment 692732 [details] File: environ
Created attachment 692733 [details] File: limits
Created attachment 692734 [details] File: backtrace
Created attachment 692735 [details] File: smolt_data
Created attachment 692736 [details] File: cgroup
Created attachment 692737 [details] File: xsession_errors
Created attachment 692738 [details] File: executable
Created attachment 692739 [details] File: maps
Created attachment 692740 [details] File: dso_list
Created attachment 692741 [details] File: proc_pid_status
Created attachment 692742 [details] File: var_log_messages
Created attachment 692743 [details] File: open_fds
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 '17'. 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 17'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 17 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 17'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 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.