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
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)
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