Bug 674824 - [abrt] pidgin-2.7.9-1.fc14: sighandler: Process /usr/bin/pidgin was killed by signal 6 (SIGABRT)
Summary: [abrt] pidgin-2.7.9-1.fc14: sighandler: Process /usr/bin/pidgin was killed by...
Keywords:
Status: CLOSED DUPLICATE of bug 702094
Alias: None
Product: Fedora
Classification: Fedora
Component: pidgin
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Stu Tomlinson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:080bc8d4bf7d6b4680df95a37bf...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-03 13:13 UTC by Michael Greenberg
Modified: 2012-03-20 16:46 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-20 16:46:25 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (27.65 KB, text/plain)
2011-02-03 13:13 UTC, Michael Greenberg
no flags Details

Description Michael Greenberg 2011-02-03 13:13:29 UTC
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: /usr/bin/pidgin
component: pidgin
crash_function: sighandler
executable: /usr/bin/pidgin
kernel: 2.6.35.10-74.fc14.i686
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: 1296738438
uid: 38111

How to reproduce
-----
1.Denied buddy request by a spammer.
2.
3.

Comment 1 Michael Greenberg 2011-02-03 13:13:32 UTC
Created attachment 476777 [details]
File: backtrace

Comment 2 Sergey Kurtsev 2011-02-06 19:02:47 UTC
Package: pidgin-2.7.9-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Canceled authorization request
2.
3.

Comment 3 abrt-bot 2012-03-20 16:46:25 UTC
Backtrace analysis found this bug to be similar to bug #702094, closing as duplicate.

Bugs which were found to be similar to this bug: bug #616246, bug #702094

This comment is automatically generated.

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


Note You need to log in before you can comment on or make changes to this bug.