regression: g-s-d no longer handles Fn+F7 as xrandr --auto

[Steve Langasek]

Binary package hint: gnome-settings-daemon

In hardy, by default Fn+F7 will cause xrandr --auto to be called on my Lenovo Thinkpad. In intrepid, this doesn't happen. I'm not sure if this is a regression in g-s-d, or in some other component.

The event seen on /proc/acpi/event is:
  ibm/hotkey HKEY 00000080 00001007

The default action for this event, defined in /etc/acpi/events/ibm-videobtn, is "/bin/true".

The keybinding configured as /apps/gnome_settings_daemon/keybindings/xrandr is "0xd6" (the default), and /apps/gnome_settings_daemon/plugins/xrandr/active is set to true.

xev shows no KeyPress events when I press this key combination; I believe this is consistent with the behavior in hardy.

While this could be worked around by configuring acpi-support to call xrandr --auto directly, that seems like an abstraction violation to me since that's only relevant when there's an associated X display.

[Steve Beattie (sbeattie)]

This bug was reported in the Intrepid development cycle; removing regression-potential and marking as regression-release.

[Sebastien Bacher (seb128)]

that should be fixed in jaunty now, could somebody try if that's working in the current version?

[Steve Langasek (vorlon)]

As near as I can tell, this is still present in jaunty.

/usr/share/gconf/schemas/apps_gnome_settings_daemon_keybindings.schemas contains:

        <schema>
            <key>/schemas/apps/gnome_settings_daemon/keybindings/xrandr</key>
            <applyto>/apps/gnome_settings_daemon/keybindings/xrandr</applyto>
            <type>string</type>
            <default>0xd6</default>
            <locale name="C">
                <short>Activate connected display</short>
                <long>Activate a connected display using xrandr</long>
            </locale>
        </schema>

If I disable my keybinding override (which had pointed this at XF86Display), then Fn+F7 has no effect. (If I re-enable my keybinding override, it has lots of broken effects, but that's for another bug report. :-)

I'm pretty sure that this is an event that belongs in the keyboard event layer (per https://wiki.ubuntu.com/Hotkeys/Architecture) rather than as a hal event; so this looks unfixed to me.

[Launchpad Janitor (janitor)]

This bug was fixed in the package gnome-settings-daemon - 2.25.3-0ubuntu2

---------------
gnome-settings-daemon (2.25.3-0ubuntu2) jaunty; urgency=low

  * Drop 19_extra_keybindings.patch, the keybinding has been wrong since
    Ubuntu 8.10 and this should be superseded by the upstream xrandr
    plugin anyway. LP: #267018.
  * 99_svn_crash_on_xrandr.patch: patch from upstream svn to fix a
    crasher bug in the xrandr plugin due to broken error handling.
    LP: #315974.

 -- Steve Langasek <email address hidden> Tue, 27 Jan 2009 15:46:19 -0800