Activity log for bug #232027

Date Who What changed Old value New value Message
2008-05-19 20:01:20 Micah Cowan bug added bug
2008-05-29 18:19:52 Pedro Villavicencio gnome-terminal: status New Incomplete
2008-05-29 18:19:52 Pedro Villavicencio gnome-terminal: assignee desktop-bugs
2008-05-29 18:19:52 Pedro Villavicencio gnome-terminal: importance Undecided Low
2008-05-29 22:14:45 Micah Cowan bug added attachment '%gconf.xml' (~/.gconf/apps/gnome-terminal/profiles/Default/%gconf.xml)
2008-05-29 22:56:13 Micah Cowan gnome-terminal: status Incomplete New
2008-05-29 23:00:13 Micah Cowan description Binary package hint: gnome-terminal Steps to reproduce (some steps may not be necessary; I'm not on my home machine right now so can't eliminate the unnecessary steps): 1. Open gnome-terminal 2. Type some stuff (may not be necessary) 3. Open a new tab via Control-Shift-T 4. Type some stuff (may not be necessary) 5. Close the tab (I usually do this via Control-D in the shell) Resulting Behavior: Keys typed in the original tab are no longer processed (they are, however, queued up: see the Workarounds). Expected Behavior: Keys typed in the original tab should be processed as normal, appearing and taking effect in the terminal. Workarounds: - Opening a new tab again will cause all the keys that had been typed in the original tab to be processed immediately. Closing that tab again results in the same buggy behavior. - Opening a new _window_, via Control-Shift-N, will cause all the keys to be processed immediately, and closing the new window does _not_ result in the original terminal window locking up again. Apologies for not specifying the gnome-terminal package version; I'm away from the affected system at this moment. However, I am running Hardy Heron (8.04), and my packages were up-to-date as of last night. Binary package hint: gnome-terminal Steps to reproduce (some steps may not be necessary; I'm not on my home machine right now so can't eliminate the unnecessary steps): 1. Open gnome-terminal 2. Type some stuff (may not be necessary) 3. Open a new tab via Control-Shift-T 4. Type some stuff (may not be necessary) 5. Close the tab (I usually do this via Control-D in the shell) Resulting Behavior: Keys typed in the original tab are no longer processed (they are, however, queued up: see the Workarounds). Expected Behavior: Keys typed in the original tab should be processed as normal, appearing and taking effect in the terminal. Workarounds: - Opening a new tab again will cause all the keys that had been typed in the original tab to be processed immediately. Closing that tab again results in the same buggy behavior. [NOTE: this does not appear to be the case lately; nothing previously typed is processed, it must be retyped.] - Opening a new _window_, via Control-Shift-N, will cause all the keys to be processed immediately, and closing the new window does _not_ result in the original terminal window locking up again. Apologies for not specifying the gnome-terminal package version; I'm away from the affected system at this moment. However, I am running Hardy Heron (8.04), and my packages were up-to-date as of last night.
2008-05-29 23:00:13 Micah Cowan title Closing tab results in not accepting input Closing tab results in not accepting input, when XIM is active
2008-07-17 06:30:50 Micah Cowan title Closing tab results in not accepting input, when XIM is active Input ignored when switching workspaces, closing windows...
2008-10-08 11:56:15 Sebastien Bacher scim: assignee desktop-bugs
2008-10-23 18:33:46 Pablo Castellano scim: status New Confirmed
2008-10-23 18:33:46 Pablo Castellano scim: statusexplanation Confirmed as for last comment
2009-04-01 04:21:29 Micah Cowan marked as duplicate 66104
2009-09-11 09:02:20 Pablo Castellano removed subscriber Pablo Castellano