Greetings all; I have been looking for help with this on the kde-pim list for 2 or 3 weeks, but apparently I am the oly victim.
Specifically, I have been using kmail for about 15 years now, so when my Ubuntu-10.04.4 LTS drive went read-only a month back, I switched the /dev/sda drive out for a fresh one and installed wheezy on it, 64 bit flavor. The old kmail was 1.13.5, and while it had some maddening warts, I had been discouraged to try another email agent because claws did seem to have a facility where it could import the email corpus I have built up since my last major drive fubar made me start over in 2002. I may have a way worked out to do that, but I would very much rather fix the problem I am having with the kmail-1.13.7 shipping in wheezy. This problem only effects kmails display, and only in the message window where you normally read the message. So, let me see if I can describe it adequately Take this alpha-numeric mixed string, such as one would read in an amanda report where amanda reports its verion number: 3.3.7p1 On the message window only, I get 3.3 ok, but the p1 is placed on top of the 7 and straddling it, so I get an overprinted 3.3.p71, where the p is backspaced and overprinted at the left edge of the 7, and the 1 is overprinted half a space to the right of the center of the 7. So its an unreadable mess. The message window has another font problem, the font is stuck, looks exactly like what I am seeing in this composer window, but the only attribute I can change in the kmail>config>appearance>font is its size. Other font choices when selected do show in the the test window at the bottom of the font selector just fine, and none of them suffer from this problem. It is also possible to crash kmail while atempting to change fonts, so really extensive experimentation is discouraged. I have had synaptic reinstall the usual suspects several times, to no avail. I have, as root, made sure I owned my whole $HOME tree in case a perms problem was the fault, again with no results. Short of trying to switch to claws, which would force a rewrite of the mail suckage support scripts because claws at last check, did not have a dbus port which I use to send kmail a "get mail" message when new mail is detected in /var/spool/mail, delivered by fetchmail from the pop3 servers I use, handed off to procmail where clamav, spamassassin and a lengthy filter recipe list delivers it, that which survives the gauntlet, into /var/spool/mail. Is there a solution to this short of switching to claws? Thank you all. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene> -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201502230850.24709.ghesk...@wdtv.com
