Upgrading Dapper Server to Hardy Server crashes

Bug #240806 reported by diqrtvpe
2
Affects Status Importance Assigned to Milestone
gconf (Ubuntu)
Triaged
High
Unassigned
Hardy
Won't Fix
Undecided
Unassigned

Bug Description

My upgrade from Dapper Server to Hardy Server went fairly smoothly until, partway through the installation phase, I hit this error message:

(gconftool-2:21975): GConf-CRITICAL **: Failed to load file "/var/lib/gconf/defaults/%gconf-tree-dz.xml": Error on line 444 char 34: Invalid UTF-8 encoded text - not valid ' </entry>
                                        <entry name="cpuload_color4">
                                                <local_schema short_desc="???????????????????????????? ???????????????????">
                                                </local_schema>
                                        </entry>
                                        <entry name="cpuload_color3">
                                                <local_schema short_desc="??????????????? ???????????????? ????????????????? ????????????? ???????????????????"> </local_schema>
                                        </entry>
                                        <entry name="cpuload_color2">
                                                <local_schema short_desc="?????????????????????????? ?????????????????????????????? ???????????????????">
                                                </local_schema>
                                        </entry>
                                        <entry name="cpuload_color1">
                                 ??'
- not valid ' </entry>
(gconftool-2:21975): GConf-CRITICAL **: Failed to load file "/var/lib/gconf/defaults/%gconf-tree-br.xml": Error reading "/var/lib/gconf/defaults/%gconf-tree-br.xml": Input/output error
(gconftool-2:21975): GConf-CRITICAL **: Failed to load file "/var/lib/gconf/defaults/%gconf-tree-mk.xml": Error on line 1 char 1: Invalid UTF-8 encoded text - not a start char
(gconftool-2:21975): GConf-CRITICAL **: Failed to load ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????

The error was fatal, and the upgrade halted. There are now a number of configuration files, etc, which are no longer present or readable, making using the computer difficult.

Revision history for this message
diqrtvpe (ccollett) wrote :
Revision history for this message
diqrtvpe (ccollett) wrote :
Revision history for this message
diqrtvpe (ccollett) wrote :
Revision history for this message
diqrtvpe (ccollett) wrote :
Revision history for this message
diqrtvpe (ccollett) wrote :
Revision history for this message
Nick Ellery (nick.ellery) wrote :

Thanks for your report. Confirming report as the necessary files for debugging have been included.

Changed in update-manager:
status: Confirmed → Triaged
Michael Vogt (mvo)
Changed in update-manager:
importance: Undecided → High
Changed in gconf (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
Revision history for this message
Mitch Towner (kermiac) wrote :

unassigned Ubuntu Desktop Bugs

Changed in gconf (Ubuntu):
assignee: Ubuntu Desktop Bugs (desktop-bugs) → nobody
Revision history for this message
Rolf Leggewie (r0lf) wrote :

Hardy has seen the end of its life and is no longer receiving any updates. Marking the Hardy task for this ticket as "Won't Fix".

Changed in gconf (Ubuntu Hardy):
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.