Your message dated Mon, 19 Mar 2007 04:44:56 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#413945: rxvt-unicode: crashes on U+FFFD; sid version
lesser affected
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)
--- Begin Message ---
Package: rxvt-unicode
Version: 5.3-1
Severity: normal
Hi,
sarge rxvt-unicode crashes when U+FFFD is to be displayed.
(Apparently this is the substitution character for invalid input;
e.g., for plain latin1 non-ascii chars in UTF-8 mode. Altough urxvt
seems to automatically up-convert at least some of them, other programs
like GNU screen run inside may substitute them before they reach urxvt.)
Before unexpected termination, sarge urxvt prints:
| X Error of failed request: BadName (named color or font does not exist)
| Major opcode of failed request: 75 (X_PolyText16)
| Serial number of failed request: 1197
| Current serial number in output stream: 1218
| Xlib: unexpected async reply (sequence 0x4c2)!
The sid version (7.9-2) doesn't crash, but doesn't render
a character either (xterm does, as a dashed hollow square)
and outputs (essentially the same):
| urxvt: An X Error occured, trying to continue after report.
| urxvt: X Error of failed request: BadName (named color or font does not
exist)
| urxvt: Major opcode of failed request: 75
| urxvt: (which is X_PolyText16)
| urxvt: Serial number of failed request: 3463
The error does _not_ occur when overriding the font list as suggested
in #294582. (Then the character is rendered, as ~"(?)".) For example:
| $ LANG=de_DE.UTF-8 urxvt -name noresources -fn 10x20
| $ LANG=de_DE.UTF-8 urxvt -name noresources -fn 8x13
| $ LANG=de_DE.UTF-8 urxvt -name noresources -fn terminus-16
| urxvt: An X Error occured, trying to continue after report.
| [...]
My usual fontlist is: "terminus-16,xft:Kochi Gothic:antialias=false"
As far as I know, urxvt also appends a built-in list of known-to-work
fonts, so apparently the character is missing in all those fonts.
However, it would be nice if urxvt could handle this more gracefully,
i.e., without printing error messages (or more specific ones?) and by
rendering a substitution character, possibly built-in. (?)
The offending character may be produced in the following way:
$ echo '�' | recode html..utf8
Composing the character via urxvt's Ctrl-Shift-{F,F,F,D} also works and
immediately leads to the above results, even before releasing the
modifier keys. (It already tries rendering it in the preview window.)
Regards, Fabian
-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.18-4-686
Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Versions of packages rxvt-unicode depends on:
ii base-passwd 3.5.9 Debian base system master password
ii libc6 2.3.2.ds1-22sarge5 GNU C Library: Shared libraries an
ii libfontconfig1 2.3.1-2 generic font configuration library
ii libfreetype6 2.1.7-6 FreeType 2 font engine, shared lib
ii libgcc1 1:3.4.3-13sarge1 GCC support library
ii libx11-6 4.3.0.dfsg.1-14sarge3 X Window System protocol client li
ii libxft2 2.1.7-1 FreeType-based font drawing librar
ii libxrender1 0.8.3-7 X Rendering Extension client libra
ii xlibs 6.9.0.dfsg.1-6~bpo.4 X Window System client libraries m
ii zlib1g 1:1.2.2-4.sarge.2 compression library - runtime
-- no debconf information
--- End Message ---
--- Begin Message ---
Package: rxvt-unicode
Version: 7.9-2
Hi,
I'd been using a self-made backport[1] of 7.9-2 to sarge for some time
now, which fixed the crashes, but introduced spurious segfaults or hangs
(100% CPU) on exit, and interestingly rendered a glyph for U+FFFD.
I attributed this to a seemingly changed dependency[2] due to my unclean
build environment (additional dependency on libfreetype6, but sid 7.9-2
seems to use that, too, only through other formal dependencies).
Strangely enough I can't reproduce any aspect of the bug any longer.
Neither with 5.3-1 nor 7.9-2*. Neither in a (mostly) sarge system (on a
local X server), nor my main system (backports.org Xorg), nor the
previous sid chroot there, nor a fresh sid chroot there (the further got
a lot of X packages installed lately to be able to run an own X server).
Neither with my default X resources, nor after "xrdb -remove".
I'm at a complete loss of explanation for this. The nearest I could
think of would be some configuration/font/... issues on my main system,
that have magically been fixed by an installation of some other font
package or anything like that. There have been no APT upgrades in the
respective time frame that seem even remotely related, according to
X-like packages' changelogs.
Therefore I've installed sarge's 5.3-1 again on my main system and it
seems to work fine. I'm closing this bug with 7.9-2 as version, as when
the symptoms did occur, 5.3-1 simply crashed but 7.9-2 continued to run,
after logging an error message. This seems to be more sane for whatever
the non-urxvt reasons for the problem might have been.
Regards, Fabian
[1] (Build logs etc. in the same directory.)
http://canvon.dyndns.org/deb/urxvt/rxvt-unicode_7.9-2~silencer.1_i386.deb
[2]
http://canvon.dyndns.org/deb/urxvt/rxvt-unicode_7.9-2~silencer.1.debdiff
--
Fabian "zzz" Pietsch - http://zzz.arara.de/
--- End Message ---