Bug 756438 - [abrt] pidgin-2.10.0-3.fc16: __GI_raise: Process /usr/bin/pidgin was killed by signal 6 (SIGABRT)
Summary: [abrt] pidgin-2.10.0-3.fc16: __GI_raise: Process /usr/bin/pidgin was killed b...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: pidgin
Version: 16
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Stu Tomlinson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:2e740aba0ef852a35b1d52ba39b...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-23 15:19 UTC by Dorin Dragan
Modified: 2013-02-13 22:30 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-13 22:30:26 UTC
Type: ---


Attachments (Terms of Use)
File: environ (2.66 KB, text/plain)
2011-11-23 15:19 UTC, Dorin Dragan
no flags Details
File: dso_list (18.25 KB, text/plain)
2011-11-23 15:19 UTC, Dorin Dragan
no flags Details
File: smolt_data (3.30 KB, text/plain)
2011-11-23 15:19 UTC, Dorin Dragan
no flags Details
File: maps (50.79 KB, text/plain)
2011-11-23 15:19 UTC, Dorin Dragan
no flags Details
File: backtrace (39.90 KB, text/plain)
2011-11-23 15:19 UTC, Dorin Dragan
no flags Details

Description Dorin Dragan 2011-11-23 15:19:33 UTC
libreport version: 2.0.7
abrt_version:   2.0.6
backtrace_rating: 4
cmdline:        pidgin
crash_function: __GI_raise
executable:     /usr/bin/pidgin
kernel:         3.1.1-2.fc16.i686.PAE
pid:            21175
pwd:            /home/dorind
reason:         Process /usr/bin/pidgin was killed by signal 6 (SIGABRT)
time:           Wed 23 Nov 2011 04:38:34 PM EET
uid:            500
username:       dorind
var_log_messages: Nov 23 16:38:35 timi112 abrt[24185]: Saved core dump of pid 21175 (/usr/bin/pidgin) to /var/spool/abrt/ccpp-2011-11-23-16:38:34-21175 (15212544 bytes)

backtrace:      Text file, 40853 bytes
dso_list:       Text file, 18691 bytes
environ:        Text file, 2719 bytes
maps:           Text file, 52007 bytes
smolt_data:     Text file, 3377 bytes

xsession_errors:
:    JS ERROR: !!!     fileName = '"/usr/share/gnome-shell/extensions/pidgin.org/extension.js"'
:    JS ERROR: !!!     stack = '"([object Object])@/usr/share/gnome-shell/extensions/pidgin.org/extension.js:203
:    JS ERROR: !!!     fileName = '"/usr/share/gnome-shell/extensions/pidgin.org/extension.js"'
:    JS ERROR: !!!     stack = '"([object Object])@/usr/share/gnome-shell/extensions/pidgin.org/extension.js:203
:    JS ERROR: !!!     fileName = '"/usr/share/gnome-shell/extensions/pidgin.org/extension.js"'
:    JS ERROR: !!!     stack = '"([object Object])@/usr/share/gnome-shell/extensions/pidgin.org/extension.js:203
:    JS ERROR: !!!     fileName = '"/usr/share/gnome-shell/extensions/pidgin.org/extension.js"'
:    JS ERROR: !!!     stack = '"([object Object])@/usr/share/gnome-shell/extensions/pidgin.org/extension.js:203
:    JS ERROR: !!!     fileName = '"/usr/share/gnome-shell/extensions/pidgin.org/extension.js"'
:    JS ERROR: !!!     stack = '"([object Object])@/usr/share/gnome-shell/extensions/pidgin.org/extension.js:203
:    JS ERROR: !!!     fileName = '"/usr/share/gnome-shell/extensions/pidgin.org/extension.js"'
:    JS ERROR: !!!     stack = '"([object Object])@/usr/share/gnome-shell/extensions/pidgin.org/extension.js:203
:http://developer.pidgin.im/simpleticket/
:http://developer.pidgin.im/wiki/GetABacktrace

Comment 1 Dorin Dragan 2011-11-23 15:19:37 UTC
Created attachment 535519 [details]
File: environ

Comment 2 Dorin Dragan 2011-11-23 15:19:39 UTC
Created attachment 535520 [details]
File: dso_list

Comment 3 Dorin Dragan 2011-11-23 15:19:41 UTC
Created attachment 535521 [details]
File: smolt_data

Comment 4 Dorin Dragan 2011-11-23 15:19:43 UTC
Created attachment 535522 [details]
File: maps

Comment 5 Dorin Dragan 2011-11-23 15:19:46 UTC
Created attachment 535523 [details]
File: backtrace

Comment 6 abrt-bot 2012-03-20 16:40:58 UTC
Backtrace analysis found this bug to be similar to some already closed bugs from other components. You might want to check those bugs for additional information.

Bugs which were found to be similar to this bug: 
  NetworkManager: bug #680767
  atk: bug #637409
  ibus: bug #640886, bug #714198

This comment is automatically generated.

Comment 7 Fedora End Of Life 2013-01-16 17:39:18 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 8 Fedora End Of Life 2013-02-13 22:30:30 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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