[Aptitude-devel] Bug#816322: aptitude: SIGABRT due to assertion failure when quitting from conflict resolver
Manuel A. Fernandez Montecelo
manuel.montezelo at gmail.com
Thu Mar 3 01:40:57 UTC 2016
Control: tags -1 - moreinfo unreproducible + pending
Hi Katsuhiko,
2016-03-01 19:05 Katsuhiko Nishimra:
>Hi, thank you for the reply.
>
>On Tue, Mar 01, 2016 at 12:30:51PM +0000, Manuel A. Fernandez Montecelo wrote:
>> I could not reproduce it in my systems with the same versions, with
>> either mini-buffer option enabled (as you seem to have) or disabled.
>>
>> Does this happen to you with .7 as well, uploaded earlier today?
>Yes, it happens with 100% reproducibility also with 0.7.7-1 on my sid
>system.
>FWIW, I attach the result from `apt-config dump' and a core-dump from a
>aptitude 0.7.7-1 killed by SIGABRT.
>Please feel free to ask me any other information you want.
I think that I fixed now, but just in case, with the next release
(should happen in a few days), please confirm if it's fixed for you.
Initially I thought that it was happening in both curses and command
line because you mentioned "SIGABRT when quitting a conflict resolver in
aptitude-curses", so I attempted to reproduce it in curses mode instead
of following your instructions more closely -- sorry.
Interestingly, if one accepts a solution then everything is fine (maybe
because the widget is destroyed). The problem happens when quitting
without accepting a solution.
Cheers.
--
Manuel A. Fernandez Montecelo <manuel.montezelo at gmail.com>
More information about the Aptitude-devel
mailing list