Bug 187878

Summary: wrong visualization of pdf
Product: [Applications] okular Reporter: Federico Muciaccia <federico1988fm>
Component: PDF backendAssignee: Okular developers <okular-devel>
Status: RESOLVED UPSTREAM    
Severity: normal CC: federico1988fm
Priority: NOR    
Version: 0.8.1   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: test document

Description Federico Muciaccia 2009-03-22 19:37:30 UTC
Version:           0.8.1 (using 4.2.1 (KDE 4.2.1), Arch Linux)
Compiler:          gcc
OS:                Linux (i686) release 2.6.28-ARCH

way to reproduce the bug:
* go to the archlinux wiki (I use konqueror) and save one page (a random topic) as a .pdf
* open it in okular
* you will notice that the document is corrupted, for example there are no occurrence of the "u" letter
* open the same document with anoter viewer (I used the GNOME evince)
* the document looks perfect (eg: the "u" letter is normally present)
Comment 1 Pino Toscano 2009-03-22 19:43:46 UTC
Please attach a sample document showing the issue.

Also, which version of poppler-qt4 do you have installed?
Comment 2 Federico Muciaccia 2009-03-23 20:51:15 UTC
Created attachment 32361 [details]
test document

a document that is bad visualized by okular
Comment 3 Federico Muciaccia 2009-03-23 20:55:42 UTC
[federico@archlinux-laptop ~]$ pacman -Si poppler
Repository     : extra                           
Nome           : poppler                         
Versione       : 0.10.2-1                        
URL            : http://poppler.freedesktop.org/ 
Licenze        : GPL  custom                     
Gruppi         : Nessuno                         
Fornisce       : Nessuno                         
Dipende da     : libjpeg  gcc-libs>=4.3.2  cairo>=1.8.6  
                 libxml2>=2.6.32-5  fontconfig>=2.6.0    
Dip. opzionali : Nessuno                                 
Conflitti con  : Nessuno
Sostituisce    : Nessuno
Dimensione pkg : 4939,49 K
Kb richiesti   : 15564,00 K
Autore         : Jan de Groot <jgc@archlinux.org>
Architettura   : i686
Creato il      : ven 26 dic 2008 17:55:39 CET
Somma MD5      : 46f6ce5af8af06e56452a47e3fe59d83
Descrizione    : PDF rendering library based on xpdf 3.0

[federico@archlinux-laptop ~]$ pacman -Si poppler-qt
Repository     : extra
Nome           : poppler-qt
Versione       : 0.10.2-1
URL            : http://poppler.freedesktop.org/
Licenze        : GPL
Gruppi         : Nessuno
Fornisce       : Nessuno
Dipende da     : qt>=4.4.3  poppler>=0.10.2
Dip. opzionali : Nessuno
Conflitti con  : Nessuno
Sostituisce    : Nessuno
Dimensione pkg : 206,07 K
Kb richiesti   : 656,00 K
Autore         : Jan de Groot <jgc@archlinux.org>
Architettura   : i686
Creato il      : ven 26 dic 2008 18:00:05 CET
Somma MD5      : 7146f321871574f79bceda90b867c992
Descrizione    : Poppler Qt bindings
Comment 4 Pino Toscano 2009-03-30 17:55:19 UTC
Hi,

Okular does not render PDF documents by itself, but uses a 3rd party library
called Poppler.
You should please report the problem to the Poppler's bug tracking system at
https://bugs.freedesktop.org, "poppler" product.

Thank you for the report.
Comment 5 Federico Muciaccia 2009-03-30 23:05:27 UTC
Bug forwarded to https://bugs.freedesktop.org/show_bug.cgi?id=20955

@Pino Toscano:
I don't think that bugs should be closed as "RESOLVED as UPSTREAM" before a bug is effectively forwarded in the "upsteam" bugtracker.
Ok: this is not a bug of KDE, but affects KDE too, so be careful!
If I were a very lazy (or a very busy) user? (I'm not :-P)
Just think:
The bug is marked as RESOLVED, it can have hundreds of duplicates, but no one is working in fixing it!

Until a bug is fixed upstream the bug should be marked as "FORWARDED to ..." (like on Launchpad)

I'm surprised there isn't such option in the bug status (is there? I am blind?)

Should I fill a bug report for the KDE bugzilla?
A wish maybe?

Federico Muciaccia
Comment 6 Pino Toscano 2009-03-31 15:28:36 UTC
(In reply to comment #5)
> Bug forwarded to https://bugs.freedesktop.org/show_bug.cgi?id=20955

Thanks.

> @Pino Toscano:
> I don't think that bugs should be closed as "RESOLVED as UPSTREAM" before a bug
> is effectively forwarded in the "upsteam" bugtracker.

I do, especially when they are not KDE issues.

> The bug is marked as RESOLVED, it can have hundreds of duplicates, but no one
> is working in fixing it!

If there will be the same problem reported again on KDE's bugzilla, it will be closed as duplicate of this one, no big deal.

> Until a bug is fixed upstream the bug should be marked as "FORWARDED to ..."
> (like on Launchpad)

Comparing with Launchpad is wrong.
KDE is not a distribution. It does not need to know the right versions of *all* the products to track for getting their latest version in the next release.

> I'm surprised there isn't such option in the bug status (is there? I am blind?)
> 
> Should I fill a bug report for the KDE bugzilla?
> A wish maybe?

RESOLVED/UPSTREAM is the correct status for that, and we agreed upon that recently.
Comment 7 Federico Muciaccia 2009-04-05 22:09:34 UTC
This bug should now be fixed upstream: http://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/?id=fbdf127904c26714ed69c2c1298c6eb7d564031e
It was a freetype2 bug.

taken from https://bugs.freedesktop.org/show_bug.cgi?id=20955 :

------- Comment #2 From Albert Astals Cid 2009-03-30 15:22:11 PST -------
For some reason freetype fails to render the character i've mailed the freetypedevels.
------- Comment #3 From Albert Astals Cid 2009-04-01 10:16:23 PST -------
As said, not our bug, a freetype one that has been fixed once i reported it,see http://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/id=fbdf127904c26714ed69c2c1298c6eb7d564031e

> RESOLVED/UPSTREAM is the correct status for that, and we agreed upon that recently.
Should I change the status to RESOLVED as FIXED or leave it to RESOLVED as UPSTREAM now?
Does it make any difference?
Comment 8 Pino Toscano 2009-04-05 22:18:23 UTC
> Should I change the status to RESOLVED as FIXED or leave it to RESOLVED as
> UPSTREAM now?

"FIXED" means "the bug is our, and we fixed it".
Given that this is not the case, please don't change the status of this bug. Thanks.