Bug 700914 - [abrt] kdebase-6:4.6.2-1.fc14: g_assertion_message_error: Process /usr/bin/konqueror was killed by signal 6 (SIGABRT)
Summary: [abrt] kdebase-6:4.6.2-1.fc14: g_assertion_message_error: Process /usr/bin/ko...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: GConf2
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:eb45545b2c047003d6d86146bb1...
: 681025 707348 742031 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-29 19:25 UTC by Egon Kastelijn
Modified: 2012-08-16 15:36 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-16 15:36:22 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (17.95 KB, text/plain)
2011-04-29 19:25 UTC, Egon Kastelijn
no flags Details

Description Egon Kastelijn 2011-04-29 19:25:16 UTC
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 18383 bytes
cmdline: /usr/bin/konqueror --silent
component: kdebase
Attached file: coredump, 11636736 bytes
crash_function: g_assertion_message_error
executable: /usr/bin/konqueror
kernel: 2.6.35.12-90.fc14.x86_64
package: kdebase-6:4.6.2-1.fc14
rating: 4
reason: Process /usr/bin/konqueror was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1304104678
uid: 500

comment
-----
I started Konqueror.
I don't think I am able to reproduce this problem.
Note: I was having some strange problems with my system at that moment.
I had a run-away Eclipse process that was causing 100% cpu-usage and other strange behaviour, like:

$ ps fax
bash: fork: retry: Resource temporarily unavailable

How to reproduce
-----
1. I started Konqueror

Comment 1 Egon Kastelijn 2011-04-29 19:25:19 UTC
Created attachment 495849 [details]
File: backtrace

Comment 2 abrt-bot 2012-03-20 15:39:50 UTC
Backtrace analysis of bugs across components suggests the actual bug is in component GConf2 instead of component kdebase, reassigning to GConf2.

Bugs which were found to be similar to this bug: 
  GConf2: bug #742031
  gnome-screensaver: bug #681025, bug #707348

This comment is automatically generated.

Comment 3 abrt-bot 2012-03-20 15:39:59 UTC
*** Bug 707348 has been marked as a duplicate of this bug. ***

Comment 4 abrt-bot 2012-03-20 15:40:13 UTC
*** Bug 742031 has been marked as a duplicate of this bug. ***

Comment 5 abrt-bot 2012-03-20 15:40:24 UTC
*** Bug 681025 has been marked as a duplicate of this bug. ***

Comment 6 Fedora End Of Life 2012-08-16 15:36:26 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached 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" (top right of this page) 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


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