*** This bug is a duplicate of bug 75273 ***
https://bugs.launchpad.net/bugs/75273
same problem here after a broken Java install using Adept, on a fresh
Kubuntu Gutsy 7.10 x86. The solution in comment #6 worked, thanks a lot
Joel!
--
segfault on apt-get upgrade
*** This bug is a duplicate of bug 75273 ***
The backtrace looks exactly like
https://launchpad.net/distros/ubuntu/+source/apt/+bug/75273
** This bug has been marked a duplicate of bug 75273
Apt constantly sigsevs on edgy
--
segfault on apt-get upgrade
https://launchpad.net/bugs/70005
--
the issue can be worked around by removing/renaming the srcpkgcache.bin
and pkgcache.bin files, located in /var/cache/apt.
of possible interest is bug 61708.
Before discovering the workaround, I manually downgraded all feisty
packages I thought would affect apt. The segfault still existed.
Thanks Joel, after removing /var/cache/apt/{src,}pkgcache.bin apt is
working again.
** Changed in: apt (Ubuntu)
Status: Needs Info = Confirmed
--
segfault on apt-get upgrade
https://launchpad.net/bugs/70005
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
I also get a segfault, but it extends to apt-get
update/upgrade/autoclean/check/autoremove/dist-upgrade. I cannot install
valgrind or the yelp package to run a backtrace as I get:
sudo apt-get install valgrind
Segmentation fault (core dumped).
If there is anything I can do, let me know.
...and the Valgrind output.
Let me know if you guys need any additional info.
Thanks in advance!
** Attachment added: apt valgrind
http://librarian.launchpad.net/4961660/valgrind-logs-apt.tar.gz
--
segfault on apt-get upgrade
https://launchpad.net/bugs/70005
--
desktop-bugs mailing list
Thank you Mateusz, here's the backtrace.
The Valgrind output will come as soon as I finish download those bastard
13.4MB... :-)
** Attachment added: apt backtrace
http://librarian.launchpad.net/4961642/gdb-apt.txt
** Description changed:
- So, here's what I think is the first feisty bug
hanks for your bug report. Could you please try to obtain a
backtrace by following the instructions on
http://wiki.ubuntu.com/DebuggingProgramCrash.
It would also be appreciable if you attached the output from Valgrind. To
generate it, please follow the guidelines:
