Eddy Petrișor wrote:
<snip>
microwaverich, could you test once more, just to be sure, that under
each one of these setups aptitude blocks:
1) etch kernel (2.6.18-6-k7 - if you no longer have it, you can grab
it from http://packages.debian.org/etch/linux-image-2.6.18-6-k7)
official aptitude from lenny (0.4.11.11-1~lenny1)
2) lenny kernel (2.6.26 -
http://packages.debian.org/lenny/linux-image-2.6.26-1-686)
official aptitude from lenny (0.4.11.11-1~lenny1)
<snip>
Eddy:
I still have both kernels installed, so this was easy.
I rebooted to 2.6.18-6-k7, switched to console 2, and invoked aptitude.
In the ncurses aptitude, I searched for xsoldier, hit '+' to select it,
and 'g' twice to install. After completing the install, aptitude did
the usual thing with the cache and looked like it had returned to
command mode, but it was frozen. It would not respond to the keyboard,
so I used ctrl-C to kill it. The keystrokes I had entered while
aptitude was frozen were then waiting there at the root '#' command prompt.
I rebooted to 2.6.26-1-686 and went through a similar procedure, except
I used '-' to deselect xsoldier. Aptitude worked fine, and exited
normally using 'q', as it has the last few times I've used it.
I'm 99% sure (nothing is 100%) that this (behaving properly under the
-686 kernel) is not what was happening when I posted the problem on
linux.debian.user. I keep a written log of everything I do on the
machine, and I noted the freeze-up problem even after switching from the
k7 to 686 kernel.
But it ain't like that no more! I don't know what has changed. Perhaps
I did make a mistake somewhere along the way.
I'm happy that the problem is 'fixed' for me. But if I can still be of
help, please feel free to ask. I'm pleased to contribute in any way I can.
... Rich
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
