adept manager unable to install /var/cache/apt/archives/mysql-server_5.0.67-0ubuntu6_all.deb

[Greg Rundlett]

Binary package hint: update-manager

subprocess pre-installation script returned error exit status 1
subprocess new pre-removal script returned error exit status 1

This error was during the system upgrade from 8.4 to 8.10
i.e. I entered
kdesudo "adept_manager --dist-upgrade"
to do the upgrade.

If it makes a difference, I had mysql-server running at the time (as it is normally running on this machine)

[Michael Vogt (mvo)]

Thanks for your bugreport.

Could you please attach the files in /var/log/dist-upgrade/* to this bugreport?

[Greg Rundlett (greg.rundlett)]

The log files are attached.

Here is some additional information from Adept while doing the upgrade:

Commit failed.
To continue, hit ok and we will try to recover. If you close the application now, we will not do anything and you may try to resolve the problem manually.
(If you suspect this is a bug in Adept, please also provide the following exception description in the report).

The error was:
APT Error. Context:
    Running dpkg,
    [ /usr/bin/dpkg, --status-fd, 3, --unpack, /var/cache/apt/archives/mysql-server-5.0_5.0.67-0ubuntu6_i386.deb, /var/cache/apt/archives/kcalc_4-0x1.91ff4bf890bf4p-1494.1.2-0ubuntu5_i386.deb, /var/cache/apt/archives/kcharselect_4-0x1.91ff4bf890bf4p-1494.1.2-0ubuntu5_i386.deb, /var/cache/apt/archives/kdessh_4-0x1.91ff4bf890bf4p-1494.1.2-0ubuntu5_i386.deb, /var/cache/apt/archives/kdf_4-0x1.91ff4bf890bf4p-1494.1.2-0ubuntu5_i386.deb, /var/cache/apt/archives/kfloppy_4-0x1.91ff4bf890bf4p-1494.1.2-0ubuntu5_i386.deb, /var/cache/apt/archives/kgpg_4-0x1.91ff4bf890bf4p-1494.1.2-0ubuntu5_i386.deb, /var/cache/apt/archives/ktimer_4-0x1.91ff4bf890bf4p-1494.1.2-0ubuntu5_i386.deb, /var/cache/apt/archives/kwalletmanager_4-0x1.91ff4bf890bf4p-1494.1.2-0ubuntu5_i386.deb, /var/cache/apt/archives/sweeper_4-0x1.91ff4bf890bf4p-1494.1.2-0ubuntu5_i386.deb, /var/cache/apt/archives/kdeutils_4-0x1.91ff4bf890bf4p-1494.1.2-0ubuntu5_all.deb, /var/cache/apt/archives/kjots_4-0x1.91ff4bf890bf4p-1494.1.2-0ubuntu2_i386.deb ],
    Sup-process returned error code 1,
    Error processing /var/cache/apt/archives/kdf_4%3a4.1.2-0ubuntu5_i386.deb : trying to overwrite `/usr/share/applications/kde4/kwikdisk.desktop', which is also in package kwikdisk-kde4.

then this...

It seems that the recovery has failed. Please fix manually (try dpkg --configure -a and/or apt-get -f install) in terminal...

The error was:
APT Error. Context:
    Running dpkg,
    [ /usr/bin/dpkg, --status-fd, 3, --configure, -a ],
    Sup-process returned error code 1,
    Error processing kdeutils : dependency problems - leaving unconfigured.

There definitely seemed to be a problem with MySQL, but there was also a problem with kdeutils. I believe the kdeutils problems were fixed with subsequent releases b/c I was able to get that resolved within a day by applying new package updates.

First MySQL Server didn't install, but after a reboot and updating the available packages, it seems that MySQL server got updated.

I'd give more details about how and when MySQL got fixed, but there is no history file in adept like there is in synaptic. It is also confusing because Adept does not show any knowledge of a package called "mysql-server" if you search for it.

Linux greg-laptop 2.6.27-7-generic #1 SMP Thu Oct 30 04:18:38 UTC 2008 i686 GNU/Linux

[Greg Rundlett (greg.rundlett)]

So, looking at the log files in /var/log/dist-upgrade, it appears that the problems all trace back to the "stop" command failing to stop the currently installed mysqld

[Mathias Gug (mathiaz)]

On Mon, Nov 03, 2008 at 02:30:22PM -0000, Greg wrote:
> So, looking at the log files in /var/log/dist-upgrade, it appears that
> the problems all trace back to the "stop" command failing to stop the
> currently installed mysqld

Could you look into /var/log/daemon.log file? There should be more
information about the failure to stop mysql server.

  status incomplete

--
Mathias Gug
Ubuntu Developer http://www.ubuntu.com

[Mathias Gug (mathiaz)]

 We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!