Bug 83479 – Binary data in error message.

Bug 83479 - Binary data in error message.

Summary:	Binary data in error message.

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Red Hat Raw Hide
Classification:	Retired
Component:	rpm (Show other bugs)
Sub Component:
Version:	1.0
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Jeff Johnson
QA Contact:	Mike McLean
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2003-02-04 14:55 EST by Ralph Loader
Modified:	2007-04-18 12:50 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2003-02-04 15:47:54 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)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Ralph Loader 2003-02-04 14:55:47 EST

Description of problem:

rpm prints error messages with binary data. (Not sure if rpm or db4 is at fault).

Version-Release number of selected component (if applicable):

rpm-4.2-0.65
db4-4.0.14-17

How reproducible:

Every time.

Steps to Reproduce:
1. As non-root, try to remove some installed rpms:

rpm -e XFree86-ISO8859-2-75dpi-fonts-4.2.99.4-20030129.4 2>&1|less

Actual results:

Some of the error message contains binary data.  Cut'n'paste from less:

rpmdb: c_del: attempt to modify a read-only tree
error: db4 error(13) from dbcursor->c_del: Permission denied
error: error(13) removing record "<CB><FC>uj-4<CC>xO<A7>#<9B>F<83>88^^" from
Filemd5s

Expected results:

The error messages should only contain text.

Comment 1 Jeff Johnson 2003-02-04 15:47:54 EST

You've got bigger problems than binary data in error message.

Try
    rm -f /var/lib/rpm/__db*
    rpm --rebuilddb -vv
and repeating whatever caused the above.

Please attach sufficient input/output to reproduce this
problem  if you reopen this bug.

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