Bug 693436

Summary: [abrt] gnome-panel-2.32.0.2-2.fc14: JS_NewObject: Process /usr/libexec/clock-applet was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Kyle <kyleki>
Component: gnome-panelAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: kyleki, rstrode
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:46ba3577fd71582454aa6f6417b38110682f8098
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-16 15:33:41 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Kyle 2011-04-04 16:50:51 UTC
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 91430 bytes
cmdline: /usr/libexec/clock-applet
comment: I use compiz.  This crash occurred during my normal login when the gnome-panel was first initializing.  I'm now unable to reload the clock applet.
component: gnome-panel
Attached file: coredump, 54194176 bytes
crash_function: JS_NewObject
executable: /usr/libexec/clock-applet
kernel: 2.6.35.11-83.fc14.x86_64
package: gnome-panel-2.32.0.2-2.fc14
rating: 4
reason: Process /usr/libexec/clock-applet was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1301935356
uid: 5487

How to reproduce
-----
1. Log in to Gnome

Comment 1 Kyle 2011-04-04 16:50:54 UTC
Created attachment 489809 [details]
File: backtrace

Comment 2 Kyle 2011-04-04 18:21:08 UTC
I just noticed that this only crashes when I use "Automatic Proxy Configuration" in my network settings.  Turning the proxy off allows the applet to load without any trouble.

Comment 3 Kyle 2011-04-06 01:12:53 UTC
It looks like this is caused by xulrunner2-2.0-1.fc14.x86_64 which was installed as a dependency on firefox4.  I installed these from the following repository:

http://repos.fedorapeople.org/repos/spot/firefox4/

Once I uninstalled xulrunner2, the clock started working fine.

Comment 4 Kyle 2011-04-06 18:29:37 UTC
Apparently xulrunner2 from spot's repo has caused other problems as well:

Bug 677825

Comment 5 Fedora End Of Life 2012-08-16 15:33:44 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached 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 to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping