Description of problem: I just booted F19 TC3 Live x86_64 and this problem appeared, as notified by abrt. Version-Release number of selected component: gnome-shell-3.8.3-1.fc19 Additional info: reporter: libreport-2.1.4 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: wrapped_gobj_toggle_notify executable: /usr/bin/gnome-shell kernel: 3.9.4-301.fc19.x86_64 runlevel: N 5 uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #2 wrapped_gobj_toggle_notify at gi/object.c:1074 #3 gjs_g_arg_release_internal at gi/arg.c:2839 #4 gjs_invoke_c_function at gi/function.c:954 #5 function_call at gi/function.c:1202 #6 CallJSNative at jscntxtinlines.h:701 #7 js::Invoke at jsinterp.cpp:696 #8 js::Interpret at jsinterp.cpp:4810 #9 js::RunScript at jsinterp.cpp:653 #10 js::Invoke at jsinterp.cpp:740 #11 ExternalInvoke at jsinterp.cpp:863
Created attachment 760554 [details] File: backtrace
Created attachment 760555 [details] File: cgroup
Created attachment 760556 [details] File: core_backtrace
Created attachment 760557 [details] File: dso_list
Created attachment 760558 [details] File: environ
Created attachment 760559 [details] File: limits
Created attachment 760561 [details] File: maps
Created attachment 760562 [details] File: open_fds
Created attachment 760563 [details] File: proc_pid_status
Created attachment 760564 [details] File: var_log_messages
This can be a blocker: In most cases, there must be no SELinux 'AVC: denied' messages or abrt crash notifications on initial boot and subsequent login (see Blocker_Bug_FAQ) http://fedoraproject.org/wiki/Fedora_19_Final_Release_Criteria However, in my 5 attempts to boot LiveCD I saw this only once.
Discussed at 2013-06-17 blocker review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-06-17/f19final-blocker-review-6.2013-06-17-16.01.log.txt . This is rejected as a blocker for now as it just doesn't seem to be happening enough to merit blocker status: Kamil's is the only report and he only saw it one out of five tries. If we start getting a lot of reports we'll re-consider this decision. Ray, if you think this ought to be fixed in final (per upstream, you're still investigating the cause), can you nominate this as a freeze exception bug? To do that, just mark it as blocking 'FinalFreezeException'. Thanks.
*** Bug 1003733 has been marked as a duplicate of this bug. ***
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 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 this bug is closed as described in the policy above. 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.