Bug 577575 - [abrt] crash in scim-1.4.9-4.fc12: Process /usr/lib64/scim-1.0/scim-panel-gtk was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in scim-1.4.9-4.fc12: Process /usr/lib64/scim-1.0/scim-panel-gtk...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: scim
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Peng Wu
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:317599895cb4f8238af79a785c1...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-28 03:10 UTC by Claude G Wilbur
Modified: 2010-09-30 06:27 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-09-30 06:27:23 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (49.07 KB, text/plain)
2010-03-28 03:10 UTC, Claude G Wilbur
no flags Details

Description Claude G Wilbur 2010-03-28 03:10:39 UTC
abrt 1.0.8 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/scim-1.0/scim-panel-gtk --display :0.0 -c socket -d --no-stay
component: scim
executable: /usr/lib64/scim-1.0/scim-panel-gtk
kernel: 2.6.31.12-174.2.22.fc12.x86_64
package: scim-1.4.9-4.fc12
rating: 4
reason: Process /usr/lib64/scim-1.0/scim-panel-gtk was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)

Comment 1 Claude G Wilbur 2010-03-28 03:10:41 UTC
Created attachment 403075 [details]
File: backtrace

Comment 2 Claude G Wilbur 2010-04-17 06:38:03 UTC

How to reproduce
-----
1.enable smart pinyin scim
2.wait
3.

Comment 3 Fedora Admin XMLRPC Client 2010-06-25 05:40:25 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 4 Parag Nemade 2010-09-01 05:31:17 UTC
Please provide detail steps how to reproduce this crash

Comment 5 Parag Nemade 2010-09-30 06:27:23 UTC
I suppose we had enough waiting here.


Note You need to log in before you can comment on or make changes to this bug.