On Mon, Jul 03, 2006 at 11:44:25AM -0700, Ross Boylan <[EMAIL PROTECTED]> was heard to say: > I suspect this has to do with aptitude trying to work out dependency > conflicts. I've been using aptitude update (from the command line) > but apt-get for my dist-upgrades and upgrades. So aptitudes notion of > how things should be is pretty far from the current system state > (e.g., the system went through the X 7 upgrade awhile ago). When > aptitude starts it shows there are conflicts, and when I go to examine > them the display of open/closed/etc keeps updating counts. I presume > this was going on during the update, and suspect the crash has > something to do with that.
Thank you for that piece of information; it's enough for me to resolve this bug and probably some of the other weird segv bugs people have filed recently (many of which mentioned updating, now that I think of it). > It might be relevant that when I started aptitude before the X > transition (but when the new X was available) it would ask if I > wanted to examine alternatives. It would show 1/1, but then when I > selected next alternative it would show 2/2, and so on, seemingly > without limit. See the documentation for an explanation of what the count indicator means. Basically, when it says [1(1)/...], that means that it doesn't know how many solutions there are, but it has generated 1 of them so far. Obviously counting the solutions up front would be better but for technical reasons -- meaning "there might be way too many of them" -- it's not feasible to do so. Daniel
signature.asc
Description: Digital signature
