Bug 356666 - Letters are randomly missing in Plasma notifications
Summary: Letters are randomly missing in Plasma notifications
Status: RESOLVED UPSTREAM
Alias: None
Product: plasmashell
Classification: Plasma
Component: Notifications (other bugs)
Version First Reported In: 5.4.2
Platform: Other Linux
: NOR normal
Target Milestone: 1.0
Assignee: Martin Klapetek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-12-14 10:00 UTC by Roman Odaisky
Modified: 2015-12-14 18:07 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Roman Odaisky 2015-12-14 10:00:31 UTC
For me, about half the time Plasma notifications in the corner of the screen are shown with half the letters randomly missing. Just blank spaces. For example, see http://qwertty.com/tmp/kde-notifications-missing-letters.png : it was supposed to say “Kopete: Connection trouble with Jabber...” but instead I got “K p   : C n   c      r  bl  wi h Jabb r ...”.

Googling suggests this isn’t limited to Plasma notifications (https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1510959), possibly being a general Qt issue instead, but for me notifications are the only place where the problem occurs.

Reproducible: Sometimes
Comment 1 Martin Klapetek 2015-12-14 14:53:43 UTC
Thanks for the report

Can I please ask what's your graphics card and driver?
Comment 2 Roman Odaisky 2015-12-14 17:51:16 UTC
10de:0de1 VGA compatible controller: NVIDIA Corporation GF108 [GeForce GT 430] (rev a1)
nvidia-352-updates 352.63-0ubuntu0.15.10.1
Comment 3 Martin Klapetek 2015-12-14 18:07:10 UTC
I'm sorry to say that this is somewhat known Qt bug [1][2]
in combination with nvidia. There isn't much we can do about
it except recommending adding 

QML_USE_GLYPHCACHE_WORKAROUND=1

into your /etc/profile.d/ OR /etc/environment and rebooting.

Also might help if you add a comment to the Qt reports.
[1] https://bugreports.qt.io/browse/QTBUG-42386
[2] https://bugreports.qt.io/browse/QTBUG-36976