Activity log for bug #96676

Date Who What changed Old value New value Message
2007-03-26 21:23:23 Dmik bug added bug
2007-03-26 21:25:46 Dmik description Binary package hint: gnome-terminal After upgrading from Edgy to Feisty, gnome-terminal started to generate "wrong" sequences when pressing Shift/Alt/Ctrl-F1..F4 keys, and some other (like Shift-Arrows). In particular, it generates: Shift Alt Ctrl F1 \EO1;2P \EO1;3P \EO1;5P F2 \EO1;2Q \EO1;3Q \EO1;5Q F3 \EO1;2R \EO1;3R \EO1;5R F4 \EO1;2S \EO1;3S \EO1;5S while it should: Shift Alt Ctrl F1 \EO2P \EO3P \EO5P F2 \EO2Q \EO3Q \EO5Q F3 \EO2R \EO3R \EO5R F4 \EO2S \EO3S \EO5S according to the output of the infocmp command (TERM is set to xterm here, by default). The second ("correct") variant of sequences is also exactly what happens in the Edgy installation on another computer. It looks like 1; gets inserted to the middle of the sequence for these function keys and also in the middle of sequences for combinations like Shift-Up/Down/Left/Right. As a result, it's no more possible to e.g. create a new file using Shift-F4 in Midnight commander, or to select text in its built-in editor using Shift+Arrows. Btw, the xterm application both in Edgy and Feisty generates sequences from the first table (i.e. with 1; inserted), but I found how to change it by editing xterm resources (/etc/X11/app-defaults/XTerm-color), which didn't influence gnome-terminal though. It also didn't completely restore the normal behavior of Midnight Commander (Shift-F1..F4 started to work but other function keys stopped to work properly). It looks like these problems in xterm and in gnome-terminal have a common root. Also, I tried to alter the xterm definition in terminfo by replacing sequences from the second table from ones from the first one. It also worked, but again, only for those F1..F4 keys only, and broke recognition of other function keys. Anyway, I don't think that changing the xterm definition is a correct way to go, because what is in terminfo by default is a kind of standard nowadays (at least for common keys and combinations). Binary package hint: gnome-terminal After upgrading from Edgy to Feisty, gnome-terminal started to generate "wrong" sequences when pressing Shift/Alt/Ctrl-F1..F4 keys, and some other (like Shift-Arrows). In particular, it generates: Shift Alt Ctrl F1 \EO1;2P \EO1;3P \EO1;5P F2 \EO1;2Q \EO1;3Q \EO1;5Q F3 \EO1;2R \EO1;3R \EO1;5R F4 \EO1;2S \EO1;3S \EO1;5S while it should: Shift Alt Ctrl F1 \EO2P \EO3P \EO5P F2 \EO2Q \EO3Q \EO5Q F3 \EO2R \EO3R \EO5R F4 \EO2S \EO3S \EO5S according to the output of the infocmp command (TERM is set to xterm here, by default). The second ("correct") variant of sequences is also exactly what happens in the Edgy installation on another computer. It looks like 1; gets inserted to the middle of the sequence for these function keys and also in the middle of sequences for combinations like Shift-Up/Down/Left/Right. As a result, it's not possible anymore to e.g. create a new file using Shift-F4 in Midnight commander, or to select text in its built-in editor using Shift+Arrows. By the way, the xterm application both in Edgy and Feisty generates sequences from the first table (i.e. with 1; inserted), but I found how to change it by editing xterm resources (/etc/X11/app-defaults/XTerm-color), which didn't influence gnome-terminal though. It also didn't completely restore the normal behavior of Midnight Commander (Shift-F1..F4 started to work but other function keys stopped to work properly). It looks like these problems in xterm and in gnome-terminal have a common root. Also, I tried to alter the xterm definition in terminfo by replacing sequences from the second table with ones from the first one. It also worked, but again, only for those F1..F4 keys only, and broke recognition of other function keys. Anyway, I don't think that changing the xterm definition is a correct way to go, because what is in terminfo by default is a kind of standard nowadays (at least for common keys and combinations).
2007-03-26 21:27:46 Dmik description Binary package hint: gnome-terminal After upgrading from Edgy to Feisty, gnome-terminal started to generate "wrong" sequences when pressing Shift/Alt/Ctrl-F1..F4 keys, and some other (like Shift-Arrows). In particular, it generates: Shift Alt Ctrl F1 \EO1;2P \EO1;3P \EO1;5P F2 \EO1;2Q \EO1;3Q \EO1;5Q F3 \EO1;2R \EO1;3R \EO1;5R F4 \EO1;2S \EO1;3S \EO1;5S while it should: Shift Alt Ctrl F1 \EO2P \EO3P \EO5P F2 \EO2Q \EO3Q \EO5Q F3 \EO2R \EO3R \EO5R F4 \EO2S \EO3S \EO5S according to the output of the infocmp command (TERM is set to xterm here, by default). The second ("correct") variant of sequences is also exactly what happens in the Edgy installation on another computer. It looks like 1; gets inserted to the middle of the sequence for these function keys and also in the middle of sequences for combinations like Shift-Up/Down/Left/Right. As a result, it's not possible anymore to e.g. create a new file using Shift-F4 in Midnight commander, or to select text in its built-in editor using Shift+Arrows. By the way, the xterm application both in Edgy and Feisty generates sequences from the first table (i.e. with 1; inserted), but I found how to change it by editing xterm resources (/etc/X11/app-defaults/XTerm-color), which didn't influence gnome-terminal though. It also didn't completely restore the normal behavior of Midnight Commander (Shift-F1..F4 started to work but other function keys stopped to work properly). It looks like these problems in xterm and in gnome-terminal have a common root. Also, I tried to alter the xterm definition in terminfo by replacing sequences from the second table with ones from the first one. It also worked, but again, only for those F1..F4 keys only, and broke recognition of other function keys. Anyway, I don't think that changing the xterm definition is a correct way to go, because what is in terminfo by default is a kind of standard nowadays (at least for common keys and combinations). Binary package hint: gnome-terminal After upgrading from Edgy to Feisty, gnome-terminal started to generate "wrong" sequences when pressing Shift/Alt/Ctrl-F1..F4 keys, and some other (like Shift-Arrows). In particular, it generates: Shift Alt Ctrl F1 \EO1;2P \EO1;3P \EO1;5P F2 \EO1;2Q \EO1;3Q \EO1;5Q F3 \EO1;2R \EO1;3R \EO1;5R F4 \EO1;2S \EO1;3S \EO1;5S while it should: Shift Alt Ctrl F1 \EO2P \EO3P \EO5P F2 \EO2Q \EO3Q \EO5Q F3 \EO2R \EO3R \EO5R F4 \EO2S \EO3S \EO5S according to the output of the infocmp command (TERM is set to xterm here, by default). The second ("correct") variant of sequences is also exactly what happens in the Edgy installation on another computer. It looks like 1; gets inserted to the middle of the sequence for these function keys and also in the middle of sequences for combinations like Shift-Up/Down/Left/Right. As a result, it's not possible anymore to e.g. create a new file using Shift-F4 in Midnight commander, or to select text in its built-in editor using Shift+Arrows. By the way, the xterm application both in Edgy and Feisty generates sequences from the first table (i.e. with 1; inserted), but I found how to change it by editing xterm resources (/etc/X11/app-defaults/XTerm-color), which didn't influence gnome-terminal though. It also didn't completely restore the normal behavior of Midnight Commander (Shift-F1..F4 started to work but other function keys stopped to work properly). It looks like these problems in xterm and in gnome-terminal have a common root. Also, I tried to alter the xterm definition in terminfo by replacing sequences from the second table with ones from the first one. It also worked, but again, only for those F1..F4 keys only, and broke recognition of other function keys. Anyway, I don't think that changing the xterm definition is a correct way to go, because what is in terminfo by default is a kind of standard nowadays (at least for common keys and combinations).
2007-03-26 21:28:54 Dmik description Binary package hint: gnome-terminal After upgrading from Edgy to Feisty, gnome-terminal started to generate "wrong" sequences when pressing Shift/Alt/Ctrl-F1..F4 keys, and some other (like Shift-Arrows). In particular, it generates: Shift Alt Ctrl F1 \EO1;2P \EO1;3P \EO1;5P F2 \EO1;2Q \EO1;3Q \EO1;5Q F3 \EO1;2R \EO1;3R \EO1;5R F4 \EO1;2S \EO1;3S \EO1;5S while it should: Shift Alt Ctrl F1 \EO2P \EO3P \EO5P F2 \EO2Q \EO3Q \EO5Q F3 \EO2R \EO3R \EO5R F4 \EO2S \EO3S \EO5S according to the output of the infocmp command (TERM is set to xterm here, by default). The second ("correct") variant of sequences is also exactly what happens in the Edgy installation on another computer. It looks like 1; gets inserted to the middle of the sequence for these function keys and also in the middle of sequences for combinations like Shift-Up/Down/Left/Right. As a result, it's not possible anymore to e.g. create a new file using Shift-F4 in Midnight commander, or to select text in its built-in editor using Shift+Arrows. By the way, the xterm application both in Edgy and Feisty generates sequences from the first table (i.e. with 1; inserted), but I found how to change it by editing xterm resources (/etc/X11/app-defaults/XTerm-color), which didn't influence gnome-terminal though. It also didn't completely restore the normal behavior of Midnight Commander (Shift-F1..F4 started to work but other function keys stopped to work properly). It looks like these problems in xterm and in gnome-terminal have a common root. Also, I tried to alter the xterm definition in terminfo by replacing sequences from the second table with ones from the first one. It also worked, but again, only for those F1..F4 keys only, and broke recognition of other function keys. Anyway, I don't think that changing the xterm definition is a correct way to go, because what is in terminfo by default is a kind of standard nowadays (at least for common keys and combinations). Binary package hint: gnome-terminal After upgrading from Edgy to Feisty, gnome-terminal started to generate "wrong" sequences when pressing Shift/Alt/Ctrl-F1..F4 keys, and some other (like Shift-Arrows). In particular, it generates: Shift...Alt.....Ctrl F1 \EO1;2P \EO1;3P \EO1;5P F2 \EO1;2Q \EO1;3Q \EO1;5Q F3 \EO1;2R \EO1;3R \EO1;5R F4 \EO1;2S \EO1;3S \EO1;5S while it should: Shift.Alt...Ctrl F1 \EO2P \EO3P \EO5P F2 \EO2Q \EO3Q \EO5Q F3 \EO2R \EO3R \EO5R F4 \EO2S \EO3S \EO5S according to the output of the infocmp command (TERM is set to xterm here, by default). The second ("correct") variant of sequences is also exactly what happens in the Edgy installation on another computer. It looks like 1; gets inserted to the middle of the sequence for these function keys and also in the middle of sequences for combinations like Shift-Up/Down/Left/Right. As a result, it's not possible anymore to e.g. create a new file using Shift-F4 in Midnight commander, or to select text in its built-in editor using Shift+Arrows. By the way, the xterm application both in Edgy and Feisty generates sequences from the first table (i.e. with 1; inserted), but I found how to change it by editing xterm resources (/etc/X11/app-defaults/XTerm-color), which didn't influence gnome-terminal though. It also didn't completely restore the normal behavior of Midnight Commander (Shift-F1..F4 started to work but other function keys stopped to work properly). It looks like these problems in xterm and in gnome-terminal have a common root. Also, I tried to alter the xterm definition in terminfo by replacing sequences from the second table with ones from the first one. It also worked, but again, only for those F1..F4 keys only, and broke recognition of other function keys. Anyway, I don't think that changing the xterm definition is a correct way to go, because what is in terminfo by default is a kind of standard nowadays (at least for common keys and combinations).
2007-03-26 21:30:19 Dmik description Binary package hint: gnome-terminal After upgrading from Edgy to Feisty, gnome-terminal started to generate "wrong" sequences when pressing Shift/Alt/Ctrl-F1..F4 keys, and some other (like Shift-Arrows). In particular, it generates: Shift...Alt.....Ctrl F1 \EO1;2P \EO1;3P \EO1;5P F2 \EO1;2Q \EO1;3Q \EO1;5Q F3 \EO1;2R \EO1;3R \EO1;5R F4 \EO1;2S \EO1;3S \EO1;5S while it should: Shift.Alt...Ctrl F1 \EO2P \EO3P \EO5P F2 \EO2Q \EO3Q \EO5Q F3 \EO2R \EO3R \EO5R F4 \EO2S \EO3S \EO5S according to the output of the infocmp command (TERM is set to xterm here, by default). The second ("correct") variant of sequences is also exactly what happens in the Edgy installation on another computer. It looks like 1; gets inserted to the middle of the sequence for these function keys and also in the middle of sequences for combinations like Shift-Up/Down/Left/Right. As a result, it's not possible anymore to e.g. create a new file using Shift-F4 in Midnight commander, or to select text in its built-in editor using Shift+Arrows. By the way, the xterm application both in Edgy and Feisty generates sequences from the first table (i.e. with 1; inserted), but I found how to change it by editing xterm resources (/etc/X11/app-defaults/XTerm-color), which didn't influence gnome-terminal though. It also didn't completely restore the normal behavior of Midnight Commander (Shift-F1..F4 started to work but other function keys stopped to work properly). It looks like these problems in xterm and in gnome-terminal have a common root. Also, I tried to alter the xterm definition in terminfo by replacing sequences from the second table with ones from the first one. It also worked, but again, only for those F1..F4 keys only, and broke recognition of other function keys. Anyway, I don't think that changing the xterm definition is a correct way to go, because what is in terminfo by default is a kind of standard nowadays (at least for common keys and combinations). Binary package hint: gnome-terminal After upgrading from Edgy to Feisty, gnome-terminal started to generate "wrong" sequences when pressing Shift/Alt/Ctrl-F1..F4 keys, and some other (like Shift-Arrows). In particular, it generates: Shift...Alt.....Ctrl F1 \EO1;2P \EO1;3P \EO1;5P F2 \EO1;2Q \EO1;3Q \EO1;5Q F3 \EO1;2R \EO1;3R \EO1;5R F4 \EO1;2S \EO1;3S \EO1;5S while it should: Shift.Alt...Ctrl F1 \EO2P \EO3P \EO5P F2 \EO2Q \EO3Q \EO5Q F3 \EO2R \EO3R \EO5R F4 \EO2S \EO3S \EO5S according to the output of the infocmp command (TERM is set to xterm here, by default). The second ("correct") variant of sequences is also exactly what happens in the Edgy installation on another computer. It looks like 1; gets inserted to the middle of the sequence for these function keys and also in the middle of sequences for combinations like Shift-Up/Down/Left/Right. As a result, it's not possible anymore to e.g. create a new file using Shift-F4 in Midnight commander, or to select text in its built-in editor using Shift+Arrows. By the way, the xterm application both in Edgy and Feisty generates sequences from the first table (i.e. with 1; inserted), but I found how to change it by editing xterm resources (/etc/X11/app-defaults/XTerm-color), which didn't influence gnome-terminal though. It also didn't completely restore the normal behavior of Midnight Commander (Shift-F1..F4 started to work but other function keys stopped to work properly). It looks like these problems in xterm and in gnome-terminal have a common root. Also, I tried to alter the xterm definition in terminfo by replacing sequences from the second table with ones from the first one. It also worked, but again, only for those F1..F4 keys only, and broke recognition of other function keys. Anyway, I don't think that changing the xterm definition is a correct way to go, because what is in terminfo by default is a kind of standard nowadays (at least for common keys and combinations). dmik@ubuntu:~$ dpkg -s gnome-terminal Package: gnome-terminal Status: install ok installed Priority: optional Section: gnome Installed-Size: 432 Maintainer: Ubuntu Core Developers <ubuntu-devel-discuss@lists.ubuntu.com> Architecture: i386 Version: 2.18.0-0ubuntu1 Replaces: gnome-terminal2 Provides: x-terminal-emulator
2007-03-26 21:33:43 Dmik description Binary package hint: gnome-terminal After upgrading from Edgy to Feisty, gnome-terminal started to generate "wrong" sequences when pressing Shift/Alt/Ctrl-F1..F4 keys, and some other (like Shift-Arrows). In particular, it generates: Shift...Alt.....Ctrl F1 \EO1;2P \EO1;3P \EO1;5P F2 \EO1;2Q \EO1;3Q \EO1;5Q F3 \EO1;2R \EO1;3R \EO1;5R F4 \EO1;2S \EO1;3S \EO1;5S while it should: Shift.Alt...Ctrl F1 \EO2P \EO3P \EO5P F2 \EO2Q \EO3Q \EO5Q F3 \EO2R \EO3R \EO5R F4 \EO2S \EO3S \EO5S according to the output of the infocmp command (TERM is set to xterm here, by default). The second ("correct") variant of sequences is also exactly what happens in the Edgy installation on another computer. It looks like 1; gets inserted to the middle of the sequence for these function keys and also in the middle of sequences for combinations like Shift-Up/Down/Left/Right. As a result, it's not possible anymore to e.g. create a new file using Shift-F4 in Midnight commander, or to select text in its built-in editor using Shift+Arrows. By the way, the xterm application both in Edgy and Feisty generates sequences from the first table (i.e. with 1; inserted), but I found how to change it by editing xterm resources (/etc/X11/app-defaults/XTerm-color), which didn't influence gnome-terminal though. It also didn't completely restore the normal behavior of Midnight Commander (Shift-F1..F4 started to work but other function keys stopped to work properly). It looks like these problems in xterm and in gnome-terminal have a common root. Also, I tried to alter the xterm definition in terminfo by replacing sequences from the second table with ones from the first one. It also worked, but again, only for those F1..F4 keys only, and broke recognition of other function keys. Anyway, I don't think that changing the xterm definition is a correct way to go, because what is in terminfo by default is a kind of standard nowadays (at least for common keys and combinations). dmik@ubuntu:~$ dpkg -s gnome-terminal Package: gnome-terminal Status: install ok installed Priority: optional Section: gnome Installed-Size: 432 Maintainer: Ubuntu Core Developers <ubuntu-devel-discuss@lists.ubuntu.com> Architecture: i386 Version: 2.18.0-0ubuntu1 Replaces: gnome-terminal2 Provides: x-terminal-emulator Binary package hint: gnome-terminal After upgrading from Edgy to Feisty, gnome-terminal started to generate "wrong" sequences when pressing Shift/Alt/Ctrl-F1..F4 keys, and some other (like Shift-Arrows). In particular, it generates: Shift...Alt.....Ctrl F1 \EO1;2P \EO1;3P \EO1;5P F2 \EO1;2Q \EO1;3Q \EO1;5Q F3 \EO1;2R \EO1;3R \EO1;5R F4 \EO1;2S \EO1;3S \EO1;5S while it should: Shift.Alt...Ctrl F1 \EO2P \EO3P \EO5P F2 \EO2Q \EO3Q \EO5Q F3 \EO2R \EO3R \EO5R F4 \EO2S \EO3S \EO5S according to the output of the infocmp command (TERM is set to xterm here, by default). The second ("correct") variant of sequences is also exactly what happens in the Edgy installation on another computer. It looks like 1; gets inserted into the middle of the sequence for these function keys and also into the middle of sequences for combinations like Shift-Up/Down/Left/Right. As a result, it's not possible anymore to e.g. create a new file using Shift-F4 in Midnight commander, or to select text in its built-in editor using Shift+Arrows. By the way, the xterm application both in Edgy and Feisty generates sequences from the first table (i.e. with 1; inserted), but I found how to change it by editing xterm resources (/etc/X11/app-defaults/XTerm-color), which didn't influence gnome-terminal though. It also didn't completely restore the normal behavior of Midnight Commander (Shift-F1..F4 started to work but other function keys stopped to work properly). It looks like these problems in xterm and in gnome-terminal have a common root. Also, I tried to alter the xterm definition in terminfo by replacing sequences from the second table with ones from the first one. It also worked, but again, only for those F1..F4 keys, and broke recognition of other function keys. Anyway, I don't think that changing the xterm definition is a correct way to go, because what is in terminfo by default seems to be a kind of standard nowadays (at least for common keys and combinations). dmik@ubuntu:~$ dpkg -s gnome-terminal Package: gnome-terminal Status: install ok installed Priority: optional Section: gnome Installed-Size: 432 Maintainer: Ubuntu Core Developers <ubuntu-devel-discuss@lists.ubuntu.com> Architecture: i386 Version: 2.18.0-0ubuntu1 Replaces: gnome-terminal2 Provides: x-terminal-emulator
2007-04-02 12:40:03 Sebastien Bacher gnome-terminal: status Unconfirmed Confirmed
2007-04-02 12:40:03 Sebastien Bacher gnome-terminal: importance Undecided Low
2007-04-02 12:40:03 Sebastien Bacher gnome-terminal: statusexplanation Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: http://bugzilla.gnome.org/show_bug.cgi?id=425462
2007-04-02 12:40:03 Sebastien Bacher gnome-terminal: assignee desktop-bugs
2007-04-02 12:40:24 Sebastien Bacher bug assigned to gnome-terminal (upstream)
2007-04-03 07:05:51 Bug Watch Updater gnome-terminal: status Unknown Unconfirmed
2007-05-04 21:56:36 Alex Mauer bug assigned to vte (Ubuntu)
2007-05-04 21:57:06 Alex Mauer vte: status Unconfirmed Confirmed
2007-05-04 21:57:06 Alex Mauer vte: statusexplanation
2007-06-20 19:34:29 Izzy bug assigned to xterm (Ubuntu)
2007-06-21 15:57:12 Alex Mauer bug assigned to ncurses (Ubuntu)
2008-05-05 22:02:56 Bryce Harrington xterm: importance Undecided Medium
2008-05-05 22:02:56 Bryce Harrington xterm: status New Confirmed
2009-01-27 02:01:05 Bryce Harrington xterm: status Confirmed Triaged
2009-01-27 02:01:05 Bryce Harrington xterm: statusexplanation Confirmed it's still an issue on Jaunty with xterm and gnome-terminal.
2009-01-27 02:01:27 Bryce Harrington xterm: assignee bryceharrington
2009-01-27 02:01:27 Bryce Harrington xterm: statusexplanation Confirmed it's still an issue on Jaunty with xterm and gnome-terminal.
2009-03-19 05:37:07 Bryce Harrington xterm (Ubuntu): assignee bryceharrington
2009-05-20 08:02:01 Roy Jamison ncurses (Ubuntu): status New Invalid
2009-06-07 05:37:45 salwanet gnome-terminal (Ubuntu): assignee Ubuntu Desktop Bugs (desktop-bugs) salwanet (fauzi-abdurrohim)
2009-09-11 13:53:15 Pedro Villavicencio gnome-terminal (Ubuntu): status Confirmed Triaged
2009-09-11 13:53:34 Pedro Villavicencio gnome-terminal (Ubuntu): assignee salwanet (fauzi-abdurrohim) Ubuntu Desktop Bugs (desktop-bugs)
2009-10-02 18:37:22 Pedro Villavicencio vte (Ubuntu): importance Undecided Low
2009-11-03 09:39:18 Tamas Fejos bug watch added http://www.midnight-commander.org/ticket/386
2009-11-03 15:31:16 Roy Jamison summary [feisty] function keys don't work in gnome-terminal function keys don't work in gnome-terminal
2009-12-05 02:30:23 Bryce Harrington removed subscriber Bryce Harrington
2010-01-08 22:36:00 Roy Jamison summary function keys don't work in gnome-terminal [KARMIC] function keys don't work in gnome-terminal
2010-01-08 23:08:15 Chris Coulson summary [KARMIC] function keys don't work in gnome-terminal function keys don't work in gnome-terminal
2010-01-08 23:22:00 Roy Jamison removed subscriber Teej
2010-05-03 21:31:08 Peter de Schulthess gnome-terminal (Ubuntu): status Triaged Confirmed
2010-05-04 11:51:45 Chris Coulson gnome-terminal (Ubuntu): status Confirmed Triaged
2010-05-04 17:08:43 Kay Parker removed subscriber Kay Parker
2010-09-16 12:22:46 Bug Watch Updater gnome-terminal: importance Unknown Medium
2011-04-28 17:54:11 Yury V. Zaytsev bug added subscriber Yury V. Zaytsev
2012-02-15 17:18:36 Andreas Raster bug added subscriber Andreas Raster
2012-10-20 13:22:09 Derek Chen-Becker bug added subscriber Derek Chen-Becker
2014-01-04 07:34:03 Bug Watch Updater gnome-terminal: status New Invalid
2014-03-16 17:08:13 Egmont Koblinger bug added subscriber Egmont Koblinger