Bug 754226 – console-kit-demon doesn't work after upgrading from F15

Bug 754226 - console-kit-demon doesn't work after upgrading from F15

Summary:	console-kit-demon doesn't work after upgrading from F15

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	selinux-policy (Show other bugs)
Sub Component:
Version:	16
Hardware:	x86_64 Linux

Priority	unspecified Severity urgent
Target Milestone:	---
Target Release:	---
Assigned To:	Miroslav Grepl
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2011-11-15 13:49 EST by Stefan Seefeld
Modified:	2011-11-23 10:46 EST (History)
CC List:	6 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2011-11-23 10:46:34 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Stefan Seefeld 2011-11-15 13:49:12 EST

Description of problem:

After booting I'm trying to log in via kdm. I get

"Warning: Cannot open ConsoleKit session: Unable to open session: Message did not receive a reply )timeout by message bus)"

Browsing /var/lib/messages for traces I find this:

[system] Successfully actyivat4d service 'org.freedesktop.ConsoleKit'
console-kit-demon[...]: process ...: D-Bus library appears to be incorrectly set up; failed to read machine uuid: Failed to open "/etc/machine-id": Permission denied


However, the "/etc/machine-id" file does exist and is world-readable. What is wrong here ? (I just upgraded from F15 to F16, so something appears to have been corrupted in the process.

Thanks,

              Stefan

Comment 1 Stefan Seefeld 2011-11-15 15:55:18 EST

It turns out I can work around the issue by disabling selinux. So this may be an issue related to issue 746456. (I'll change the component, but leave it up to someone more knowledgeable to decide whether this is actually a duplicate.

Comment 2 Miroslav Grepl 2011-11-16 02:35:46 EST

Did you try to boot in permissive mode? If no, could you boot with kernel parameter

# enforcing=0

and after booot

# dmesg |grep avc

# ausearch -m avc -ts recent

Comment 3 Daniel Walsh 2011-11-16 15:49:29 EST

restorecon -R -v /etc

Should fix your machineid problem.

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