Bug#350155: marked as done (xterm: crash with non-ascii characters)
Your message dated Sat, 28 Jan 2006 11:41:21 +0200
with message-id <20060128094120.GA9146@jumper.lonesom.pp.fi>
and subject line Bug#350155: xterm: crash with non-ascii characters
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 27 Jan 2006 18:54:29 +0000
>From liiwi@debian.org Fri Jan 27 10:54:29 2006
Return-path: <liiwi@debian.org>
Received: from ip212-226-133-181.adsl.kpnqwest.fi ([212.226.133.181] helo=lonesom.pp.fi)
by spohr.debian.org with esmtp (Exim 4.50)
id 1F2Yjt-000322-DA
for submit@bugs.debian.org; Fri, 27 Jan 2006 10:54:29 -0800
Received: by lonesom.pp.fi (Postfix, from userid 1000)
id CDCCE23CA8; Fri, 27 Jan 2006 20:53:57 +0200 (EET)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Jaakko Niemi <liiwi@debian.org>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: xterm: crash with non-ascii characters
Message-ID: <[🔎] 20060127185357.3951.8037.reportbug@jumper.hurmos.net>
X-Mailer: reportbug 3.18
Date: Fri, 27 Jan 2006 20:53:57 +0200
Delivered-To: submit@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
Package: xterm
Version: 208-3.1
Severity: important
Hello,
With up-to-date sid systems xterm has recently started crashing with
error:
xterm: warning, error event received:
X Error of failed request: BadValue (integer parameter out of range for
operation)
Major opcode of failed request: 77 (X_ImageText16)
Value in failed request: 0x0
Serial number of failed request: 293923
Current serial number in output stream: 293923
Major opcode is always the same. I first noticed this when opening
a message on debian-devel with mutt:
http://lists.debian.org/debian-devel/2006/01/msg01482.html
The problem goes away if I set LC_ALL to "C".
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (990, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
Versions of packages xterm depends on:
ii libc6 2.3.5-12 GNU C Library: Shared libraries an
ii libfontconfig1 2.3.2-1.1 generic font configuration library
ii libfreetype6 2.1.10-1 FreeType 2 font engine, shared lib
ii libice6 6.9.0.dfsg.1-4 Inter-Client Exchange library
ii libncurses5 5.5-1 Shared libraries for terminal hand
ii libsm6 6.9.0.dfsg.1-4 X Window System Session Management
ii libx11-6 6.9.0.dfsg.1-4 X Window System protocol client li
ii libxaw8 6.9.0.dfsg.1-4 X Athena widget set library
ii libxext6 6.9.0.dfsg.1-4 X Window System miscellaneous exte
ii libxft2 2.1.7-1 FreeType-based font drawing librar
ii libxmu6 6.9.0.dfsg.1-4 X Window System miscellaneous util
ii libxrender1 1:0.9.0.2-1 X Rendering Extension client libra
ii libxt6 6.9.0.dfsg.1-4 X Toolkit Intrinsics
ii xlibs-data 6.9.0.dfsg.1-4 X Window System client data
ii zlib1g 1:1.2.3-9 compression library - runtime
Versions of packages xterm recommends:
ii xutils 6.9.0.dfsg.1-4 X Window System utility programs
-- no debconf information
---------------------------------------
Received: (at 350155-close) by bugs.debian.org; 28 Jan 2006 09:41:53 +0000
>From liiwi@lonesom.pp.fi Sat Jan 28 01:41:53 2006
Return-path: <liiwi@lonesom.pp.fi>
Received: from ip212-226-133-181.adsl.kpnqwest.fi ([212.226.133.181] helo=lonesom.pp.fi)
by spohr.debian.org with esmtp (Exim 4.50)
id 1F2maf-0001Aj-4y
for 350155-close@bugs.debian.org; Sat, 28 Jan 2006 01:41:53 -0800
Received: by lonesom.pp.fi (Postfix, from userid 1000)
id 2B0FF23CA8; Sat, 28 Jan 2006 11:41:21 +0200 (EET)
Date: Sat, 28 Jan 2006 11:41:21 +0200
From: Jaakko Niemi <liiwi@lonesom.pp.fi>
To: Thomas Dickey <dickey@radix.net>
Cc: 350155-close@bugs.debian.org
Subject: Re: Bug#350155: xterm: crash with non-ascii characters
Message-ID: <20060128094120.GA9146@jumper.lonesom.pp.fi>
References: <5zH97-2jH-37@gated-at.bofh.it> <[🔎] 20060128002045.GA7531@saltmine.radix.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[🔎] 20060128002045.GA7531@saltmine.radix.net>
User-Agent: Mutt/1.5.11
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
On Fri, 27 Jan 2006, Thomas Dickey wrote:
> On Fri, Jan 27, 2006 at 08:10:17PM +0100, Jaakko Niemi wrote:
> > Package: xterm
> > Version: 208-3.1
> > Severity: important
> >
> > Hello,
> >
> > With up-to-date sid systems xterm has recently started crashing with
> > error:
>
> That sounds like a problem down in the X libraries, though it is hard
> to be sure without being able to reproduce this. Is this something that
> you can trigger by just viewing the same message with mutt, or is it
> while composing (which is harder to reproduce)?
Previously I was able to reproduce this with just about any
application. http://liiwi.idle.fi/foo7.bin is what used to
be a pdf file. Just opening it with less reproduced the
problem, so I kept cutting the file in half till the problem
did not happen any more, and that's the last version which
manifested the issue.
However, I did restart X couple hours ago, and cannot reproduce
the problem anymore, so I'm closing this bug for now. If this
happens again later on, I'll reopen.
--j
Reply to: