Bug 447564 - gconfd stores lock files in /tmp
gconfd stores lock files in /tmp
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: GConf (Show other bugs)
9
All Linux
low Severity low
: ---
: ---
Assigned To: Ray Strode [halfline]
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-05-20 10:59 EDT by Need Real Name
Modified: 2008-05-20 15:18 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-05-20 15:18:02 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Need Real Name 2008-05-20 10:59:19 EDT
Description of problem:
gconfd stores personal lockfiles in /tmp. After a change of uid and chown of
home directory, user can't log in using the graphical interface any more

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

How reproducible:
change user id, chown home directory, try to log in


Steps to Reproduce:
1. create user
2. log in
3. log out
4. change uid
5. chown home directory to new uid
5. log in
  
Actual results:
graphical log in hangs, can only be fixed when root removes file in /tmp


Expected results:
user can log in, /tmp files should not play such a severe role


Additional info:
Comment 1 Ray Strode [halfline] 2008-05-20 15:18:02 EDT
This is a long standing problem that we have fixed in rawhide, but probably
won't fix in earlier releases.

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