Update Manager is broken

Bug #1307238 reported by Kathy Kaskiw

This bug report was converted into a question: question #246982: Update Manager is broken.

10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
software-center (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

From the Update Manager, when I click "Install Updates" a dialog appears with the following:

"The package system is broken

Check if you are using third party repositories. If so disable them, since they are a common source of problems.
Furthermore run the following command in a Terminal: apt-get install -f

Details
The following packages have unmet dependencies:

libssl1.0.0: Depends: libc6 (>= 2.14) but 2.15-0ubuntu10.3 is installed
             Depends: zlib1g (>= 1:1.1.4) but 1:1.2.3.4.dfsg-3ubuntu4 is installed
libssl1.0.0:i386: Depends: libc6 (>= 2.7) but 2.15-0ubuntu10.3 is installed
                  Depends: zlib1g (>= 1:1.1.4) but 1:1.2.3.4.dfsg-3ubuntu4 is installed"

As instructed in the error message, from Terminal I executed:
$ sudo apt-get install -f

[sudo] password for hello:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following extra packages will be installed:
  libssl1.0.0:i386
The following packages will be upgraded:
  libssl1.0.0:i386
1 upgraded, 0 newly installed, 0 to remove and 9 not upgraded.
2 not fully installed or removed.
Need to get 0 B/1,009 kB of archives.
After this operation, 4,096 B of additional disk space will be used.
Do you want to continue [Y/n]?
E: Internal Error, No file name for libssl1.0.0

Launching the Software Center results in the following dialog to appear:
"Items cannot be installed or removed until the paclage catalog is repaired. Do you want to repair it now?
Once Update Manager has finished the repairs, you can close it and return to the store."
Clicking "Repair" displays the following dialog:
"Package operation failed
The installation or removal of a software package failed.
Details
installArchives() failed: Error in function:
dpkg: error processing libssl1.0.0 (--configure):
 libssl1.0.0:amd64 1.0.1-4ubuntu5.6 cannot be configured because libssl1.0.0:i386 is in a different version (1.0.1-4ubuntu5.5)
dpkg: error processing libssl1.0.0:i386 (--configure):
 libssl1.0.0:i386 1.0.1-4ubuntu5.5 cannot be configured because libssl1.0.0:amd64 is in a different version (1.0.1-4ubuntu5.6)"

In an attempt at self-help, I read through other Launchpad entries and tried :
$ sudo apt-get autoclean

Reading package lists... Done
Building dependency tree
Reading state information... Done
hello@Qwerty:~$ sudo apt-get --purge autoremove
Reading package lists... Done
Building dependency tree... 50%
Building dependency tree
Reading state information... Done
You might want to run 'apt-get -f install' to correct these.
The following packages have unmet dependencies:
 libssl1.0.0 : Breaks: libssl1.0.0:i386 (!= 1.0.1-4ubuntu5.6) but 1.0.1-4ubuntu5.5 is installed
 libssl1.0.0:i386 : Breaks: libssl1.0.0 (!= 1.0.1-4ubuntu5.5) but 1.0.1-4ubuntu5.6 is installed
E: Unmet dependencies. Try using -f.

Questions:
1) I am running a 64 bit installation. Why is a "i386" library being referenced?
2) How do I tell who is referencing the libssl1.0.0 package?
3) The Update Manager error message suggests: "Check if you are using third party repositories. If so disable them...". As far as I know no third party repositories are used. Why doesn't it display entries that should be disabled?
4) Shouldn't the Software Center allow the removal of a package?

Kind regards,
John

Revision history for this message
Manfred Hampl (m-hampl) wrote :

I doubt the validity of this bug report. The text has been copy/pasted from the question doucment https://answers.launchpad.net/ubuntu/+source/software-center/+question/222801 that is more than a year old, and that is aready solved.

In that question document the command sequence
sudo apt-get install --download-only libssl1.0.0:amd64 libssl1.0.0:i386
sudo dpkg -i /var/cache/apt/archives/libssl1.0.0_1.0.1-4ubuntu5.6_*.deb
resolved the problem.

To the reporter of that bug: What is your name? John or Kathy?
What is the output of the following terminal commands:

uname -a
lsb_release -a
sudo dpkg --audit

Changed in software-center (Ubuntu):
status: New → Incomplete
Revision history for this message
Kathy Kaskiw (kathy-kaskiw) wrote : Re: [Bug 1307238] Re: Update Manager is broken

Hi Manfred,

I'm not very tech savy, so I just cut paste John's bug report into mine
... none of it makes sense to me, but the messages John was getting are
the same I've been getting for about a year. On the weekend I thought I
should try and figure out what to do. I haven't been able to use my
Update Manager since then. I think it started shortly after the Ubuntu
version was updated.

This is a real bug report (my first one).

Thanks,

Kathy

On 14-04-14 01:56 AM, Manfred Hampl wrote:
> I doubt the validity of this bug report. The text has been copy/pasted
> from the question doucment https://answers.launchpad.net/ubuntu/+source
> /software-center/+question/222801 that is more than a year old, and that
> is aready solved.
>
> In that question document the command sequence
> sudo apt-get install --download-only libssl1.0.0:amd64 libssl1.0.0:i386
> sudo dpkg -i /var/cache/apt/archives/libssl1.0.0_1.0.1-4ubuntu5.6_*.deb
> resolved the problem.
>
> To the reporter of that bug: What is your name? John or Kathy?
> What is the output of the following terminal commands:
>
> uname -a
> lsb_release -a
> sudo dpkg --audit
>
> ** Changed in: software-center (Ubuntu)
> Status: New => Incomplete
>

Revision history for this message
Manfred Hampl (m-hampl) wrote :

I am converting that bug report into a question document, because that seems to me the better area for dealing with it.

Changed in software-center (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.