On Mon, Jul 20, 2009 at 01:49:36PM -0700, Bill Wohler woh...@newt.com was
heard to say:
Daniel Burrows dburr...@debian.org wrote:
I have no idea what's causing these symptoms. A backtrace from an
affected system (or maybe a state snapshot generated by
aptitude-create-state-bundle)
Daniel Burrows dburr...@debian.org wrote:
On Mon, Jul 20, 2009 at 01:49:36PM -0700, Bill Wohler woh...@newt.com was
heard to say:
Daniel Burrows dburr...@debian.org wrote:
I have no idea what's causing these symptoms. A backtrace from an
affected system (or maybe a state snapshot
On Sun, Jul 19, 2009 at 02:51:06PM -0700, Bill Wohler woh...@newt.com was
heard to say:
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
Daniel Burrows dburr...@debian.org wrote:
I have no idea what's causing these symptoms. A backtrace from an
affected system (or maybe a state snapshot generated by
aptitude-create-state-bundle) would be helpful.
Thanks, Daniel. I happened to run aptitude-create-state-bundle before I
fixed
Package: aptitude
Version: 0.4.11.11-1~lenny1
Severity: grave
Justification: renders package unusable
aptitude segmentation faults on start up, as root or normal user, on my armel
machine.
apt-get and other apt utilities seem fine.
Weirdly when I use strace I no longer get the segmentation
Package: aptitude
Version: 0.4.11.11-1~lenny1
Severity: normal
I'm seeing the same problem too after installing some software from sid.
Would love some advice on how to recover!
Here's a message I just sent to debian-user:
After making the following changes to pull in sid's bluez 4.0 package in
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
7 matches
Mail list logo
