Need help getting rid of this notification

[GoinEasy9]

For the last few days this notification has been coming up at the login screen and on the desktop after login. It's a PIA, but I don't want to just change permissions. I would like it to be fixed through updates, but, there has been no answer from the bugzilla. Any advice would be appreciated. Screenshot attached.

[SlowJet]

It part of the new power system.
Back Light has to do with the brightnes control of some monitors, specificly laptop type machine that need this to make the fonts show up, and also, I think, make the vedio work correctly.
This helper program needs to run as root, hence the security authorization.

In the olden days of f10, f11 there was a policykit (polkit) gui to contol such things that could be set perently.
I don't see that on f14 or f13 anymore. It may be in some clii thingy dependent on the "never compiles or breaks gnome stuff" gnome-python2-settings-daemon. Don't known for sure but I am guessing it is a wip, with some trail and error, and bits and pieces development.

So there ya go.
Think of it as a root password memorization reminder. :)
File a Bugzilla and maybe you can get an answer and let use Cheydora users known the scoop.

SJ

[GoinEasy9]

Think of it as a root password memorization reminder.

Hah, Heh, yes, it has been good for that. I filed a BZ when it first started. https://bugzilla.redhat.com/show_bug.cgi?id=600163 no response yet.

Am I the only one seeing this?

[SlowJet]

I'm see it, twice on my Pent II system. Before and after the logon screen.

I clicked on the "Show other bugs for power-manager.
There are 518

SJ

[BugRocks1]

I think the place to look for that is in the policykit rules if there is none probably is consolekit using PAM.

/usr/share/polkit-1/actions/org.freedesktop.upower.policy
/usr/share/polkit-1/actions/org.freedesktop.upower.qos.policy

or

locate gnome-power-backlight-helper

$ locate consolekit
/usr/share/polkit-1/actions/org.freedesktop.consolekit.policy
/usr/share/selinux/devel/include/services/consolekit.if

[GoinEasy9]

Thanks SlowJet and BugRocks1. Tommorrow's another day and I'll try approaching it the way BugRocks suggested. When I filed the BZ I commented that I might have filed the bug against PolicyKit, but, gnome-power-manager was in the updates the night the notification started. I'll see tomorrow, maybe I'll file against PolicyKit also.

[BugRocks1]

Jun 3 23:33:33 localhost polkitd(authority=local): Operator of
unix-session:/org/freedesktop/ConsoleKit/Session1 successfully authenticated as
unix-user:root to gain ONE-SHOT authorization for action
org.freedesktop.policykit.exec for unix-process:1512:2216 [gnome-power-manager]

/usr/libexec/polkit-gnome-authentication-agent-1

Jun 3 23:33:33 localhost pkexec[1527]: gdm: Executing command [USER=root]
[TTY=unknown] [CWD=/var/gdm] [COMMAND=/usr/sbin/gnome-power-backlight-helper
--get-max-brightness]
Jun 3 23:33:41 localhost pam: gdm-password[1530]:

Those lines lead me to believe that there is a PAM module somewhere for gnome-power-backlight-helper that you can configure, I just don't remember where those modules are stored I know I made a tutorial but I just don't remember where it is also LoL

I will try to find it.

[GoinEasy9]

Thanks BugRocks1, no hurry, have work tomorrow, so, will play with it afterward. Appreciate the help.

[BugRocks1]

Found it:

http://forums.fedoraforum.org/showthread.php?t=239223

/etc/pam.d/
/etc/security/console.apps/

If you find the PAM module you can configure it so the GDM user don't have to ask for permission

[GoinEasy9]

Wow, that link is a keeper, I'll let you know how I make out.

[rockdoctor]

Found it:

http://forums.fedoraforum.org/showthread.php?t=239223

/etc/pam.d/
/etc/security/console.apps/

If you find the PAM module you can configure it so the GDM user don't have to ask for permission
It's not gdm asking for anything, at least in my case. I boot into runlevel3 and start X using startx from the command line.

[GoinEasy9]

I couldn't find a specific PAM module for it, so, I'm dealing with it until it's fixed. It has comments in the bugzilla, so, at least they know it there and it's buggin' a few people.