Bug 23776

Summary: Firefox: Bad application for PDF after update
Product: Mageia Reporter: Pierre Jarillon <jarillon>
Component: RPM PackagesAssignee: All Packagers <pkg-bugs>
Status: RESOLVED OLD QA Contact:
Severity: major    
Priority: High CC: fri, gm2.asp, marja11, ouaurelien, sebsweb
Version: 6   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: firefox CVE:
Status comment:

Description Pierre Jarillon 2018-10-28 17:49:07 CET
With recent updates 60.2 and 6.3 of Firefox, the application used to read (or print) a PDF was setted to Gimp.
This happen on a production machine and users were unable to repair. They were unable to get and print indispensable documents.

I have modified and set PDF instead of Gimp.
Pierre Jarillon 2018-10-28 17:49:41 CET

Priority: Normal => High

Comment 1 Sébastien Morin 2018-10-28 20:13:02 CET
Sorry, I can't reproduce this bug:
when I click on a link to open a PDF file, this PDF document is opened in Firefox (in the current tab if I left-click, in a new tab when I middle-click) as usual.

The PDF file is not sent into Gimp for viewing.

Version used:
firefox-fr-60.3.0-1.mga6
firefox-60.3.0-1.mga6

CC: (none) => sebsweb

Comment 2 Marja Van Waes 2018-10-29 08:38:53 CET
Can anyone reproduce it?

(In a different Mga version, the cauldron I'm using now, pdf files open fine in FF.)

Assigning to all packagers collectively, since there is no registered maintainer for this package.

Assignee: bugsquad => pkg-bugs
CC: (none) => marja11

Comment 3 Arne Spiegelhauer 2018-10-29 22:03:01 CET
I had this problem as well.

When checking Firefox preferences, I found that the application setting for "Portable Document Format (PDF)" was: "Use GIMP (default)".

Before the upgrade to Firefox 60, PDF files opened in okular, so I assume that in a previous version I had changed "Preview in Firefox" to "Use okular (default)".

My guess is that Firefox 60 changed the default application for PDF from ocular to GIMP and translated the PDF setting "Use okular (default)" to "Use GIMP (default)" on upgrade.

CC: (none) => gm2.asp

Comment 4 Pierre Jarillon 2018-10-30 10:38:57 CET
I confirm your guess. This happened when firefox was upgraded to firefox-60.2.2-1.mga6.
The first installation on this machine was Mga6, 10 month ago, regularly upgraded.
Comment 5 Morgan Leijström 2018-10-30 15:10:27 CET
I had FF open pdf in okular before upgrade, now it opens them internally.

CC: (none) => fri

Comment 6 Arne Spiegelhauer 2018-10-30 16:59:05 CET
Inspired by the thread https://forum.kde.org/viewtopic.php?f=225&t=142829, I tried to remove gimp.desktop; from the application/pdf= line in /usr/share/applications/mimeinfo.cache.
The result was that the Firefox application setting for "Portable Document Format (PDF)" changed from "Use GIMP (default)" to "Use Okular (default)", so apparently Firefox is reading the default application from here.

This is not a safe choice, as the man page for update-desktop-database, which builds this file, states:
"The order of the desktop files found for a MIME type is not  significant.   Therefore,  an  external mechanism must be used to determine what is the preferred desktop file for a MIME type"

However, Firefox will have tried other methods and failed, before choosing mimeinfo.cache, maybe as a last resort.
One such method is checking for a PDF entry in ~/.config/mimeapps.list and 
/usr/share/applications/mimeapps.list

I found that, on a Plasma desktop, changing "Application Preference Order" for pdf files in System Settings added pdf entries to ~/.config/mimeapps.list. These entries are updated on further preference order changes (and not removed, even if set back to the original settings). Consequently, when the "Use XXXX (default) setting is chosen in Firefox preferences, Firefox will after the first change comply with the Plasma Application Preference Order setting.

What is missing, is that Firefox should be able to find the preferred PDF application, also when it has not been modified through System Settings.
Comment 7 Aurelien Oudelet 2020-08-16 21:20:21 CEST
Mageia 6 changed to end-of-life (EOL) status on 2019-09-30. It is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan 
to fix it in a currently maintained version, simply change the 'version' to 
a later Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we 
weren't able to fix it before Mageia 6's end of life. If you are able to 
reproduce it against a later version of Mageia, you are encouraged to click 
on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a more recent
Mageia release includes newer upstream software that fixes bugs or makes them
obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Best regards,
Aurélien
Bugsquad Team

Resolution: (none) => OLD
Status: NEW => RESOLVED
CC: (none) => ouaurelien