Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 498112 - =media-gfx/qiv-2.3.1 - qiv -n,--no_filter fails for files without a filename extension
Summary: =media-gfx/qiv-2.3.1 - qiv -n,--no_filter fails for files without a filename ...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: AMD64 Linux
: Normal normal (vote)
Assignee: Gentoo Graphics Project
URL:
Whiteboard:
Keywords: PATCH
Depends on:
Blocks:
 
Reported: 2014-01-14 23:46 UTC by Mark Casagrande
Modified: 2018-07-01 15:13 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
emerge --info for my machine (emerge-info.txt,6.51 KB, text/plain)
2014-01-14 23:46 UTC, Mark Casagrande
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mark Casagrande 2014-01-14 23:46:32 UTC
Created attachment 367860 [details]
emerge --info for my machine

qiv-2.3.1 does not open files that do not have an "extension" when using the -n or --no_filter option.

Steps to reproduce:
1. Obtain a supported image file that does not have an "extension", for example:
cp foo.jpg bar

2. Attempt view the file with qiv, using the '-n' or '--no_filter' options:
qiv --no_filter bar

Result:
qiv does not display the file:

qiv: cannot load any images.
qiv (Quick Image Viewer) v2.3.1
Usage: qiv [options] files ...
See 'man qiv' or type 'qiv --help' for options.

If I compile the unmodified qiv-2.3.1 source, qiv works properly.

If I make the following modification to the qiv-2.3.1 ebuild and re-emerge, qiv works properly:

src_prepare() {
#       sed -i \
#               -e 's:$(CC) $(CFLAGS):$(CC) $(LDFLAGS) $(CFLAGS):' \
#               Makefile || die

If I add the contents of $LDFLAGS (as reported by 'emerge --info') to the otherwise-unmodified qiv-2.3.1 Makefile and recompile, qiv works properly.
Comment 1 Tim Harder gentoo-dev 2018-07-01 15:13:51 UTC
Closing since I can't reproduce this with 2.3.2.