Error on configuring

Bug #1456396 reported by Removed by request
52
This bug affects 15 people
Affects Status Importance Assigned to Milestone
debconf (Ubuntu)
Confirmed
Undecided
Unassigned
openssl (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I'm using Ubuntu 15.10 dev with libssl1.0.0 1.0.2a-1ubuntu1 and on upgrading the system I'm getting this error if libssl1.0.0 gets configured:

root@ubuntu:~# dpkg --configure libssl1.0.0
Setting up libssl1.0.0:amd64 (1.0.2a-1ubuntu1) ...
Checking for services that may need to be restarted...done.
Checking for services that may need to be restarted...done.
Checking init scripts...
debconf: Unable to load Debconf::Element::Dialog. Failed because: Can't locate Debconf/Element/Dialog.pm in @INC (you may need to install the Debconf::Element::Dialog module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.20.2 /usr/local/share/perl/5.20.2 /usr/lib/x86_64-linux-gnu/perl5/5.20 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.20 /usr/share/perl/5.20 /usr/local/lib/site_perl .) at (eval 19) line 2, <GEN1> line 2.
BEGIN failed--compilation aborted at (eval 19) line 2, <GEN1> line 2.

Can't locate object method "new" via package "Debconf::Element::Dialog" (perhaps you forgot to load "Debconf::Element::Dialog"?) at /usr/share/perl5/Debconf/FrontEnd.pm line 68, <GEN1> line 2.
dpkg: error processing package libssl1.0.0:amd64 (--configure):
 subprocess installed post-installation script returned error exit status 2
Errors were encountered while processing:
 libssl1.0.0:amd64

Revision history for this message
Seth Arnold (seth-arnold) wrote :

Try adding DEBIAN_FRONTEND=readline to the command line:

# DEBIAN_FRONTEND=readline dpkg --configure libssl1.0.0

I suspect this isn't related to openssl.

Thanks

Changed in openssl (Ubuntu):
status: New → Incomplete
Revision history for this message
Removed by request (removed3425744) wrote :

Now I'm getting this:

root@ubuntu:~# DEBIAN_FRONTEND=readline dpkg --configure libssl1.0.0
Setting up libssl1.0.0:amd64 (1.0.2a-1ubuntu1) ...
Checking for services that may need to be restarted...done.
Checking for services that may need to be restarted...done.
Checking init scripts...
debconf: Unable to load Debconf::Element::Teletype. Failed because: Can't locate Debconf/Element/Teletype.pm in @INC (you may need to install the Debconf::Element::Teletype module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.20.2 /usr/local/share/perl/5.20.2 /usr/lib/x86_64-linux-gnu/perl5/5.20 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.20 /usr/share/perl/5.20 /usr/local/lib/site_perl .) at (eval 22) line 2, <GEN1> line 2.
BEGIN failed--compilation aborted at (eval 22) line 2, <GEN1> line 2.

Can't locate object method "new" via package "Debconf::Element::Teletype" (perhaps you forgot to load "Debconf::Element::Teletype"?) at /usr/share/perl5/Debconf/FrontEnd.pm line 68, <GEN1> line 2.
dpkg: error processing package libssl1.0.0:amd64 (--configure):
 subprocess installed post-installation script returned error exit status 2
Errors were encountered while processing:
 libssl1.0.0:amd64

Changed in openssl (Ubuntu):
status: Incomplete → New
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in debconf (Ubuntu):
status: New → Confirmed
Changed in openssl (Ubuntu):
status: New → Confirmed
Revision history for this message
Adrien Nader (adrien-n) wrote :

I'm going to mark this bug as a Invalid on the openssl side since the issue is more likely with debconf or at least makes more sense to handle from there or the like.

Btw, I've gone over many years of openssl tickets on launchpad and I've marked several tickets as duplicate of this bug, which explains the high karma/affects.

Changed in openssl (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
Adrien Nader (adrien-n) wrote :

And searching for "new" on the debconf tracker returns a number of other results.

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.