Bug#541089: marked as done (xterm: bold color attribute now displaying as black by default)
Your message dated Sat, 22 Aug 2009 22:47:32 + with message-id e1mezmy-0004jw...@ries.debian.org and subject line Bug#541089: fixed in xterm 246-1 has caused the Debian Bug report #541089, regarding xterm: bold color attribute now displaying as black by default 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 541089: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=541089 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: xterm Version: 244-1 Severity: minor With yesterday's update of xterm, bold attributes are displaying in the color black. I'm assuming '+bdc' got set by default somehow instead of '-bdc'? Anyway, since a lot of people probably use black as their default background color, this might cause a lot of problems. Not only did portions of my prompt string disappear in my shell (minor issue), but man pages are pretty much unreadable. Simply setting the resource (or passing the '-bdc' option to my xterm) fixes the problem. I'm not sure if this is something you need to address, but I'm submitting this report for reference sake at the very least. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (700, 'unstable'), (600, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.30-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages xterm depends on: ii libc6 2.9-24 GNU C Library: Shared libraries ii libfontconfig12.6.0-4generic font configuration library ii libice6 2:1.0.5-1 X11 Inter-Client Exchange library ii libncurses5 5.7+20090803-1 shared libraries for terminal hand ii libx11-6 2:1.2.2-1 X11 client-side library ii libxaw7 2:1.0.6-1 X11 Athena Widget library ii libxft2 2.1.13-3 FreeType-based font drawing librar ii libxmu6 2:1.0.4-2 X11 miscellaneous utility library ii libxt61:1.0.5-3 X11 toolkit intrinsics library ii xbitmaps 1.0.1-2Base X bitmaps Versions of packages xterm recommends: ii x11-utils 7.4+1 X11 utilities ii xutils1:7.4+3X Window System utility programs m Versions of packages xterm suggests: pn xfonts-cyrillic none (no description available) -- no debconf information ---End Message--- ---BeginMessage--- Source: xterm Source-Version: 246-1 We believe that the bug you reported is fixed in the latest version of xterm, which is due to be installed in the Debian FTP archive: xterm_246-1.diff.gz to pool/main/x/xterm/xterm_246-1.diff.gz xterm_246-1.dsc to pool/main/x/xterm/xterm_246-1.dsc xterm_246-1_amd64.deb to pool/main/x/xterm/xterm_246-1_amd64.deb xterm_246.orig.tar.gz to pool/main/x/xterm/xterm_246.orig.tar.gz A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 541...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Julien Cristau jcris...@debian.org (supplier of updated xterm package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 23 Aug 2009 00:35:21 +0200 Source: xterm Binary: xterm Architecture: source amd64 Version: 246-1 Distribution: unstable Urgency: low Maintainer: Debian X Strike Force debian-x@lists.debian.org Changed-By: Julien Cristau jcris...@debian.org Description: xterm - X terminal emulator Closes: 531597 541089 541160 541236 541603 Changes: xterm (246-1) unstable; urgency=low . * New upstream release + interaction between allowSendEvents and the various allowXXXOps resources clarified in manpage (closes: #531597) + remove obsolete logic for saving/restoring wrapping flags, which did not work on 64-bit platform. Wrapping flags (stored in the line-index) are now copied with line-data (closes: #541160) + modify comments in app-defaults files to avoid problem with C preprocessor used by xrdb (closes: #541603) + restore special case in makeColorPair needed
Bug#541089: marked as done (xterm: bold color attribute now displaying as black by default)
Your message dated Tue, 11 Aug 2009 19:53:46 +0200 with message-id 20090811175346.go23...@patate.is-a-geek.org and subject line Re: Bug#541089: xterm: bold color attribute now displaying as black by default has caused the Debian Bug report #541089, regarding xterm: bold color attribute now displaying as black by default 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 541089: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=541089 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: xterm Version: 244-1 Severity: minor With yesterday's update of xterm, bold attributes are displaying in the color black. I'm assuming '+bdc' got set by default somehow instead of '-bdc'? Anyway, since a lot of people probably use black as their default background color, this might cause a lot of problems. Not only did portions of my prompt string disappear in my shell (minor issue), but man pages are pretty much unreadable. Simply setting the resource (or passing the '-bdc' option to my xterm) fixes the problem. I'm not sure if this is something you need to address, but I'm submitting this report for reference sake at the very least. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (700, 'unstable'), (600, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.30-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages xterm depends on: ii libc6 2.9-24 GNU C Library: Shared libraries ii libfontconfig12.6.0-4generic font configuration library ii libice6 2:1.0.5-1 X11 Inter-Client Exchange library ii libncurses5 5.7+20090803-1 shared libraries for terminal hand ii libx11-6 2:1.2.2-1 X11 client-side library ii libxaw7 2:1.0.6-1 X11 Athena Widget library ii libxft2 2.1.13-3 FreeType-based font drawing librar ii libxmu6 2:1.0.4-2 X11 miscellaneous utility library ii libxt61:1.0.5-3 X11 toolkit intrinsics library ii xbitmaps 1.0.1-2Base X bitmaps Versions of packages xterm recommends: ii x11-utils 7.4+1 X11 utilities ii xutils1:7.4+3X Window System utility programs m Versions of packages xterm suggests: pn xfonts-cyrillic none (no description available) -- no debconf information ---End Message--- ---BeginMessage--- On Tue, Aug 11, 2009 at 12:41:18 -0500, Mark Nipper wrote: On 11 Aug 2009, Julien Cristau wrote: I can't reproduce this. manpages are readable for me with the default settings, and xterm +bdc makes bold text disappear. Anything particular in your setup? You may not have gotten my update to that bug report. I Right, I got it just after replying to the initial report :) think you inadvertently fixed something with this most recent release. The fact that colorBDMode was enabled was actually my own fault (I had it in my .Xresources). But I've had it in my .Xresources for years now, and this only just now became an issue. So disabling colorBDMode fixed my problem. And regarding this issue, xterm is actually working as documented now (which apparently it wasn't before). So thanks! :) Closing the bug per submitter, thanks! Cheers, Julien ---End Message---
