installing console-setup in X without $DISPLAY set kills X keyboard

Bug #61723 reported by Fabio Massimo Di Nitto
Affects Status Importance Assigned to Milestone
console-setup (Ubuntu)
Fix Released
Colin Watson

Bug Description

Hi Colin,

i was doing a texted based distupgrade in X and during console-setup run i noticed all kind of weird things happening on different xterm's (the highlited one).
Weird as in different chars being repeated tons of times, no response from the keyboard. X had to be killed to restore the keyboard.

I am not sure what to look here, but a test like this takes about 2 hours from dapper install to edgy upgrade. Probably it can be reproduced in vmware?


Colin Watson (cjwatson)
Changed in console-setup:
assignee: nobody → kamion
importance: Untriaged → High
status: Unconfirmed → Confirmed
Revision history for this message
Colin Watson (cjwatson) wrote :

This is because Fabio was upgrading inside a 'su -' session, so didn't have $DISPLAY set, so my check to avoid screwing X didn't fire.

Revision history for this message
Colin Watson (cjwatson) wrote :

console-setup (1.7ubuntu12) edgy; urgency=low

  * Don't run the init script (and thereby setupcon) on upgrade; just print
    a message telling you to run setupcon from a virtual console if you want
    to update your console configuration (closes: Malone #61723).
  * Update debian-installer/keymap handling from trunk (Anton Zinoviev).
    Drop /etc/X11/xorg.conf upgrade handling, also per trunk, as I've been
    convinced that that is much less safe due to the prevalence of GNOME/KDE
    keymap overrides, and furthermore it made it more difficult to have
    ubiquity tell console-setup just to guess a default from the locale.
  * Drop the priority of the model and layout questions to medium if a
    configuration file already exists, since they'll have been asked at
    medium first time round and if we then ask them at critical the second
    time round they will be unexpectedly shown (closes: Malone #59883).
  * Backport from trunk:
    - config.proto: Handle properly the case when the user backs up from the
      first Debconf question.

 -- Colin Watson <email address hidden> Sat, 23 Sep 2006 00:40:48 +0100

Changed in console-setup:
status: Confirmed → Fix Released
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.