Bug 665177

Summary: [abrt] krb5-auth-dialog-0.16-3.fc15: Process /usr/bin/krb5-auth-dialog was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Matěj Cepl <mcepl>
Component: krb5-auth-dialogAssignee: Itamar Reis Peixoto <itamar>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: itamar, mcepl
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:ad6784e1fe735f767b22326baaa35555f593ec4c
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-30 15:25:46 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 Matěj Cepl 2010-12-23 01:06:46 UTC 
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: krb5-auth-dialog -A
component: krb5-auth-dialog
executable: /usr/bin/krb5-auth-dialog
kernel: 2.6.37-0.rc6.git5.1.fc15.x86_64
package: krb5-auth-dialog-0.16-3.fc15
reason: Process /usr/bin/krb5-auth-dialog was killed by signal 11 (SIGSEGV)
release: Fedora release 15 (Rawhide)
time: 1293066051
uid: 500

How to reproduce
-----
1.while upgrading system, krb5-auth-dialog crashed
2.
3.
Comment 1 Matěj Cepl 2010-12-23 01:06:48 UTC 
Created attachment 470360 [details]
File: backtrace
Comment 2 Matěj Cepl 2010-12-23 12:10:58 UTC 
Package: krb5-auth-dialog-0.16-3.fc15
Architecture: x86_64
OS Release: Fedora release 15 (Rawhide)


How to reproduce
-----
1.just running it, I had active ticket
2.
3.
Comment 3 abrt-bot 2012-03-30 15:25:46 UTC 
Backtrace analysis found this bug to be similar to bug #656292, closing as duplicate.

Bugs which were found to be similar to this bug: bug #649659, bug #656292, bug #694946, bug #700741

This comment is automatically generated.

*** This bug has been marked as a duplicate of bug 656292 ***