Your message dated Fri, 7 Jun 2013 19:31:58 +0200
with message-id <[email protected]>
and subject line Re: Bug#690234: Acknowledgement (icedove: Mail displayed 
incorrectly)
has caused the Debian Bug report #690234,
regarding icedove: Mail displayed incorrectly
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.)


-- 
690234: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690234
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: icedove
Version: 11.0-1
Severity: normal

Dear Maintainer,
   * What led up to the situation?
I wanted to find an old email
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
I found the email
   * What was the outcome of this action?
the list displays the email message but the mail view displays what I can only
assume to be some random offset into the compacted mail store.
   * What outcome did you expect instead?
To view the email I selected
*** End of the template - remove these lines ***



-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.5-trunk-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

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-35
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-2
ii  libgtk2.0-0               2.24.10-2
ii  libhunspell-1.3-0         1.3.2-4
ii  libjpeg8                  8d-1
ii  libnspr4-0d               2:4.9.2-1
ii  libnss3-1d                2:3.13.6-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  hunspell-en-us [hunspell-dictionary]  20070829-6

Versions of packages icedove suggests:
ii  gconf-service     3.2.5-1+build1
ii  libgconf-2-4      3.2.5-1+build1
ii  libgssapi-krb5-2  1.10.1+dfsg-2
ii  libnotify4        0.7.5-1
pn  ttf-lyx           <none>

-- no debconf information

<<attachment: icedove.png>>


--- End Message ---
--- Begin Message ---
Version: 17.0.5-1

No more feedback from the reporter, so closing this bug.

On Sun, Apr 14, 2013 at 03:06:39PM +0200, Carsten Schoenert wrote:
> Hello Philip,
> 
> On Thu, Oct 11, 2012 at 02:10:41PM +0100, Philip Ashmore wrote:
> > I'm also getting a lot of messages in the error console, shame
> > there's no way to save them to a text file.
> > 
> > [Exception... "Component returned failure code: 0x80004005
> > (NS_ERROR_FAILURE) [nsIMsgFolder.getStringProperty]" nsresult:
> > "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame ::
> > chrome://messenger/content/folderPane.js :: getSmartFolderName ::
> > 2460" data: no]
> > chrome://messenger/content/folderPane.js
> > 
> > Sorry if I've mistyped anything.
> 
> I can't reproduce this. Works here as expected. Can you append such a
> mail where we can reflect this?
> This happen with current versions too? Do you tried with a clean fresh
> profile and disabled extensions? If we can't reproduce it we can't fix
> it.
> 
> Regards
> Carsten

--- End Message ---

Reply via email to