* ldconfig problem
@ Sergei V. Fleytin
` Gaijin
` Kirk Reiser
0 siblings, 2 replies; 6+ messages in thread
From: Sergei V. Fleytin @ UTC (permalink / raw)
To: speakup
Hello, list.
I just decided to upgrade my Ubuntu Feisty system to Gutsy and run
into following problem after upgrade. Dpkg failed to configure libc6
with the following error message:
Setting up libc6 (2.6.1-1ubuntu9) ...
Processing triggers for libc6 ...
ldconfig deferred processing now taking place
Bus error (core dumped)
dpkg: subprocess post-installation script returned error exit status
135
Running ldconfig manually returns the same error message from bus.
It actually prevents me from doing any further update or upgrade for
my system since aptitude says that not all packages are properly
configured since dpkg exited abnormally and I have to run dpkg
--configure -a. And after running that command I get the message shown
above.
Any clue to the solution would be highly appreciated.
Sergei.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: ldconfig problem
ldconfig problem Sergei V. Fleytin
@ ` Gaijin
` Sergei V. Fleytin
` Kirk Reiser
1 sibling, 1 reply; 6+ messages in thread
From: Gaijin @ UTC (permalink / raw)
To: Speakup is a screen review system for Linux.
"Sergei V. Fleytin" <fleytin&yandex,ru> wrote:
> I just decided to upgrade my Ubuntu Feisty system to Gutsy and run
> into following problem after upgrade.
Hello Sergei,
How did you upgrade? Did you...
apt-get dist-upgrade
...to Gutsy, or upgrade from CD? I can only relate my own experience
with dpkg in Debian on the subject. I tried the dist-upgrade route in
Debian from Potato to Woody, and although it didn't break the system, it
sure left a mess. I ended up having to do a scratch install of Woody
from CD to clean up everything.
If you've installed or upgraded from CD, then it sounds like your
hardware isn't fully supported. I wish I could offer more help, but I
no longer use dpkg based Linux distros. (Personal preference; I don't
learn nearly enough when the computer does it all for me.)
Michael
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: ldconfig problem
` Gaijin
@ ` Sergei V. Fleytin
0 siblings, 0 replies; 6+ messages in thread
From: Sergei V. Fleytin @ UTC (permalink / raw)
To: Speakup is a screen review system for Linux.
Hello, Michael.
>>>>> "G" == Gaijin <gaijin@clearwire.net> writes:
G> How did you upgrade? Did you...
G> apt-get dist-upgrade
First I did:
aptitude upgrade
and after that:
aptitude dist-upgrade.
All of this on the installed Feisty via network.
G> I can only relate my own experience with dpkg in Debian on the
G> subject. I tried the dist-upgrade route in Debian from Potato to
G> Woody, and although it didn't break the system, it sure left a
G> mess. I ended up having to do a scratch install of Woody from CD to
G> clean up everything.
It seems to me that I will have to do the same. Windows way! :-(
Sergei.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: ldconfig problem
ldconfig problem Sergei V. Fleytin
` Gaijin
@ ` Kirk Reiser
` Sergei V. Fleytin
` Sergei V. Fleytin
1 sibling, 2 replies; 6+ messages in thread
From: Kirk Reiser @ UTC (permalink / raw)
To: Speakup is a screen review system for Linux.
I'm never quite sure with this particular error why it crops up but
I've seen it a lot on debian and to a lesser extent ubuntu. The down
and dirty approach in this case is to rm the package.postinst script.
There are a few scripts which get run prior to and after installing a
new package to make sure the permissions are correct, the directories
are empty or removed or who knows what else.. The dpkg system is
suppose to notice when one of the scripts is modified or changed for
some new improved reason but occasionally it fumbles and doesn't
notice. If you remove the offending file by hand then the package
installation system is forced to replace the file with the one in the
.deb file. So for the sake of information because you've probably
already done something more drastic try these two commands:
rm /var/lib/info/libc6.postinst
apt-get -f install
Now with the libc6 package it is a more dangerous process because if
something goes wrong you absolutely cannot operate without libc6 but
this is a script which is being run after the basic installation is
complete so if it were to destroy your system it would probably have
already trashed it.
In anyevent good luck.
Kirk
--
Kirk Reiser The Computer Braille Facility
e-mail: kirk@braille.uwo.ca University of Western Ontario
phone: (519) 661-3061
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: ldconfig problem
` Kirk Reiser
@ ` Sergei V. Fleytin
` Sergei V. Fleytin
1 sibling, 0 replies; 6+ messages in thread
From: Sergei V. Fleytin @ UTC (permalink / raw)
To: Speakup is a screen review system for Linux.
Hi, Kirk! Thank you very much for your advice. It did the trick!
Sergei.
>>>>> "KR" == Kirk Reiser <kirk@braille.uwo.ca> writes:
KR> I'm never quite sure with this particular error why it crops up
KR> but I've seen it a lot on debian and to a lesser extent ubuntu.
KR> The down and dirty approach in this case is to rm the
KR> package.postinst script. There are a few scripts which get run
KR> prior to and after installing a new package to make sure the
KR> permissions are correct, the directories are empty or removed or
KR> who knows what else.. The dpkg system is suppose to notice when
KR> one of the scripts is modified or changed for some new improved
KR> reason but occasionally it fumbles and doesn't notice. If you
KR> remove the offending file by hand then the package installation
KR> system is forced to replace the file with the one in the .deb
KR> file. So for the sake of information because you've probably
KR> already done something more drastic try these two commands:
KR> rm /var/lib/info/libc6.postinst apt-get -f install
KR> Now with the libc6 package it is a more dangerous process because
KR> if something goes wrong you absolutely cannot operate without
KR> libc6 but this is a script which is being run after the basic
KR> installation is complete so if it were to destroy your system it
KR> would probably have already trashed it.
KR> In anyevent good luck. Kirk
KR> --
KR> Kirk Reiser The Computer Braille Facility e-mail:
KR> kirk@braille.uwo.ca University of Western Ontario phone: (519)
KR> 661-3061
KR> _______________________________________________ Speakup mailing
KR> list Speakup@braille.uwo.ca
KR> http://speech.braille.uwo.ca/mailman/listinfo/speakup
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: ldconfig problem
` Kirk Reiser
` Sergei V. Fleytin
@ ` Sergei V. Fleytin
1 sibling, 0 replies; 6+ messages in thread
From: Sergei V. Fleytin @ UTC (permalink / raw)
To: Speakup is a screen review system for Linux.
Hi, Kirk! Thank you very much for your advice. It did the trick!
Sergei.
>>>>> "KR" == Kirk Reiser <kirk@braille.uwo.ca> writes:
KR> I'm never quite sure with this particular error why it crops up
KR> but I've seen it a lot on debian and to a lesser extent ubuntu.
KR> The down and dirty approach in this case is to rm the
KR> package.postinst script. There are a few scripts which get run
KR> prior to and after installing a new package to make sure the
KR> permissions are correct, the directories are empty or removed or
KR> who knows what else.. The dpkg system is suppose to notice when
KR> one of the scripts is modified or changed for some new improved
KR> reason but occasionally it fumbles and doesn't notice. If you
KR> remove the offending file by hand then the package installation
KR> system is forced to replace the file with the one in the .deb
KR> file. So for the sake of information because you've probably
KR> already done something more drastic try these two commands:
KR> rm /var/lib/info/libc6.postinst apt-get -f install
KR> Now with the libc6 package it is a more dangerous process because
KR> if something goes wrong you absolutely cannot operate without
KR> libc6 but this is a script which is being run after the basic
KR> installation is complete so if it were to destroy your system it
KR> would probably have already trashed it.
KR> In anyevent good luck. Kirk
KR> --
KR> Kirk Reiser The Computer Braille Facility e-mail:
KR> kirk@braille.uwo.ca University of Western Ontario phone: (519)
KR> 661-3061
KR> _______________________________________________ Speakup mailing
KR> list Speakup@braille.uwo.ca
KR> http://speech.braille.uwo.ca/mailman/listinfo/speakup
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~ UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
ldconfig problem Sergei V. Fleytin
` Gaijin
` Sergei V. Fleytin
` Kirk Reiser
` Sergei V. Fleytin
` Sergei V. Fleytin
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).