apt-get broken, packages not fully installed or removed

[Charles Hallenbeck]

Hi list,

I am running Debian unstable without x, except that some console apps
seem to require some of the x infrastructure. Lately my apt-get upgrade,
dist-upgrade, install, and remove all seem to fail because of a package
or two that are neither fully installed or removed. I can't seem to find
A handle on this problem, and hope someone can suggest how to fix it, or
how to get more info about it.

Below are snapshots of two failed apt-get comands. The first is an
apt-get dist-upgrade, issued after a normal apt-get update. The second
is from the apt-get -f install command without specifying any packages.

Snapshot 1: apt-get dist-upgrade

Script started on Wed 14 Jun 2006 04:48:03 AM EDT

Reading package lists... 0%

Reading package lists... 100%

Reading package lists... Done


Building dependency tree... 0%

Building dependency tree... 0%

Building dependency tree... 50%

Building dependency tree... 50%

Building dependency tree... Done

You might want to run `apt-get -f install' to correct these.
The following packages have unmet dependencies:
libice6: Depends: x11-common but it is not installed
libsm6: Depends: x11-common but it is not installed
libx11-6: PreDepends: x11-common (>= 1:7.0.0) but it is not installed
libx11-data: PreDepends: x11-common (>= 1:7.0.0) but it is not installed
libxau6: Depends: x11-common but it is not installed
libxaw7: Depends: x11-common but it is not installed
libxdmcp6: Depends: x11-common (>= 1:7.0) but it is not installed
libxext6: Depends: x11-common but it is not installed
libxfixes3: PreDepends: x11-common (>= 1:7.0.0) but it is not installed
libxft2: PreDepends: x11-common (>= 1:7.0.0) but it is not installed
libxi6: Depends: x11-common but it is not installed
libxinerama1: Depends: x11-common but it is not installed
libxmu6: Depends: x11-common but it is not installed
libxpm4: Depends: x11-common but it is not installed
libxrandr2: Depends: x11-common but it is not installed
libxt6: PreDepends: x11-common (>= 1:7.0.0) but it is not installed
libxv1: Depends: x11-common but it is not installed
libxvmc1: Depends: x11-common but it is not installed
libxxf86dga1: Depends: x11-common but it is not installed
libxxf86vm1: Depends: x11-common but it is not installed
E: Unmet dependencies. Try using -f.

Script done on Wed 14 Jun 2006 04:48:04 AM EDT

Snapshot 2: apt-get -f install
Script started on Wed 14 Jun 2006 04:55:13 AM EDT

Reading package lists... 0%

Reading package lists... 100%

Reading package lists... Done


Building dependency tree... 0%

Building dependency tree... 0%

Building dependency tree... 50%

Building dependency tree... 50%

Building dependency tree... Done

Correcting dependencies... Done
The following extra packages will be installed:
x11-common
The following NEW packages will be installed:
x11-common
0 upgraded, 1 newly installed, 0 to remove and 23 not upgraded.
1 not fully installed or removed.
Need to get 0B/285kB of archives.
After unpacking 598kB of additional disk space will be used.
Do you want to continue [Y/n]? y




Reading package fields... 0%

Reading package fields... Done


Reading package status... 0%

Reading package status... Done


Retrieving bug reports... 0% [0/1]

Retrieving bug reports... 0% [0/1]

Retrieving bug reports... Done
Preconfiguring packages ...
x11-common failed to preconfigure, with exit status 1
Setting up debconf (1.5.2) ...
dpkg: error processing debconf (--configure):
subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
debconf

Script done on Wed 14 Jun 2006 04:55:59 AM EDT

Thanks for any suggestions.
Chuck

[Dave Patterson]

* Charles Hallenbeck <***@hhs48.com> [2006-06-14 05:42:43 -0400]:

Try:
apt-get remove --purge X11-common
apt-get dist-upgrade

[Charles Hallenbeck]

Hi Dave,

Post by Dave Patterson
apt-get remove --purge X11-common
apt-get dist-upgrade

Here is what happens when I do the remove:

Script started on Wed 14 Jun 2006 06:05:37 AM EDT

Reading package lists... 0%

Reading package lists... 100%

Reading package lists... Done


Building dependency tree... 0%

Building dependency tree... 0%

Building dependency tree... 50%

Building dependency tree... 50%

Building dependency tree... Done

Package x11-common is not installed, so not removed
You might want to run `apt-get -f install' to correct these:
The following packages have unmet dependencies:
libice6: Depends: x11-common but it is not going to be installed
libsm6: Depends: x11-common but it is not going to be installed
libx11-6: PreDepends: x11-common (>= 1:7.0.0) but it is not going to be installed
libx11-data: PreDepends: x11-common (>= 1:7.0.0) but it is not going to be installed
libxau6: Depends: x11-common but it is not going to be installed
libxaw7: Depends: x11-common but it is not going to be installed
libxdmcp6: Depends: x11-common (>= 1:7.0) but it is not going to be installed
libxext6: Depends: x11-common but it is not going to be installed
libxfixes3: PreDepends: x11-common (>= 1:7.0.0) but it is not going to be installed
libxft2: PreDepends: x11-common (>= 1:7.0.0) but it is not going to be installed
libxi6: Depends: x11-common but it is not going to be installed
libxinerama1: Depends: x11-common but it is not going to be installed
libxmu6: Depends: x11-common but it is not going to be installed
libxpm4: Depends: x11-common but it is not going to be installed
libxrandr2: Depends: x11-common but it is not going to be installed
libxt6: PreDepends: x11-common (>= 1:7.0.0) but it is not going to be installed
libxv1: Depends: x11-common but it is not going to be installed
libxvmc1: Depends: x11-common but it is not going to be installed
libxxf86dga1: Depends: x11-common but it is not going to be installed
libxxf86vm1: Depends: x11-common but it is not going to be installed
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).

