Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 160037 - WARNING **: Wrong permissions for /tmp/orbit-sangu
Summary: WARNING **: Wrong permissions for /tmp/orbit-sangu
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy-targeted
Version: rawhide
Hardware: noarch
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Daniel Walsh
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-06-10 09:49 UTC by sangu
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-06-10 13:19:50 UTC


Attachments (Terms of Use)
xsession-error message file in /tmp (deleted)
2005-06-10 09:49 UTC, sangu
no flags Details

Description sangu 2005-06-10 09:49:37 UTC
Description of problem:
Executing gnome application, "WARNING **: Wrong permissions for
/tmp/orbit-sangu" happens.

$ls -Zald /tmp/orbit-sangu*
drwxr-xr-x  2 user_u:object_r:tmp_t            sangu sangu 4096 Jan  1  1970
/tmp/orbit-sangu
drwx------  2 user_u:object_r:tmp_t            sangu sangu 4096 Jun 10 18:36
/tmp/orbit-sangu-a8e8c858


Version-Release number of selected component (if applicable):
selinux-policy-targeted-1.23.18-3

How reproducible:
always

Steps to Reproduce:
1. Execute gnome applicaiton
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 sangu 2005-06-10 09:49:38 UTC
Created attachment 115288 [details]
xsession-error message file in /tmp

Comment 2 sangu 2005-06-10 13:19:50 UTC
After installing selinux-policy-strict-1.23.18-4.noarch.rpm, this bug was fixed.

But installing selinux-policy-targeted-strict-1.23.18-3 don't need
selinux-policy-strict-1.23.18-4.noarch.rpm.


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