Bug 356680

Summary:	Faulty font rendering in Calendar
Product:	[Plasma] plasmashell	Reporter:	Viorel-Cătălin Răpițeanu <rapiteanu.catalin>
Component:	Calendar widget	Assignee:	Martin Klapetek <mklapetek>
Status:	RESOLVED UPSTREAM
Severity:	minor	CC:	plasma-bugs, rapiteanu.catalin
Priority:	NOR
Version:	5.5.0
Target Milestone:	1.0
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	Faulty font rendering in Calendar popup

Description Viorel-Cătălin Răpițeanu 2015-12-14 12:30:19 UTC

The numbers 6 and 7 are not rendered in the calendar created from the clock popup.

Reproducible: Always

Steps to Reproduce:
1. Open calendar popup.


Actual Results:  
The numbers 6 and 7 are not rendered in the calendar.

Expected Results:  
All the calendar numbers should be correctly rendered.

- Attached screenshot of the described problem.

Comment 1 Viorel-Cătălin Răpițeanu 2015-12-14 12:30:52 UTC

Created attachment 96061 [details]
Faulty font rendering in Calendar popup

Comment 2 Martin Klapetek 2015-12-14 14:25:40 UTC

Thanks for the report

I'm really not sure what's up with that. Does it stay like that when you reboot?

Comment 3 Viorel-Cătălin Răpițeanu 2015-12-14 14:42:33 UTC

> I'm really not sure what's up with that. Does it stay like that when you reboot?
No. The font is being rendered correctly after a reboot.
I'll try to see if I'm able to reproduce this issue again, and reply back.

Additional info:
I'm using nouveau driver as a video driver:
- xf86-video-nouveau 1.0.12-1
- mesa 11.0.7-1

Comment 4 Martin Klapetek 2015-12-14 18:08:42 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.

Additionally changing your fonts might help too, although
I realize that this is less than ideal suggestion.

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

Comment 5 Viorel-Cătălin Răpițeanu 2015-12-14 18:23:42 UTC

I've tried a few more times, but I was unable to reproduce this problem.

> [1] https://bugreports.qt.io/browse/QTBUG-42386
This is indeed be the problem I was seeing. If I'll encounter this problem again, I'll add a comment on the Qt report posting all the debugging information I can.

Thanks for the reply!