Ubuntu

distupgrade crashed during conf file change review

Reported by Jonathan Riddell on 2010-10-08
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Critical
boogaerts marcel

Bug Description

Upgrading from 10.04 LTS to 10.10 the Dist Upgrade tool crashes. Running KDE frontend. Crash was when reviewing a conffile change.
Logs are at http://muse.19inch.net/~jr/tmp/dist-upgrade/

tags: added: iso-testing
Jonathan Riddell (jr) wrote :

This is the error

/usr/bin/python: symbol lookup error: /usr/lib/qt4/plugins/inputmethods/libqimsw-multi.so: undefined symbol: _ZN9QListData11detach_growEPii

So it's trying to load the input method module when the text area gets shown, but the Qt version has already been upgraded so it causes a symbol lookup error.

Jonathan Riddell (jr) on 2010-10-09
Changed in ubuntu:
status: New → Confirmed
importance: Undecided → Critical
Jonathan Riddell (jr) wrote :

TEST CASE: do a 10.04 LTS to 10.10 upgrade
with the old DistUpgrade version it will crash when viewing the conffile changes
with the new DistUpgrade version you will be unable to view the conffile changes

affects: ubuntu → update-manager (Ubuntu)
tags: added: verification-needed

Accepted into lucid-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Jonathan Riddell (jr) wrote :

Accepted into maverick-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Scott Kitterman (kitterman) wrote :

Worked here. Verified the other changes in the proposed update and they are fine too.

tags: added: verification-done
removed: verification-needed
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package update-manager - 1:0.142.20

---------------
update-manager (1:0.142.20) maverick-proposed; urgency=low

  [ Michael Vogt ]
  * UpdateManager/UpdateManager.py:
    - do not crash if the free space check fails (LP: #656881)
  * DistUpgrade/DistUpgrade.cfg:
    - add blcr-dkms to the "BadVersions" variable. The current blcr-dkms
      source will not build with 2.6.35. Adding it here will cause the
      upgrade to abort with a message if it is installed.
      It also means that if support for 2.6.35 is added to blcr-dkms via
      a SRU that will automatically unblock the upgrade (LP: #555729)
  * DistUpgrade/DistUpgradeViewGtk.py,
    DistUpgrade/DistUpgradeViewKDE.py,:
    - workaround dpkg not sending the correct filename on conffile
      prompts over the status-fd (LP: #656912)

  [ Jonathan Riddell ]
  * DistUpgrade/DistUpgradeViewKDE.py:
    - disable confDialogue.show_difference_button, workaround for
      "distupgrade crashed during conf file change review" (LP: #656876)
      requires release note that user needs to view changes manually on command line
 -- Jonathan Riddell <email address hidden> Sat, 09 Oct 2010 19:08:23 +0100

Changed in update-manager (Ubuntu):
status: Confirmed → Fix Released
Jonathan Riddell (jr) wrote :

copied to maverick-updates

Jonathan Riddell (jr) wrote :

I am testing a better workaround which shows then hides a text area at the start of the upgrade process thus loading the IM plugin before Qt gets upgraded

Jonathan Riddell (jr) wrote :

show then hide qtextarea idea didn't work, so we'll go with no conffile review and I'll add a release note

Greg (iskimj) wrote :

I've been upgrading my machines and ran into this bug and crash. It crashed when I tried to review the changes to my /etc/hdparm.conf file. On my other machines, I reviewed conf file changes without issue, but this was the only machine that I had a customized hdparm.conf file. I'm upgrading using the kubuntu alternate x86 image. I don't think this bug is fully resolved.

rihad (rihad) wrote :

OMG, the kpackagekit was on its way doing the upgrade, when I learned about this bug... About 33 minutes remain, then it will crash? Why is there no recommended way to do the dist-upgrade in the old way? Only through the buggy GUI: https://help.ubuntu.com/community/MaverickUpgrades/Kubuntu
This is embarrassing. I regret very much the day I went from Debian to Kubuntu.

Changed in update-manager (Ubuntu):
assignee: nobody → boogaerts marcel (boogaertsm)
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers