Your message dated Mon, 16 Jul 2018 08:27:03 +0200
with message-id <[email protected]>
and subject line Re: Bug#666898: icedove: inconsistent spacing between folder
icon and folder name
has caused the Debian Bug report #666898,
regarding icedove: inconsistent spacing between folder icon and folder name
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.)
--
666898: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666898
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: icedove
Version: 10.0.3-3
Severity: minor
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Since the upgrade to 10.0.x the spacing between the icon and the name of folder
is inconsistent. Folders with new unread messages have less space between the
icon and the name than folders with unread messages or no unread messages.
The attached screenshot contains an example of the situation.
Kind regards
- -- System Information:
Debian Release: wheezy/sid
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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.8.0-3.1
ii libasound2 1.0.25-2
ii libatk1.0-0 2.4.0-1
ii libc6 2.13-27
ii libcairo2 1.12.0-2
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.8.0-3.1
ii libfreetype6 2.4.9-1
ii libgcc1 1:4.7.0-1
ii libgdk-pixbuf2.0-0 2.26.0-2
ii libglib2.0-0 2.32.0-3
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-1
ii libvpx1 1.0.0-2
ii libx11-6 2:1.4.4-4
ii libxext6 2:1.3.0-3
ii libxrender1 1:0.9.6-2
ii libxt6 1:1.1.1-2
ii psmisc 22.16-1
ii zlib1g 1:1.2.6.dfsg-2
Versions of packages icedove recommends:
ii hunspell-de-at [hunspell-dictionary] 20110609-1
ii hunspell-en-us [hunspell-dictionary] 20070829-5
Versions of packages icedove suggests:
ii gconf-service 3.2.3-4
ii libgconf-2-4 3.2.3-4
ii libgssapi-krb5-2 1.10+dfsg~beta1-2
ii libnotify4 0.7.5-1
ii ttf-lyx 2.0.3-2
- -- no debconf information
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAEBCAAGBQJPeYfPAAoJEGny/FFupxmTpVcP/0Hi2KVmAh9xQG9WAck9uude
BU8Tt8N2OwhcgQjBkRiMimWbLsxy75xMNTgpXdnyjtVCOvY/XTZgCPPOEbiYIZnW
k2V80Ky/k3ArRVbauA0vj7LNyLYHT6eV6erVfnIJ45jD0X4wZ4wlj5fTjN3/qPVW
GxlD2wSgB0L1k8vPK8uIlOhra4wsflAjDGFYitNJqVWUOCh+HRVJnWECEmd7iMSP
3eyr+tK4rZKNDk1XJCxF48xjC2jNOVTPil1m4q0xLT7ZigAbA6QYU7SlT2ia/aIK
xgIBnDp4ahNVrNPt2fwxF8VDqfgIO8STnhSLEpPLg9n2z4HyxZnTDQNy/KUZ7GKE
nrEdoE4Eybl0ceBauzG5tSc5Zqwuko+nc4eHlQLp5avKOsv+Vx/FcNKh9630W8MU
esjSan+LG4RoGUmaMM3//pY+Hn5ooEUh2Enr6LgZLnfKtbIiaK69UKgzzRpCKJkM
2rJRLeMxDfZzMDGs9unDFVg3TCr3rxn/caRcis+/J0czobjLFg2CJXIrSID+7fKw
jgw1XLxkw1QFb0YXbdkP9ZGFA5bVm+4VqX2c6bMlFqCZ8ofeCxZ4ZFWCEeSSgW+g
8/ewtm5VaJB06Fh3ZVHernKvfz/wKzfBn1zJSbiWqF6Lk2vSkwOThXsRr8jenheG
47oR38IC8LBjjVD3xi24
=E8gi
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
No more feedback an this issue and obvioulsy fixed long time ago.
So closing the report.
Regards
Carsten
On Sun, Jul 24, 2016 at 06:07:04PM +0200, Carsten Schoenert wrote:
> Hi,
>
> On Tue, Jun 18, 2013 at 01:47:23PM +0100, Klaus wrote:
> > the mis-alignment is now much more severe, see attached
> > screenshot. In my experience this effects only folders that have new
> > un-read mail. Clicking on that folder label once, and subsequently
> > selecting any other folder, re-draws the "wrongly" labelled folder and
> > everything is fine.
>
> I can't reproduce this issue in any case, I think this gone now, should
> we close this report then?
>
> Regards
> Carsten
--- End Message ---
