Bug 684497 - [abrt] glom-1.16.2-1.fc14: g_mutex_free_posix_impl: Process /usr/bin/glom was killed by signal 6 (SIGABRT)
Summary: [abrt] glom-1.16.2-1.fc14: g_mutex_free_posix_impl: Process /usr/bin/glom was...
Keywords:
Status: CLOSED DUPLICATE of bug 659562
Alias: None
Product: Fedora
Classification: Fedora
Component: glom
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Haïkel Guémar
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:651d3ba9005849bcc8e9f855a6f...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-13 03:18 UTC by musicalboss
Modified: 2012-03-21 17:37 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-21 17:37:22 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (23.54 KB, text/plain)
2011-03-13 03:18 UTC, musicalboss
no flags Details

Description musicalboss 2011-03-13 03:18:17 UTC
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 24105 bytes
cmdline: glom
component: glom
Attached file: coredump, 41889792 bytes
crash_function: g_mutex_free_posix_impl
executable: /usr/bin/glom
kernel: 2.6.35.11-83.fc14.i686
package: glom-1.16.2-1.fc14
rating: 4
reason: Process /usr/bin/glom was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1299983401
uid: 500

How to reproduce
-----
1.Crashed on starting the application
2.
3.

Comment 1 musicalboss 2011-03-13 03:18:22 UTC
Created attachment 483943 [details]
File: backtrace

Comment 2 Murray Cumming 2011-07-22 18:21:00 UTC
This seems to be a duplicate of bug #659562 , though I don't seem to have access rights to make it as a duplicate.

Comment 3 abrt-bot 2012-03-21 17:37:22 UTC
Backtrace analysis found this bug to be similar to bug #659562, closing as duplicate.

Bugs which were found to be similar to this bug: bug #659562, bug #670183, bug #678972

This comment is automatically generated.

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


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