[SOLVED] E: Internal Error, No file name for libss2 messing up apt-get

User Name

Remember Me?

Password

UbuntuThis forum is for the discussion of Ubuntu Linux.

Notices

Welcome to LinuxQuestions.org, a friendly and active Linux Community.

You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!

Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.

If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.

Having a problem logging in? Please visit this page to clear all LQ-related cookies.

Introduction to Linux - A Hands on Guide

This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.

The title pretty much says it, whenever I use apt-get I get this message after it: "E: Internal Error, No file name for libss2" messing up apt-get. It doesn't let me apt-get install anything or apt-get remove either. apt-get update works fine, though. I recently upgraded from Ubuntu 11.10 to 12.04.

Last edited by timebirds; 06-02-2012 at 11:16 AM.

Click here to see the post LQ members have rated as the most helpful post in this thread.

aha, so it looks like "dpkg --audit" is telling you that there are a bunch of packages that failed to fully install. They are unpacked but not configured. I guess you never actually completed that upgrade you mentioned in your first post.
Try to configure all the pending packages with the following command:

Code:

sudo dpkg --configure --pending

The above command is one of the standard tools in recovering from a botched upgrade.

thanks evo2. I had the same issue with libslang2.....I have never used --audit, I always just use apt-get, and after some large dist-upgrades I tend to re-run it again to make sure it went OK since I sometimes don't hang around to watch the upgrade. Thanks timebirds for pointing me over to this thread too.