I actually saw this again recently -- it was after upgrading the X
server again, but without an intervening X server restart. Should I try
to figure out a reproducible case (install X version foo, start X,
upgrade to version bar, start xterm), or is that an "isn't supposed to
work" case?
--
T
On Tue, Jul 26, 2005 at 07:12:04PM -0400, Andrew Moise wrote:
> On Mon, 2005-07-25 at 05:20 -0400, Thomas Dickey wrote:
> > Is this for "any" file, or for only particular ones?
> > (There was a similar report last year that was apparently in the X
> > libraries).
>
> Er, sorry, my report was a
On Tue, 2005-07-26 at 19:43 -0400, Thomas Dickey wrote:
> On Tue, Jul 26, 2005 at 07:12:04PM -0400, Andrew Moise wrote:
> > On Mon, 2005-07-25 at 05:20 -0400, Thomas Dickey wrote:
> > > Also - is this for the bitmap fonts, or for some TrueType font?
> >
> > I'm not sure what fonts xterm is using
On Mon, 2005-07-25 at 05:20 -0400, Thomas Dickey wrote:
> Is this for "any" file, or for only particular ones?
> (There was a similar report last year that was apparently in the X libraries).
Er, sorry, my report was a little incoherent I guess. Running vim on
no file (just 'vim') crashed the x
On Mon, Jul 25, 2005 at 07:50:09AM +0200, Andrew Moise wrote:
> Package: xterm
> Version: 6.8.2.dfsg.1-4
> Severity: important
...
> Within the uxterm, I'm just typing 'vim' to cause the error. I can
> open some files with vim, but as soon as I switch to insert mode I get
> that crash again. Pl
Package: xterm
Version: 6.8.2.dfsg.1-4
Severity: important
Every time I launch vim from within a uxterm, the xterm exits with
an X error:
[EMAIL PROTECTED] ~]$ uxterm
xterm: warning, error event received:
X Error of failed request: BadValue (integer parameter out of range for
operation)
Ma
6 matches
Mail list logo
