Package: mlterm Version: 3.0.1-1 Severity: important After upgrading mlterm from 2.9.4-5 to 3.0.1-1 Ctrl+F1 (Open new window/screen) has stopped working. On pressing this key-combination I get the symbols "1;5~" instead of a new window.
Downgrading mlterm mlterm-common mlterm-tools to 2.9.4-5 fixes the issue. (Which shows that it is not X or my windowmanager that broke). I have verified the issue both with icewm and wmaker. Personally I consider this a serious bug, Ctrl+F1 has always been one of mlterm's major selling points for me. cu andreas -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages mlterm depends on: ii libc6 2.11.2-5 Embedded GNU C Library: Shared lib ii libfribidi0 0.19.2-1 Free Implementation of the Unicode ii libglib2.0-0 2.24.1-1 The GLib library of C routines ii libgtk2.0-0 2.20.1-1+b1 The GTK+ graphical user interface ii libx11-6 2:1.3.3-3 X11 client-side library ii libxft2 2.1.14-2 FreeType-based font drawing librar ii mlterm-common 3.0.1-1 MultiLingual TERMinal, common file Versions of packages mlterm recommends: ii mlterm-tools 3.0.1-1 MultiLingual TERMinal, additional Versions of packages mlterm suggests: pn mlterm-im-m17nlib <none> (no description available) pn mlterm-im-scim <none> (no description available) pn mlterm-im-uim <none> (no description available) pn t1-cyrillic <none> (no description available) pn ttf-arphic-bsmi00lp <none> (no description available) pn ttf-arphic-gbsn00lp <none> (no description available) pn ttf-baekmuk <none> (no description available) ii ttf-freefont 20090104-7 Freefont Serif, Sans and Mono True pn ttf-vlgothic <none> (no description available) ii unifont 1:5.1.20080914-1 font with a glyph for each visible ii xfonts-efont-unicode 0.4.2-3 /efont/ Unicode fonts for X which -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
