[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#916297: reportbug: crash after using "Display modified configuration files"



That. IS. the. Full. Traceback.

And speaking of making lives much easier, get off my back.



On 13/12/2018 15.57, Sandro Tosi wrote:
> Just. Report. The. Full. Traceback.
> 
> That would make our lives so much easier
> 
> Thanks!
> 
> On Thu, Dec 13, 2018, 18:45 nemo Inis <nemoinis@hotmail.com wrote:
> 
>> Sandro,
>>
>> 1) that one 'TypeError' line IS the 'unaltered, complete reportbug
>> traceback'
>>
>> 2) I don't think the specific package matters, only that it had a modified
>> config file. e.g. in
>> my case apt-cacher-ng, or apache2, or <insert package name here>
>>
>> 3) the bug is in reportbug/ui/gtk2_ui.py, in the class 'SystemPage(Page)'
>> which defines
>> 'on_child_exited' with two parameters when it should be three (the third
>> parameter being the
>> child's exit status code, as per Vte.Terminal.signals.child_exited
>> documentation for Vte 2.91)
>>
>>
>>
>> On 12/12/2018 12.13, Sandro Tosi wrote:
>>>> When reporting a bug, reportbug sometimes issues a warning that "The
>> following
>>>> configuration files have been modified:" (for the package being reported
>>>> against).
>>>> It then gives the option to Send the modified files, or "Display
>> modified
>>>> configuration files (exit with "q")"
>>>>
>>>> Clicking that button displays the pertinent configuration files OK, but
>> after
>>>> pressing q to exit back to the bug, reportbug dies with:
>>>>
>>>> TypeError: on_child_exited() takes 2 positional arguments but 3 were
>> given
>>>
>>> please report the unaltered. complete reportbug traceback.
>>>
>>> Does it happen for a specific package only or for multiple ones? in
>>> any case, report the exact package this is happening on
>>>
>>
> 

Reply to: