Public bug reported:
Binary package hint: gpointing-device-settings
By default, Ubuntu will disable touchpads via gnome-settings-daemon when
XF86TouchpadToggle (Fn+F8 on ThinkPads) is pressed, and this is
accompanied by a notify-osd notification. This no longer functions when
gpointing-device-settings is installed, and the functionality does not
return when gpointing is uninstalled. This occurs with gpointing-device-
settings 1.3.2 and Debian's 1.5.1 package.
Gconf key /desktop/gnome/peripherals/touchpad/touchpad_enabled is
normally toggled by XF86TouchpadToggle. The touchpad can always be
toggled by using this gconf key, but the keyboard button that
corresponds to XF86TouchpadToggle does not function on machines that had
at some point installed gpointing-device-settings.
I don't know if this is a bug of gpointing or gnome-settings-daemon.
** Affects: gpointing-device-settings (Ubuntu)
Importance: Undecided
Status: New
** Tags: gnome-settings-daemon gpointing pointing stick touchpad trackpad
trackpoint xf86touchpadtoggle
** Description changed:
Binary package hint: gpointing-device-settings
By default, Ubuntu will disable touchpads via gnome-settings-daemon when
XF86TouchpadToggle (Fn+F8 on ThinkPads) is pressed. This no longer
functions when gpointing-device-settings is installed, and the
- functionality does not return when gpointing is removed.
+ functionality does not return when gpointing is uninstalled. This occurs
+ with 1.3.2 and Debian's 1.5.1 package.
Gconf key /desktop/gnome/peripherals/touchpad/touchpad_enabled is
normally toggled by XF86TouchpadToggle. The touchpad can always be
toggled by using this gconf key, but the keyboard button that
corresponds to XF86TouchpadToggle does not function on machines that had
at some point installed gpointing-device-settings.
I don't know if this is a bug of gpointing or gnome-settings-daemon.
** Description changed:
Binary package hint: gpointing-device-settings
By default, Ubuntu will disable touchpads via gnome-settings-daemon when
- XF86TouchpadToggle (Fn+F8 on ThinkPads) is pressed. This no longer
- functions when gpointing-device-settings is installed, and the
- functionality does not return when gpointing is uninstalled. This occurs
- with 1.3.2 and Debian's 1.5.1 package.
+ XF86TouchpadToggle (Fn+F8 on ThinkPads) is pressed, and this is
+ accompanied by a notify-osd notification. This no longer functions when
+ gpointing-device-settings is installed, and the functionality does not
+ return when gpointing is uninstalled. This occurs with 1.3.2 and
+ Debian's 1.5.1 package.
Gconf key /desktop/gnome/peripherals/touchpad/touchpad_enabled is
normally toggled by XF86TouchpadToggle. The touchpad can always be
toggled by using this gconf key, but the keyboard button that
corresponds to XF86TouchpadToggle does not function on machines that had
at some point installed gpointing-device-settings.
I don't know if this is a bug of gpointing or gnome-settings-daemon.
** Description changed:
Binary package hint: gpointing-device-settings
By default, Ubuntu will disable touchpads via gnome-settings-daemon when
XF86TouchpadToggle (Fn+F8 on ThinkPads) is pressed, and this is
accompanied by a notify-osd notification. This no longer functions when
gpointing-device-settings is installed, and the functionality does not
- return when gpointing is uninstalled. This occurs with 1.3.2 and
- Debian's 1.5.1 package.
+ return when gpointing is uninstalled. This occurs with gpointing-device-
+ settings 1.3.2 and Debian's 1.5.1 package.
Gconf key /desktop/gnome/peripherals/touchpad/touchpad_enabled is
normally toggled by XF86TouchpadToggle. The touchpad can always be
toggled by using this gconf key, but the keyboard button that
corresponds to XF86TouchpadToggle does not function on machines that had
at some point installed gpointing-device-settings.
I don't know if this is a bug of gpointing or gnome-settings-daemon.
--
gnome-settings-daemon XF86TouchpadToggle actions do not work when
gpointing-device-settings is installed
https://bugs.launchpad.net/bugs/577250
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
