Bug 1798743

Summary:	feh is looking for images in wrong directory
Product:	[Fedora] Fedora	Reporter:	Antony Lee <anntzer.lee>
Component:	feh	Assignee:	Ben Boeckel <fedora>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	31	CC:	alebastr89, fedora, ivazqueznet, me
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	feh-3.4-1.fc32	Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-04-25 02:21:54 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Antony Lee 2020-02-05 21:30:02 UTC

Description of problem:
feh is looking for images in wrong directory, causing it to emit warnings when opening menus.

Version-Release number of selected component (if applicable):
feh-3.1.3-3.fc31.x86_64

How reproducible:
Always (locally).

Steps to Reproduce:
Open an image, right click to open a menu.

Actual results:
feh WARNING: /usr/local/share/feh/images/menubg_default.png - File does not exist
(Note: the rpm package instead contains /usr/share/feh/images/menubg_default.png)

Expected results:
No such warning.

Additional info:
This appears to be exactly the same as https://bugzilla.redhat.com/show_bug.cgi?id=845256, which was supposedly fixed in feh-2.3-3.fc18, but somehow came back.

Comment 1 Aleksei Bavshin 2020-04-15 07:23:48 UTC

Fixed with feh 3.4 update in Fedora 32: https://bodhi.fedoraproject.org/updates/FEDORA-2020-1d091eeeac

Comment 2 Fedora Update System 2020-04-15 21:06:55 UTC

FEDORA-2020-1d091eeeac has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-1d091eeeac

Comment 3 Fedora Update System 2020-04-25 02:21:54 UTC

FEDORA-2020-1d091eeeac has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.