Bug 18020 - Gwenview is associated with tiff files but does not display them
Summary: Gwenview is associated with tiff files but does not display them
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Rémi Verschelde
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-16 10:05 CET by Jüri Ivask
Modified: 2016-04-25 19:51 CEST (History)
1 user (show)

See Also:
Source RPM: gwenview-16.04.0-1.mga6
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Jüri Ivask 2016-03-16 10:05:24 CET 
Description of problem:Gwenview is associated with tiff files but does not display them


Version-Release number of selected component (if applicable): 15.12.3


How reproducible:


Steps to Reproduce:
1.Try to open a tif file by right-click -> open with gwenview
2.Result: Loading âfile.tifâ failed. Loading meta information failed.

Support for tiff (and some other) images is provided by qtimageformats5 package (installing it makes gwenview to display tiff files OK) and it does not contain according .desktop files so I guess it should be a dependency of gwenview package...
Comment 1 Jüri Ivask 2016-04-25 10:20:41 CEST 
Bug still present in gwenview-16.04.0-1.mga6...
Comment 2 Rémi Verschelde 2016-04-25 13:20:19 CEST 
I'll look into it asap.

CC: (none) => mageia
Assignee: mageia => rverschelde
Source RPM: gwenview-15.12.3-1.mga6.src.rpm => gwenview-16.04.0-1.mga6

Comment 3 Rémi Verschelde 2016-04-25 19:51:43 CEST 
Should be fixed by gwenview-16.04.0-2.mga6.

@Nicolas: I added qtimageformats5 as a Requires, since the mime types for TIFF, WEBP and Co. are provided by gwenview. We could add it as a Recommends if need be (as Arch did [0]), but we'd likely have to filter out the mime types.

[0] https://bugs.archlinux.org/task/43633

Resolution: (none) => FIXED
Status: NEW => RESOLVED
Note You need to log in before you can comment on or make changes to this bug.