Bug 272186

Summary: After Plasma startup text is painted invisible on black background if cut and paste it
Product: [Unmaintained] plasma4 Reporter: Alexey Chernov <4ernov>
Component: widget-microbloggingAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED FIXED    
Severity: normal CC: kde-bugzilla, thelwyn
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Alexey Chernov 2011-05-01 22:50:26 UTC
Version:           unspecified (using KDE 4.6.1) 
OS:                Linux

Some strange behaviour takes place in Microblogging plasmoid right after the startup of Plasma (or soon after that). If I type some text to message text box, then cut and paste it, it is painted on black background and the text color is black either, i.e. it's invisible (see the screenshot). Taken a look at the code I found that the text box is Plasma::TextEdit object and most possible cause seems to be that on cut (Ctrl+X or whatever) it tooks toHtml() of the text and then pastes it some illegal way.

If I remove all the text from the box with Backspace and start to type and Cut/Copy/Paste again everything works correctly.

Reproducible: Always

Steps to Reproduce:
1. Start Plasma (start KDE, for instance).
2. Type some text in message text box of Microblogging plasmoid.
3. Ctrl+X it and Ctrl+V it.
4. Notice that it's painted with black foreground and background color and you can't read it.
5. Try to type some text further. It's painted the same way. Try to paste some text from another source. It's still painted just the same.
6. Clear the content with Backspace.
7. Type some text and Cut/Paste it. Notice that it's not painted incorrectly anymore.
Comment 1 Kolia 2011-12-03 14:04:34 UTC
Hi Alexey I can't reproduce it in KDE 4.7.3. Can you try again in a more recent version? (I think you forgot to attach the screenshot too)
Comment 2 Alexey Chernov 2011-12-03 15:46:34 UTC
Hi, Kolia. Yes, you're right, it was fixed in 4.7.3 I think (it's actually a workaround, the discussion on it is here: http://git.reviewboard.kde.org/r/102698/). I just lost this report so it can be closed I think.
Comment 3 Kolia 2011-12-03 15:48:45 UTC
Great! closing..
Comment 4 Kolia 2011-12-03 15:49:05 UTC
*** Bug 224216 has been marked as a duplicate of this bug. ***