Bug 411844

Summary: Info panel displays EXIF data for all documents (DOC etc.)
Product: [Applications] dolphin Reporter: Branimir Amidzic <mail>
Component: panels: informationAssignee: Dolphin Bug Assignee <dolphin-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: normal CC: nate, postix
Priority: NOR    
Version First Reported In: 19.08.1   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Screenshot of document details

Description Branimir Amidzic 2019-09-12 08:26:18 UTC
Created attachment 122622 [details]
Screenshot of document details

SUMMARY
Info panel (as well as document "tooltip") displays bogus data about files. If I select some MS Word document, it displays EXIF image data, like Width, Height, Camera, Exposure, Shutter Speed... (probably remained in cache from some JPG).


STEPS TO REPRODUCE
1. In Gwenview in "Metadata" pane check that you want to display Camera details (manufacturer, model).
2. In Dolphin, move mouse pointer over some file that has no EXIF data (like MS Word document), or
3. in Dolphin, open info pane and select some file that has no EXIF data (like MS Word document).

OBSERVED RESULT
The file tooltip or info pane displays bogus data about the file.


EXPECTED RESULT
Info pane should display only data relevant to selected file.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux (current, kernel 4.19.71-1-lts)
KDE Plasma Version: 5.16.5
KDE Frameworks Version: 5.61.0
Qt Version: 5.13.0

ADDITIONAL INFORMATION
Comment 1 postix 2020-02-10 20:51:35 UTC
Cannot reproduce this on

Operating System: Manjaro Linux 
KDE Plasma Version: 5.17.5
KDE Frameworks Version: 5.67.0
Qt Version: 5.14.1
Kernel Version: 5.5.2-1-MANJARO

The tested MS docx and odt files don't show any kind of exif data in Dolphin's info panel for me.
Comment 2 Branimir Amidzic 2020-02-11 09:32:04 UTC
I haven't seen it lately. Maybe this should be closed, since it is not known how to reproduce the behavior.
Comment 3 postix 2020-02-11 10:29:33 UTC
(In reply to Branimir Amidzic from comment #2)
> I haven't seen it lately. Maybe this should be closed, since it is not known
> how to reproduce the behavior.

Let's reopen it once the bug comes back.