Bug 8503 – Loading .ppm failes - convert called with wrong path

Bug 8503 - Loading .ppm failes - convert called with wrong path

Summary:	Loading .ppm failes - convert called with wrong path

Status:	CLOSED RAWHIDE

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	imlib (Show other bugs)
Sub Component:
Version:	5.2
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Havoc Pennington
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2000-01-15 19:47 EST by pere
Modified:	2008-05-01 11:37 EDT (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2000-02-03 18:02:06 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
PPM test image (54.88 KB, image/ppm) 2000-01-15 19:49 EST, pere	no flags	Details
Xlib test program. (1.74 KB, text/plain) 2000-01-15 19:50 EST, pere	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description pere 2000-01-15 19:47:28 EST

When I try the Xlib example program, enclosed in the documentation for
imlib, to load a simple .ppm file, I get the following error:

  sh: /convert: No such file or directory
  sh: /convert: No such file or directory
  IMLIB ERROR: Cannot load image: tmp.ppm
  All fallbacks failed.

I guess this means someone forgot to compile in PPM support, and that
the path to fallback tool convert is wrong.  I tried to check the imlib
documentation to find a way to set the path to convert, but did not
find anything.

Comment 1 pere 2000-01-15 19:49:59 EST

Created attachment 56 [details]
PPM test image

Comment 2 pere 2000-01-15 19:50:59 EST

Created attachment 57 [details]
Xlib test program.

Comment 3 Havoc Pennington 2000-02-03 18:02:59 EST

This seems to be fixed now.

Note You need to log in before you can comment on or make changes to this bug.