Bug 814034 - [abrt] kde-baseapps-4.8.1-1.fc16: __GI_raise: Process /usr/bin/kdialog was killed by signal 6 (SIGABRT)
Summary: [abrt] kde-baseapps-4.8.1-1.fc16: __GI_raise: Process /usr/bin/kdialog was ki...
Alias: None
Product: Fedora
Classification: Fedora
Component: kde-baseapps
Version: 16
Hardware: i686
OS: Unspecified
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:2f60ac2d189443d2015e06c869d...
Depends On:
TreeView+ depends on / blocked
Reported: 2012-04-19 04:50 UTC by Kerry
Modified: 2013-02-13 23:32 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2013-02-13 23:32:21 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (10.58 KB, text/plain)
2012-04-19 04:50 UTC, Kerry
no flags Details
File: dso_list (6.56 KB, text/plain)
2012-04-19 04:51 UTC, Kerry
no flags Details
File: environ (4.20 KB, text/plain)
2012-04-19 04:51 UTC, Kerry
no flags Details
File: maps (21.53 KB, text/plain)
2012-04-19 04:51 UTC, Kerry
no flags Details

Description Kerry 2012-04-19 04:50:54 UTC
libreport version: 2.0.8
abrt_version:   2.0.7
backtrace_rating: 4
cmdline:        kdialog --geometry 200x200+100+2 --title 'NOW SCROBBLING:' --passivepopup 'Acid Mothers Temple|What\'s Your Name|Goodbye John Peel - Live in London 2004|371|1334806149' 10
crash_function: __GI_raise
executable:     /usr/bin/kdialog
kernel:         3.3.0-8.fc16.i686.PAE
pid:            31901
reason:         Process /usr/bin/kdialog was killed by signal 6 (SIGABRT)
time:           Thu 19 Apr 2012 13:29:14 EST
uid:            500
username:       nice
var_log_messages: Apr 19 13:29:16 politemadness abrt[31908]: Saved core dump of pid 31901 (/usr/bin/kdialog) to /var/spool/abrt/ccpp-2012-04-19-13:29:14-31901 (2408448 bytes)

backtrace:      Text file, 10836 bytes
dso_list:       Text file, 6722 bytes
environ:        Text file, 4298 bytes
maps:           Text file, 22044 bytes


Comment 1 Kerry 2012-04-19 04:50:59 UTC
Created attachment 578501 [details]
File: backtrace

Comment 2 Kerry 2012-04-19 04:51:01 UTC
Created attachment 578502 [details]
File: dso_list

Comment 3 Kerry 2012-04-19 04:51:03 UTC
Created attachment 578503 [details]
File: environ

Comment 4 Kerry 2012-04-19 04:51:05 UTC
Created attachment 578504 [details]
File: maps

Comment 5 Fedora End Of Life 2013-01-16 19:57:20 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: 

Comment 6 Fedora End Of Life 2013-02-13 23:32:24 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.