debconf failed to configure phpmyadmin for mysql
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
debconf (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
mysql-5.5 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
phpmyadmin (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
On phpmyadmin install debconf comes up two times.
The first time to ask which webserver should be utilized. -> This works.
The second time to configure the database for phpmyadmin with dbconfig-common. -> This works not.
Every time I agree debconf tells me to retry it(a dropdown menu with abort, retry, ignore).
Steps to reproduce:
1.Install apache2
2.Install mysql and set root account for it.
3.Install phpmyadmin
4.See during phpmyadmin installation debconf coming up for apache2 configuration(no problems there).
5.See during phpmyadmin installation debconf coming up for mysql configuration.
6.Choose to configure database with dbconfig-common.
7.See it failing.
Additional:
The mysql database is configured(with root account just with installation).
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: debconf 1.5.45ubuntu1
ProcVersionSign
Uname: Linux 3.5.0-6-generic x86_64
ApportVersion: 2.4-0ubuntu6
Architecture: amd64
Date: Sat Jul 28 19:31:12 2012
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120722)
InterpreterPath: /usr/bin/perl
PackageArchitec
ProcEnviron:
PATH=(custom, no username)
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: debconf
UpgradeStatus: No upgrade log present (probably fresh install)
Thank you for taking the time to report this bug and helping to make Ubuntu better.
If there is a bug here, it is mostly likely in phpmyadmin rather than debconf or mysql-5.5, so I'm rearranging the assignment accordingly.
But I could not reproduce this on the current version of Quantal. I followed your steps, except that on step 7, it worked. Please could you retest your steps on a fresh, fully upgraded installation of Quantal, and confirm that your exact steps do reproduce the problem? Once done, please change the bug status on phpmyadmin back to New.