Bug 608182 - [abrt] crash in pidgin-2.7.1-1.fc12: raise: Process /usr/bin/pidgin was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in pidgin-2.7.1-1.fc12: raise: Process /usr/bin/pidgin was kille...
Keywords:
Status: CLOSED DUPLICATE of bug 601650
Alias: None
Product: Fedora
Classification: Fedora
Component: pidgin
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Warren Togami
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:f6f676f4c5236bd194e46abe7ee...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-25 21:52 UTC by Rob
Modified: 2010-06-26 01:16 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-06-26 01:16:05 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (41.92 KB, text/plain)
2010-06-25 21:52 UTC, Rob 		no flags Details
View All

Description Rob 2010-06-25 21:52:45 UTC 
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: pidgin
comment: No real steps to follow, Pidgin simply appears to be crashing out at random since today's update, which included an update for Pidgin.  I first thought it may be due to custom smileys being loaded, but before the second crash no smileys were used in any of my chats
component: pidgin
crash_function: raise
executable: /usr/bin/pidgin
global_uuid: f6f676f4c5236bd194e46abe7ee43097bed14520
kernel: 2.6.32.14-127.fc12.i686
package: pidgin-2.7.1-1.fc12
rating: 4
reason: Process /usr/bin/pidgin was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1.
2.
3.
Comment 1 Rob 2010-06-25 21:52:47 UTC 
Created attachment 427003 [details]
File: backtrace
Comment 2 Rob 2010-06-25 21:54:39 UTC 
Also worth noting that before today's update (allowing all available updates to be applied on a daily basis, as and when available), Pidgin has never once crashed on this system.
Comment 3 Stu Tomlinson 2010-06-26 01:16:05 UTC 

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