xterm title won't change with kde (xttitle, xtermset, xtermcontrol all broken)

[David Sharnoff]

Binary package hint: xterm

Was this broken by bug #311983?

Running ubuntu 9.10, Karmic, xterm titles won't change with the normal escape sequences under KDE. They will change under gnome.

The utility programs to manipulate the title (xttitle, xtermset, xtermcontrol) are all broken.

Setting titles is important. Ask anyone who uses screen a lot.

xrdb -q |grep allow
*VT100*allowSendEvents: on
XTerm*allowTitleOps: true
XTerm*allowWindowOps: true

ProblemType: Bug
Architecture: amd64
Date: Fri Dec 11 17:34:12 2009
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
MachineType: Shuttle Inc SG45
Package: xterm 243-1ubuntu1
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-16-generic root=UUID=e034abc7-0fb4-42d9-ae4d-7c0e6ca62005 ro quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/tcsh
ProcVersionSignature: Ubuntu 2.6.31-16.53-generic
RelatedPackageVersions:
 xserver-xorg 1:7.4+3ubuntu10
 libgl1-mesa-glx 7.6.0-1ubuntu4
 libdrm2 2.4.14-1ubuntu1
 xserver-xorg-video-intel 2:2.9.0-1ubuntu2
 xserver-xorg-video-ati 1:6.12.99+git20090929.7968e1fb-0ubuntu1
SourcePackage: xterm
Uname: Linux 2.6.31-16-generic x86_64
XorgConf: Error: [Errno 2] No such file or directory: '/etc/X11/xorg.conf'
XsessionErrors:
 (rhythmbox:8888): Rhythmbox-WARNING **: Unable to grab media player keys: Could not get owner of name 'org.gnome.SettingsDaemon': no such name
 (polkit-gnome-authentication-agent-1:9025): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (thunderbird-bin:9058): GLib-WARNING **: g_set_prgname() called multiple times
 (firefox:9235): GLib-WARNING **: g_set_prgname() called multiple times
 (npviewer.bin:9301): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libqtcurve.so: wrong ELF class: ELFCLASS64
dmi.bios.date: 11/04/2008
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: FG45
dmi.board.vendor: Shuttle Inc
dmi.board.version: V10
dmi.chassis.type: 3
dmi.chassis.vendor: Shuttle Inc
dmi.chassis.version: H7
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd11/04/2008:svnShuttleInc:pnSG45:pvrV10:rvnShuttleInc:rnFG45:rvrV10:cvnShuttleInc:ct3:cvrH7:
dmi.product.name: SG45
dmi.product.version: V10
dmi.sys.vendor: Shuttle Inc
fglrx: Not loaded
system:
 distro: Ubuntu
 architecture: x86_64kernel: 2.6.31-16-generic

[Thomas Dickey (dickey-his)]

I don't see xterm's version number anywhere, and don't see a pointer
to the package definition for xterm, to see what changes may have been
made from the upstream source.

[David Sharnoff (launchpad-trust)]

xterm version is 243-1ubuntu1.

[Thomas Dickey (dickey-his)]

If it's the same executable (and unless KDE now has some feature for disabling changes
to the titlebar), then it's probably a difference in X resource settings due to starting
xrdb with a slightly different set of files.

If it's X resources, then you should be able to see the "Allow Title Ops" menu entry
unchecked (control/right mouse menu) when running in KDE.

[David Sharnoff (launchpad-trust)]

I checked. Allow Title Ops *is* checked but greyed out.

[Thomas Dickey (dickey-his)]

It would be greyed out if "Allow SendEvents" (control/left/menu) is
enabled (in turn, that could be a resource-difference between GNOME/KDE).

man xterm

       allowSendEvents (class AllowSendEvents)
               Specifies whether or not synthetic key and button events (gen-
               erated using the X protocol SendEvent request) should be inter-
               preted or discarded. The default is "false" meaning they are
               discarded. Note that allowing such events creates a very large
               security hole, and forcefully disables the allowXXXOps
               resources. The default is "false."

[Thomas Dickey (dickey-his)]

This should be either closed (not a bug in xterm),
or reassigned to KDE (in case someone changed
the default resources for xterm).

[Bryce Harrington (bryce)]

As per last comment, this is not a valid bug for xterm. Feel free to let the kde folks know if you can verify it is indeed an issue with what they're doing.