Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1059388

Summary: /run/user/<UID>/dconf/user
Product: [Fedora] Fedora Reporter: W Agtail <crash70>
Component: mate-file-managerAssignee: Dan Mashal <dan.mashal>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: dan.mashal, fedora, rdieter, stefano
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-01-29 19:24:19 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description W Agtail 2014-01-29 18:33:53 UTC
Description of problem:
File permissions on /run/user/<UID>/dconf/user, change from <user:group> to root:root and then causes several issues with different desktop applications. 

Version-Release number of selected component (if applicable):
F19 and all updates.
mate-file-manager-1.6.3-1.fc19.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Open caja
2. Close caja and you will notice /run/user/<UID>/dconf/user disappears.
3. From a terminal session, switch to root (su -) and run pluma
4. Now you will see /run/user/<UID>/dconf/user created and owned by root:root.

Actual results:
File permissions are changed to root:root on file /run/user/<UID>/dconf/user.

Expected results:
/run/user/<UID>/dconf/user should slways be owned by <user>:<usergroup>

Additional info:
I'm using Mate Desktop

Comment 1 Wolfgang Ulbrich 2014-01-29 19:24:19 UTC

*** This bug has been marked as a duplicate of bug 753882 ***