Bug 694946

Summary: [abrt] krb5-auth-dialog-0.16-1.fc14: IA__gtk_style_detach: Process /usr/bin/krb5-auth-dialog was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Braden McDaniel <braden>
Component: krb5-auth-dialogAssignee: Itamar Reis Peixoto <itamar>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: itamar
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:fedfda14409c7ac7a9e61027528f3cc6fe3762b6
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-30 15:25:30 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 Braden McDaniel 2011-04-09 02:18:18 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 26575 bytes
cmdline: krb5-auth-dialog
component: krb5-auth-dialog
Attached file: coredump, 31158272 bytes
crash_function: IA__gtk_style_detach
executable: /usr/bin/krb5-auth-dialog
kernel: 2.6.35.11-83.fc14.x86_64
package: krb5-auth-dialog-0.16-1.fc14
rating: 4
reason: Process /usr/bin/krb5-auth-dialog was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1302315269
uid: 500

How to reproduce
-----
1. Crash happened in the background, several minutes (more than an hour, perhaps) after the dialog was last used.
Comment 1 Braden McDaniel 2011-04-09 02:18:20 UTC 
Created attachment 490909 [details]
File: backtrace
Comment 2 abrt-bot 2012-03-30 15:25:30 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 #665177, bug #700741

This comment is automatically generated.

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