breezy -> dapper update fails to preconfigure with exit status 20

Bug #41716 reported by Fabio Massimo Di Nitto
28
Affects Status Importance Assigned to Milestone
cupsys (Ubuntu)
Fix Released
High
Martin Pitt

Bug Description

Just plain breezy install and upgrade to dapper.

Fabio

Revision history for this message
Michael Vogt (mvo) wrote :

I can't reproduce this here on my auto-dist-upgrade tester (i386). What arch did that happen?

Thanks,
 Michael

Revision history for this message
Fabio Massimo Di Nitto (fabbione) wrote :

i386. I did use apt-get update && apt-get dist-upgrade from console.

Fabio

Revision history for this message
Martin Pitt (pitti) wrote :

It worked fine for me, too, however, I will do some more upgrading tests. '20' sounds like something debconf-ish.

Revision history for this message
Michael Vogt (mvo) wrote :

I have seen crashes when the debconf frontend is set to gnome during upgrades. The frontend crashs sometimes because of pango in a in-between-state.

Revision history for this message
Fabio Massimo Di Nitto (fabbione) wrote :

Micheal is it possible that the frontend is set to gnome at all on a fresh breezy install? If so upgrades on console will be all borked.

Fabio

Revision history for this message
Martin Pitt (pitti) wrote :

For the record, I can't reproduce this in a clean breezy->dapper upgrade in pbuilder either. Seems that needs a properly installed breezy and DEBCONF_DEBUG=developer.

Revision history for this message
Emmanuel Touzery (emmanuel-touzery) wrote :

i can confirm that. it happened to me yesterday when i upgraded my breezy to dapper. but the message was quite hidden, using the ubuntu update manager with -d switch to update to dapper, the error is "hidden" you only see it if you open the terminal. and it didn't stop the ugprade process. it didn't seem to have much consequence for my upgrade which ran smoothly otherwise.

i did change my cupsd.conf file by hand in breezy and later the upgrade process breezy->dapper, i was asked me whether i want to keep my changes or take the new cupsd.conf from dapper. i chose the dapper file, but i kept the diff my file<->dapper default if that can help you.

i didn't test printing yet, i hope i won't have problems connected to that :-/
i don't know if the update manager deleted log files about the upgrade, too. if it didn't (i already rebooted in dapper) and if they can help, i'll be glad to send them (just tell me where they are ;-) ).

Revision history for this message
Emmanuel Touzery (emmanuel-touzery) wrote :

btw, i386. my computer was a hoary beta dist-upgraded to breezy beta now dist-upgraded to dapper beta.
maybe it only happens with breezy that was dist-upgraded for hoary or breezy that was installed as beta and not from the release CD?

Revision history for this message
Bob (tpf) wrote :

I did breezy - dapper upgrade over dial-up ( about 16hr/day x 5 days), just finished this afternoon. Used ubuntu update manager with -d switch. Notice that cups message on terminal during install session. However the startup is stalling so I will continue looking at other feedback..

My machine - AMD, had breezy k7 with ubuntu and KDE installed later

Revision history for this message
Emmanuel Touzery (emmanuel-touzery) wrote :

btw, for what it's worth. i got the message when upgrading with "-d", but then install went fine as i already said and i can print now (at least from local computer, didn't try network yet).
so for me the warning didn't seem to have ill effects. it's true that i chose to overwrite my cupsd.conf.

Revision history for this message
Michael Vogt (mvo) wrote :

Could you please attach the /var/log/dist-upgrade*.log files to this bugreport? This may help diagnosing the problem.

@Fabbio: to my knowledge the debconf frontend is not set to gnome for new installs. Synaptic and the dist-upgrade tool set it explicitly (via the environment) before performing apt installs though.

Thanks,
 Michael

Revision history for this message
Emmanuel Touzery (emmanuel-touzery) wrote : my dist-upgrade logs

you can see the message "cupsys failed to preconfigure, with exit status 20" in dist-upgrade-term.log

otherwise as i said my upgrade went well appart from that message and my printer works fine after the ugprade.

Martin Pitt (pitti)
Changed in cupsys:
assignee: nobody → pitti
status: Unconfirmed → In Progress
Revision history for this message
Martin Pitt (pitti) wrote :

 cupsys (1.1.99.rc3-0ubuntu3) dapper; urgency=low
 .
   * debian/cupsys.config: Print migration note to stderr, not stdout, to not
     confuse debconf. Closes: LP#41716
   * debian/cupsys.postinst: Fix ownership of files in /var/cache/cups/ so that
     they are writable by non-root cupsd. Earlier dapper versions got the
     ownership wrong, so fix this for intra-dapper upgrades. Closes: LP#40795
   * Add debian/local/{sharing_status,enable_sharing}: Scripts to control
     printer sharing (by opening or closing the TCP port). Thanks to Ante
     Karamatić for his initial scripts and research!

Changed in cupsys:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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