Bug 108780

Summary:	info unusable: wrong permissions on /usr/share/info/dir
Product:	[Fedora] Fedora	Reporter:	J. J. Ramsey <jjramsey>
Component:	bc	Assignee:	Thomas Woerner <twoerner>
Status:	CLOSED NOTABUG	QA Contact:	Ben Levenson <benl>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rawhide	CC:	twaugh
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2004-10-07 14:07:50 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 J. J. Ramsey 2003-11-01 22:19:05 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1)
Gecko/20031027

Description of problem:
If I type "info ld", I get the error message "info: dir: Permission
denied". This is because only root has permission to read
/usr/share/info/dir. I can fix the problem easily with chmod.


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

How reproducible:
Always

Comment 1 J. J. Ramsey 2003-11-01 22:22:36 UTC

Due to braindeadness in the new Bugzilla, I was forced to enter a
false value for the component. "info" was not available from the list
of components, and having anything in the "Component Text" box made
Bugzilla tell me to press "Back" and choose a component.

Comment 2 Tim Waugh 2003-11-03 09:20:59 UTC

What's the history of this installation?

Comment 3 J. J. Ramsey 2003-11-03 13:17:55 UTC

> What's the history of this installation?

Originally test3, updated to the latest Rawhide/Fedora-updates.

Comment 4 Tim Waugh 2003-11-04 16:48:40 UTC

What does 'umask' say, as root?

Comment 5 J. J. Ramsey 2003-11-04 17:35:23 UTC

> What does 'umask' say, as root?

0022

Comment 6 Tim Waugh 2003-11-04 17:47:59 UTC

A fresh installation of Fedora Core (latest tree) doesn't have this
problem.  I think this probably occurred during an upgrade of a
separate package.  It sounds like an errant scriptlet adjusting that
file without using install-info.

One package whose scriptlet looks particularly suspicious is bc. 
Reassigning.

Comment 7 Thomas Woerner 2004-10-07 14:07:50 UTC

Closing as "NOT A BUG".