package startupmanager 1.9.13-5 failed to install/upgrade: package startupmanager is already installed and configured

[Rehan Anis]

The package startupmanager failed to install with the the message that it is already installed

ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: startupmanager 1.9.13-5
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
NonfreeKernelModules: fglrx
AptOrdering:
 menu: Configure
 startupmanager: Configure
Architecture: i386
Date: Tue Jul 12 14:26:12 2011
DpkgTerminalLog:
 dpkg: error processing menu (--configure):
  package menu is already installed and configured
 dpkg: error processing startupmanager (--configure):
  package startupmanager is already installed and configured
ErrorMessage: package startupmanager is already installed and configured
PackageArchitecture: all
SourcePackage: dpkg
Title: package startupmanager 1.9.13-5 failed to install/upgrade: package startupmanager is already installed and configured
UpgradeStatus: No upgrade log present (probably fresh install)

[Raphaël Hertzog (hertzog)]

We need the complete upgrade log where you saw this error message, without it this bug cannot be further investigated.

[Rehan Anis (anisrehan)]

I don't know what logs are required, but following are what I thought could be required
/var/log/dpkg.log
/var/log/apt/history.log
/var/aptitude

[Raphaël Hertzog (hertzog)]

We need a log of the "terminal" where we see the output of the calls to dpkg. I think it's /var/log/apt/term.log or something like that (I can't remember).

[Rehan Anis (anisrehan)]

Well, get it this time.
its /var/log/apt/term.log

[Raphaël Hertzog (hertzog)]

Thank you, that was the right file. It looks like "apt" is the culprit. It installs both packages entirely and then tries to configure it a second time for no good reason. It's weird because apt usually does unpack + configure in 2 steps, and here it looks like it called "dpkg -i" directly for those 2 packages (see extract below). Thus I'm reassigning this bug.

Log started: 2011-07-12 14:25:40
Selecting previously deselected package menu.

199802 files and directories currently installed.)

Unpacking menu (from .../menu_2.1.44ubuntu1_i386.deb) ...

Selecting previously deselected package startupmanager.

Unpacking startupmanager (from .../startupmanager_1.9.13-5_all.deb) ...

Processing triggers for man-db ...

Processing triggers for install-info ...

Processing triggers for doc-base ...

Processing 1 added doc-base file(s)...

Registering documents with scrollkeeper...

Processing triggers for python-gmenu ...

Rebuilding /usr/share/applications/desktop.en_US.UTF8.cache...

Processing triggers for bamfdaemon ...

Rebuilding /usr/share/applications/bamf.index...

Processing triggers for desktop-file-utils ...

Processing triggers for python-support ...

Setting up menu (2.1.44ubuntu1) ...

Processing triggers for menu ...

Setting up startupmanager (1.9.13-5) ...

Processing triggers for menu ...

Processing triggers for python-support ...

Log ended: 2011-07-12 14:26:09

Log started: 2011-07-12 14:26:11
dpkg: error processing menu (--configure):

 package menu is already installed and configured

dpkg: error processing startupmanager (--configure):

 package startupmanager is already installed and configured

Errors were encountered while processing:

 menu

 startupmanager

Log ended: 2011-07-12 14:26:12

[Michael Vogt (mvo)]

This part of the log looks like apt was of the opinion that the package was unconfigured and did its recovery:

Log started: 2011-07-12 14:26:11
dpkg: error processing menu (--configure):

 package menu is already installed and configured

dpkg: error processing startupmanager (--configure):

 package startupmanager is already installed and configured

Errors were encountered while processing:

 menu

 startupmanager

Log ended: 2011-07-12 14:26:12

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 541595, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.