Bug 667961 - [abrt] pidgin-2.7.9-1.fc14: handle_error: Process /usr/bin/pidgin was killed by signal 6 (SIGABRT)
Summary: [abrt] pidgin-2.7.9-1.fc14: handle_error: Process /usr/bin/pidgin was killed ...
Keywords:
Status: CLOSED DUPLICATE of bug 656104
Alias: None
Product: Fedora
Classification: Fedora
Component: pidgin
Version: 14
Hardware: x86_64
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Stu Tomlinson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:ea6ad112de28bc0af5ee0fc1e1b...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-07 12:49 UTC by tammorelli
Modified: 2012-03-21 16:33 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-03-21 16:33:58 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (31.75 KB, text/plain)
2011-01-07 12:49 UTC, tammorelli 		no flags Details
View All

Description tammorelli 2011-01-07 12:49:05 UTC 
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: pidgin
component: pidgin
crash_function: handle_error
executable: /usr/bin/pidgin
kernel: 2.6.35.10-74.fc14.x86_64
package: pidgin-2.7.9-1.fc14
rating: 4
reason: Process /usr/bin/pidgin was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1294321585
uid: 500

How to reproduce
-----
1.a
2.
3.
Comment 1 tammorelli 2011-01-07 12:49:10 UTC 
Created attachment 472228 [details]
File: backtrace
Comment 2 Kris Buytaert 2011-01-28 11:35:54 UTC 
Package: pidgin-2.7.9-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
Resized Pidgin
Comment 3 abrt-bot 2012-03-21 16:33:58 UTC 
Backtrace analysis found this bug to be similar to bug #656104, closing as duplicate. This bug seems to belong to component gtk2 or libX11.

Bugs which were found to be similar to this bug: 
  evolution: bug #702174
  nautilus: bug #656104, bug #666736, bug #706978

This comment is automatically generated.

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