Bug 968983 - Error runing gnome-shell, error: dconf-CRITICAL: unable to create directory '/run/user/0/dconf'
Error runing gnome-shell, error: dconf-CRITICAL: unable to create directory '...
Status: CLOSED NOTABUG
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: selinux-policy (Show other bugs)
7.0
Unspecified Linux
unspecified Severity unspecified
: rc
: ---
Assigned To: Miroslav Grepl
BaseOS QE Security Team
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-05-30 08:15 EDT by Jaroslav Škarvada
Modified: 2013-07-30 11:34 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-07-30 11:34:26 EDT
Type: Bug
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 Jaroslav Škarvada 2013-05-30 08:15:17 EDT
Description of problem:
I was unable to run gnome shell for the first time after the installation, the following errors show in the journal:

kvě 30 12:03:59 dhcp-25-243.brq.redhat.com /usr/bin/dbus-launch[3872]: gnome-session[3872]: dconf-CRITICAL: unable to create directory '/run/user/0/dconf': Operace zamítnuta.  dconf will not work properly.
kvě 30 12:03:59 dhcp-25-243.brq.redhat.com gnome-session[3872]: dconf-CRITICAL: unable to create directory '/run/user/0/dconf': Operace zamítnuta.  dconf will not work properly.
kvě 30 12:03:59 dhcp-25-243.brq.redhat.com /usr/bin/dbus-launch[3872]: gnome-session[3872]: dconf-CRITICAL: unable to create directory '/run/user/0/dconf': Operace zamítnuta.  dconf will not work properly.
kvě 30 12:03:59 dhcp-25-243.brq.redhat.com /usr/bin/dbus-launch[3872]: gnome-session[3872]: dconf-CRITICAL: unable to create directory '/run/user/0/dconf': Operace zamítnuta.  dconf will not work properly.

When I switched to permissive mode, the gnome-shell started as expected and the error messages gone.

I saw the related AVCs, but the audit logs were wiped (by another test), so I am unable the provide them. Also I am no more able to reproduce this (also tried rm -rf /run/user/0/dconf). I could try to reinstall the machine later if the problem re-appear. I think the problem was caused by selinux.

Version-Release number of selected component (if applicable):
selinux-policy-3.12.1-46.el7.noarch

How reproducible:
Sometimes, not sure about the reproducer, the following steps trigger it for me

Steps to Reproduce:
1. Install RHEL-7 server, X and gnome-shell
2. Run gnome-shell by startx as root

Actual results:
The above mentioned errors

Expected results:
No errors, gnome-shell start.

Additional info:
I used compose RHEL-7.0-20130529.n.1
Comment 1 Jaroslav Škarvada 2013-05-30 08:17:46 EDT
"Operace zamítnuta." - this mean "operation is not permitted" (ran with czech locale).
Comment 3 Miroslav Grepl 2013-05-30 08:38:53 EDT
Well I guess the problem was with mislabeling. 

Michal, Milos,
are you getting also this with a fresh install?

# ls -lZ /run/user/0/dconf
Comment 4 Jaroslav Škarvada 2013-05-30 17:35:40 EDT
What I exactly did:

I upgraded RHEL-7 Alpha 3 (with no GUI, no X) to the latest compose RHEL-7.0-20130529.n.1 by 'yum upgrade'. Then ran 'yum groupinstall "Server with GUI"'.
Comment 5 Miroslav Grepl 2013-07-30 11:34:26 EDT
Let's open it if we see it again.

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