Control: reopen 510589
On 01/11/2013 01:14 PM, Carsten Schoenert wrote: there are no more news from
you. So I will asume that no more errors
happen and I will close this bug.
If you have some useful debugging infos from your icedove missbehavior
please send them and reopen this bug.
Funny
On 11/02/2012 07:24 PM, Carsten Schoenert wrote:
any good (or bad) news on this?
Hopefully there are no more crashes of icedove ...
alas, i actually *have* had some segfaults with icedove
10.0.10-1 recently, but wasn't able to get a backtrace from either of
them (always running icedove under
Hello Daniel,
any good (or bad) news on this?
Hopefully there are no more crashes of icedove ...
Regards
Carsten
On Tue, Jul 24, 2012 at 04:56:25PM -0400, Daniel Kahn Gillmor wrote:
On 07/24/2012 03:56 PM, Carsten Schönert wrote:
over the last weeks I have expanded the Wiki page, there
Hello again,
over the last weeks I have expanded the Wiki page, there should be
mostly all written to make a backtrace off any crash from icedove.
For the first it would be fine to know which versions you use.
Regards
Carsten
Am 24.06.2012 09:05, wrote Carsten Schonert:
Hello Daniel,
Am
On 07/24/2012 03:56 PM, Carsten Schönert wrote:
over the last weeks I have expanded the Wiki page, there should be
mostly all written to make a backtrace off any crash from icedove.
For the first it would be fine to know which versions you use.
at the moment, i'm using 10.0.5-1 (from debian
Hello Daniel,
Am 22.06.2012 04:37, schrieb Daniel Kahn Gillmor:
Alas, yes, i have had segfault crashes of icedove in the last month
(though not in the last couple weeks) running packages from
testing/unstable. However, i have not been able to successfully capture
any sort of backtrace or
On 06/12/2012 01:11 PM, Carsten Schoenert wrote:
I know it's a long time gone since your bugreport. Do you have this crashes
also with the actual versions of icedove?
If yes the debugging has to be done in an other way because icedove is
multithreaded. In your reports are the debugging
Hello Daniel,
I know it's a long time gone since your bugreport. Do you have this crashes
also with the actual versions of icedove?
If yes the debugging has to be done in an other way because icedove is
multithreaded. In your reports are the debugging symbols for the glibc
are missing for
found 510589 2.0.0.22-1
thanks
I'm still seeing crashes in icedove after having upgraded to 2.0.0.22-1.
Below is the backtrace prior to the latest segfault. It happened about
24 hours after installing the new version (and restarting icedove after
the upgrade, of course). The only extensions i
9 matches
Mail list logo
