Am 10.08.2016 um 18:18 schrieb Philipp Klaus Krause: [...] >> 833532: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833532 >> 833591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833591 >> 833635: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833635 > > These bug reports are about a segfault on startup. My segfaul thappens > later. > >> 833698: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833698 > > This bug report is about a segfault on the first read from IMAP folders. > My segfaul thappens later. > >> 833864: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833864 >> > > This bug report is about a segfault that happens deterministically upon > some user action. My segfault seems to happens independent of user action. [...]
And there is no other report that fits your regression? I won't believe this. I count 8 bugs with segfaults about Icedove >= 45.1.0 https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=id-crash-45.1.0;users=c.schoen...@t-online.de If all those reports don't correlate your issue than reopen this report and please create a gdb log with some explanation why other bug reports aren't the same. Try to take make a look from my/our side. We have over 200 bug reports with various things. Every new report with a existing issue is just taking times from real fixing issues as we need to go to every single report and collect identical reports and prepare merging and fixing. There is reason why reportbug is showing existing bug reports right after the start. -- Regards Carsten Schoenert
