Bug 447564 - gconfd stores lock files in /tmp
Summary: gconfd stores lock files in /tmp
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: GConf
Version: 9
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-05-20 14:59 UTC by Need Real Name
Modified: 2008-05-20 19:18 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-05-20 19:18:02 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Need Real Name 2008-05-20 14:59:19 UTC
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 19:18:02 UTC
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.