Script done on Wed 14 Jun 2006 06:05:37 AM EDT


I just can't get past this point.

Chuck

[Joris Huizer]

Post by Charles Hallenbeck
Package x11-common is not installed, so not removed

Hmm, you could try `dpkg --purge x11-common`

HTH,

Joris

[Charles Hallenbeck]

Hi, Joris

Post by Joris Huizer

Post by Charles Hallenbeck
Package x11-common is not installed, so not removed

Hmm, you could try `dpkg --purge x11-common`

Unfortunately I get the same familiar output:

Script started on Wed 14 Jun 2006 06:38:49 AM EDT
dpkg: dependency problems prevent removal of x11-common:
libxau6 depends on x11-common.
libxt6 depends on x11-common (>= 1:7.0.0).
libxxf86vm1 depends on x11-common.
libsm6 depends on x11-common.
libx11-data depends on x11-common (>= 1:7.0.0).
libice6 depends on x11-common.
libx11-6 depends on x11-common (>= 1:7.0.0).
libxft2 depends on x11-common (>= 1:7.0.0).
libxaw7 depends on x11-common.
libxmu6 depends on x11-common.
libxfixes3 depends on x11-common (>= 1:7.0.0).
libxi6 depends on x11-common.
libxv1 depends on x11-common.
libxrandr2 depends on x11-common.
libxpm4 depends on x11-common.
libxvmc1 depends on x11-common.
libxext6 depends on x11-common.
libxxf86dga1 depends on x11-common.
libxinerama1 depends on x11-common.
libxdmcp6 depends on x11-common (>= 1:7.0).
dpkg: error processing x11-common (--purge):
dependency problems - not removing
Errors were encountered while processing:
x11-common

Script done on Wed 14 Jun 2006 06:38:50 AM EDT



--
The Moon is Waning Gibbous (91% of Full)
Get downloads from http://www.mhcable.com/~chuckh
and remember, INFORMATION WANTS TO BE FREE!

[Joris Huizer]

Post by Charles Hallenbeck
Hi, Joris

