Bug 375719

Summary:	Blue rendering artifacts in Okular with "draw border around links" turned on
Product:	[Applications] okular	Reporter:	argo_ <l676476>
Component:	general	Assignee:	Okular developers <okular-devel>
Status:	RESOLVED FIXED
Severity:	normal	CC:	aacid, mjr
Priority:	NOR
Version First Reported In:	1.0.0
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:	https://commits.kde.org/okular/af6e9a9b0b7998aeb5bf2a902916f4bba9cc8d71	Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	problematic setting turned on problematic setting turned off

Description argo_ 2017-01-29 18:33:13 UTC

Created attachment 103703 [details]
problematic setting turned on

In 16.12 Okular release there is some weird rendering/clipping issue (occurs with PDFs and EPUBs at least) with links when "draw border around links" option is checked. If my memory's not at fault 16.08 were free of this bug.
Some info on my system:
Qt: 5.7.1
Okular: 16.12.1
KDE Frameworks: 5.30
Plasma: 5.8.5
xorg-server: 1.19.1
GPU: Intel(R) HD Graphics 530 (Skylake GT2)
GPU driver: xf86-video-intel 2.99.917+747+g028c946d-1
Mesa: 13.0.3

See attached screenshots of second page from http://alexvermeer.com/download/8760-hours-v2.pdf in full screen mode.

Comment 1 argo_ 2017-01-29 18:34:50 UTC

Created attachment 103704 [details]
problematic setting turned off

Comment 2 Albert Astals Cid 2017-02-01 00:00:45 UTC

Yeah somethings wrong.

Comment 3 Albert Astals Cid 2017-02-01 23:27:34 UTC

Git commit af6e9a9b0b7998aeb5bf2a902916f4bba9cc8d71 by Albert Astals Cid.
Committed on 01/02/2017 at 23:26.
Pushed by aacid into branch 'Applications/16.12'.

Fix rendering artifacts in Okular with "draw border around links" turned on

Qt5 changed the default QPen to not be cosmetic, so we need to specify we want it to be cosmetic

M  +1    -1    ui/pagepainter.cpp
M  +2    -2    ui/pagepainter.h

https://commits.kde.org/okular/af6e9a9b0b7998aeb5bf2a902916f4bba9cc8d71

Comment 4 Albert Astals Cid 2017-02-09 22:24:53 UTC

*** Bug 376222 has been marked as a duplicate of this bug. ***