Could not install the upgrades

Bug #66347 reported by Matt Gilbert
This bug report is a duplicate of:  Bug #67028: Could not install "firestarter". Edit Remove
6
Affects Status Importance Assigned to Milestone
firestarter (Ubuntu)
New
Undecided
Unassigned

Bug Description

Upgraded from Dapper to Edgy, downloaded packages.

In the fetching and installing the upgrades stage it failed to set up firestarter firewall and then displayed a message saying:

"The upgrade aborts now. Your system could be in an unstable state. A recovery was run (dpkg --configure -a).

Please report this bug against the 'update-manager' package and include the files is /var/log/dist-upgrade/ in the bugreport."

installArchives() failed

The last few lines of term.log are:

Setting up language-pack-gnome-en-base (6.10+20061011) ...
 * Reloading GNOME Display Manager configuration...
Setting up beep-media-player-dev (0.9.7.1+cvs20050803-1.1ubuntu1) ...
Setting up xlibs-dev (1.1) ...
Errors were encountered while processing:
 firestarter
edgy: Fatal IO error 9 (Bad file descriptor) on X server :0.0.
Setting up firestarter (1.0.3-1.2ubuntu3) ...
 * Starting the Firestarter firewall...
 * Starting the Firestarter firewall... [fail]
invoke-rc.d: initscript firestarter, action "start" failed.
dpkg: error processing firestarter (--configure):
 subprocess post-installation script returned error exit status 2

The last few lines from main.log are:

2006-10-16 08:53:51,800 DEBUG got a conffile-prompt from dpkg for file: '/etc/gdm/gdm.conf-custom'
2006-10-16 09:04:18,653 ERROR got an error from dpkg for pkg: 'firestarter': 'subprocess post-installation script returned error exit status 2
'
2006-10-16 09:09:29,239 WARNING no activity on terminal for 240 seconds (Configuring firestarter)

Tags: edgy-upgrade
Revision history for this message
Matt Gilbert (matt-scarfieflats) wrote :
Revision history for this message
Matt Gilbert (matt-scarfieflats) wrote :
Revision history for this message
Matt Gilbert (matt-scarfieflats) wrote :
Revision history for this message
Matt Gilbert (matt-scarfieflats) wrote :
description: updated
Revision history for this message
Philipp Schroeder (philipp.schroeder) wrote :

I got the same error message, but in a different context, see bug 68400 .

Revision history for this message
Vassilis Pandis (pandisv) wrote :

Thanks for the bug report. This particular bug has already been
reported into our bug tracking system, but please feel free to report
any further bugs which you find.

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.