[Intrepid] Distribution Upgrade gets stuck on libapache2-mod-php5

[ANDREA]

Binary package hint: update-manager

Hi
Yesterday/today I tried to upgrade to Intrepid using the distrubution-upgrader. Well comparing to previous upgrades it worked very well up - up to the point where libapache3-mod-php5 tried to install. For some reason it simply got stuck, apparently it's because it tried to present a dialog that never showed up. I then killed the background process associated with it and of course other upgrades failed thereafter. I've run sudo dpkg --configure -a now so that should fix it.

Another application - virtualbox - asked me right in the console if I wanted to upgrade it. I think not everybody would check the console as a lot of people - such as myself - walk away during the upgrade. A possible improvement might be to skip certain upgrades that require user attention until the very end ... and then ask them together (or make a check beforehand) That way you can actually make an almost unattended upgrade :-)

Ok here's the promised console output:

Setting up php5-common (5.2.6-2ubuntu3) ...
Installing new version of config file /etc/cron.d/php5 ...
Setting up libapache2-mod-php5 (5.2.6-2ubuntu3) ...
debconf: unable to initialize frontend: Kde
debconf: (--- No method to call for :)
debconf: falling back to frontend: Dialog
debconf: unable to initialize frontend: Dialog
debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell buffer, or without a controlling terminal.)
debconf: falling back to frontend: Readline
Modified configuration file
---------------------------

looking forward to your responses and as usual if there are any questions don't hesitate to ask!

ANDREA

[Salze (stefan-sarzio)]

I've had a similar problem. It stuck at "Configuring landscape-common" with the same messages in the terminal log.

I then killed /usr/bin/python /usr/bin/landscape-sysinfo and the upgrade continued.

Those error messages appeared several times again in the terminal window. But it never got stuck again.

I will attach the logfiles from /var/log/dist-upgrade. First apt.log.

[Salze (stefan-sarzio)]

apt-term.log is empty.

Now main.log:

[Salze (stefan-sarzio)]

main_pre_req.log

[Salze (stefan-sarzio)]

And finally term.log

[Michael Vogt (mvo)]

@Salze: thanks, your bug is unreleated to the one reported here, but the logs showed whats the problem and it should be fixed in bzr now.

[Michael Vogt (mvo)]

@ANDREA: thanks for your bugreport. Could you please attach the full upgrade logs (/var/log/dist-upgrade/*)?

[ANDREA (andrea54)]

Ok it won't let me upload apt-term.log .... i've copied the content and pasted it into a new file.

[ANDREA (andrea54)]

Hi Michael
Thank you for your interest in this issue. I've attached all the files you requested; should you need anything else do not hesitate to ask!
thanks

ANDREA

[Launchpad Janitor (janitor)]

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

---------------
update-manager (1:0.93.26) intrepid; urgency=low

  * DistUpgrade/DistUpgradeController.py:
    - workaround kde tmpfile permissions (LP: #277431)
  * UpdateManager/Common/utils.py:
    - do not crash if gconfd is not availabe/unusable
      (LP: #281248)
  * DistUpgrade/DistUpgradeViewKDE.py:
    - do not use "kde" frontend during the upgrade, it
      crashes because of the kde3->kde4 transition
      if run at the wrong time (LP: #283942)
  * DistUpgrade/DistUpgradeView.py:
    - ignore SIGPIPE when forking the Dpkg::Pre-Install
      scripts to fix error with etckeeper (LP: #283642)

 -- Michael Vogt <email address hidden> Wed, 15 Oct 2008 22:03:05 +0200