On Wed, Jul 15, 2009 at 08:14:16AM -0000, Darshaka Pathirana wrote:
> > The correct fix for this bug is for the toshiba kernel module to
> > generate a key event using the kernel input layer. Can you follow
> > https://wiki.ubuntu.com/Hotkeys/Troubleshooting to verify whether the
> > kernel is outputting a key event, and if not, can you check whether this
> > is fixed in the 2.6.31 kernel in karmic?
> Thanks for the link! I will have a look at it.
> To double check again: Installing the 2.6.31 kernel is enough? (I
> had no intension on upgrading to karmic.)
Yes, you should be able to install the 2.6.31 kernel package from karmic on
jaunty, and this should be sufficient for testing on this bug. If it's
easier for you, a test with the upstream 2.6.31 kernel should also tell us
everything we need to know.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
<email address hidden> <email address hidden>
On Wed, Jul 15, 2009 at 08:14:16AM -0000, Darshaka Pathirana wrote: /wiki.ubuntu. com/Hotkeys/ Troubleshooting to verify whether the
> > The correct fix for this bug is for the toshiba kernel module to
> > generate a key event using the kernel input layer. Can you follow
> > https:/
> > kernel is outputting a key event, and if not, can you check whether this
> > is fixed in the 2.6.31 kernel in karmic?
> Thanks for the link! I will have a look at it.
> To double check again: Installing the 2.6.31 kernel is enough? (I
> had no intension on upgrading to karmic.)
Yes, you should be able to install the 2.6.31 kernel package from karmic on
jaunty, and this should be sufficient for testing on this bug. If it's
easier for you, a test with the upstream 2.6.31 kernel should also tell us
everything we need to know.
-- www.debian. org/
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://
<email address hidden> <email address hidden>