Bug 277254

Summary:	PDF file displays wrong title in titlebar
Product:	[Applications] okular	Reporter:	Jim <guilfordstuff>
Component:	general	Assignee:	Okular developers <okular-devel>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	creichert07
Priority:	NOR
Version:	0.12.2
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Jim 2011-07-07 02:07:06 UTC

Version:           0.12.2 (using KDE 4.6.2) 
OS:                Linux

Some of my PDF files display the correct filename in the titlebar.  Others display messages like: "ime20133 1..6" or "j403_6g 103..108".  It's not consistent.  These are scientific journal articles.  The journal might have embedded data suggesting a file name, or, it could be a more generic bug.  

Reproducible: Sometimes

Steps to Reproduce:
Open pdf file.
Look at title bar.
Verify that title bar name isn't the actual file name.


Expected Results:  
The title bar should display the filename as it exists on my computer.

OS: Linux (x86_64) release 2.6.38-8-generic
Compiler: cc

Comment 1 Christopher Reichert 2011-07-07 05:46:21 UTC

Could you please attach one of the documents you are having problems with?

Comment 2 Pino Toscano 2011-07-07 07:44:08 UTC

See what you have in each document as "Title" in File -> Properties.

Comment 3 Jim 2011-07-07 14:29:56 UTC

@Pino Toscano:  That's exactly what it is.  The File->Properties->Title shows some bogus database title from the publisher.  The ones that display the proper filename as the title do not.  

It seems like a design decision to not always use the filename.  This really messes things up when I have multiple files open.  Other PDF readers I've used ignore the filename property.  Can you set a policy that filename over rides Property Title or vice-versa?  You can leave it as an option in settings, although, I can't think of a scenario where you would need it.  It seems like the sort of thing that could be exploited for phishing.

Comment 4 Albert Astals Cid 2011-07-10 20:32:38 UTC


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