Bug 1013033

Summary:	Glom cannot be started
Product:	[Fedora] Fedora	Reporter:	Derek P. Moore <derek.p.moore>
Component:	glom	Assignee:	Haïkel Guémar <karlthered>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	19	CC:	ben, diazbastian, karlthered, murrayc
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-09-05 14:19:17 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Derek P. Moore 2013-09-27 16:19:23 UTC

Description of problem:
Glom fails when attempting to start up.

Version-Release number of selected component (if applicable):
glom-1.22.1-4.fc19.x86_64

How reproducible:
Always.

Steps to Reproduce:
1. try to start glom
2. ???
3. CRASH

Actual results:
$ glom
bool GlomBakery::Document::write_to_disk(): m_file_uri is empty.

(glom:23309): glibmm-ERROR **: 
unhandled exception (type std::exception) in signal handler:
what: Error code from xmlParseChunk(): 111

Trace/breakpoint trap (core dumped)

Expected results:
Glom window

Additional info:

Comment 1 Murray Cumming 2013-10-21 08:18:43 UTC

This was caused by a change in libxml behaviour. This commit in Glom fixes it:
https://git.gnome.org/browse/glom/commit/?h=glom-1-22&id=6f01d7d8f79cd127418c2a4b234de670225fb71a


There are other fixes in the glom-1-22 branches, so it would be best to just update the package with the latest bugfix release (glom 1.22.3)


A couple of Fedora users reported this upstream:
https://bugzilla.gnome.org/show_bug.cgi?id=687996
https://bugzilla.gnome.org/show_bug.cgi?id=710358

Comment 2 Murray Cumming 2013-11-02 20:52:39 UTC

Does anyone know what we can do to get the Glom package updated?

Comment 3 Haïkel Guémar 2013-11-03 09:04:18 UTC

Sorry, i had hectic days, i'll push update this morning.
If there's an emergency, you can ping me on freenode (number80)

Comment 4 Fedora Update System 2013-11-03 10:46:22 UTC

glom-1.22.4-1.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/glom-1.22.4-1.fc19

Comment 5 Haïkel Guémar 2013-11-03 10:46:29 UTC

*** Bug 1022294 has been marked as a duplicate of this bug. ***

Comment 6 Murray Cumming 2013-11-03 19:27:03 UTC

Thanks.

Comment 7 Fedora Update System 2013-11-05 02:54:44 UTC

Package glom-1.22.4-1.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing glom-1.22.4-1.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-20641/glom-1.22.4-1.fc19
then log in and leave karma (feedback).