Bug 1113949

Summary: Error code from xmlParseChunk(): 111
Product: [Fedora] Fedora Reporter: Enolynn <enolynn>
Component: glomAssignee: Haïkel Guémar <karlthered>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: karlthered, murrayc, ToddAndMargo
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-21 16:57:24 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:
Embargoed:
Attachments:
Description Flags
core dump that ABRT can't send none

Description Enolynn 2014-06-27 10:15:42 UTC 
Created attachment 912747 [details]
core dump that ABRT can't send

Description of problem:
Start glom in terminal (because it don't start with desktop link). An error was return and Glom don't start (Error code from xmlParseChunk(): 111).


Version-Release number of selected component (if applicable):
Glom 1.22.1-6.fc20 for x86_64 system


How reproducible:
Simply start Glom in terminal... and it don't start :)


Actual results:
In terminal :
glibmm-ERROR **: unhandled exception (type std::exception) in signal handler:
what: Error code from xmlParseChunk(): 111
Comment 1 Enolynn 2014-06-27 10:23:54 UTC 
And I don't see (my eyes don't open this morning), but after run "$ glom" in terminal, the error say exactly :

bool GlomBakery::Document::write_to_disk(): m_file_uri is empty.

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

Trappe pour point d'arrêt et de trace (core dumped)
Comment 2 Murray Cumming 2014-07-17 20:44:24 UTC 
Apparently this update (to 1.24) has not actually got into Fedora 20:
https://bugzilla.redhat.com/show_bug.cgi?id=1022294#c8

And I guess that the fix for the same problem in Fedora 19 for Glom 1.22 is not in Fedora 20 (assuming that it's the same problem - it looks the same):
https://bugzilla.redhat.com/show_bug.cgi?id=1013033#c7