kernel-packages team mailing list archive

["Christopher M. Penalver" <christopher.m.penalver@xxxxxxxxx>]

finn, this bug was reported a while ago and there hasn't been any
activity in it recently. We were wondering if this is still an issue? If
so, could you please test for this with the latest development release
of Ubuntu? ISO images are available from http://cdimage.ubuntu.com
/daily-live/current/ .

If it remains an issue, could you please run the following command in
the development release from a Terminal
(Applications->Accessories->Terminal), as it will automatically gather
and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's
Status as Confirmed. Please let us know your results. Thank you for your
understanding.

** This bug is no longer a duplicate of bug 659712
   New device name enumerated after suspend/resume cycle

** Tags added: maverick needs-kernel-logs needs-upstream-testing

** Package changed: ubuntu => linux (Ubuntu)

** Changed in: linux (Ubuntu)
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/665600

Title:
  Trackpoint settings are gone after resume from standby

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Since update to Maverick trackpoint settings are gone after resume
  from standby. I have made the Settings with gnome-pointing-devices and
  by creating a file /etc/init/trackpoint.conf with the following
  content:

  description "Trackpoint-Einstellungen"
  env TPDIR=/sys/devices/platform/i8042/serio1/serio2
  start on virtual-filesystems
  script
    while [ ! -f $TPDIR/sensitivity ]; do
          sleep 2
    done
    echo -n 200 > $TPDIR/sensitivity
    echo -n 150 > $TPDIR/speed
    echo -n 1 > $TPDIR/press_to_select
  end script

  It seems like the problem is that the path to the driver settings
  changes after resume. See this Post:
  http://ubuntuforums.org/showpost.php?p=9996740&postcount=7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/665600/+subscriptions