g-s-d needs to set mouse properties when a new device appears

Your touchpad likely disappears and reappears across suspend (most don't). gnome-settings-daemon should know to reset things upon resuming.

From Xorg.0.log:

(II) config/hal: removing device AlpsPS/2 ALPS GlidePoint

...

(II) config/hal: Adding input device AlpsPS/2 ALPS GlidePoint

Any workaround for this? For example, running a command that makes gnome-settings-daemon apply the right settings on resume?

The package (gnome-settings-daemon_2.24.0-0ubuntu4~wgrant1) in wgrant's PPA fixes the issue for me.

Also this (gnome-settings-daemon_2.24.0-0ubuntu4~wgrant1) works for me :)
dell latitude 430 Intrepid RC

As people have mentioned here, I have a gnome-settings-daemon in my PPA to fix this. We can hopefully get the patch blessed by upstream and some Ubuntu GNOME people, and SRU it.

What about people using KDE ?

I'm not sure which bit of KDE should be setting this.

On a more pleasant note, a (largely) cosmetically-altered version of my patch was just committed upstream. A new version (~wgrant2) with this patch is building in my PPA right now; please test it once it's built.

Am Samstag, den 01.11.2008, 13:08 +0000 schrieb William Grant:
> On a more pleasant note, a (largely) cosmetically-altered version of my
> patch was just committed upstream. A new version (~wgrant2) with this
> patch is building in my PPA right now; please test it once it's built.

No apparent problems with bluetooth mouse for me... Thank you for your
great work!

Tomas

That's is my upstream patch ported to Intrepid's g-s-d. This isn't yet fixed in Jaunty, as we are still quite frozen.

I wonder if the X logs I attached to my original bug (currently marked as duplicate of this one) revealed anything useful that could make this work for me too?

Uploaded. Don't worry about jaunty, I'll copy the package from -proposed to jaunty once it's accepted and built.

Accepted into intrepid-proposed, please test and give feedback here. Please see https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

There's an apparent nasty regression in bug #293318, but it doesn't seem to leak at all here... looking into it.

Version from -proposed works for me. Thanks!

vers. 2.24.0-0ubuntu3
I got my settings to work after I flushed all my gconf settings (they got corrupted somehow) anyways, after getting everything back to how i want, the settings stick now.

intrepid-proposed package copied to jaunty.

Martin, it seems that the real fix is what's currently in wgrant6. Could a package with the equivalent patch be pushed into intrepid-updates? As far as I can tell, it's one of the only show stoppers preventing people from safely upgrading to Intrepid. If there's gonna be a 8.10.1 CD image, it might also be worth including it there. Thanks!

ubuntu-sru is subscribed to bug #293318, the regression bug. I suspect the delay in uploading to intrepid-proposed is just the weekend.

Another update was just accepted into intrepid-proposed:

gnome-settings-daemon (2.24.0-0ubuntu3.2) intrepid-proposed; urgency=low

  * debian/patches/20_mouse_devicepresencenotify.patch:
    - Fix the DevicePresenceNotify storm. Now we only watch for DeviceEnabled
      (rather than DeviceAdded) events. (LP: #293318)
  * debian/patches/08_extra_touchpad_options.patch:
    - device_is_touchpad: Decide that it's not a touchpad unless it is of type
      XI_TOUCHPAD.
    - set_tap_to_click: Fix a couple of potential memory leaks.

 -- William Grant <email address hidden> Sat, 08 Nov 2008 11:46:30 +1100

Please test this version as well and verify that it still fixes this bug. Thank you!

On Mon, Nov 10, 2008 at 9:31 AM, Martin Pitt wrote:
> Another update was just accepted into intrepid-proposed:
>
> gnome-settings-daemon (2.24.0-0ubuntu3.2) intrepid-proposed; urgency=low

Btw the version numbers used for the wgrant packages will prevent
automatic upgrades to intrepid-proposed:

 *** 2.24.0-0ubuntu4~wgrant6 0
        500 http://ppa.launchpad.net intrepid/main Packages
        100 /var/lib/dpkg/status
     2.24.0-0ubuntu3.1 0
        500 http://archive.ubuntu.com intrepid-proposed/main Packages
        100 http://archive.ubuntu.com jaunty/main Packages
     2.24.0-0ubuntu3 0

0ubuntu4~wgrant versions will always trump 0ubuntu3, simply because of
the bump from ubuntu3 to ubuntu4, while intrepid-proposed remains at
3.x releases.

This of course won't matter for users who only track intrepid-updates
and never heard of wgrant packages. :)

On Mon, Nov 10, 2008 at 9:31 AM, Martin Pitt wrote:
> Another update was just accepted into intrepid-proposed:
>
> gnome-settings-daemon (2.24.0-0ubuntu3.2) intrepid-proposed; urgency=low

> Please test this version as well and verify that it still fixes this
> bug. Thank you!

This one works just as well as wgrant6 did for me. Hurray!

I guess this means 2.24.0-0ubuntu3.2 for Intrepid-updates and
2.24.0-0ubuntu4 for Jaunty?

--
Best Regards,
Martin-Éric

2.24.0-0ubuntu3.2 can be copied to Jaunty fine, at the moment.

2.24.0-0ubuntu3.2 copied to jaunty.

Copied to intrepid-updates.

Updates fixed it for me! YAY!!!! Thank you devs!!!

I have a laptop with which I use an external keyboard at times, and I use two keyboard layouts. I have the same symptoms as others report here: after suspend/resume or plugging in the keyboard, the second keyboard layout becomes inaccessible. I have intrepid-updates enabled and gnome-settings-daemon is at version 2.24.0-0ubuntu3.3. I thought that should fix the problem. Am I missing something?

Exactly same as Larry - this is not fixed. Left mouse button is lost both on resume and on a reboot. Have to use mouse properties to flip the left-right option to ensure the right mouse button on my laptop behaves as a left-hand mouse button. Extremely annoying - can this status be changed to "not fix" please?

... its worse than I thought - if I close firefox and reopen firefox the left-handiness is lost! If I just close firefox then left-handiness is not lost. I've changed the status of this to new and assigned to nobody. Is that ok to do?

Larry's problem is a different one - this does not cover keyboard issues.

David, which version of gnome-settings-daemon do you have? Does left-handedness carry over to an external mouse if you unplug and replug it a few times? This is definitely still fixed for me.

I have version 2.24.0-0ubuntu3.3. Tested the following. On resume or shutdown-reopen firefox, loses left-handedness even with an external mouse. However if I unplug the mouse and plug into separate USB port, left-handedness works. However this is lost if I suspend/resume or close-reopen firefox.

That's a different bug, then - the Firefox thing in particular is very strange. Please file a new bug against gnome-settings-daemon and assign me.

I'm not sure that this is a Firefox-specific bug. Rather, the deal seems to be between GNOME and non-GNOME applications not receiving the mouse properties the same way. I briefly had the same issue while on Hardy and, again, briefly during Jaunty alpha. Everything seems to be back to normal on Jaunty beta, now.

For those who got here because you're losing one or more keyboard layouts, see bug #363169 (https://bugs.launchpad.net/ubuntu/+source/libxklavier/+bug/363169). The following fixed the keyboard layout problem for me on 9.04:

1) Read about updating from PPAs here: https://help.launchpad.net/Packaging/PPA#Installing%20software%20from%20a%20PPA

2) Add Sergey's PPA to your apt sources: https://launchpad.net/~sergey-udaltsov/+archive/ppa

3) Update your software, making sure that one of the packages updated is "libxklavier - 3.9-0ubuntu3"

4) Restart your computer