Bug 684507 - [abrt] gjs-0.7.1-3.fc14: getNext: Process /usr/bin/gjs-console was killed by signal 11 (SIGSEGV)
Summary: [abrt] gjs-0.7.1-3.fc14: getNext: Process /usr/bin/gjs-console was killed by ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: gjs
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Robinson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:37f7bb15239ac12875704b90600...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-13 06:59 UTC by Timur Kristóf
Modified: 2011-04-05 12:37 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-04-05 12:37:51 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (27.05 KB, text/plain)
2011-03-13 06:59 UTC, Timur Kristóf 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Timur Kristóf 2011-03-13 06:59:41 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 27697 bytes
cmdline: /usr/bin/gjs-console -c 'const ClockPreferences = imports.prefs.clockPreferences;\nClockPreferences.main({ progName: \'gnome-shell-clock-preferences\',\n                        uiFile: \'/usr/share/gnome-shell/clock-preferences.ui\',\n                        localeDir: \'/usr/share/locale\' });'
component: gjs
Attached file: coredump, 15265792 bytes
crash_function: getNext
executable: /usr/bin/gjs-console
kernel: 2.6.35.11-83.fc14.x86_64
package: gjs-0.7.1-3.fc14
rating: 4
reason: Process /usr/bin/gjs-console was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1299999511
uid: 500

How to reproduce
-----
1. Go to System/Preferences
2. Click on Clock
3. This crash is detected
Comment 1 Timur Kristóf 2011-03-13 06:59:47 UTC 
Created attachment 483958 [details]
File: backtrace
Comment 2 Dan Winship 2011-04-05 12:37:51 UTC 
crash in the old JS clock preferences UI, which no longer exists
Note You need to log in before you can comment on or make changes to this bug.