Bug 655147

Summary: [abrt] kdepim-6:4.4.7-1.fc12: KCmdLineArgs::count: Process /usr/bin/korganizer was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Bill Newton <spiderbill>
Component: kdepimAssignee: Than Ngo <than>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: jreznik, kevin, ltinkl, rdieter, rnovacek, ry, smparrish, than, thomasj
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:d1e444e38dbd2b6cec5a278140fb7c949108906b
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-12-03 12:00:13 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Bill Newton 2010-11-19 18:11:51 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: korganizer
comment: Unknown, exactly. Kontact sometimes starts, fails to bring up the kwallet prompt for password, then crashes.
component: kdepim
crash_function: KCmdLineArgs::count
executable: /usr/bin/korganizer
kernel: 2.6.32.23-170.fc12.x86_64
package: kdepim-6:4.4.7-1.fc12
rating: 4
reason: Process /usr/bin/korganizer was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)
time: 1290189613
uid: 500
Comment 1 Bill Newton 2010-11-19 18:11:53 UTC 
Created attachment 461616 [details]
File: backtrace
Comment 2 Bug Zapper 2010-12-03 12:00:13 UTC 
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.

Thank you for reporting this bug and we are sorry it could not be fixed.