Bug 700741 - [abrt] krb5-auth-dialog-0.16-1.fc14: g_type_check_instance_is_a: Process /usr/bin/krb5-auth-dialog was killed by signal 11 (SIGSEGV)
Summary: [abrt] krb5-auth-dialog-0.16-1.fc14: g_type_check_instance_is_a: Process /usr...
Keywords:
Status: CLOSED DUPLICATE of bug 656292
Alias: None
Product: Fedora
Classification: Fedora
Component: krb5-auth-dialog
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Itamar Reis Peixoto
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:c6fb27f80529a670fb3a8ee2bc7...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-29 09:47 UTC by Tomas Pelka
Modified: 2012-03-30 15:25 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-30 15:25:38 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (29.19 KB, text/plain)
2011-04-29 09:47 UTC, Tomas Pelka 		no flags Details
View All

Description Tomas Pelka 2011-04-29 09:47:33 UTC 
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 29887 bytes
cmdline: krb5-auth-dialog
comment: Not sure what happen. Just use my desktop as usual. 
component: krb5-auth-dialog
Attached file: coredump, 22802432 bytes
crash_function: g_type_check_instance_is_a
executable: /usr/bin/krb5-auth-dialog
kernel: 2.6.35.12-88.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: 1303888895
uid: 500

How to reproduce
-----
1. Not sure.
2.
3.
Comment 1 Tomas Pelka 2011-04-29 09:47:36 UTC 
Created attachment 495742 [details]
File: backtrace
Comment 2 abrt-bot 2012-03-30 15:25:38 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 #694946

This comment is automatically generated.

*** This bug has been marked as a duplicate of bug 656292 ***
Note You need to log in before you can comment on or make changes to this bug.