Bug 479572 - yum-updating evolution gives errors about XML in %gconf-tree-dz.xml
Summary: yum-updating evolution gives errors about XML in %gconf-tree-dz.xml
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 10
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-01-11 15:35 UTC by David Tonhofer
Modified: 2009-03-08 13:06 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-03-08 13:06:26 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Yum output on the command line (9.81 KB, text/plain)
2009-01-11 15:35 UTC, David Tonhofer
no flags Details

Description David Tonhofer 2009-01-11 15:35:40 UTC
Created attachment 328662 [details]
Yum output on the command line

Description of problem:

Running yum update yields:

---------------
Updating: evolution 16/104 

(gconftool-2:3641): GConf-CRITICAL **: Failed to load file "/etc/gconf/gconf.xml.defaults/%gconf-tree-dz.xml": Error on line 5906 char 77: Invalid UTF-8 encoded text - not valid (followed by XML dump)

(gconftool-2:3647): GConf-CRITICAL **: Failed to load file "/etc/gconf/gconf.xml.defaults/%gconf-tree-or.xml": Error on line 2266 char 112: Odd character '\u001a', expected a '>' or '/' character to end the start tag of element 'local_schema', or optionally an attribute; perhaps you used an invalid character in an attribute name

(gconftool-2:3647): GConf-CRITICAL **: Failed to load file "/etc/gconf/gconf.xml.defaults/%gconf-tree-sk.xml": Error on line 614 char 33: Invalid UTF-8 encoded text - not valid (followed by XML dump)
---------------

Apparently, evolution was installed anyway.

Version-Release number of selected component (if applicable):

evolution-2.24.2-3.fc10.x86_64

How reproducible:

Once

Comment 1 Matthew Barnes 2009-01-27 17:44:52 UTC
Looks like translation issues in GConf schemas.

Did you happen to see this again when updating to 2.24.3?

Comment 2 David Tonhofer 2009-01-27 18:51:13 UTC
No, I don't think so. I wasn't specifically checking, but I can't remember seeing it.

Comment 3 Mike Chambers 2009-03-07 15:17:42 UTC
Does this need to remain open or can it be closed?  Has this been fixed since then?

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 4 David Tonhofer 2009-03-08 12:22:22 UTC
Can be closed. Didn't reappear and no further problems encountered.

Additionally I had undetected RAM problems at the time, which may or may not have something to do with this error.


Note You need to log in before you can comment on or make changes to this bug.