Post by Joris Huizer

Post by Charles Hallenbeck
Package x11-common is not installed, so not removed

Hmm, you could try `dpkg --purge x11-common`

Script started on Wed 14 Jun 2006 06:38:49 AM EDT

Now I remember, dpkg has --force-* options; try with the --force-depends
flag, or (a bit more risky) the --force-all flag

HTH,

Joris

[Charles Hallenbeck]

Hi Joris,

When I add either the --force-depends or the --force-all option to the
dpkg --purge x11-common command, they also fail to remove the package.
When I then do an apt-get -f install, I get the same familiar failure as
I reported earlier.

I may have to save what I can and reinstall my system, although there
has GOT to be a better way. I am beginning to think like a Windows user,
and I have never been one!

Chuck

[John Miller]

Why not just keep x11-common? It looks like a whole ton of X libraries
are already installed. Otherwise, figure out which programs depend on
each individual library, either by dpkg --show <programname>, or by
trying to remove each library individually.

Up until a month or two ago (when I gave it away), I ran a console-only
laptop (sarge, however) that ran into these issues from time to time.
I'm just now checking e-mail and saw the words 'reinstall' float by....

Post by Charles Hallenbeck
Hi Joris,
When I add either the --force-depends or the --force-all option to the
dpkg --purge x11-common command, they also fail to remove the package.
When I then do an apt-get -f install, I get the same familiar failure as
I reported earlier.
I may have to save what I can and reinstall my system, although there
has GOT to be a better way. I am beginning to think like a Windows user,
and I have never been one!
Chuck

[John Miller]

Apologies for not reading the original message closely enough. I got
stuck on the 'x11-common' part and didn't pay enough attention to the
debconf error.

If debconf is having trouble, that's really weird. Perhaps doing a dpkg
-r debconf, then doing a clean reinstall of debconf? Using wget to
download a fresh .deb of debconf and installing with dpkg -i?
Reinstalling from your /var/cache/apt/archives? dpkg-reconfigure
debconf? I know that there is a reinstall option to apt.... That's
about all I know at this point.

--John

Post by John Miller
Why not just keep x11-common? It looks like a whole ton of X libraries
are already installed. Otherwise, figure out which programs depend on
each individual library, either by dpkg --show <programname>, or by
trying to remove each library individually.
Up until a month or two ago (when I gave it away), I ran a console-only
laptop (sarge, however) that ran into these issues from time to time.
I'm just now checking e-mail and saw the words 'reinstall' float by....

Post by Charles Hallenbeck
Hi Joris,
When I add either the --force-depends or the --force-all option to the
dpkg --purge x11-common command, they also fail to remove the package.
When I then do an apt-get -f install, I get the same familiar failure as
I reported earlier.
I may have to save what I can and reinstall my system, although there
has GOT to be a better way. I am beginning to think like a Windows user,
and I have never been one!
Chuck

[Simone Soldateschi]

Post by Charles Hallenbeck
Hi Dave,

Post by Dave Patterson
apt-get remove --purge X11-common
apt-get dist-upgrade

I had a similar problem two days ago trying to update 'libwx2.6-dev' from
backports.
'apt-get' failed package upgrade due to unmet dependencies and I was unable
to fix the problem with 'apt -f install'.
A debian user suggested me to fix the problem using synaptic and filtering
defective packages.. it did the job.

Now I'm doubtful: is it safe using backports? why 'apt-get -f install' did
not solve the problem?

bye

// SS

[Dave Patterson]

Post by Simone Soldateschi
A debian user suggested me to fix the problem using synaptic and filtering
defective packages.. it did the job.

Sorry. Here, he can't do that because he isn't even running X, only some
components of it are needed for his console. So Synaptic won't work in
this situation.

[Charles Hallenbeck]

Hi Simone,

Post by Simone Soldateschi
I had a similar problem two days ago trying to update 'libwx2.6-dev' from
backports.
'apt-get' failed package upgrade due to unmet dependencies and I was unable
to fix the problem with 'apt -f install'.
A debian user suggested me to fix the problem using synaptic and filtering
defective packages.. it did the job.

