*** This bug is a duplicate of bug 24626 ***
https://bugs.launchpad.net/bugs/24626
Marking as duplicate of bug 24626.
** Changed in: apt (Ubuntu)
Status: New = Invalid
** This bug has been marked a duplicate of bug 24626
Too many repositories dynamic mmap ran out of room
--
Ray, 16,777,216 is the default size -- the Linux forums where you got
this value may be referencing an older version of apt or, perhaps, the
upstream one. At least for Gutsy, this is the default (actually, it is
set as 16*1024*1024, which is just a different way).
RIght now I am running apt with
I did clean out the lists folder straight after the whoops and rebuilt with
another lazy value which does now work it just happens to be 2 meg smaller than
the one you suggested but i'll up the value anyway since theres no harm in more
space.
Im using the Mircrosoft stuff at the monent so Ill
Well done. As you say It doubling probably is sufficient I just did it
that way because it required no thought (lazy). Well I can confirm it's
still working without any problems.
--
apt-get and apt-cache Segmentation fault (core dumped)
https://bugs.launchpad.net/bugs/113424
You received this
I just changed the Cache-Limit to 16777216 which is exactly double
8388608 the original value I grabbed from Linux forums. Apt and synaptic
worked fine. There is one problem with all this as more and more shiny
things appear in the lists its gona come back.
--
apt-get and apt-cache Segmentation
Whoops Spoke too soon.
E: Dynamic MMap ran out of room
E: Read error - read (14 Bad address)
E: The package lists or status file could not be parsed or opened.
E: _cache-open() failed, please report.
Here we go again.
--
apt-get and apt-cache Segmentation fault (core dumped)
Sorry for the delay, got entangled on some other issues.
What I found is that Cache-Limit gets defaulted to either 16M (in apt-
pkg/pkgcachegen.cc, at function pkgMakeStatusCache, or to 12M (same
source, function pkgMakeOnlyStatusCache.
So... I think you are correct. I have not stopped to find
Depends on how you look at it. Here is a plausible account of what might have
happened .
Apt-get update starts to update then runs out of Cache-Limit space which
corrupts some files in the lists folder.
Next time you run apt-get it goes bang with a core dump error.
Clearing out the lists folder
PS I confirm there were a lot of items in the sources list but trimming the
list did not resolve the problem.
removing the contents of /var/lib/apt/lists/ changed the problem and revealed
the Cache-Limit error which was handled correctly.
--
apt-get and apt-cache Segmentation fault (core
I cannot find a reference to the default size of the cache. Will look at
the source.
--
apt-get and apt-cache Segmentation fault (core dumped)
https://bugs.launchpad.net/bugs/113424
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
I cannot find a reference to the default size of the cache. Will look at
the source. Also, I am not sure this is a bug by itself, since (I am
*guessing*) tyhis will only happen if one has lots of distributions in
the apt source list.
No matter what, perhaps a bit more of docs? keeping
How I fixed this.
http://www.linuxforums.org/forum/debian-linux-help/51937-aptitude-problem-problem-mergelist.html
Do the following.
sudo rm /var/lib/apt/lists/* -vf
Back it up first of course.
This may not be necessary but you must understand these are the steps I took.
Next do sudo apt-get
Copy of the crash dump file.
** Attachment added: crash dump file
http://librarian.launchpad.net/7585721/_usr_bin_apt-cache.0.crash
--
apt-get and apt-cache Segmentation fault (core dumped)
https://bugs.launchpad.net/bugs/113424
You received this bug notification because you are a member of
13 matches
Mail list logo
