Package: console-tools
Version: 1:0.2.3dbs-68
Severity: normal

The new update is still referencing setup(), which no longer exists.
Here are the last few lines in /etc/init.d/console-screen.sh:

        *)
            setup
            ;;
    esac

What function is that?

Also, in my previous message I offered alternative code, but
accidentally hit Ctrl-y twice in Emacs.  Here is the corrected form:

    case "$1" in
        stop)
           ;;
        *)
           if pidof usplash ; then
                # Changing the fonts make usplash exit.  Avoid this.
                log_action_msg "Setting console screen modes"
           else
                log_action_msg "Setting console screen modes and fonts"
                setup_fonts
           fi

           setup_keymaps
           setup_screensaver
           setup_keyboard
           ;;
    esac


-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (350, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32.2-0git+k10temp+f71889fg+r600fix.091222.desktop.kms (SMP 
w/4 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages console-tools depends on:
ii  debconf [debconf-2.0]      1.5.28        Debian configuration management sy
ii  libc6                      2.10.2-5      Embedded GNU C Library: Shared lib
ii  libconsole                 1:0.2.3dbs-68 Shared libraries for Linux console
ii  lsb-base                   3.2-23        Linux Standard Base 3.2 init scrip

Versions of packages console-tools recommends:
ii  console-common                0.7.85     basic infrastructure for text cons
ii  console-data                  2:1.10-2   keymaps, fonts, charset maps, fall

Versions of packages console-tools suggests:
pn  kbd-compat                    <none>     (no description available)

-- no debconf information



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to