Special keys spit out nonsense on terminal on ThinkPad

Bug #46207 reported by Tony Yarusso
10
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Medium
Unassigned
linux-source-2.6.22 (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

The volume-control special keys have some strange behaviour in Dapper (they all worked fine in Breezy). This is a tty-specific issue; gnome-terminal does not have any of these problems. On a normal command line, the volume-down button produces a ~ (tilde) and beeps the system bell. The mute button spits out a ~ as well, but without the beep. The volume-up button is fine in all cases. In irssi running within screen, volume-down puts 6~ on the line, and mute 5~ . At the login prompt, volume-down gives [26~ and mute [25~ . This is on an IBM/Lenovo ThinkPad T43. Again, this is new in Dapper, Breezy was fine.

Tags: cft-2.6.27
Revision history for this message
jjackso1 (jjackso1) wrote :

Hello I have a problem related to this one in dapper the when i push the volume key down to the point where it mutes the volume (while looking at the Volume Control), it mutes at a point where the Master fader do not go all the way down. I can still color under the faders.
(before in breezy it was the case that pcm could be all the way up and the master all the way down and i could still hear volume thank you for fixing that)
 this is one a HP ZE5500 Series laptop

Revision history for this message
Caroline Ford (secretlondon) wrote :

jjackso1 - your bug is a different bug. Please submit as a separate bug. Thanks.

Revision history for this message
Tony Yarusso (tonyyarusso) wrote :

This bug is still present in current Feisty (23 Nov 2006)

Revision history for this message
Evan Klitzke (eklitzke2) wrote :

Tony,

I don't have this problem (either running irssi locally, or within a screen session) on my Thinkpad X40. When I press the volume keys running irssi, the volume is changed (as usual), and there is no output on the irssi command line. Do your volume buttons work at all? I believe that if they are working (i.e. pressing them adjusts the volume), pressing them should not send any events to the terminal or irssi.

-- Evan

Changed in irssi:
status: New → Incomplete
Revision history for this message
Tony Yarusso (tonyyarusso) wrote :

Yes, they do work. Perhaps there is something different between the T and X series? (although I don't know why there would be)

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for irssi (Ubuntu) because there has been no activity for 60 days.]

Revision history for this message
Tony Yarusso (tonyyarusso) wrote :

Poke poke janitor - still exists on up-to-date Feisty. Will try on Gutsy after release.

Revision history for this message
Tony Yarusso (tonyyarusso) wrote :

This bug _still_ exists on a completely fresh vanilla 7.10 "Gutsy Gibbon" installation on this machine. Changing the the package hint to the kernel though, since I'm now thinking that's more likely.

Changed in irssi:
status: Invalid → New
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Tony, can you please attach the following information:

* uname -a > uname-a.log
* cat /proc/version_signature > version.log
* dmesg > dmesg.log
* sudo lspci -vvnn > lspci-vvnn.log

Please be sure to attach each file as a separate attachment. Can you also capture the dmesg after you do a few key presses to see if anything useful is captured. For more information regarding the kernel team bug policy, please refer to https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks in advance!

Changed in linux-source-2.6.22:
status: New → Incomplete
Revision history for this message
Tony Yarusso (tonyyarusso) wrote :

Here they are:

Revision history for this message
Tony Yarusso (tonyyarusso) wrote :
Revision history for this message
Tony Yarusso (tonyyarusso) wrote :
Revision history for this message
Tony Yarusso (tonyyarusso) wrote :
Revision history for this message
Tony Yarusso (tonyyarusso) wrote :
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Hardy Heron kernel was recently uploaded for testing. We'd really appreciate it if you could try testing with this newer kernel and verify if this issue still exists. Unfortunately, the Hardy Heron Alpha1 LiveCD was released with the older 2.6.22 kernel. You'll have to manually install the newer Hardy Heron kernel in order to test. This should not be the case for Alpha2. However, here are the instructions to install (if you choose to do so):

1) edit the file /etc/apt/sources.list and add the following line:

deb http://archive.ubuntu.com/ubuntu hardy main restricted

2) sudo apt-get update
3) sudo apt-get install linux-image-2.6.24-1-generic
4) reboot and select the new kernel from the grub menu

After you've tested, please feel free to revert back - ie boot into the old kernel, sudo apt-get remove linux-image-2.6.24-1-generic, and remove the line from /etc/apt/sources.list . Please update this report with your results. Thanks in advance!

Changed in linux:
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Against linux-source-2.6.22 this bug does not meet the criteria for a stable release update and is being marked as Won't Fix. You can learn more about the stable release update process at https://wiki.ubuntu.com/StableReleaseUpdates . However, we are still interested in resolving this in the Hardy Heron kernel. Thanks!

Changed in linux-source-2.6.22:
status: Incomplete → Won't Fix
Revision history for this message
Tony Yarusso (tonyyarusso) wrote :

Bother, behavior still present in the following version:

anthony@experimental:~$ uname -r
2.6.24-12-generic
anthony@experimental:~$ apt-cache policy linux-image-2.6.24-12-generic
linux-image-2.6.24-12-generic:
  Installed: 2.6.24-12.22
  Candidate: 2.6.24-12.22
  Version table:
 *** 2.6.24-12.22 0
        500 http://archive.ubuntu.com hardy/main Packages
        100 /var/lib/dpkg/status

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
Ralph Janke (txwikinger) wrote :

Unfortunately this bug report is being closed because we received no response to the last inquiry for information. However, the Intrepid Ibex 8.10 Beta release was most recently announced - http://www.ubuntu.com/testing/intrepid/beta . If you are able to confirm this is still an issue with this most recent release please feel free to reopen this report. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks.

Changed in linux:
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.