Bug 836758 - [abrt] pidgin-2.10.2-1.fc17: __GI_raise: Process /usr/bin/pidgin was killed by signal 6 (SIGABRT)
[abrt] pidgin-2.10.2-1.fc17: __GI_raise: Process /usr/bin/pidgin was killed b...
Product: Fedora
Classification: Fedora
Component: pidgin (Show other bugs)
x86_64 Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Stu Tomlinson
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2012-06-30 19:55 EDT by gerfert
Modified: 2013-08-01 07:10 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-08-01 07:10:16 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (103.82 KB, text/plain)
2012-06-30 19:55 EDT, gerfert
no flags Details
File: xsession_errors (106 bytes, text/plain)
2012-06-30 19:55 EDT, gerfert
no flags Details
File: maps (131.17 KB, text/plain)
2012-06-30 19:55 EDT, gerfert
no flags Details
File: dso_list (46.14 KB, text/plain)
2012-06-30 19:55 EDT, gerfert
no flags Details
File: build_ids (11.81 KB, text/plain)
2012-06-30 19:55 EDT, gerfert
no flags Details

  None (edit)
Description gerfert 2012-06-30 19:55:42 EDT
libreport version: 2.0.10
abrt_version:   2.0.10
backtrace_rating: 4
cmdline:        pidgin
crash_function: __GI_raise
executable:     /usr/bin/pidgin
kernel:         3.3.4-5.fc17.x86_64
pid:            5050
pwd:            /home/pupoque
time:           Вс. 01 июля 2012 03:41:07
uid:            1000
username:       pupoque
var_log_messages: Jul  1 03:41:08 lenovko abrt[5063]: Saved core dump of pid 5050 (/usr/bin/pidgin) to /var/spool/abrt/ccpp-2012-07-01-03:41:07-5050 (42479616 bytes)

backtrace:      Text file, 106316 bytes
build_ids:      Text file, 12095 bytes
dso_list:       Text file, 47243 bytes
maps:           Text file, 134320 bytes
xsession_errors: Binary file, 106 bytes


:a4ec59d7fc9c453fb4287d7ebc5fcf6579792e65 0x35965 raise libc.so.6 -
:a4ec59d7fc9c453fb4287d7ebc5fcf6579792e65 0x37118 abort libc.so.6 -
:29be652d1c987706c1b77542f9dbe6d4c84beaff 0x8dc8a - [exe] -

:'IMSETTINGS_MODULE=X compose table'
:'LESSOPEN=||/usr/bin/lesspipe.sh %s'

:Limit                     Soft Limit           Hard Limit           Units     
:Max cpu time              unlimited            unlimited            seconds   
:Max file size             unlimited            unlimited            bytes     
:Max data size             unlimited            unlimited            bytes     
:Max stack size            8388608              unlimited            bytes     
:Max core file size        0                    unlimited            bytes     
:Max resident set          unlimited            unlimited            bytes     
:Max processes             1024                 15856                processes 
:Max open files            1024                 4096                 files     
:Max locked memory         65536                65536                bytes     
:Max address space         unlimited            unlimited            bytes     
:Max file locks            unlimited            unlimited            locks     
:Max pending signals       15856                15856                signals   
:Max msgqueue size         819200               819200               bytes     
:Max nice priority         0                    0                    
:Max realtime priority     0                    0                    
:Max realtime timeout      unlimited            unlimited            us        

:pos:	0
:flags:	0100000
:pos:	6196
:flags:	0102002
:pos:	6196
:flags:	0102002
:pos:	0
:flags:	02
:pos:	0
:flags:	02
:pos:	0
:flags:	02004002
:pos:	0
:flags:	02004002
:pos:	0
:flags:	02004002
:pos:	0
:flags:	02
:pos:	0
:flags:	02004002
:pos:	0
:flags:	02000002
:pos:	0
:flags:	02004002
:pos:	0
:flags:	0100002
:pos:	0
:flags:	02004002
:pos:	0
:flags:	00
Comment 1 gerfert 2012-06-30 19:55:45 EDT
Created attachment 595487 [details]
File: backtrace
Comment 2 gerfert 2012-06-30 19:55:47 EDT
Created attachment 595488 [details]
File: xsession_errors
Comment 3 gerfert 2012-06-30 19:55:49 EDT
Created attachment 595489 [details]
File: maps
Comment 4 gerfert 2012-06-30 19:55:51 EDT
Created attachment 595490 [details]
File: dso_list
Comment 5 gerfert 2012-06-30 19:55:53 EDT
Created attachment 595491 [details]
File: build_ids
Comment 6 Fedora End Of Life 2013-07-03 23:30:41 EDT
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 '17'.

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 17'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 17 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  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

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.
Comment 7 Fedora End Of Life 2013-08-01 07:10:21 EDT
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.