updating console-setup in X destroys screen

Hi,
I cant reproduce this here.
/etc/init.d/console-setup contains here (on feisty) :

    start|force-reload|restart|reload)
        if [ -z "$DISPLAY" ] && ....
            ...
        elif ! run_by_init; then
            log_action_begin_msg "Saving console font and keymap for next boot"
            if setupcon --save-only; then
                log_action_end_msg 0
            else
                log_action_end_msg $?
            fi
        fi

so it does only some saving even with apt-get --reinstall .
Do you have a modified version of that file ?

Or not exported/empty DISPLAY ?
export|grep DISPLAY
declare -x DISPLAY=":0.0"

"Or not exported/empty DISPLAY ?"

That was the problem! Thank you!
I'm using rxvt and "su - " to get a root shell. I don't know if it's a proper way or not. How can I make that declare thing permanent?

If you would use su without the '-' the environment should be left intact.

OK I changed
       if [ -z "$DISPLAY" ] && ! pidof usplash >/dev/null; then
to
       if ! ps -Af | grep -q 'bin/X.* vt$(fgconsole) ' && ! pidof usplash >/dev/null; then
in
 /etc/init.d/console-setup
here. Now it works with su - too.

Ooops - I'm sorry but the above patch does not work as expected, since grep finds itself allways. Here a fixed version:

Change
       if [ -z "$DISPLAY" ] && ! pidof usplash >/dev/null; then
to
       if ! ps -Ao comm,command | grep -q "^X.* vt$(fgconsole) " &&
           ! pidof usplash >/dev/null; then
(starting a new line after && should be OK)

I have a feisty host that has X running. From an ssh session into that machine I run xen-tools's xen-create-image to creating a feisty domU.
When that runs debootstrap (in the host, not the guest), and installs console-setup, that corrupts video ram on X. I image the same thing could happen if you run debootstrap for a chroot setup, but have not tested that.

Perhaps console-setup should use "pidof X" instead of checking $DISPLAY? I think that would have helped Simonics too.

But I imagine the real problem here is that console-setup runs from the debootstrap, affecting the host instead of the target. Please advise.

Thanks for the suggestions. As fgconsole doesn't always actually return a console number under X, I've taken a somewhat different approach involving just checking whether the output of fgconsole is in [1-6]. I know this isn't perfect, but since running setupcon is just a nice-to-have I think it's good enough.

console-setup (1.13ubuntu10) feisty; urgency=low

  * Source debconf confmodule earlier in postinst (it should always be
    sourced as early as possible, as it re-executes the calling script).
  * Fix horrible confusion if the locale has no supported default codeset
    (LP: #84401).
  * Fix console-setup/codeset default to be one of the available choices.
  * Try harder to ensure that we aren't running under X when deciding
    whether to run setupcon on upgrade (thanks to Kurt J. Bosch for
    suggestions; LP: #93338).
  * Don't set an AltGr key by default for US layouts (LP: #76901).

 -- Colin Watson <email address hidden> Sun, 1 Apr 2007 16:49:02 +0100