Bug 659562 - [abrt] glom-1.16.1-1.fc14: g_mutex_free_posix_impl: Process /usr/bin/glom was killed by signal 6 (SIGABRT)
Summary: [abrt] glom-1.16.1-1.fc14: g_mutex_free_posix_impl: Process /usr/bin/glom was...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: glom
Version: 14
Hardware: x86_64
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Haïkel Guémar
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:9ec0d1e18110d479d32ba691790...
: 670183 678972 684497 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-12-03 00:57 UTC by Usama Akkad
Modified: 2012-08-16 18:37 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-08-16 18:37:34 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (27.27 KB, text/plain)
2010-12-03 00:57 UTC, Usama Akkad
no flags Details

Description Usama Akkad 2010-12-03 00:57:15 UTC
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: glom
component: glom
crash_function: g_mutex_free_posix_impl
executable: /usr/bin/glom
kernel: 2.6.35.6-48.fc14.x86_64
package: glom-1.16.1-1.fc14
rating: 4
reason: Process /usr/bin/glom was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1291334853
uid: 500

How to reproduce
-----
1.Start the program for the first time
2.Create database from template
3.Continue and the program will crash by it self

Comment 1 Usama Akkad 2010-12-03 00:57:21 UTC
Created attachment 464478 [details]
File: backtrace

Comment 2 Nazim Aliyev 2010-12-07 00:49:13 UTC
Package: glom-1.16.1-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.Open glom
2.Create empty document
3. Close and glom will crash

PS digging into this issue will give you updates when will find anything else

Comment 3 Doug Hutcheson 2010-12-28 04:22:41 UTC
Package: glom-1.16.1-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Running Glom for the first time on Fedora 14 just upgraded from 12


Comment
-----
Selected 'Small Business Example' from the new database options and clicked to proceed.

Comment 4 collura 2011-02-01 20:48:14 UTC
Package: glom-1.16.1-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. started glom
2. created one of sample instances
3. crashed

Comment 5 Murray Cumming 2011-07-22 18:23:41 UTC
The backtrace shows that the crash is happening in _gda_open_internal_sqlite_connection().

Bug #684497 seems to be a duplicate though I can't mark that here.

The Glom versions is too old. I (upstream) would rather not investigate until it can be reproduced with recent versions.

Comment 6 Ben Konrath 2011-07-23 02:49:05 UTC
*** Bug 670183 has been marked as a duplicate of this bug. ***

Comment 7 abrt-bot 2012-03-21 17:37:22 UTC
*** Bug 684497 has been marked as a duplicate of this bug. ***

Comment 8 abrt-bot 2012-03-21 17:37:32 UTC
*** Bug 678972 has been marked as a duplicate of this bug. ***

Comment 9 Fedora End Of Life 2012-08-16 18:37:37 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.