OK, go ahead and close this one. Something was really fucked up on that
system. The difference in ltrace output for the working vs non-working
setup made no sense so for sanity I did a cmp on the xterm binaries and
they were different! The xterm binary on the broken system was somehow
corrupt
On Tue, Jun 29, 2004 at 04:20:33PM -0700, Jeff Bowden wrote:
> >>$ xterm -sb
> >>xterm: bad command line option "-sb"
> >>
> >>usage: xterm [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] []
> >>[] []
> >> [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [-C] [-Sccn]
> >>
>
Thomas Dickey wrote:
On Wed, Jun 30, 2004 at 12:10:18AM +0200, Jeff wrote:
Package: xterm
Version: 4.3.0.dfsg.1-5
Severity: normal
I'm running it from within a vncserver session using xfce4 as
session/window manager. Same version of xterm seems to not exhibit
these problems on another mach
On Wed, Jun 30, 2004 at 12:10:18AM +0200, Jeff wrote:
> Package: xterm
> Version: 4.3.0.dfsg.1-5
> Severity: normal
>
> I'm running it from within a vncserver session using xfce4 as
> session/window manager. Same version of xterm seems to not exhibit
> these problems on another machine running X
Package: xterm
Version: 4.3.0.dfsg.1-5
Severity: normal
I'm running it from within a vncserver session using xfce4 as
session/window manager. Same version of xterm seems to not exhibit
these problems on another machine running X to the screen and
gnome/metacity.
$ xterm -sb
xterm: bad command l
5 matches
Mail list logo