I do not have synaptic installed, and can no longer install anything
until I get this thing fixed. Catch 22! I'll keep that in mind though.

Chuck

[Greg Folkert]

Post by Charles Hallenbeck
Hi Simone,

Post by Simone Soldateschi
I had a similar problem two days ago trying to update 'libwx2.6-dev' from
backports.
'apt-get' failed package upgrade due to unmet dependencies and I was unable
to fix the problem with 'apt -f install'.
A debian user suggested me to fix the problem using synaptic and filtering
defective packages.. it did the job.

I do not have synaptic installed, and can no longer install anything
until I get this thing fixed. Catch 22! I'll keep that in mind though.

There is always dpkg-deb

dpkg-deb -X /var/cache/apt/archives/x11-common_1%
3a7.0.20_i386.deb /

That will extract and make certain things usable until you can get the
packages correctly installed. Personally I have saved a couple of
peoples machines this way. One fixing an upgrade from Breezy Badger to
Dapper Duck (being of course Ubuntu)... but I digress.

Use of these commands is exceptionally "use at your own risk of blowing
up your machines config, with no sympathy from anyone". So use caution.
--
greg, ***@gregfolkert.net

The technology that is
Stronger, Better, Faster: Linux

Use Debian GNU/Linux, its a bazaar thing

NOTICE: Due to Presidential Executive Orders, the
National Security Agency may have read this email
without warning, warrant, or notice, and certainly
without probable cause. They may do this without
any judicial or legislative oversight. You have no
recourse nor protection.

[Dave Patterson]

Ok, it looks like x11-common can't do anything because somethings hosed
with debconf.
Try apt-get -f install debconf, or dpkg-reconfigure debconf, and see what
happens there.

[Charles Hallenbeck]

Post by Dave Patterson
Ok, it looks like x11-common can't do anything because somethings hosed
with debconf.
Try apt-get -f install debconf, or dpkg-reconfigure debconf, and see what
happens there.

The apt-get -f install debconf gives me the same complaint, and the
dpkg-reconfigure debconf says this:

hq:~# dpkg-reconfigure debconf
/usr/sbin/dpkg-reconfigure: debconf is broken or not fully installed


Do I dare try to remove debconf? I better do a backup first, this is
getting serious <smile>

[Dave Patterson]

Post by Charles Hallenbeck
Do I dare try to remove debconf? I better do a backup first, this is
getting serious <smile>

'Eek!' said I, and yes, do a backup.

Then, yank it out.

Then, pull debconf from the testing
repository manually and install with dpkg -i (full packagename.deb) from the
directory you put it in.

Or, do this: add the testing repository to you /etc/apt/sources.list

apt-get update

apt-get remove --purge debconf

apt-get -t testing install debconf

[Charles Hallenbeck]

Dave,

Post by Dave Patterson
'Eek!' said I, and yes, do a backup.
Then, yank it out.

Yeah, but I can't yank it out! It is not fully installed, and nothing in
my arsenal can yank it out.

Post by Dave Patterson
Then, pull debconf from the testing
repository manually and install with dpkg -i (full packagename.deb) from the
directory you put it in.
Or, do this: add the testing repository to you /etc/apt/sources.list
apt-get update
apt-get remove --purge debconf

I wish that command would work, but it will not.
Ditto.

The real trouble with abandoning the problem by reinstalling my system
from scratch is, since I don't know what caused it, I might just run
into it again. I think I will rummage around some more before pulling
the plug.

[Joris Huizer]

just thinking aloud, maybe `apt-get --reinstall install debconf` could
help out on debconf, and then also on x11-common... I hope?

HTH,

Joris

[Joris Huizer]

one more note, in case you have aptitude installed, you may try using
that, too, as it is known to be handle conflicts and brakage slightly
different from apt-get; The interactive interface can show what is
broken and such
(just calling out a few suggestions now)

