Description of problem: Can't really say how it happened; my guess is through having about 7 tabs open in Firefox, but that's a SWAG (scientific wild-arse guess). Version-Release number of selected component: xulrunner-18.0-6.fc18 Additional info: backtrace_rating: 4 cmdline: /usr/lib64/xulrunner/plugin-container /usr/lib64/mozilla/plugins/libgnome-shell-browser-plugin.so -greomni /usr/lib64/xulrunner/omni.ja -appomni /usr/lib64/firefox/omni.ja 1978 true plugin crash_function: _invokedefault executable: /usr/lib64/xulrunner/plugin-container kernel: 3.7.1-5.fc18.x86_64 remote_result: NOTFOUND uid: 1000 var_log_messages: Jan 11 16:01:04 localhost abrt[3252]: Saved core dump of pid 3165 (/usr/lib64/xulrunner/plugin-container) to /var/spool/abrt/ccpp-2013-01-11-16:01:03-3165 (42426368 bytes) Truncated backtrace: Thread no. 1 (10 frames) #0 _invokedefault at /usr/src/debug/xulrunner-18.0/mozilla-release/dom/plugins/ipc/PluginModuleChild.cpp:1378 #1 mozilla::plugins::child::_invokedefault at /usr/src/debug/xulrunner-18.0/mozilla-release/dom/plugins/ipc/PluginModuleChild.cpp:1369 #2 install_extension_cb at browser-plugin.c:626 #3 g_simple_async_result_complete at gsimpleasyncresult.c:775 #4 reply_cb at gdbusproxy.c:2632 #5 g_simple_async_result_complete at gsimpleasyncresult.c:775 #6 g_dbus_connection_call_done at gdbusconnection.c:5333 #7 g_simple_async_result_complete at gsimpleasyncresult.c:775 #8 complete_in_idle_cb at gsimpleasyncresult.c:787 #12 g_main_context_iteration at gmain.c:3351
Created attachment 677117 [details] File: backtrace
Created attachment 677118 [details] File: cgroup
I believe my installation suffers from the same problem, worse abrt can trace it and fails: --- Running report_uReport --- Server side error: '"Validation failed: error validating 'core_backtrace': missing mandatory element 'buildid'"' (exited with 1)
This is an automated bug processing. If you can reproduce the reported bug, please reopen it and assign directly to me (stransky). Thanks!
I hit this issue today on two different F18 machines with xulrunner-19.0-1.fc18.x86_64 and gnome-shell-3.6.3-2.fc18.x86_64. It occurred when trying to quickly install a bunch of different extensions from extensions.gnome.org that I had open in a bunch of tabs. Re-opening and re-assigning to the gnome-shell.
https://retrace.fedoraproject.org/faf/reports/35401
I think this is a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=952336
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.