Bug 754226 - console-kit-demon doesn't work after upgrading from F15
Summary: console-kit-demon doesn't work after upgrading from F15
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 16
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Miroslav Grepl
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-15 18:49 UTC by Stefan Seefeld
Modified: 2011-11-23 15:46 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-23 15:46:34 UTC
Type: ---


Attachments (Terms of Use)

Description Stefan Seefeld 2011-11-15 18:49:12 UTC
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 20:55:18 UTC
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 07:35:46 UTC
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 20:49:29 UTC
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.