Package: icedove
Version: 1:45.6.0-2
Followup-For: Bug #829188
Me too, in 45.6.0-2 (running on stretch).
I'll try upgrading to unstable's version and running through the recommended
command-line. This is from a simple gdb, non-stopping on SIGPIPE, with
extensions enabled (iceowl, google provider
Package: icedove
Version: 1:45.6.0-2
Followup-For: Bug #829188
Dear Maintainer,
the crash still happens with 1:45.6.0-2, see attached log. Excerpt:
[...]
Thread 1 "icedove-bin" received signal SIGSEGV, Segmentation fault.
[...]
Thread 1 (Thread 0x77fb8740 (LWP 11724)):
#0 0x7fffb6064578
Package: icedove
Version: 1:45.4.0-1
Followup-For: Bug #829188
backtraces as described in https://wiki.debian.org/Icedove#Debugging are
attached
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectu
Hello.
I've got another crash, bt attached.
I want to specify that I've Iceowl and Provider for Google Calendar
installed and disabled.
Regards
On 09/14/16 11:11, Elio Voci wrote:
Hello.
Icedove keeps crashing several times a day, with no apparent reason.
I've collected two distinct bt, at
Tony Houghton ha scritto il 20/08/2016 alle 21:49:
On 12/07/16 19:00, Carsten Schoenert wrote:
this file is not available (any longer).
The information on how to get a "valid" backtrace can be found in the
Debian Wiki. Please do a log by the way described in the wiki.
https://wiki.debian.or
Package: icedove
Version: 1:45.2.0-3
Followup-For: Bug #829188
Hi,
I am also having this bug - which is a SIGSEGV related to
nsDisplayList::DeleteAll. I also reported bug #834392 - which is a SIGSEGV in
morkNode::SlotStrongNode. The log attached to comment #142 seems to relate to
#834392. Com
Severity: important
thanks
On Fri, Jul 01, 2016 at 10:43:33AM +0100, Matthew Vernon wrote:
> Package: icedove
> Version: 1:45.1.0-1
> Severity: serious
decreasing the severity to important.
The package isn't violating the Debian policy nor the package is
unsuitable for release.
https://www.debi
Hello Tony,
On Tue, Jul 12, 2016 at 03:47:27PM +0100, Tony Houghton wrote:
> I've also been experiencing frequent crashes with version 4x. I'm not
> sure, but it seems to occur just after it's opened and displayed a
> message. One particular message has just triggered a crash twice in a
> row, but
Package: icedove
Version: 1:45.2~b1-1
Followup-For: Bug #829188
I've also been experiencing frequent crashes with version 4x. I'm not
sure, but it seems to occur just after it's opened and displayed a
message. One particular message has just triggered a crash twice in a
row, but not every time I o
Package: icedove
Version: 1:45.1.0-1~deb8u1
Followup-For: Bug #829188
Hi,
I can confirm this happens often. I use IMAPS for mail access and the only
extensions I have are the IceOwl included in Debian, Enigmail and
tb-personal-level-indicator.
Simon
-- System Information:
Debian Release: 8.5
Package: icedove
Version: 1:45.1.0-1
Severity: serious
Hi,
The most recent icedove is far too unstable; it SEGVs fairly frequently.
I run it on my workstation at work, starting it afresh in the morning
and closing it when I leave work. I estimate I'm seeing a SEGV about
every other work-day. T
11 matches
Mail list logo
