dpkg segmentation fault
I am helping a buddy with his Sid system. He went several months without upgrading. Then recently tried to upgrade. This resulted in some problems. Currently the system produces a segmentation fault when trying to install packages. For example: # dpkg-reconfigure debconf Segmentation fault # dpkg -i debconf_1.5.49_all.deb (Reading database ... 387854 files and directories currently installed.) Preparing to replace debconf 1.5.49 (using debconf_1.5.49_all.deb) ... Unpacking replacement debconf ... Setting up debconf (1.5.49) ... dpkg: error processing debconf (--install): subprocess installed post-installation script was killed by signal (Segmentation fault) Errors were encountered while processing: debconf Of course the segfault makes it difficult to make any forward progress with dpkg. dpkg is up to date Sid version 1.17.1. But almost all other packages are older revs from previous days of Sid. I tried downgrading dpkg to the version in Wheezy but the result was the same. Thought before I did extreme things that I would ask here in case someone already hit this in Sid sometime between a few months ago and now? If so what was the solution? Thanks! Bob signature.asc Description: Digital signature
Re: dpkg segmentation fault
On Wed, Oct 02, 2013 at 03:11:24 -0600, Bob Proulx wrote:
I am helping a buddy with his Sid system. He went several months
without upgrading. Then recently tried to upgrade. This resulted in
some problems. Currently the system produces a segmentation fault
when trying to install packages. For example:
# dpkg-reconfigure debconf
Segmentation fault
# dpkg -i debconf_1.5.49_all.deb
(Reading database ... 387854 files and directories currently installed.)
Preparing to replace debconf 1.5.49 (using debconf_1.5.49_all.deb) ...
Unpacking replacement debconf ...
Setting up debconf (1.5.49) ...
dpkg: error processing debconf (--install):
subprocess installed post-installation script was killed by signal
(Segmentation fault)
Errors were encountered while processing:
debconf
Of course the segfault makes it difficult to make any forward progress
with dpkg. dpkg is up to date Sid version 1.17.1. But almost all
other packages are older revs from previous days of Sid. I tried
downgrading dpkg to the version in Wheezy but the result was the same.
Thought before I did extreme things that I would ask here in case
someone already hit this in Sid sometime between a few months ago and
now? If so what was the solution?
My guess would be an incomplete or otherwise screwed-up Perl transition
(dpkg-reconfigure is a Perl script and debconf's postinst calls a bunch
of Perl scripts as well). Check the status of the Perl packages on your
friend's machine, here is what I have on up-to-date Sid/amd64:
$ dpkg -l perl\* libperl\* | awk '/^ii/{print $2,$3}'
libperl4-corelibs-perl 0.003-1
libperl5.18 5.18.1-4
perl 5.18.1-4
perl-base 5.18.1-4
perl-doc 5.18.1-4
perl-modules 5.18.1-4
perl-tk 1:804.031-1+b1
perlmagick 8:6.7.7.10-6
Other than that, I can only say that I cannot recall having any problems
with my Sid system in recent months, even though upgrading all packages
that can be upgraded is how I start almost every day.
--
Regards,|
Florian | http://www.florian-kulzer.eu
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20131002193058.GA14522@isar.localhost
Re: dpkg segmentation fault
Florian Kulzer wrote:
On Wed, Oct 02, 2013 at 03:11:24 -0600, Bob Proulx wrote:
I am helping a buddy with his Sid system. He went several months
without upgrading. Then recently tried to upgrade. This resulted in
some problems. Currently the system produces a segmentation fault
when trying to install packages. For example:
# dpkg-reconfigure debconf
Segmentation fault
# dpkg -i debconf_1.5.49_all.deb
(Reading database ... 387854 files and directories currently installed.)
Preparing to replace debconf 1.5.49 (using debconf_1.5.49_all.deb) ...
Unpacking replacement debconf ...
Setting up debconf (1.5.49) ...
dpkg: error processing debconf (--install):
subprocess installed post-installation script was killed by signal
(Segmentation fault)
Errors were encountered while processing:
debconf
Of course the segfault makes it difficult to make any forward progress
with dpkg. dpkg is up to date Sid version 1.17.1. But almost all
other packages are older revs from previous days of Sid. I tried
downgrading dpkg to the version in Wheezy but the result was the same.
Thought before I did extreme things that I would ask here in case
someone already hit this in Sid sometime between a few months ago and
now? If so what was the solution?
My guess would be an incomplete or otherwise screwed-up Perl transition
(dpkg-reconfigure is a Perl script and debconf's postinst calls a bunch
of Perl scripts as well). Check the status of the Perl packages on your
friend's machine, here is what I have on up-to-date Sid/amd64:
$ dpkg -l perl\* libperl\* | awk '/^ii/{print $2,$3}'
libperl4-corelibs-perl 0.003-1
libperl5.18 5.18.1-4
perl 5.18.1-4
perl-base 5.18.1-4
perl-doc 5.18.1-4
perl-modules 5.18.1-4
perl-tk 1:804.031-1+b1
perlmagick 8:6.7.7.10-6
Other than that, I can only say that I cannot recall having any problems
with my Sid system in recent months, even though upgrading all packages
that can be upgraded is how I start almost every day.
I get fewer Perl hits with an uptodate Sid:
hugo@hdbb:/sdc1$ dpkg -l perl\* libperl\* | awk '/^ii/{print $2,$3}'
+ dpkg -l 'perl*' 'libperl*'
+ awk '/^ii/{print $2,$3}'
libperl4-corelibs-perl 0.003-1
perl 5.18.1-4
perl-base 5.18.1-4
perl-modules 5.18.1-4
Hugo
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/l2i0jb$u97$1...@ger.gmane.org
Re: dpkg segmentation fault
Hugo Vanwoerkom wrote:
Florian Kulzer wrote:
My guess would be an incomplete or otherwise screwed-up Perl transition
(dpkg-reconfigure is a Perl script and debconf's postinst calls a bunch
of Perl scripts as well). Check the status of the Perl packages on your
friend's machine, here is what I have on up-to-date Sid/amd64:
A good suggestion. Very likely related. I manually walked through
the packages and upgraded them with dpkg -i perl-foo_X.Y.deb and I
think all of them are now at current Sid levels. Unfortunately the
dpkg segfault continues.
I also found a large number of removed-config state packages.
dpkg -l | awk '$1~/^rc/{print$2}'| wc -l
469
Mostly libraries.
dpkg -l | awk '$1~/^rc/$2~/^lib/{print$2}' | wc -l 345
Those seem safe to purge so purging them to simplify things somewhat.
dpkg -l | awk '$1~/^rc/{print$2}'| wc -l
124
I am able to manually upgrade by 'dpkg -i' for individual packages. A
little tedious. But making some progress. I am going to try to get
perl completely up to date. That hopefully will fix the sig segv
problem.
Thanks!
Bob
signature.asc
Description: Digital signature
Re: dpkg segmentation fault
Bob Proulx wrote:
Hugo Vanwoerkom wrote:
Florian Kulzer wrote:
My guess would be an incomplete or otherwise screwed-up Perl transition
(dpkg-reconfigure is a Perl script and debconf's postinst calls a bunch
of Perl scripts as well). Check the status of the Perl packages on your
friend's machine, here is what I have on up-to-date Sid/amd64:
$ dpkg -l perl\* libperl\* | awk '/^ii/{print $2,$3}'
A good suggestion. Very likely related. I manually walked through
the packages and upgraded them with dpkg -i perl-foo_X.Y.deb and I
think all of them are now at current Sid levels. Unfortunately the
dpkg segfault continues.
...
I am able to manually upgrade by 'dpkg -i' for individual packages. A
little tedious. But making some progress. I am going to try to get
perl completely up to date. That hopefully will fix the sig segv
problem.
# dpkg -l | awk '$2~/-perl/{print$2}' | wc -l
374
I scripted a quick command line for loop to download using apt-get
(apt-get download foo) and then install it (dpkg -i foo) and walked
through all of the perl packages. That took some machine time to
complete but I could let it run without my interaction to slow it
down. After that the segfault problem was gone. Yay! Then it was
off to 'apt-get -f install' to fix the rest of things. A few other
fixes and the next set of things are just normal Sid upgrade issues.
Those hints set me on the path to success.
Thanks!
Bob
signature.asc
Description: Digital signature
Re: dpkg segmentation fault
--- Christopher Parker [EMAIL PROTECTED] wrote:
I recently compiled perl from source on my Debian system, unknowingly breaking
debconf (and
probably other programs).
It seems as though merely moving DebianNet.pm into one of the directories in @INC
temporarily
fixed this problem. However, now if I try to install the latest unstable dpkg and/or
debconf (or
anything else, for that matter), I get an error like this:
# dpkg --install dpkg_1.10.22_i386.deb
dpkg: error processing dpkg_1.10.22_i386.deb (--install):
subprocess dpkg-split killed by signal (Segmentation fault)
Errors were encountered while processing:
dpkg_1.10.22_i386.deb
Is there any way I can fix this so I can use the apt system again? Without it, my
system is
relatively unusable at the moment.
I was just wondering if anybody had actually seen my post. I'm still unable to fix
this problem.
My server has been pretty much unusable for a while now. If ANYONE could perhaps shed
some light
on my problem, I would be grateful.
Thank you.
=
Christoph von Gröenwald [EMAIL PROTECTED]
Home page: http://www.cparker15.com/
[EMAIL PROTECTED]:~# find / -name \*yourbase\* -exec chown us:us {} \;
-BEGIN GEEK CODE BLOCK-
Version: 3.1
GAT/CS/E/ED/IT/MU/P/TW/O d-@ s++:+++:- a--? C++(+++)$ UBL(S@) P+++$ L+ E++
W++(+++)$ N+(++) o? K- w? O-- M@ V? PS+(+++) PE Y+(++) PGP++ t 5 X+@ R* tv-@ b+
DI++ D++(+++) G+++ e+(*) h---(++@) r+++ y+++**
--END GEEK CODE BLOCK--
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
dpkg segmentation fault
Hello all,
I recently compiled perl from source on my Debian system, unknowingly breaking debconf
(and
probably other programs).
It seems as though merely moving DebianNet.pm into one of the directories in @INC
temporarily
fixed this problem. However, now if I try to install the latest unstable dpkg and/or
debconf (or
anything else, for that matter), I get an error like this:
# dpkg --install dpkg_1.10.22_i386.deb
dpkg: error processing dpkg_1.10.22_i386.deb (--install):
subprocess dpkg-split killed by signal (Segmentation fault)
Errors were encountered while processing:
dpkg_1.10.22_i386.deb
Is there any way I can fix this so I can use the apt system again? Without it, my
system is
relatively unusable at the moment.
Thanks!
=
Christoph von Gröenwald [EMAIL PROTECTED]
Home page: http://www.cparker15.com/
[EMAIL PROTECTED]:~# find / -name \*yourbase\* -exec chown us:us {} \;
-BEGIN GEEK CODE BLOCK-
Version: 3.1
GAT/CS/E/ED/IT/MU/P/TW/O d-@ s++:+++:- a--? C++(+++)$ UBL(S@) P+++$ L+ E++
W++(+++)$ N+(++) o? K- w? O-- M@ V? PS+(+++) PE Y+(++) PGP++ t 5 X+@ R* tv-@ b+
DI++ D++(+++) G+++ e+(*) h---(++@) r+++ y+++**
--END GEEK CODE BLOCK--
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
[SOLVED]Re: dpkg segmentation fault
Rob Weir [EMAIL PROTECTED]: On Tue, Nov 04, 2003 at 07:29:22AM +1100, Jonathan Wheelhouse said Hi I get this when running aptitude: [snip] E: Sub-process /usr/bin/dpkg received a segmentation fault. Ack! Something bad happened while installing packages. Trying to recover: [snip] I cannot install the new version what do I do? A .deb is an ar archive containing two tarballs. You can extract the new libc like this: $ ar x libc6_2.3.2.ds1-9_i386.deb [snip some good advice] Thanks, I did something like this by essentially following the same advice from another thread. However, I had one complication - my / partition (about 50 meg) was 100% full. I had to move some stuff to /var before being able to follow the advice. Tonight I fixed the filling up / partition by using GNU parted to copy /dev/hda5 (mounted as /) to the windows partition (/dev/hda1 which is about 600 meg), modifying /etc/fstab and /etc/lilo.conf and running lilo. Crossed my fingers - everything went almost smoothly; Debian is running fine now. I know 600 meg is too much for / as I have /var, /tmp/, /home, /usr and /usr/local on separate partitions but resizing partitions is pretty dangerous and I don't really have a backup strategy yet (other than saving a gnucash file to floppy). So this is something I will leave for another day. Anyhow, thanks again for the good advice. Jonathan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dpkg segmentation fault
On Tue, Nov 04, 2003 at 07:29:22AM +1100, Jonathan Wheelhouse said Hi I get this when running aptitude: The following packages will be upgraded: libc6 locales 2 packages upgraded, 0 newly installed, 1 to remove and 127 not upgraded. Need to get 0B/8785kB of archives. After unpacking 4694kB will be freed. Do you want to continue? [Y/n/?] Writing extended state information... Done Reading changelogs... Done Preconfiguring packages ... (Reading database ... 63087 files and directories currently installed.) Preparing to replace libc6 2.3.2-8 (using .../libc6_2.3.2.ds1-9_i386.deb) ... Unpacking replacement libc6 ... E: Sub-process /usr/bin/dpkg received a segmentation fault. Ack! Something bad happened while installing packages. Trying to recover: dpkg-deb: subprocess paste killed by signal (Broken pipe) dpkg: dependency problems prevent configuration of locales: locales depends on glibc-2.3.2.ds1-8; however: Package glibc-2.3.2.ds1-8 is not installed. dpkg: error processing locales (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: locales Reading Package Lists... Done Building Dependency Tree Reading extended state information... Done I read libc6 bug reports which suggest that it has the problem but if I cannot install the new version what do I do? A .deb is an ar archive containing two tarballs. You can extract the new libc like this: $ ar x libc6_2.3.2.ds1-9_i386.deb which will give you the control.tar.gz and data.tar.gz files. Unpack the data.tar.gz in /: $ cd / tar -zxvf /tmp/data.tar.gz If this fixes your system, then use dpkg to reinstall libc6_2.3.2.ds1-9_i386.deb so all the control files get updated accordingly. -- Rob Weir [EMAIL PROTECTED] | [EMAIL PROTECTED] | Do I look like I want a CC? Words of the day: cypherpunk corporate security BLU-114/B satellite imagery signature.asc Description: Digital signature
dpkg segmentation fault
Hi I get this when running aptitude: The following packages will be upgraded: libc6 locales 2 packages upgraded, 0 newly installed, 1 to remove and 127 not upgraded. Need to get 0B/8785kB of archives. After unpacking 4694kB will be freed. Do you want to continue? [Y/n/?] Writing extended state information... Done Reading changelogs... Done Preconfiguring packages ... (Reading database ... 63087 files and directories currently installed.) Preparing to replace libc6 2.3.2-8 (using .../libc6_2.3.2.ds1-9_i386.deb) ... Unpacking replacement libc6 ... E: Sub-process /usr/bin/dpkg received a segmentation fault. Ack! Something bad happened while installing packages. Trying to recover: dpkg-deb: subprocess paste killed by signal (Broken pipe) dpkg: dependency problems prevent configuration of locales: locales depends on glibc-2.3.2.ds1-8; however: Package glibc-2.3.2.ds1-8 is not installed. dpkg: error processing locales (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: locales Reading Package Lists... Done Building Dependency Tree Reading extended state information... Done I read libc6 bug reports which suggest that it has the problem but if I cannot install the new version what do I do? Jonathan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
