RE: dpkg/apt-get broken, seg fault on "updating MIME db"
Check your memory recently? (www.memtest86.com)
-----Original Message-----
From: Brendan [mailto:mailinglist@endosquid.com]
Sent: Tuesday, April 26, 2005 8:37 PM
To: debian-user@lists.debian.org
Subject: Re: dpkg/apt-get broken, seg fault on "updating MIME db"
On Tuesday 26 April 2005 03:49 pm, Sven Arvidsson wrote:
> Brendan wrote:
> > Output is below (then more output below that):
> > Unpacking replacement planner ...
> > /var/lib/dpkg/info/planner.postrm: line 34: 13902 Segmentation
> > fault /usr/bin/update-mime-database /usr/share/mime
> > dpkg: warning - old post-removal script returned error exit status
139
> > dpkg - trying script from the new package instead ...
> > /var/lib/dpkg/tmp.ci/postrm: line 39: 13908 Segmentation
> > fault /usr/bin/update-mime-database /usr/share/mime
> > dpkg: error processing
/var/cache/apt/archives/planner_0.13-0.3_i386.deb
> > (--unpack):
> > subprocess new post-removal script returned error exit status 139
> > /var/lib/dpkg/tmp.ci/postrm: line 39: 13914 Segmentation
> > fault /usr/bin/update-mime-database /usr/share/mime
> > dpkg: error while cleaning up:
> > subprocess post-removal script returned error exit status 139
> > Errors were encountered while processing:
> > /var/cache/apt/archives/bluefish_1.0-1_i386.deb
> > /var/cache/apt/archives/planner_0.13-0.3_i386.deb
> > E: Sub-process /usr/bin/dpkg returned an error code (1)
> >
> > So, I run an strace /usr/bin/update-mime-database, and the only odd
> > things I see in it are:
> > access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
> > directory)
> > open("/lib/tls/libc.so.6", O_RDONLY) = 3
>
> What happens if you try to run "update-mime-database /usr/share/mime/"
> (as root) manually? (Maybe something in the mime-database is corrupt?)
Tried that. Segfaults...
A few other commands (like vim) are segfaulting as well...
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact
listmaster@lists.debian.org
Reply to: