Bug 492595

Summary:	fiascotopnm fails on an image generated by pnmtofiasco
Product:	Red Hat Enterprise Linux 4	Reporter:	Petr Šplíchal <psplicha>
Component:	netpbm	Assignee:	Jindrich Novy <jnovy>
Status:	CLOSED WONTFIX	QA Contact:	BaseOS QE <qe-baseos-auto>
Severity:	medium	Docs Contact:
Priority:	low
Version:	4.8	CC:	ohudlick, ovasik, pknirsch
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-02-18 13:10:28 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Petr Šplíchal 2009-03-27 15:59:50 UTC

Description of problem:
fiascotopnm fails with "Can't read next bit from bitfile" error
when run on a fiasco file generated with pnmtofiasco.

Version-Release number of selected component (if applicable):
netpbm-10.35.58-6.el4.ppc

How reproducible:
Always on ppc, s390 and s390x

Steps to Reproduce:
1. ppmwheel 100 | ppmtopgm > test.pgm
2. pnmtofiasco <test.pgm >test.fiasco
3. fiascotopnm <test.fiasco >test.pnm

Actual results:
fiascotopnm: fiascotopnm.c: line 271:
Error: Can't read next bit from bitfile -.

Expected results:
a PNM image test.pnm

Additional info:
The same fault is futhermore reproducable with original ppm image
on 390x and original pbm image on ppc. To sum up:

s390:  pgm
s390x: pgm, ppm
ppc:   pgm, pbm

Comment 1 Ondrej Vasik 2011-02-18 13:10:28 UTC

Thanks for report, but we will not be able to address the issue in RHEL-4.
RHEL-4.9 was the last RHEL-4 regular update. As RHEL-4 now targets only
critical and security fixes, closing this bugzilla WONTFIX.