Your message dated Sun, 17 Jan 2010 12:54:57 +0100
with message-id <[email protected]>
and subject line Closing
has caused the Debian Bug report #296486,
regarding Fonts have color fringes - subpixel antialiasing - without request
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.)
--
296486: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=296486
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: licq-plugin-qt
Version: 1.3.0-2
Severity: normal
I'm a long-time happy licq user, but I've recently (like in the last
few days, perhaps? Last week, anyway) noticed that the letters in the
message window have blue and red fringes on the sides. It looks a lot
like subpixel antialiasing is turned on. But I didn't ask for that,
and I don't know how to turn it off.
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.11rc4
Locale: LANG=C, LC_CTYPE=en_US.ISO-8859-1 (charmap=ISO-8859-1)
Versions of packages licq-plugin-qt depends on:
ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an
ii libgcc1 1:3.4.3-9 GCC support library
ii libice6 4.3.0.dfsg.1-10 Inter-Client Exchange library
ii libqt3c102-mt 3:3.3.3-8 Qt GUI Library (Threaded runtime v
ii libsm6 4.3.0.dfsg.1-10 X Window System Session Management
ii libstdc++5 1:3.3.5-8 The GNU Standard C++ Library v3
ii libx11-6 4.3.0.dfsg.1-10 X Window System protocol client li
ii libxext6 4.3.0.dfsg.1-10 X Window System miscellaneous exte
ii licq 1.3.0-2 ICQ client (base files)
ii xlibs 4.3.0.dfsg.1-12 X Keyboard Extension (XKB) configu
-- no debconf information
--- End Message ---
--- Begin Message ---
This looks more like an environment problem and as it is very old I'm
closing it.
Please reopen the bug if the problem persists with the latest version of Licq.
Thanks,
/Erik
--- End Message ---
