Your message dated Tue, 14 May 2013 23:47:14 +0200
with message-id <[email protected]>
and subject line Re: Bug#560073: icedove (64-bit) + dovecot (32-bit);
communication sometimes breaks down
has caused the Debian Bug report #560073,
regarding icedove (64-bit) + dovecot (32-bit); communication sometimes breaks
down
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.)
--
560073: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560073
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: icedove
Version: 2.0.0.22-0lenny1
Severity: normal
For several months now (but since before I started using iceweasel from sid),
I've noticed that, from my 64-bit icedove client only, sometimes communications
between icedove and dovecot will stop. Icedove will show new messages in the
folder (and I have procmail delivering mail to many separate folders, which
icedove watches for new messages), but when I click on the folder, the new
messages cannot be displayed (none are even shown). Furthermore, old messages
in the same folder cannot be displayed, although the index does continue to
list them.
I think this problem also shows up when I search messages, because sometimes
searches miss messages I know are there.
I have one (32-bit) dovecot IMAP server and multiple clients; however, I've
only seen the probem from the 64-bit version of the client.
This bug sounds similar to 515569, which is also from a 64-bit client, so
perhaps this is a duplication.
My personal suspicion is that this is a dovecot issue, since I recall it
starting after an upgrade to that package, but I don't recall whether that
update also brought a new version of icedove and since the problem only shows
up from the 64-bit client, I figured it's worth reporting here.
I'm happy to provide any debugging assistance necessary.
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.30-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=ANSI_X3.4-1968)
(ignored: LC_ALL set to C)
Shell: /bin/sh linked to /bin/dash
Versions of packages icedove depends on:
ii debianutils 3.2.2 Miscellaneous utilities specific t
ii fontconfig 2.6.0-4 generic font configuration library
ii libatk1.0-0 1.28.0-1 The ATK accessibility toolkit
ii libc6 2.10.2-2 GNU C Library: Shared libraries
ii libcairo2 1.8.8-2 The Cairo 2D vector graphics libra
ii libfontconfig1 2.6.0-4 generic font configuration library
ii libfreetype6 2.3.11-1 FreeType 2 font engine, shared lib
ii libgcc1 1:4.4.2-3 GCC support library
ii libglib2.0-0 2.22.3-1 The GLib library of C routines
ii libgtk2.0-0 2.18.3-1 The GTK+ graphical user interface
ii libhunspell-1.2-0 1.2.8-5 spell checker and morphological an
ii libjpeg62 6b-15 The Independent JPEG Group's JPEG
ii libnspr4-0d 4.8.2-1 NetScape Portable Runtime Library
ii libnss3-1d 3.12.4-1 Network Security Service libraries
ii libpango1.0-0 1.26.1-1 Layout and rendering of internatio
ii libpng12-0 1.2.40-1 PNG library - runtime
ii libstdc++6 4.4.2-3 The GNU Standard C++ Library v3
ii libx11-6 2:1.2.2-1 X11 client-side library
ii libxft2 2.1.13-3 FreeType-based font drawing librar
ii libxinerama1 2:1.0.3-2 X11 Xinerama extension library
ii libxrender1 1:0.9.5-1 X Rendering Extension client libra
ii libxt6 1:1.0.7-1 X11 toolkit intrinsics library
ii psmisc 22.8-1 utilities that use the proc file s
ii zlib1g 1:1.2.3.3.dfsg-15 compression library - runtime
icedove recommends no packages.
Versions of packages icedove suggests:
pn icedove-gnome-support <none> (no description available)
ii latex-xft-fonts 1.6.4-1 TrueType versions of some TeX font
ii libthai0 0.1.12-1 Thai language support library
-- debconf information:
icedove/browser: Debian
--- End Message ---
--- Begin Message ---
No more feedback from the reporter, also the reported version is now
really out of time. So closing this bug
On Fri, Mar 22, 2013 at 06:50:43PM +0100, Carsten Schoenert wrote:
> Hello Mario,
>
> On Tue, Dec 08, 2009 at 11:46:44AM -0700, Mario Nigrovic wrote:
> > Package: icedove
> > Version: 2.0.0.22-0lenny1
> > Severity: normal
> >
> > For several months now (but since before I started using iceweasel
> > from sid), I've noticed that, from my 64-bit icedove client only,
> > sometimes communications between icedove and dovecot will stop.
> > Icedove will show new messages in the folder (and I have procmail
> > delivering mail to many separate folders, which icedove watches for
> > new messages), but when I click on the folder, the new messages cannot
> > be displayed (none are even shown). Furthermore, old messages in the
> > same folder cannot be displayed, although the index does continue to
> > list them.
> >
> > I think this problem also shows up when I search messages, because
> > sometimes searches miss messages I know are there.
> >
> > I have one (32-bit) dovecot IMAP server and multiple clients; however,
> > I've only seen the probem from the 64-bit version of the client.
> >
> > This bug sounds similar to 515569, which is also from a 64-bit client,
> > so perhaps this is a duplication.
> >
> > My personal suspicion is that this is a dovecot issue, since I recall
> > it starting after an upgrade to that package, but I don't recall
> > whether that update also brought a new version of icedove and since
> > the problem only shows up from the 64-bit client, I figured it's worth
> > reporting here.
> >
> > I'm happy to provide any debugging assistance necessary.
>
> your reported bug is still active.
> The reported version isn't available anymore on any current version of
> Debian. I can't reproduce the use case from you but I believe this bug
> is gone. So can you please give some (hopefully positive :) ) feedback
> if this bug could be closed or not?
>
> Regards
> Carsten
--- End Message ---
