Your message dated Tue, 25 Aug 2015 10:06:47 +0200
with message-id <[email protected]>
and subject line Re: Bug#672366: Disabling "Automatically mark messages as 
read" does no longer work properly
has caused the Debian Bug report #672366,
regarding Disabling "Automatically mark messages as read" does no longer work 
properly
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.)


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

Hello,

Since recently, Icedove has started marking (some) messages as read
when I display them, even though I explicitly disabled "Automatically
mark messages as read" in preferences. It happens when I click on a
message, or when I navigate through them with keyboard shortcuts (b,
f, n).

I've understood this very annoying behaviour today, but the last time
I've upgraded icedove (from version 3.1.16-1) was on April 9th, and I
upgrade quite often. I cannot reproduce it deterministically and it
took me time to understand what was going wrong, so it could be that
the bug has been there for one month.


Cheers,

-- 
Stéphane


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

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

Versions of packages icedove depends on:
ii  debianutils               4.3
ii  fontconfig                2.9.0-3
ii  libasound2                1.0.25-2
ii  libatk1.0-0               2.4.0-2
ii  libc6                     2.13-32
ii  libcairo2                 1.12.2-1
ii  libdbus-1-3               1.5.12-1
ii  libdbus-glib-1-2          0.98-1
ii  libevent-2.0-5            2.0.18-stable-1
ii  libffi5                   3.0.10-3
ii  libfontconfig1            2.9.0-3
ii  libfreetype6              2.4.9-1
ii  libgcc1                   1:4.7.0-7
ii  libgdk-pixbuf2.0-0        2.26.1-1
ii  libglib2.0-0              2.32.0-4
ii  libgtk2.0-0               2.24.10-1
ii  libhunspell-1.3-0         1.3.2-4
ii  libjpeg8                  8d-1
ii  libnspr4-0d               4.9-1
ii  libnss3-1d                3.13.3-1
ii  libpango1.0-0             1.30.0-1
ii  libpixman-1-0             0.24.4-1
ii  libsqlite3-0              3.7.11-2
ii  libstartup-notification0  0.12-1
ii  libstdc++6                4.7.0-7
ii  libvpx1                   1.0.0-2
ii  libx11-6                  2:1.4.99.901-2
ii  libxext6                  2:1.3.1-2
ii  libxrender1               1:0.9.7-1
ii  libxt6                    1:1.1.3-1
ii  psmisc                    22.16-1
ii  zlib1g                    1:1.2.6.dfsg-2

Versions of packages icedove recommends:
ii  hunspell-fr [hunspell-dictionary]  1:3.3.0-3

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

-- no debconf information



--- End Message ---
--- Begin Message ---
Version: 38.0.1-1

Hello Stéphane,

On Thu, May 10, 2012 at 01:54:01PM +0200, Stéphane Glondu wrote:
> Package: icedove
> Version: 10.0.3-3
> Severity: normal
> 
> Hello,
> 
> Since recently, Icedove has started marking (some) messages as read
> when I display them, even though I explicitly disabled "Automatically
> mark messages as read" in preferences. It happens when I click on a
> message, or when I navigate through them with keyboard shortcuts (b,
> f, n).
> 
> I've understood this very annoying behaviour today, but the last time
> I've upgraded icedove (from version 3.1.16-1) was on April 9th, and I
> upgrade quite often. I cannot reproduce it deterministically and it
> took me time to understand what was going wrong, so it could be that
> the bug has been there for one month.

while going thrue the bug queue I tried to readjust this behaviour. On
current versions 38.x and 40.0 I can't reproduce it. I think this issue
was fixed some longer time ago.

I will close your report by this email. Please reopen if I missed
something here.

Regards
Carsten

--- End Message ---

Reply via email to