Le 10/08/2016 à 08:26, Carsten Schoenert a écrit : > Hello Jean-Philippe, > > On Tue, Aug 09, 2016 at 10:45:35PM +0200, Jean-Philippe MENGUAL wrote: >>> Please follow the hints from the wiki site to create a proper gdb log. >>> >>> https://wiki.debian.org/Icedove#Debugging >> >> Well this page is interesting but very complicated for me. I'm not a >> dev. I can help with instructions to track some bug, some traces, but I >> can't try to get all introduced traces without knowing what is useful or >> not. I'M unable to know exactly what to trace. >> >> To start with something, I installed icedove-dbg, I ran the suggested >> command and follo9ed gdb process. In the command, I removed LANG= (so it >> runs in fr_FR.utf8 locale), and --safe-mode. It doesn't segfaults in >> safe-mode and with LANG= >> >> Here's the full log. > > the log is fine and is showing what I expected. So you've done > everything well and correctly. > The only thing what makes my life harder here is the LANG environment. > As you wrote you don't have done any unsetting here the system will use > your prefered language and that is French. But I'm and most of the other > guys on the Icedove packaging don't speak or can read the french > language. That's the reason for the 'LANG= ' at the beginning of the > command line. So please use the 'LANG= ' variable the next time you > make a gdb log. That's common to all gdb logs for the BTS.
Actually I guessed this. :) I didn't use it as with it, I didn't reproduce the bug as obviously as without it. But I understood the purpose of it. Anyway, if you need me to translate some things, tell me, I'll do it. > And yes, bug triaging is most of the time difficult and time consuming. > So it needs it's time to get similar with the routines and workflows on > that. For me it's in the end more fun to see if some challanges could be > solved than frustration, otherwise I wouldn't do that at all. Sure. Glad to help in such tasks. > [...] >> That's right these bugs are closely mine, especially the last one. Note >> I don't have iceowl enabled, but it's installed however. > > The problem is not iceowl-extension or calendar-google-provider or any > other XUL based extension. The problem is the Icedove binary itself that > is executing stuff in machine code called by the extensions. > >> What makes me write here (but maybe we should merge bug reports), is >> that I didn't experience this with previous release (45.2). In other >> words, I didn't reproduce above bugs, which arrive now after upgrade. > > I will merge the bugs together. > It's easier to clone existing bugs into two or more reports than > coordinate up to five existings bugs like here. We have a great bug > reporting and tracking engine, but it has some limitations (like every > helping tool). Sure. You're right. Make me Cc of merge so that I can test eventual upgrades, etc. > [...] >> I understand and would be glad to help. Just I need to be oriented, as I >> don't know exactly the differences with Thunderbird, if some Thunderbird >> come back is planned as Firefox, and 9here to search in a such big >> project. What I caN do here is reproduce, test, send precise reports, >> test packaging, and dialog. > > Fine. That's excately what we need as legwork from the users that > reporting bugs and issues. :-) > And yes, there will be Thunderbird back in Debian. ok nice. I stay available for any help. Best regards, > Regards > Carsten > -- Jean-Philippe MENGUAL HYPRA, progressons ensemble Tél.: 01 84 73 06 61 Mail: cont...@hypra.fr Site Web: http://hypra.fr
