Bug 3727

Summary:	2_a1: Error statting file /var/run/ConsoleKit/database runlevel 3
Product:	Mageia	Reporter:	Bit Twister <bittwister2>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	dmorganec, mageia, marja11
Version:	Cauldron
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	consolekit-0.4.5-2.mga2.src.rpm	CVE:
Status comment:

Description Bit Twister 2011-12-13 10:44:22 CET

Description of problem:

Dec 13 03:10:32 localhost polkitd[1378]: started daemon version 0.102 using authority implementation `local' version `0.102'
Dec 13 03:10:32 localhost dbus-daemon[1346]: Error loading /var/run/ConsoleKit/database: Error statting file /var/run/ConsoleKit/database: No such file or directoryUsing authority class PolkitBackendLocalAuthority

Version-Release number of selected component (if applicable):


How reproducible: Always


Steps to Reproduce:
1. clean install, apply updates,
2. set system to boot runlevel 3
3. /bin/cp /dev/null /var/log/messages
4. reboot
5. grep "No such file" /var/log/messages

Comment 1 D Morgan 2011-12-13 11:32:06 CET

should we %ghost it in consolekit rpm ?

CC: (none) => dmorganec

Comment 2 Bit Twister 2011-12-13 12:20:33 CET

(In reply to comment #1)
> should we %ghost it in consolekit rpm ?

My guess it is not going to help since it is deleted, then populated as each /org/freedesktop/ConsoleKit seat requests are made. :)

Comment 3 Colin Guthrie 2011-12-15 16:10:07 CET

Well, /var/run should (in theory at least) just be a symlink to /run. We don't do this yet in Mga, but we should look at that soon (the problem case is upgrades, we cannot just replace /var/run at runtime otherwise all sorts of things break. The way fedora handle it is to do a bind mount on boot of /var/run to /run for the upgrade cases (but for fresh installs, just ensure it's a symlink). I've not looked into adopting a similar approach yet. 

So %ghost wont help either.

Anyway, consolekit should be dying... not sure if polkit can be built without CK support (or what that would mean - CK is not yet fully deprecated AFAIK and it's still needed for non-systemd boots anyway.

Just some general info, not sure about the bug itself.

CC: (none) => mageia

Comment 4 Marja Van Waes 2012-01-31 07:56:28 CET

any news about this issue?

CC: (none) => marja11

Comment 5 Bit Twister 2012-01-31 08:49:14 CET

(In reply to comment #4)
> any news about this issue?

If there is more than one person in the bug report, it helps if you click the [reply] link so everyone knows who you are talking to and trim to just what you are responding about.

I am not sure you are asking Colin abut polkit resolution, or Colin's 
"about the bug itself"

If about the bug, I can not say. I am seeing intermittent problems. I was about to close a problem I had not seen for 3 days but it did show up on this last reboot.

systemd is really not stable on my testbed.
See today's bug 4352 and bug 4353
Hotplug service is hanging for about 20 seconds.
Last two reboots show dhcpd is now working. 
Nic selection failure just went to 75%, and initrd has picked up an extra minute,(initrd) + 6min 31s 57ms :(

All my virtualbox guest now abort when kde almost completes the desktop setup after startx.

Pulseaudio audio controls no longer work like they should. Worked fine in alpha2.

Comment 6 Marja Van Waes 2012-01-31 09:07:20 CET

(In reply to comment #5)
> (In reply to comment #4)
> > any news about this issue?
> 
> If there is more than one person in the bug report, it helps if you click the
> [reply] link so everyone knows who you are talking to and trim to just what you
> are responding about.

It was a general question to everyone.

Thanks for your reply :)

Comment 7 Bit Twister 2012-02-22 17:55:50 CET

clean beta1 install does not have the problem.

Status: NEW => RESOLVED
Resolution: (none) => FIXED