GNOME Bugzilla – Bug 107031
device-control-string error
Last modified: 2008-11-29 07:56:58 UTC
If I use gnome-terminal compiled with vte (tested with 0.17 and 0.20), and start up vim, I get these errors in .xsession-errors: ** (gnome-terminal:19064): WARNING **: No handler for control sequence `device-control-string' defined. These are repeated several times each time I use vim. I have seen a couple of gnome-terminal crashes, and not sure if it is related. I don't see the problem when compiling gnome-terminal against libzvt2.
The vte widget doesn't currently implement any of the device-control functions. I'll have to fix that.
This is also present in GNOME Terminal 2.4.2. Can someone with the right privileges change the keyword from GNOMEVER2.2 to GNOMEVER2.4?
will this be fixed anytime?
Patches are accepted...
What OS is this? I don't see those when starting vim here.
It was originally Debian with gnome2.2 backport. But it is still present in Debian Sarge (gnome 2.8). Steps to reproduce: tail -f ~/.xsession-errors in one terminal vim ./newfile .xsession-errors shows these warnings. The file can be empty or not. Vim 6.13-013+2. I do use ksh now, but it was a problem in bash too. Attached is my '.vimrc' file as well. -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.8-1-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages libvte4 depends on: ii libatk1.0-0 1.8.0-4 The ATK accessibility toolkit ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an ii libfontconfig1 2.2.3-4 generic font configuration library ii libfreetype6 2.1.7-2.3 FreeType 2 font engine, shared lib ii libglib2.0-0 2.4.8-1 The GLib library of C routines ii libgtk2.0-0 2.4.14-2 The GTK+ graphical user interface ii libncurses5 5.4-4 Shared libraries for terminal hand ii libpango1.0-0 1.6.0-3 Layout and rendering of internatio ii libvte-common 1:0.11.11-6 Terminal emulator widget for GTK+ ii libx11-6 4.3.0.dfsg.1-8 X Window System protocol client li ii libxft2 2.1.2-6 FreeType-based font drawing librar ii libxrender1 0.8.3-7 X Rendering Extension client libra ii xlibs 4.3.0.dfsg.1-8 X Window System client libraries m ii zlib1g 1:1.2.2-3 compression library - runtime Note that this version of vim is patched with performance patches from http://www.nishra.com/debian/unstable/. These are unrelated however since I have seen this in vte 0.10 and 0.11 from the gnome2.2 backport and official debian sarge as well.
Created attachment 35554 [details] vimrc file
I don't see any of these warnings with current CVS nor with the Fedora Core 3 packages. Could this be a problem related to patches in debian or are people seeing the problem with other distros?
@Kjartan Maraas: Could you explain your setups and your steps to reproduce this? This still occurs with vte from todays (Feb 19) CVS. gnome2.10beta2, vim 6.1 It is Mandrake based. * Make sure your session is acutally logging things in ~/.xsession-errors * Make sure you did not exceed the filesize limit of ~/.xsession-errors (or send SIGXFSZ) I you see "...Too much output, ignoring rest..." there won't be any further logging.
This is visible with mdk 10.1 (or cooker).
and still with gnome 2.12.0 @Kjartan Maraas: Please check again.
Also reported in SuSE, https://bugzilla.novell.com/show_bug.cgi?id=145282
Weird, I don't get that, but get this instead: ** (lt-vte:13097): WARNING **: DECSET/DECRESET mode 12 not recognized, ignoring.
Hitting this in Gentoo. Very annoying; it makes ~/.xsession-errors unusable. Possibly ncurses/termcap/terminfo dependent?
Fixed (or worked around, depending on your opinion) by setting TERM="gnome"; bug 115750.
The repeating of warnings has been fixed. There are no crashes related to this. DCS are still unimplemented, and the warning is there so that when something actually fails because of that we know. (vim is using the device-control-string « DCS + q Pt ST» to as for some termcap entries, instead of using the termcap (!!!); that's why we see this) Can we close this and open a «Implement device-control-string» bug? Until that's done, the warning should be kept IMHO.
Well, the repeating might be better, but still fills up the .xsession-errors when you got a lengthier session. Nobody claimed there were crashes. I never had anything fail because of this not being implemented, and would be delighted if you could tell me a way to reproduce something that only works with the control-strings implemented. Honestly, it it would be required/needed by vim or some other app, I'd expect vim to inform me that the stuff is not supported by the terminal, rather than a warning by the terminal itself. If you want to keep the warning (I wouldn't keep it though), then if possible add what device-control-string it was and what application it triggered. To me, the warning is pretty useless and only leads to "...Too much output, ignoring rest..." in my .xsession-errors, hiding the output of other failures that might print more useful messages. You know already that gnome-terminal/vte doesn't support this, so either print it when gnome-terminal is launched, remove it completely, or at least add some more info to the message My 0,02€
I'm seeing this warning on Ubuntu Feisty when starting vim too: Version information: Ubuntu Feisty libvte9 0.16.0-0ubuntu2 (can the version of vte this bug is filed against be increased or should distros be working around this some other way?)
I made it not write that warning more than once per widget a couple years ago. Removed the warning (replaced with vte debug message) now. 2008-11-29 Behdad Esfahbod <behdad@gnome.org> Bug 107031 – device-control-string error * src/table.c (_vte_table_addi): * src/vte.c (vte_terminal_handle_sequence): * src/vteseq.c (vte_sequence_handler_decset_internal): Replace some g_warning's with vte debug output.