[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#409230: marked as done (Aptitude / apt-get causes segmentation faults)

Your message dated Thu, 27 Nov 2008 15:55:14 +0200
with message-id <492EA6C2.4010206@gmail.com>
and subject line Re: Bug#409230: state of #409230
has caused the Debian Bug report #409230,
regarding Aptitude / apt-get causes segmentation faults
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
409230: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=409230
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: aptitude
Version: 0.4.4-1

I have recently been experiencing problems with aptitude and apt-get segfaulting on Etch.

I downloaded the first for CD images for Etch RC1, and used those to install the system on a laptop.  After obtaining a network card for the laptop, my sources.list looks like this:
--/etc/apt/sources.list--
deb cdrom:[Debian GNU/Linux testing _Etch_ - Official Snapshot i386 Binary-4 (20061110)]/ etch contrib main
deb cdrom:[Debian GNU/Linux testing _Etch_ - Official Snapshot i386 Binary-3 (20061110)]/ etch main
deb cdrom:[Debian GNU/Linux testing _Etch_ - Official Snapshot i386 Binary-2 (20061110)]/ etch main
deb cdrom:[Debian GNU/Linux testing _Etch_ - Official Snapshot i386 Binary-1 (20061110)]/ etch contrib main

deb http://debian.............../ testing main contrib
deb-src http://debian.............../ testing main contrib
deb http://debian-security.............../ testing/updates main contrib
deb-src http://debian-security.............../ testing/updates main contrib

deb http://ftp.nz.debian.org/debian testing main contrib
deb-src http://ftp.nz.debian.org/debian testing main contrib
deb http://ftp.nz.debian.org/debian-security testing/updates main contrib
deb-src http://ftp.nz.debian.org/debian-security testing/updates main contrib

deb http://ftp.debian.org/debian testing main contrib
deb-src http://security.debian.org/ testing/updates main contrib
deb http://security.debian.org/ testing/updates main contrib
deb-src http://security.debian.org/ testing/updates main contrib
deb http://secure-testing.debian.net/debian-secure-testing testing/security-updates main contrib
deb-src http://secure-testing.debian.net/debian-secure-testing testing/security-updates main contrib
----

Since the installation, apt and aptitude have been updated a few times, and aptitude is now at version 0.4.4-1.  At that time, I did not have the public key for the secure-testing archive installed, and aptitude complained several times that some packages could not be downloaded.

Shortly after installing the public key for secure-testing ( gpg --keyserver wwwkeys.eu.pgp.net --receive-keys 946aa6e18722e71e ; gpg --export -a 946aa6e18722e71e | apt-key add - ; apt-get update ; possibly aptitude update ), I began experiencing problems with aptitude and (later) "apt-get -f install" segfaulting.

I started aptitude interactively, and then started browsing through the newly "Upgradable Packages".  Simply by cursoring down to browse the list, aptitude segfaulted.  After that, I think I ran aptitude again and it segfaulted after building the tag database, perhaps even during building the view.

Following advice on the Internet, I performed a "rm /var/cache/apt/*.bin".  This allowed aptitude to start up but, after performing an update, aptitude segfaulted while I was browsing through the list.

I then decided to try re-installing aptitude, so I did a "apt-get remove aptitude ; apt-get install aptitude".  However, apt-get complained, and suggested I run "apt-get -f install".  When I tried this, apt-get segfaulted while correcting dependancies.

After reading that this could be the result of a bug causing apt to become corrupted, I decided to "rm -r /var/lib/apt/lists ; apt-get update".  apt-get complained about /var/lib/apt/lists/lock missing, so I re-created the /var/lib/apt/lists directory and re-ran "apt-get update".

I then re-ran "apt-get -f install", which reported that there was nothing to be done.  However, when I then re-ran aptitude, it began to segfault on startup again.  Since it was reproducible, I ran "gdb aptitude" and captured the following backtrace:
--aptitude.backtrace--
(gdb) bt
#0  0xa7f1e2d4 in pkgCache::VerIterator::Downloadable ()
   from /usr/lib/libapt-pkg-libc6.3-6.so.3.11
#1  0x081e7cf5 in std::operator+<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> > ()
#2  0x081e833f in std::operator+<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> > ()
#3  0x082277d8 in std::operator+<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> > ()
#4  0x0822eff3 in std::operator+<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> > ()
#5  0x08231287 in std::operator+<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> > ()
#6  0x0820fdbe in std::operator+<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> > ()
#7  0x0821011c in std::operator+<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> > ()
#8  0x08231d7c in std::operator+<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> > ()
#9  0xa7e860bd in start_thread () from /lib/tls/libpthread.so.0
#10 0xa7d0492e in clone () from /lib/tls/libc.so.6
(gdb)
----

I then tried running "apt-get -f install", which also segfaulted.  "gdb --args apt-get -f install" produced the following:
--apt-get backtrace--
Reading package lists... Done
Building dependency tree... Done
Correcting dependencies...
Program received signal SIGSEGV, Segmentation fault.
0xa7ea634c in pkgDepCache::Update () from /usr/lib/libapt-pkg-libc6.3-6.so.3.11
(gdb) bt
#0  0xa7ea634c in pkgDepCache::Update ()
   from /usr/lib/libapt-pkg-libc6.3-6.so.3.11
#1  0xa7ea6700 in pkgDepCache::Update ()
   from /usr/lib/libapt-pkg-libc6.3-6.so.3.11
#2  0xa7ea6cfc in pkgDepCache::MarkInstall ()
   from /usr/lib/libapt-pkg-libc6.3-6.so.3.11
#3  0xa7eb35cc in pkgProblemResolver::Resolve ()
   from /usr/lib/libapt-pkg-libc6.3-6.so.3.11
#4  0xa7eb4fb0 in pkgFixBroken () from /usr/lib/libapt-pkg-libc6.3-6.so.3.11
#5  0x0804d255 in ?? ()
#6  0x0805d22b in ?? ()
#7  0xa7e944ab in CommandLine::DispatchArg ()
   from /usr/lib/libapt-pkg-libc6.3-6.so.3.11
#8  0x0804f59f in ?? ()
#9  0xa7c35ea8 in __libc_start_main () from /lib/tls/libc.so.6
#10 0x0804c5a1 in ?? ()
(gdb)
----

To see if I could reproduce the problem another way, I interactively ran dselect.  From dselect's menu, I ran "Update", which took some time ("Replacing available packages info, using /var/cache/apt/available"), and then "Select", which seemed to cause dselect to hang.  After "Ctrl-C"-ing dselect, I re-deleted "/var/cache/apt/*.bin".  After this, aptitude appears to be working (I was able to interactively use it to install "openssh-server", although dpkg took quite a long time, and allocated about 32MB of memory to read the dependancy database).

I hope I have not left out anything useful, but if I have, I will do my best to provide the information.

--------------------------------------
Protect yourself from spam, 
use http://sneakemail.com

--- End Message ---
--- Begin Message --- 
Brendon Green wrote:
> Eugene V. Lyubimkin jackyf.devel-at-gmail.com |DebianBug| wrote:
>> Hello Brendon.
>>
>> Have you similar problems with the newest apt (>= 0.7.18) ?
>>
>>   
> I can't remember the last time I had a problem like this.  Also, I no
> longer have possession of the laptop in question (re-installed Win98SE
> on it, because I couldn't find a GNU/Linux desktop that would run
> happily on such a low spec).
> 
> I currently run Debian on 2 computers.  One is a desktop running
> Lenny/Sid (and thus is upgraded almost daily), the other a server
> running Etch/Lenny (apt, aptitude and all dependencies from Lenny).  I
> switched the desktop from Etch/Lenny to full Lenny about half a year ago.
> 
> Both have just now upgraded themselves to apt 0.7.18.  The last time
> aptitude (or apt) segfaulted on either of them must have been months ago.
> 
> Sorry I couldn't be of more help.
> 
> Brendon
Thanks for answer. I will close bug for now then.

-- 
Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com
Ukrainian C++ Developer, Debian APT contributor

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
Reply to: