Apt-get "Segmentation faultsts ... 0%" SOLVED

>It worked yesterday. Could be failed update killed it?

>Kpackage will display installed packages, not new or updated.

I went to reportbug to do this. There were a bunch of bugs previously filed a
while back about segfaults caused by corrupt /var/cache/apt/*.bin. Taking the
clue, I deleted the contents and let it redo them. Voile.

--

0

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Apt-get "Segmentation faultsts ... 0%" SOLVED

On Thursday 30 November 2006 16:38, David Baron wrote:
> >It worked yesterday. Could be failed update killed it?
> >
> >Kpackage will display installed packages, not new or updated.
>
> I went to reportbug to do this. There were a bunch of bugs previously filed
> a while back about segfaults caused by corrupt /var/cache/apt/*.bin. Taking
> the clue, I deleted the contents and let it redo them. Voile.

... except trying to install anything yields a million dependency problems and
then segfaults. So something else needs be fixed up as well.

--

Apt-get "Segmentation faultsts ... 0%" SOLVED

On Thursday 30 November 2006 17:09, David Baron wrote:
> On Thursday 30 November 2006 16:38, David Baron wrote:
> > >It worked yesterday. Could be failed update killed it?
> > >
> > >Kpackage will display installed packages, not new or updated.
> >
> > I went to reportbug to do this. There were a bunch of bugs previously
> > filed a while back about segfaults caused by corrupt
> > /var/cache/apt/*.bin. Taking the clue, I deleted the contents and let it
> > redo them. Voile.
>
> ... except trying to install anything yields a million dependency problems
> and then segfaults. So something else needs be fixed up as well.

Repeated the above. Seems to work now.

--

apt-get "Segmentation faultsts ... x%" not solved

Hello,
I keep having problems with apt-get which throws a "segmentation faultsts" at me regardless of my attempts to remove the /var/cache/apt/*.bin files.
I am running the stable version 0.5.28.6 on a kurobox (PowerPC).
The segmentation fault appears at random points anywhere from 0% to as high as 60%...
Any other ideas?
Thanks!
- JP

apt-get "Segmentation faultsts ... x%" not solved

jdevoo writes:

> The segmentation fault appears at random points anywhere from 0% to
> as high as 60%...

Have you already tested the memory of your machine with memtest?

--
-- Jhair

--

apt-get "Segmentation faultsts ... x%"

JHair,
when I look at /proc/meminfo (don't have memtest) I get:

total: used: free: shared: buffers: cached:
Mem: 130138112 123412480 6725632 0 8929280 93880320
Swap: 268877824 15884288 252993536
MemTotal: 127088 kB
MemFree: 6568 kB
MemShared: 0 kB
Buffers: 8720 kB
Cached: 87716 kB
SwapCached: 3964 kB
Active: 12372 kB
Inactive: 95124 kB
HighTotal: 0 kB
HighFree: 0 kB
LowTotal: 127088 kB
LowFree: 6568 kB
SwapTotal: 262576 kB
SwapFree: 247064 kB

Memory seems was not an issue until I had this problem appear. I've been running apt-get updates before successfully despite the small memory footprint.

I guess I could dump all the lists in /var/lib/apt/lists...
- JP

apt-get "Segmentation faultsts ... x%" SOLVED

Hello again,
I just dropped the /var/lib/apt/lists and re-created both lists and the partial subdirectory.
Re-issued apt-get update and this time the "Reading Package Lists..." went through.
Cool.
- JP

apt-get "Segmentation faultsts ... x%" not solved

On Saturday 16 December 2006 11:11, jdevoo wrote:
> Hello,
> I keep having problems with apt-get which throws a "segmentation faultsts"
> at me regardless of my attempts to remove the /var/cache/apt/*.bin files. I
> am running the stable version 0.5.28.6 on a kurobox (PowerPC).
> The segmentation fault appears at random points anywhere from 0% to as high
> as 60%... Any other ideas?
> Thanks!
> - JP

Try moving the two .bin files from /var/cache/apt. The corruption of one of
these makes the segfaultsts. You might have to repeat this but in the end,
these files are rebuilt successfully and all is well.

--

Re: apt-get "Segmentation faultsts ... x%" not solved

Hi,

Thanks for all the information. None of the tips helped me, though. What did the trick was to increase the cache limit: http://blog.springenwerk.com/2008/05/speicherzugriffsfehleresen-97.html

- Johannes

Syndicate content