Activity log for bug #113444

Date Who What changed Old value New value Message
2007-05-08 22:12:55 Carl Nobile bug added bug
2007-05-08 22:54:59 Micah Cowan None: status Unconfirmed Needs Info
2007-05-08 22:54:59 Micah Cowan None: assignee micahcowan
2007-05-08 22:54:59 Micah Cowan None: statusexplanation Hello, and thank you for taking the time to submit this bug report. What sort of keyboard are you using, and what keyboard is set as your default in System -> Preferences -> Keyboard, in the Layouts tab?
2007-05-09 01:42:40 Micah Cowan None: status Needs Info Unconfirmed
2007-05-09 01:42:40 Micah Cowan None: assignee micahcowan
2007-05-09 01:42:40 Micah Cowan None: statusexplanation Hello, and thank you for taking the time to submit this bug report. What sort of keyboard are you using, and what keyboard is set as your default in System -> Preferences -> Keyboard, in the Layouts tab?
2007-05-16 22:41:28 Micah Cowan None: status Unconfirmed Needs Info
2007-05-16 22:41:28 Micah Cowan None: assignee micahcowan
2007-05-16 22:41:28 Micah Cowan None: statusexplanation Is there any change after you run "setupcon" on the VT?
2007-05-17 00:22:07 Carl Nobile bug added attachment 'console-setup' (console-setup)
2007-05-17 05:30:43 Micah Cowan None: status Needs Info Unconfirmed
2007-05-17 05:30:43 Micah Cowan None: assignee micahcowan
2007-05-17 05:30:43 Micah Cowan None: statusexplanation Is there any change after you run "setupcon" on the VT? I'm at a loss. I'm assigning it to ubiquity, as it seems probable that whatever environmental difference is affecting the keyboard, was introduced via selections at install time; hopefully someone managing those bugs will have a better idea what package to forward this to.
2007-06-15 10:43:59 Colin Watson ubiquity: status Unconfirmed Needs Info
2007-06-15 10:43:59 Colin Watson ubiquity: assignee kamion
2007-06-15 10:43:59 Colin Watson ubiquity: statusexplanation I'm at a loss. I'm assigning it to ubiquity, as it seems probable that whatever environmental difference is affecting the keyboard, was introduced via selections at install time; hopefully someone managing those bugs will have a better idea what package to forward this to. The problem is that you're using the 'intl' variant of the 'us' keymap, which gives you what are known as "dead keys" - i.e. some punctuation characters turn into modifiers that attach accent marks to the next character, so that for example 'e might give you e-acute. Clearly this isn't what you want. You mentioned that the installer told you that the detected keyboard layout was "us-en". Are you sure that's entirely accurate? I don't think it can ever say exactly that. I wonder if perhaps it said "us:intl" instead? Would it be possible for you to boot the Feisty alternate CD again, go through keyboard layout detection, and note down exactly what you did? I can then go through that in more detail. You can press the reset button after keyboard detection, and it won't touch your existing installation in any way.
2008-04-29 13:09:49 Colin Watson console-setup: status Incomplete Triaged
2008-04-29 13:09:49 Colin Watson console-setup: assignee kamion
2008-04-29 13:10:04 Colin Watson title Single & double quotes, tildys, etc. need to type twice. us:intl selected instead of plain us
2008-04-29 15:48:23 Carl Nobile bug added attachment 'unnamed' (unnamed)