maemo.org Bugzilla – Bug 3071
In "screen", backspace key gives "^@" (nul character) instead of "^?"
Last modified: 2009-10-22 07:57:11 UTC
You need to
before you can comment on or make changes to this bug.
OS2008 / 2.2007.50-2
STEPS TO REPRODUCE THE PROBLEM:
1. Open osso-xterm.
2. Start the "screen" utility.
3. Type "cat" [Enter].
4. Type a few characters, then the backspace key.
The last character should be erased (but if Ctrl-V is typed first, one should
One gets "^@".
This seems to be a known problem in screen with some terminals, see
Unfortunately this problem occurs in osso-xterm. Moreover the workaround
described in the above URL, more specifically
bindkey -d -k kb stuff "\177"
in the .screenrc, doesn't change anything here.
Diablo 5.2008.43-7 ships libvte4 1:0.12.2-0mh7.
Patch against 0.16.14 available, not reviewed/committed in upstream GNOME, but
already committed in Ubuntu.
> 2. Start the "screen" utility.
What is this? Where can I get that? Exact steps welcome.
Note to myself:
Fremantle SDK beta ships vte, libvte-common, libvte-dev and vte4 in version
So the upstream patch should be more or less easy to apply.
(In reply to comment #2)
> > 2. Start the "screen" utility.
> What is this? Where can I get that? Exact steps welcome.
Here's information I get from "apt-cache show screen":
Pre-Depends: debconf (>= 0.5) | debconf-2.0
Depends: libc6 (>= 2.3.5-1), libncursesw5 (>= 5.4-1), base-passwd (>= 18.104.22.168),
passwd (>= 1:4.0.3-10), ncurses-base
Conflicts: suidmanager (<< 0.52)
Maintainer: maemo integration <firstname.lastname@example.org>
Description: a terminal multiplexor with VT100/ANSI terminal emulation
screen is a terminal multiplexor that runs several separate "screens" on a
single physical character-based terminal. Each virtual terminal emulates a
DEC VT100 plus several ANSI X3.64 and ISO 2022 functions. Screen sessions
can be detached and resumed later on a different terminal.
Screen also supports a whole slew of other features. Some of these are:
configurable input and output translation, serial port support, configurable
logging, multi-user support, and utf8 charset support.
Upstream was closed as WONTFIX:
"What vte does is exactly what xterm does. Fix screen. Or explain to me why
this works in xterm but not vte."
Comments to http://bugzilla.gnome.org/show_bug.cgi?id=543379 answering that
The problem can be fixed in two ways (I haven't tried):
1. There's a patch for vte here:
but it seems to have been dropped. I don't know why.
2. There's a patch for GNU screen here:
Until the problem is fixed, here's a possible workaround: before running
screen, ssh to localhost (and each time the screen session is attached, it must
be done after a ssh in order to avoid the bug).
(In reply to comment #5)
> 2. There's a patch for GNU screen here:
I've recompiled screen using this patch and this solved the problem. FYI:
$ wget http://ftp.gnu.org/gnu/screen/screen-4.0.3.tar.gz
$ tar xzf screen-4.0.3.tar.gz
$ cd screen-4.0.3
$ wget -O -
$ ./configure --prefix=/path/to/prefix
$ sudo gainroot
# make install
is not included in an upstream *tarball* yet and as the internal screen diff.gz
for Fremantle does not list the patch this should be still valid in Fremantle.
Setting version info + importing.
Just tested this in latest Fremantle myself and "^?" is correctly displayed.
Unfortunately this is a WONTFIX for Diablo as Diablo is in maintenance mode and
Nokia will only provide bugfixes for critical issues if at all.
For your interest the Mer project aims to provide a community backport of
Fremantle for N8x0 devices. See http://wiki.maemo.org/Mer for more information.
Marking patches of interest to Diablo (Maemo4) community updates, please excuse