Thanks, Vasa1.
==========================================
tldr summary:
Seems to be a bug in the 32 bit software, but shows up only in restricted circumstances that are easily avoided,, at least for the cases I've checked.
==========================================
Some interesting commands there I didn't know. I get:
Code:
me@u32:~$ lxterminal -t blah
me@u32:~$ # ^ gave me an untitled lxterminal window
me@u32:~$ lxterminal -t "blah blah"
me@u32:~$ # ^ gave the same result, an untitled lxterminal window
me@u32:~$ apt-cache policy lxterminal
lxterminal:
Installed: 0.1.11-4ubuntu3
Candidate: 0.1.11-4ubuntu3
Version table:
*** 0.1.11-4ubuntu3 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe i386 Packages
100 /var/lib/dpkg/status
me@u32:~$ apt-cache depends lxterminal
lxterminal
Depends: libc6
Depends: libgdk-pixbuf2.0-0
Depends: libglib2.0-0
Depends: libgtk2.0-0
Depends: libvte9
Depends: libx11-6
me@u32:~$
So I have to assume this is a bug in the 32 bit version of one or more of the above.
BUT: I've been stupid - in practice this turns out to be unimportant. When I write scripts, I often test a command in a terminal to be sure I remembered the syntax correctly. That's how I ran into this issue. In actual USE, I'd be following the t option with an " -e somecommand". I just noticed one of my old scripts that uses this is still working, so I tested with -e options:
Code:
me@u32:~$ lxterminal -t blah -e ls
elicits a barely visible flicker, presumably a titled terminal window opening and closing, whereas:
Code:
me@u3:~$ lxterminal -t blah -e sleep 6
gives me a properly titled lxterminal window.
Thanks again, champ.
Bookmarks