Most excellent! I found a workaround. First run apt-get -f install and get the segmentation fault again:
$ sudo apt-get -f install Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Segmentation fault However, run it again, and smile when you don't see the segmentation fault! $ sudo apt-get -f install Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Indeed, I can now continue on with what I was doing with aptitude: $ sudo aptitude install Reading package lists... Done Building dependency tree Reading state information... Done Reading extended state information Initializing package states... Done Reading task descriptions... Done The following NEW packages will be installed: bluez-compat [4.42-2] 0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0B/80.3kB of archives. After unpacking 242kB will be used. Do you want to continue? [Y/n/?] Phew! Any ideas on how I got into this situation? The only unusual thing I did was "uninstall" some packages that were recommended after selecting blueman for installation in aptitude. This was mostly just python-all-dev, I think, which just wanted to install python 2.4 which seems unnecessary since python 2.5 is installed. -- Bill Wohler <woh...@newt.com> http://www.newt.com/wohler/ GnuPG ID:610BD9AD -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org