Bug 133649

Summary: firefox: general scariness in files and directory layout
Product: [Fedora] Fedora Reporter: Zack Cerza <zcerza>
Component: firefoxAssignee: Christopher Aillon <caillon>
Status: CLOSED CANTFIX QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: mcepl, wtogami
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-02-09 16:44:43 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:
Attachments:
Description Flags
rpm -q --qf "[%{FILEMODES:perms} %{FILENAMES}\n]" firefox none

Description Zack Cerza 2004-09-25 17:40:20 UTC
So I'm looking for firefox's changelog. Not in /usr/share/doc/firefox,
so I rpm -ql it. /usr/lib64/firefox is apparently where 90% of
firefox's files go, so I look there. An ls --color=auto shows the .so
files being the same color as the README.txt - the color of executables.

I found the changelog now, via 'man rpm' - but this just struck me as
odd. An attachment will show you what I mean.

I don't have access to an i386 box right now so I don't know if
they're affected.

Comment 1 Zack Cerza 2004-09-25 17:42:42 UTC
Created attachment 104322 [details]
rpm -q --qf "[%{FILEMODES:perms} %{FILENAMES}\n]" firefox

I don't know which of these two issues are (most) important:

Many files are +x that should not be.
Many files (such as the .txt, .html and likely the .js files) should not even
be in /usr/lib*.

Comment 2 Matěj Cepl 2007-02-09 16:44:43 UTC
Since this bugzilla report was filed, there have been several major updates,
which may have resolved this issue. Users who have experienced this problem are
encouraged to upgrade their system to the latest version available. Therefore
closing this bug as obsolete.

If you experience this problem on the up-to-date system, please reopen this bug
with an additional information.