[TAG] segmentation fault in aptitude

Benjamin A. Okopnik ben at linuxgazette.net
Thu Apr 7 08:59:38 MSD 2005


On Thu, Apr 07, 2005 at 01:23:26AM -0400, Suramya Tomar wrote:
> Hi Everyone,
> I had the exact same problem a few days ago after I ran a apt-get 
> dist-upgrade on my system. The following changes were made during this:
> 
> The following packages will be REMOVED:
>   xprt-common
> The following NEW packages will be installed:
>   gaim-data libboost-python1.32.0 libdevmapper1.01 sudo xprint 
> xprint-common
> The following packages will be upgraded:
> 
> capplets capplets-data fontconfig gaim gedit gedit-common gksu 
> gnome-control-center gnome-panel gnome-panel-data gnome-terminal 
> gs-common gstreamer0.8-oss ifupdown kdeedu kig kvim libcurl3 libecal6 
> libedataserver3 libexif10 libgimp2.0 libgstreamer-plugins0.8-0 
> libgstreamer0.8-0 libgtksourceview-common libgtksourceview1.0-0 libidl0 
> libieee1284-3 libmyspell3 libmysqlclient14 libmysqlclient14-dev 
> liborbit2 libpanel-applet2-0 libsane libselinux1 libvte-common libvte4 
> libwrap0 libxml2 libxslt1 libxslt1.1 lilo lsof mysql-common-4.1 portmap 
> sane-utils   tasksel tcpd time vim vim-common whois xprt xprt-xprintorg
> 
> I guess one of these is causing apt to die.
 
Hmmm. Interesting idea, Suramya...

``
ben at Fenrir:~$ ldd `which apt-get`
                libapt-pkg-libc6.3-5.so.3.3 => /usr/lib/libapt-pkg-libc6.3-5.so.3.3 (0x4001e000)
        libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0x41253000)
        libm.so.6 => /lib/tls/libm.so.6 (0x4114f000)
        libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x41312000)
        libc.so.6 => /lib/tls/libc.so.6 (0x41019000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x41000000)
''

It's _possible_ that Joydeep's "apt-get" depends on libs within the list
you quote, but there's no crossover with mine. 

> Another issue I noticed was that KDE was refusing to run after the 
> upgrade. I kept getting an error saying that "There is already an 
> instance of X-server running at :0 do you want to attempt starting a new 
> instance at :1".

In my opinion, KDE is the reason that Debian calls one of their releases
"unstable"; if it wasn't for that, they'd call it something like
"stable_but_not_guaranteed". :) I've uninstalled KDE from my system...
it takes up huge amounts of room, is very resource-intensive, brings an
entire range of its own problems, and is - in my opinion - just not
worth the hassle. There are people out there who love it, but I'm not
counted among their ranks.


* Ben Okopnik * Editor-in-Chief, Linux Gazette * http://linuxgazette.net *




More information about the TAG mailing list