We're closing this bug since it is has been some time with no response from the
original reporter. However, if the issue still exists please feel free to
reopen with the requested information. Also, if you could, please test against
the latest development version of Ubuntu, since this confirm
This is probably because some laptops have their touchpads appear as a
new device upon resume. I'd like somebody affected to try it in Karmic,
as syndaemon is significantly rewritten there.
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Importance: Undecided => Low
** Changed in: xserver
I can confirm that the above mentioned problem is also seen on a freshly
installed Jaunty on an Acer Extensa laptop.
The fix above has worked a few times, but more often it fails and the
daemon must be manually started.
--
syndaemon gone after resume on intrepid and jaunty
https://bugs.launchpad
** Package changed: xfree86-driver-synaptics (Ubuntu) => xserver-xorg-
input-synaptics (Ubuntu)
--
syndaemon gone after resume on intrepid and jaunty
https://bugs.launchpad.net/bugs/326117
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Problem seem to persist on Jaunty.
I _may_ have seen it survive a few times, but I am uncertain of the
circumstances, and can't reliably reproduce.
Anyway I have found a workaround.
In /usr/lib/pm-utils/sleep.d/ I have created "50syndaemon" as follows:
#!/bin/sh
resume_syndaemon()
{
if [ !
** Summary changed:
- syndaemon gone after resume on intrepid
+ syndaemon gone after resume on intrepid and jaunty
** Tags removed: needs-xorglog
--
syndaemon gone after resume on intrepid and jaunty
https://bugs.launchpad.net/bugs/326117
You received this bug notification because you are a mem
