Description of problem: Screen Brightness control in the Power Management applet does not work. The slider stays at leftmost position although brightness is at maximum, moving it does nothing. The problem started after some package update. If restart messagebus, brightness control starts to work until the next login. in the /var/log/messages: Feb 6 19:30:01 localhost dbus: Rejected send message, 1 matched rules; type="method_call", sender=":1.18" (uid=500 pid=4072 comm="/ur/bin/plasma-desktop) interface="org.freedesktop.Hal.Device.LaptopPanel" member="SetBrightness" error name="(unset)" requested_reply= destination="org.freedesktop.Hal" (uid=68 pid=1164 comm="hald)) Feb 6 19:30:01 localhost dbus: Rejected send message, 1 matched rules; type="method_call", sender=":1.18" (uid=500 pid=4072 comm="/ur/bin/plasma-desktop) interface="org.freedesktop.Hal.Device.LaptopPanel" member="GetBrightness" error name="(unset)" requested_reply= destination="org.freedesktop.Hal" (uid=68 pid=1164 comm="hald)) these seems to be related: Feb 6 19:27:55 localhost dbus: Rejected send message, 1 matched rules; type="method_call", sender=":1.17" (uid=500 pid=4058 comm="kded4) interface="org.freedesktop.Hal.Device.CPUFreq" member="GetCPUFreqAvailableGovernors" error name="(unset)" requested_reply=0 destination="org.freedesktop.Hal" (uid=68 pid=1164 comm="hald)) ... Feb 6 20:06:34 localhost dbus: Rejected send message, 1 matched rules; type="method_call", sender=":1.17" (uid=500 pid=4058 comm="kded4) interface="org.freedesktop.Hal.Device.SystemPowerManagement" member="SetPowerSave" error name="(unset)" requested_reply=0 destination="org.freedesktop.Hal" (uid=68 pid=1164 comm="hald)) Version-Release number of selected component (if applicable): kdebase-workspace-4.3.5-2.fc12.i686 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: some other related package versions: hal-0.5.13-9.fc12.i686 ConsoleKit-0.4.1-3.fc12.i686 ConsoleKit-libs-0.4.1-3.fc12.i686 dbus-1.2.16-9.fc12.i686 ConsoleKit-x11-0.4.1-3.fc12.i686 DeviceKit-power-014-1.fc12.i686 kdm-4.3.5-2.fc12.i686 This happnens on ASUS X80L laptop.
I think this is one of the "something creates /tmp/.X11-unix with a wrong SELinux context, preventing pam_console and thus D-Bus's at_console detection from working" bugs, i.e. bug 499183 or bug 550013.
Yes, that was it, doing restorecon /tmp/.X11-unix fixed the problem. This fixed bug 562452 too. Now question is why it is creating with wrong context?
Well, do you have freenx-server installed? Or maybe tigervnc-server (the vncserver executable)?
(In reply to comment #3) Yes, I have freenx-server installed, wanted to write comment about this, but you was first.
*** This bug has been marked as a duplicate of bug 499183 ***