Bug 374455

Summary:	scaling, using scaling leads to pointing and displaying problems
Product:	[Plasma] plasmashell	Reporter:	Philippe ROUBACH <philippe.roubach>
Component:	general	Assignee:	David Edmundson <kde>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	bhush94, plasma-bugs
Priority:	NOR
Version:	5.6.1
Target Milestone:	1.0
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:

Description Philippe ROUBACH 2017-01-02 10:58:16 UTC

if i choose scale = 1.2 for example then there are problems
if i revert to scaling=1 then no more problems


1. - konsole display
  strange white line

2. kmail 
2.1.

if you click an url in a mail then between the central column and the right column is added an image of a part of the central column

2.2.

if i put mouse cursor above an url in a mail then the mouse cursor does not switch to "hand" cursor then if i click on the url nothing happens

if i put 3 lines above the url the mouse cursor then it switches to "hand" cursor
then
if i click FF is launched.

3. akregator 

if you click an url in a news then a kontact windows is opened with the content of the url (good) but to move the vertical slider you must put the mouse cursor beside the slider at right.

Comment 1 David Edmundson 2017-01-02 19:32:09 UTC

Then you need to file bugs with those programs.

Comment 2 David Edmundson 2017-01-02 19:39:46 UTC

See also linked reports, it seems one has been filed for kmail.

*** This bug has been marked as a duplicate of bug 374014 ***

Comment 3 Philippe ROUBACH 2017-01-02 22:32:20 UTC

(In reply to David Edmundson from comment #1)
> Then you need to file bugs with those programs.

Those applications has no problem.
As i said:
>>if i choose scale = 1.2 for example then there are problems
>>if i revert to scaling=1 then no more problems

it's a scaling problem
and
it's not a font rendering problem so i don't understand you mark it as a duplicate of bug 374014

Comment 4 David Edmundson 2017-01-03 23:54:00 UTC

it's a problem with the apps not supporting the scaling.

It's not a font problem, but it's where scaling artifacts are most visible if they go via a (non scaled) pixmap cache.

It's an application problem because this scaling is just a setting, actually doing the scaling is the responsibility of the application.