HTH,

Joris

[Dave Patterson]

Post by Joris Huizer
one more note, in case you have aptitude installed, you may try using
that, too, as it is known to be handle conflicts and brakage slightly
different from apt-get; The interactive interface can show what is
broken and such

Good idea - aptitude's installed by default in most systems...

My wife's calling...

back in a bit.

[Dave Patterson]

Post by Charles Hallenbeck
Yeah, but I can't yank it out! It is not fully installed, and nothing in
my arsenal can yank it out.

Ok,then:
Look at /var/lib/dpkg/info/debconf.postinst
and see what's in that file-perhaps we can hack a fix from there. The
postinstall script is what messed it up, and it's a hard hang.

Once we get that sorted out, we'll file a bug report with the maintainer,
but s/he has to know what the problem is...

Post by Charles Hallenbeck
I think I will rummage around some more before pulling
the plug.

I like rummaging. I sometimes find pretty girls and free beer that way...
remember, it's only a bug, not a system-wide disaster.

Post by Charles Hallenbeck
--
The Moon is Waning Gibbous (91% of Full)
Get downloads from http://www.mhcable.com/~chuckh
and remember, INFORMATION WANTS TO BE FREE!

[Charles Hallenbeck]

The strange problem of the "not fully installed or removed" packages I
have been reporting has been resolved, but I do not understand it.

It seems that a short while ago I have switched shells from bash to zsh
to explore its new features. I did it gradually, first doing a usermod
for each of my accounts to make /bin/zsh the login shell, then after
hammering out an agreeable configuration, changing the symbolic link
/bin/sh to point to /bin/zsh instead of /bin/bash.

After looking at those files in /var/lib/dpkg/info mentioned by Dave and
Joey, I changed the link to point to /bin/bash again, re-ran apt-get -f
install successfully, then ran apt-get upgrade also successfully, and I
have a resolved system.

But why? I do upgrades at least once a day, and they usually went
without a hitch using zsh. But evidently this was somehow the cause of
the current problem.

It's a little vague to report it as a zsh bug just yet, I think. And I
am nervous about trying to replicate the problem. So what do I do? give
up zsh?

Chuck

[Joshua J. Kugler]

