Bug 692871 - [abrt] gconf-cleaner-0.0.3-1.fc12: Process /usr/bin/gconf-cleaner was killed by signal 6 (SIGABRT)
Summary: [abrt] gconf-cleaner-0.0.3-1.fc12: Process /usr/bin/gconf-cleaner was killed ...
Keywords:
Status: CLOSED DUPLICATE of bug 714634
Alias: None
Product: Fedora
Classification: Fedora
Component: gconf-cleaner
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Orphan Owner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:9795c4df8974e876a8b7ef2d00a...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-01 13:16 UTC by Frank Ybanez
Modified: 2012-03-21 16:45 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-21 16:45:39 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (31.01 KB, text/plain)
2011-04-01 13:16 UTC, Frank Ybanez
no flags Details

Description Frank Ybanez 2011-04-01 13:16:19 UTC
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 31759 bytes
cmdline: gconf-cleaner
component: gconf-cleaner
Attached file: coredump, 41996288 bytes
crash_function: _gconf_cleaner_value_to_string
executable: /usr/bin/gconf-cleaner
kernel: 2.6.35.11-83.fc14.x86_64
package: gconf-cleaner-0.0.3-1.fc12
rating: 4
reason: Process /usr/bin/gconf-cleaner was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1301663700
uid: 500

comment
-----
GConf-Cleaner:ERROR:main.c:265:_gconf_cleaner_value_to_string: code should not be reached
Aborted (core dumped

How to reproduce
-----
1.again, just using the thing, running a gconf-cleaner (because some of my menus are missing), and the process just crashes.
2.
3.

Comment 1 Frank Ybanez 2011-04-01 13:16:22 UTC
Created attachment 489388 [details]
File: backtrace

Comment 2 abrt-bot 2012-03-21 16:45:39 UTC
Backtrace analysis found this bug to be similar to bug #714634, closing as duplicate.

This comment is automatically generated.

*** This bug has been marked as a duplicate of bug 714634 ***


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