- Original Message -
| From: "Vincent Lefevre"
| To: "Thomas Dickey" , 916349-qu...@bugs.debian.org
| Cc: 916...@bugs.debian.org
| Sent: Thursday, December 13, 2018 7:20:00 PM
| Subject: Bug#916349: xterm: X error (BadLength) with GNU screen
| Control: retitle -1 xterm: X error
Processing commands for cont...@bugs.debian.org:
> forwarded 633849 https://gitlab.freedesktop.org/xorg/xserver/issues/266
Bug #633849 [xserver-xorg] xserver-xorg: XKB settings lost after suspend
(hibernate) / resume or USB keyboard plugged in
Changed Bug forwarded-to-address to
Processing commands for cont...@bugs.debian.org:
> forwarded 677173 https://gitlab.freedesktop.org/xorg/xserver/issues/303
Bug #677173 [xserver-xorg-input-evdev] after some time, some keyboard no longer
works in the current X session
Bug #677242 [xserver-xorg-input-evdev] virtualbox-guest-x11:
Control: retitle -1 xterm: X error (BadLength) when trying to display some
glyphs
On 2018-12-13 18:35:43 -0500, Thomas Dickey wrote:
> On Thu, Dec 13, 2018 at 06:25:42PM -0500, Thomas Dickey wrote:
> > On Thu, Dec 13, 2018 at 02:11:28PM +0100, Vincent Lefevre wrote:
> > > Package: xterm
> > >
Processing control commands:
> retitle -1 xterm: X error (BadLength) when trying to display some glyphs
Bug #916349 [xterm] xterm: X error (BadLength) when trying to display some
glyphs
Ignoring request to change the title of bug#916349 to the same title
--
916349:
Processing control commands:
> retitle -1 xterm: X error (BadLength) when trying to display some glyphs
Bug #916349 [xterm] xterm: X error (BadLength) with GNU screen
Changed Bug title to 'xterm: X error (BadLength) when trying to display some
glyphs' from 'xterm: X error (BadLength) with GNU
On Thu, Dec 13, 2018 at 06:35:43PM -0500, Thomas Dickey wrote:
> On Thu, Dec 13, 2018 at 06:25:42PM -0500, Thomas Dickey wrote:
> > On Thu, Dec 13, 2018 at 02:11:28PM +0100, Vincent Lefevre wrote:
> > > Package: xterm
> > > Version: 338-1
> > > Severity: grave
>
> make it normal (and read the
On Thu, Dec 13, 2018 at 06:25:42PM -0500, Thomas Dickey wrote:
> On Thu, Dec 13, 2018 at 02:11:28PM +0100, Vincent Lefevre wrote:
> > Package: xterm
> > Version: 338-1
> > Severity: grave
make it normal (and read the guidelines...)
> 1281 openat(AT_FDCWD,
On Thu, Dec 13, 2018 at 02:11:28PM +0100, Vincent Lefevre wrote:
> Package: xterm
> Version: 338-1
> Severity: grave
> Justification: renders package unusable
>
> After upgrading xterm to 338-1, I get X errors when using GNU screen:
>
> zira% xterm -e screen -r
> /usr/bin/xterm: warning, error
On Wed, 12 Dec 2018, Sven Joachim wrote:
> xterm (338-1) unstable; urgency=medium
> .
>* New upstream release.
[…]
> - Revert the change which prevented concurrent ownership of different
>selection targets, and instead modify selection storage so that
>different
On 2018-12-13 14:51:26 +0100, Vincent Lefevre wrote:
> After downgrading xterm to 337-1, then reupgrading to 338-1, I can
> no longer reproduce the bug (for the moment).
The error occurs again. So, it seems to occur only after some time.
I don't know what triggers it.
--
Vincent Lefèvre - Web:
On 2018-12-13 14:17:48 +0100, Julien Cristau wrote:
> Please share your xterm config.
Here's the "appres XTerm" output:
*tek4014*fontLarge: 9x15
*tek4014*font2: 8x13
*tek4014*font3: 6x13
*tek4014*fontSmall: 6x10
*MenuButton*borderWidth:0
*Scrollbar.thickness: 8
On 12/13/18 2:11 PM, Vincent Lefevre wrote:
> Package: xterm
> Version: 338-1
> Severity: grave
> Justification: renders package unusable
>
> After upgrading xterm to 338-1, I get X errors when using GNU screen:
>
> zira% xterm -e screen -r
> /usr/bin/xterm: warning, error event received:
> X
Package: xterm
Version: 338-1
Severity: grave
Justification: renders package unusable
After upgrading xterm to 338-1, I get X errors when using GNU screen:
zira% xterm -e screen -r
/usr/bin/xterm: warning, error event received:
X Error of failed request: BadLength (poly request too large or
14 matches
Mail list logo