Post by Charles Hallenbeck
changing the symbolic link
/bin/sh to point to /bin/zsh instead of /bin/bash.
I changed the link to point to /bin/bash again, [ran apt commands
successfully
But why? I do upgrades at least once a day, and they usually went
without a hitch using zsh. But evidently this was somehow the cause of
the current problem.
It's a little vague to report it as a zsh bug just yet, I think. And I
am nervous about trying to replicate the problem. So what do I do? give
up zsh?

I believe the issue is that /bin/sh is expected to be a bourne shell, or at
least closely compatible. zsh, "most closely resembles ksh but includes many
enhancements." ksh has "command language [that is ] is a superset of the
sh(1) shell language." While this means, in theory, ksh should do everything
sh would do, there might be expected behaviors that zsh (which "resembles"
ksh) does not live up to.

j

[Carl Fink]

Post by Joshua J. Kugler
I believe the issue is that /bin/sh is expected to be a bourne shell, or at
least closely compatible. zsh, "most closely resembles ksh but includes many
enhancements." ksh has "command language [that is ] is a superset of the
sh(1) shell language." While this means, in theory, ksh should do everything
sh would do, there might be expected behaviors that zsh (which "resembles"
ksh) does not live up to.

Shouldn't apt-get then refuse to run under zsh, or itself spawn /bin/sh and
run scripts under that instead of the default shell?

[Joey Hess]

Post by Carl Fink
Shouldn't apt-get then refuse to run under zsh, or itself spawn /bin/sh and
run scripts under that instead of the default shell?

/bin/sh is the default shell, and it is required on Debian that that
symlink only be pointed to POSIX compliant shells.

[Dave Patterson]

Post by Charles Hallenbeck
The strange problem of the "not fully installed or removed" packages I
have been reporting has been resolved...

Hooray!

Post by Charles Hallenbeck
It seems that a short while ago I have switched shells from bash to zsh
to explore its new features. I did it gradually, first doing a usermod
for each of my accounts to make /bin/zsh the login shell, then after
hammering out an agreeable configuration, changing the symbolic link
/bin/sh to point to /bin/zsh instead of /bin/bash.
After looking at those files in /var/lib/dpkg/info mentioned by Dave and
Joey, I changed the link to point to /bin/bash again, re-ran apt-get -f
install successfully, then ran apt-get upgrade also successfully, and I
have a resolved system.
But why? I do upgrades at least once a day, and they usually went
without a hitch using zsh. But evidently this was somehow the cause of
the current problem.

Hmm...

Post by Charles Hallenbeck
It's a little vague to report it as a zsh bug just yet, I think.

Agreed. I think it's more of a problem with APT. It should call bash if it
wants to use it.

Post by Charles Hallenbeck
So what do I do? give up zsh?

Nah. Figure out how to make APT point to BASH and file the bug there. Be
interesting to see what the APT people have to say.

[John Hasler]

Post by Dave Patterson
Figure out how to make APT point to BASH and file the bug there. Be
interesting to see what the APT people have to say.

Policy requires that /bin/sh point to a POSIX shell. Zsh is not
POSIX-compliant. You can break many things other than Apt by pointing
/bin/sh to Zsh.

[Joey Hess]

Post by Charles Hallenbeck
Retrieving bug reports... Done
Preconfiguring packages ...
x11-common failed to preconfigure, with exit status 1
Setting up debconf (1.5.2) ...
subprocess post-installation script returned error exit status 1
debconf

Edit /var/lib/dpkg/info/x11-common.config and
/var/lib/dpkg/info/debconf.postinst and add a new line as the second
line of each script:

set -e

Then re-run this apt-get -f install and we should be able to figure out
what's really wrong.

[Dave Patterson]

Post by Joey Hess
set -e
Then re-run this apt-get -f install and we should be able to figure out
what's really wrong.

This will tell you where in the script it's exiting...

[Greg Folkert]

Post by Dave Patterson

Post by Joey Hess
set -e
Then re-run this apt-get -f install and we should be able to figure out
what's really wrong.

This will tell you where in the script it's exiting...

Seeing as Joey Hess has a big hand in debconf and many other critical
packages, he wants to see what is really wrong, because the script may
exit in a completely different area than where the script hits the bad
function/command/typo.

Chuck needs to have a large scrollback and paste it to here for us to
understand the entire functional problem.
--
greg, ***@gregfolkert.net

The technology that is
Stronger, Better, Faster: Linux

Use Debian GNU/Linux, its a bazaar thing

NOTICE: Due to Presidential Executive Orders, the
National Security Agency may have read this email
without warning, warrant, or notice, and certainly
without probable cause. They may do this without
any judicial or legislative oversight. You have no
recourse nor protection.

[Charles Hallenbeck]

Post by Greg Folkert
Chuck needs to have a large scrollback and paste it to here for us to
understand the entire functional problem.

I have had good luck using "script" to capture as much output as
necessary. If someone would like to tell me what to run, I'll be happy
to generate output. But I sure don't want to put my system to risk, now
that it is resolved.

I have not seen my mail describing the resolution of the problem yet.
Turns out to be a problem of dueling shells, zsh vs. bash.

Chuck

[Charles Hallenbeck]

Hi Joey,

Post by Joey Hess
Edit /var/lib/dpkg/info/x11-common.config and
/var/lib/dpkg/info/debconf.postinst and add a new line as the second
set -e
Then re-run this apt-get -f install and we should be able to figure out
what's really wrong.

The first of those files, x11-common.config, does not exist, and the
other one, debconf.postinst, already has set -e on the second line.

Chuck

[Joey Hess]

Post by Joey Hess
set -e

Of course that should have been -x, the point being to see where the
script is failing.