Your message dated Sun, 1 Jun 2014 18:24:02 +0200
with message-id <[email protected]>
and subject line Re: Bug#695149: icedove: Corrupt address book causes icedove
to segfault
has caused the Debian Bug report #695149,
regarding icedove: Corrupt address book causes icedove to segfault
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
695149: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695149
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: icedove
Version: 17.0-1
Severity: normal
My Icedove address book got corrupted for an unknown reason, and this
caused the program to segfault hard, without any kind of useful error
message. I eventually had to install the icedove-dbg package and use
gdb to figure out what was wrong. Now, I'm a developer so using a
debugger comes to me naturally, but an ordinary user would've probably
hit a brick wall, with there not even being any message to google for.
The address book is still in the Mork text-database format, which has
been criticized for its failed attempt in being human-readable, as well
as inefficient use of space. It appears that fault tolerance can be
added to this list. Even if the file cannot be repaired, the user
should be told what's happening, and offered an option to delete the
damaged file and start over.
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 3.5.0-core2 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages icedove depends on:
ii debianutils 4.3.4
ii fontconfig 2.9.0-7
ii libasound2 1.0.25-4
ii libatk1.0-0 2.4.0-2
ii libc6 2.13-37
ii libcairo2 1.12.2-2
ii libdbus-1-3 1.6.8-1
ii libdbus-glib-1-2 0.100-1
ii libevent-2.0-5 2.0.19-stable-3
ii libffi5 3.0.10-3
ii libfontconfig1 2.9.0-7
ii libfreetype6 2.4.9-1
ii libgcc1 1:4.7.2-4
ii libgdk-pixbuf2.0-0 2.26.1-1
ii libglib2.0-0 2.33.12+really2.32.4-3
ii libgtk2.0-0 2.24.10-2
ii libhunspell-1.3-0 1.3.2-4
ii libjpeg8 8d-1
ii libnspr4 2:4.9.3-1
ii libnss3 2:3.14-1
ii libnss3-1d 2:3.14-1
ii libpango1.0-0 1.30.0-1
ii libpixman-1-0 0.26.0-3
ii libsqlite3-0 3.7.14.1-1
ii libstartup-notification0 0.12-1
ii libstdc++6 4.7.2-4
ii libvpx1 1.1.0-1
ii libx11-6 2:1.5.0-1
ii libxext6 2:1.3.1-2
ii libxrender1 1:0.9.7-1
ii libxt6 1:1.1.3-1
ii psmisc 22.20-1
ii zlib1g 1:1.2.7.dfsg-13
Versions of packages icedove recommends:
ii myspell-en-gb [myspell-dictionary] 1:3.3.0-4
ii myspell-en-us [myspell-dictionary] 1:3.3.0-4
ii myspell-fi [myspell-dictionary] 0.7-18
Versions of packages icedove suggests:
pn fonts-lyx <none>
ii libgssapi-krb5-2 1.10.1+dfsg-3
-- no debconf information
--- End Message ---
--- Begin Message ---
No more feedback from the reporter in all the time.
Without a backtrace or more infos it's quite impossible to find any
issue.
Unfortunately closing this report.
Please reopen if there are further informations.
Regards
Carsten
On Sun, Apr 14, 2013 at 02:14:55PM +0200, Carsten Schoenert wrote:
> Hello Mikko,
>
> On Tue, Dec 04, 2012 at 06:16:52PM +0200, Mikko Rasa wrote:
> > Package: icedove
> > Version: 17.0-1
> > Severity: normal
> >
> > My Icedove address book got corrupted for an unknown reason, and this
> > caused the program to segfault hard, without any kind of useful error
> > message. I eventually had to install the icedove-dbg package and use
> > gdb to figure out what was wrong. Now, I'm a developer so using a
> > debugger comes to me naturally, but an ordinary user would've probably
> > hit a brick wall, with there not even being any message to google for.
> >
> > The address book is still in the Mork text-database format, which has
> > been criticized for its failed attempt in being human-readable, as well
> > as inefficient use of space. It appears that fault tolerance can be
> > added to this list. Even if the file cannot be repaired, the user
> > should be told what's happening, and offered an option to delete the
> > damaged file and start over.
>
> yes, Icedove should act better here, but this fixing has to be done
> upstream. So can you please check if there is a entry in the bugtracker
> on Mozilla? Did found some time make a GDB log with a backtrace?
>
> Regards
> Carsten
--- End Message ---
