Red Hat Bugzilla – Bug 1013033
Glom cannot be started
Last modified: 2014-09-05 10:19:17 EDT
Description of problem:
Glom fails when attempting to start up.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. try to start 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)
This was caused by a change in libxml behaviour. This commit in Glom fixes it:
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:
Does anyone know what we can do to get the Glom package updated?
Sorry, i had hectic days, i'll push update this morning.
If there's an emergency, you can ping me on freenode (number80)
glom-1.22.4-1.fc19 has been submitted as an update for Fedora 19.
*** Bug 1022294 has been marked as a duplicate of this bug. ***
* 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:
then log in and leave karma (feedback).