Version: unspecified (using KDE 4.5.4) OS: Linux The copying function in KMail produces garbage. Reproducible: Always Steps to Reproduce: Select some text in a message in KMail, press C-C to copy it. For example, I've selected word 'Slashdot' in my email. Pasting it gives: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "DTD/xhtml1-strict.dtd"> <body>Slashdot</body> In order to correctly paste the text 'Slashdot' I need to click the Klipper icon and select this text (it appears just below the garbage; it seems that the text is copied and then again the garbage is copied). Actual Results: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "DTD/xhtml1-strict.dtd"> <body>Slashdot</body> Expected Results: Slashdot
The same with Kmail in KDE 4.6 RC2
Bleh, I'm tired today. Back to KMail 1. This cannot be reproduced with KMail2.
*** Bug 266320 has been marked as a duplicate of this bug. ***
Busted in KDE 4.6 release (Kubuntu packages on Ubuntu 10.10). Any chance of an immediate fix rather than waiting for the next point update, this is a fairly horrible bug !
Can't even copy from preview window in KMail Kontact component to new compose window without the HTML stuff appearing. Oops. Surely the KMail developers have seen this, and a fix is already done ?
Still busted in 4.6.1 !
*** Bug 269304 has been marked as a duplicate of this bug. ***
Hmm, interesting observation: If I double click a word in Kmail to highlight it, then middle (well, left and right at the same time) click in (say) FireFox, the text comes through OK. If I TAB back to Kontact and CTRL-C and then CTRL-V in FireFox, you get HTML-wrapped-garbage again. Odd. FWIW My Klipper settings are to prevent empty clipboard and ignore selection.
Please eleminate this bug! Mandriva 2010.2 KDE 4.5.4. Regards, TeaAge
(In reply to comment #9) > Please eleminate this bug! > Mandriva 2010.2 KDE 4.5.4. > > Regards, > TeaAge fixed since January.. Make sure you use kmail 1.13.6 *** This bug has been marked as a duplicate of bug 259468 ***
*** Bug 274770 has been marked as a duplicate of this bug. ***