This is still broken in Q as I stated before, although it appears to be fixed in Gnome 3.4 and 3.6 trunks.
Here are all my notes: 1) The signal "Changed" is coming from g-s-d when the brightness hotkeys are pressed: $ dbus-monitor --session "type='signal',sender='org.gnome.SettingsDaemon'" In Quantal: signal sender=:1.6 -> dest=org.gnome.SettingsDaemon serial=397 path=/org/gnome/SettingsDaemon/Power; interface=org.gnome.SettingsDaemon.Power.Screen; member=Changed On Precise, we see the same signal: signal sender=:1.17 -> dest=org.gnome.SettingsDaemon serial=8416 path=/org/gnome/SettingsDaemon/Power; interface=org.gnome.SettingsDaemon.Power.Screen; member=Changed 2) I instrumented the on_signal call inside gnome-control- center/panels/sceen/cc-screen-panel.c to emit a g_warning whenever any signal was received, I never saw anything come out in Q. When the same code was used in P, the message was printed. This implies, rather obviously that g-c-c is never getting the signal. 3) I then wrote a simplified test application that attempted to synchronously (for simplicity) connect to the same signal and just print a message if one was received and again, no message was received. I modified this code slightly to listen for signals from Gnome Screensaver and I get signals, so I think my sample code is fine. The sample code is attached later. To run it with the gnome-screensaver and get results, start the code and run "gnome-screensaver-command -a" in another terminal, and you should see: ** (process:17715): WARNING **: we get signal from :1.89: ActiveChanged If you swap the 3 screensaver related lines with the SettingsDaemon code you will get no output. (replace lines 39-41 with 46-48) 4) I see one more interesting thing that may or may not be a problem: The signals from SettingsDaemon have a Destination field of the settings daemon itself. Those from Gnome Screensaver have a "null" destination: signal sender=:1.6 -> dest=org.gnome.SettingsDaemon serial=397 path=/org/gnome/SettingsDaemon/Power; interface=org.gnome.SettingsDaemon.Power.Screen; member=Changed signal sender=:1.89 -> dest=(null destination) serial=78 path=/org/gnome/ScreenSaver; interface=org.gnome.ScreenSaver; member=ActiveChanged Perhaps this is a problem? I don't know enough about dbus to be sure. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/893851 Title: Brightness adjustment gauge in gnome-control-center screen not responding to brightness hot-keys Status in GNOME Control Center: Fix Released Status in OEM Priority Project: Fix Released Status in OEM Priority Project precise series: Fix Released Status in “gnome-control-center” package in Ubuntu: In Progress Status in “gnome-control-center” source package in Precise: Fix Released Bug description: [Impact] Using brightness hotkeys currently changes brightness correctly, but such changes fail to be visible in the gnome-control-center UI; which leads to confusion and unpredictable behavior if the brightness is then adjusted using UI in the same session. [Test Case] 1) Open gnome-control-center (power indicator -> System Settings...) 2) Switch to "Brightness and Lock" 3) Use the brightness hotkeys to adjust screen brightness 4) Observe slider behavior. Without the patch the slider should not move. With the patch, slider should follow brightness adjustments done via hot keys. [Regression Potential] Minimal risk. The slider does not currently follow key brightness adjustments. Possible regression scenarios could include the slider no longer responding or changing brightness when interacting with it; or more confusion in mixing up hot key and slider brightness adjustments. ---- For systems equipped with hot keys to adjust screen brightness, the brightness gauge in "gnome-control-center screen" is not responding to brightness hot-key actions. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/893851/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
