Bug 193650

Summary:	sun jdk fails to install with "select frontend other than noninteractive"
Product:	[Unmaintained] kpackagekit	Reporter:	nik <cosmicvisitor>
Component:	general	Assignee:	Toivo Pedaste <toivo>
Status:	RESOLVED DOWNSTREAM
Severity:	normal	CC:	cosmicvisitor, dantti12, echidnaman
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description nik 2009-05-22 16:54:43 UTC

Version:           unknown (using 4.2.2 (KDE 4.2.2), Kubuntu packages)
Compiler:          cc
OS:                Linux (i686) release 2.6.28-11-generic

When attempting to apply kpackage changes to install the sun-java6-jdk package,
the installation process fails with this error message:

----------------------------------------------------------------------------------------------------------------------
/var/cache/apt/archives/sun-java6-jre_6-13-1_all.deb
Preconfiguring packages ...
Preconfiguring packages ...
Preconfiguring packages ...
(Reading database ... 95507 files and directories currently installed.)
Unpacking sun-java6-jre (from .../sun-java6-jre_6-13-1_all.deb) ...

sun-dlj-v1-1 license could not be presented
try 'dpkg-reconfigure debconf' to select a frontend other than noninteractive
----------------------------------------------------------------------------------------------------------------------

The way I went around this is by using command line to install the package:
apt-get install sun-java6-jdk

This way the installer can show you the license dialog it requires, which is the reason it fails in the first place.
But this is just a workaround, as it is a misconfiguration issue. 

The installation should work out of the box, as in previous Kubuntu versions.

Users have to use "dpkg-reconfigure debconf" to change the preferred frontend to fix this, but why isn't KDE the default on Kubuntu anyway?

peace out

Comment 1 Jonathan Thomas 2009-05-22 20:22:18 UTC

Are you sure you didn't mean "KPackageKit"?
This is a known limitation of PackageKit in general (specifically the Debian packaging backend.)

Comment 2 nik 2009-05-23 20:13:43 UTC

Sorry, I meant KPackageKit indeed.

I think a very effective way to deal with it would be for the debconf to be configured to work with KDE (for Kubuntu only of course) out of the box.

Comment 3 Jonathan Thomas 2009-10-02 14:28:50 UTC

This is due to a limitation of the PackageKit project itself. (Not the KPackageKit GUI)