Bug#266701: xterm: Backspace behavior over non-ASCII characters in UTF-8 locale incorrect

2004-08-18 Thread Andrew Moise
On Wed, 2004-08-18 at 16:07, Thomas Dickey wrote:
> On Wed, Aug 18, 2004 at 09:10:13PM +0200, Andrew Moise wrote:
> > Package: xterm
> > Version: 4.3.0.dfsg.1-6
> > Severity: normal
> 
> wrong package.  This is a defect in your shell.

  Yes, quite right -- aterm and my console are silently using a non-UTF8
locale, masking the problem for them.  A glance at the source shows that
zsh is not wide-character aware.  Not only that, there's already a bug
open against zsh (#205651) describing the problem.
  I'm very sorry for the noise and disturbance.  Carry on, sir.





Bug#266336: xterm changes meta-X to meta-8 in en_US.UTF-8 locale

2004-08-18 Thread Thomas Dickey
On Tue, Aug 17, 2004 at 06:00:15PM +0200, Andrew Moise wrote:
> Package: xterm
> Version: 4.3.0.dfsg.1-6
> Severity: normal
> 
>   When I run emacs inside an xterm which was started in the en_US.UTF-8 
> locale, 
> and press alt-X, emacs seems to receive a meta-8 keypress instead of a meta-X
> keypress.  When I start the xterm in the en_US.ISO-8859-1 locale instead, 
> alt-X
> is correctly received as meta-X (as it is when I run emacs in its own X
> window).

Perhaps you have a resource setting confusing things.  I see the proper
symbol (a lowercase "o" with a slash through it).  The eightBitInput and
metaSendsEscape resources related to "meta-X" (sending an escape character
before the code).

However, the reference to 4.3.0.dfsg.1-6 sounds more as if you're running
into problems with modifiers (a library issue).

>   This sounds like it could be related to #135075, BTW.

no (I read that report, and it looks different).

-- 
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net


pgpgn5KPFwWj8.pgp
Description: PGP signature


Bug#266701: xterm: Backspace behavior over non-ASCII characters in UTF-8 locale incorrect

2004-08-18 Thread Thomas Dickey
On Wed, Aug 18, 2004 at 09:10:13PM +0200, Andrew Moise wrote:
> Package: xterm
> Version: 4.3.0.dfsg.1-6
> Severity: normal

wrong package.  This is a defect in your shell.

-- 
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net


pgpFqnEDAQkAT.pgp
Description: PGP signature


Bug#266684: xterm: Segmentation fault on start

2004-08-18 Thread Thomas Dickey
On Wed, Aug 18, 2004 at 08:20:07PM +0200, Anton wrote:
> Package: xterm
> 
> xterm crashes on start in XtToolkitThreadInitialize () from 
> /usr/X11R6/lib/libXt.so.6
> 
> I am using debian sarge installed from debian-installer-rc1

It is likely (given recent reports) that the problem lies in the X libraries.
A walkback would be useful for collating the various reports.

-- 
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net


pgpvqBglcP5GN.pgp
Description: PGP signature


Processed: reassign 264792 to xserver-xfree86, severity of 229850 is important, merging 229850 264792

2004-08-18 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.8.2
> reassign 264792 xserver-xfree86
Bug#264792: read-edid not really used for X config
Bug reassigned from package `installation-reports' to `xserver-xfree86'.

> severity 229850 important
Bug#229850: xserver-xfree86: [debconf] monitor selection methods need to be 
more careful about clobbering autodetected monitor sync ranges
Severity set to `important'.

> merge 229850 264792
Bug#229850: xserver-xfree86: [debconf] monitor selection methods need to be 
more careful about clobbering autodetected monitor sync ranges
Bug#264792: read-edid not really used for X config
Merged 229850 264792.

>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)



Bug#266701: xterm: Backspace behavior over non-ASCII characters in UTF-8 locale incorrect

2004-08-18 Thread Andrew Moise
Package: xterm
Version: 4.3.0.dfsg.1-6
Severity: normal

  In the en_US.UTF-8 locale, inserting any non-ascii character into the command
line and then backspacing over it seems to backspace over bytes rather than
characters.  If I insert "áõã" (either with compose keys or by cut-and-paste),
I can then backspace over the last few characters of my prompt:

[EMAIL PROTECTED] ~]$
[EMAIL PROTECTED] ~]$ áõã
[EMAIL PROTECTED] ~]$ áõ
[EMAIL PROTECTED] ~]$ á
[EMAIL PROTECTED] ~]$
[EMAIL PROTECTED] ~]$
[EMAIL PROTECTED] ~�

  Also, if I type "lsã" and then backspace one time, I get "zsh: command not
found: ls\M-C" when I hit enter.
  This only happens with zsh (not bash), so it could easily be a zsh bug.  It
doesn't happen with aterm or on the console, though, so I've arbitrarily filed
the bug against xterm :-).
  Just like #266336, this happens with both xterm and "xterm -class UXTerm
-title 'uxterm' -u8" (the guts of uxterm) when LANG and LC_ALL are en_US.UTF-8,
and not with either with en_US.ISO-8859-1.

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.7+mppe
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8

Versions of packages xterm depends on:
ii  libc6 2.3.2.ds1-16   GNU C Library: Shared libraries an
ii  libexpat1 1.95.6-8   XML parsing C library - runtime li
ii  libfontconfig12.2.3-1generic font configuration library
ii  libfreetype6  2.1.7-2.2  FreeType 2 font engine, shared lib
ii  libice6   4.3.0.dfsg.1-6 Inter-Client Exchange library
ii  libncurses5   5.4-4  Shared libraries for terminal hand
ii  libsm64.3.0.dfsg.1-6 X Window System Session Management
ii  libxaw7   4.3.0.dfsg.1-6 X Athena widget set library
ii  libxext6  4.3.0.dfsg.1-6 X Window System miscellaneous exte
ii  libxft2   2.1.2-6FreeType-based font drawing librar
ii  libxmu6   4.3.0.dfsg.1-6 X Window System miscellaneous util
ii  libxpm4   4.3.0.dfsg.1-6 X pixmap library
ii  libxrender1   0.8.3-7X Rendering Extension client libra
ii  libxt64.3.0.dfsg.1-6 X Toolkit Intrinsics
ii  xlibs 4.3.0.dfsg.1-6 X Window System client libraries m
ii  xlibs-data4.3.0.dfsg.1-6 X Window System client data

-- no debconf information



Bug#266692: xserver-xfree86: X get sig 11 when loading pcidata module on 3D Rage Pro 215GP (rev 5c) (on Sun Ultra5) with kernels >2.6.7

2004-08-18 Thread Torbjörn Olander
Package: xserver-xfree86
Version: 4.3.0.dfsg.1-6
Severity: important

ig 11 when loading pcidata module on 3D Rage Pro 215GP (rev 5c) (on Sun
Ultra5) with kenels >2.6.7


-- Package-specific info:

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: sparc (sparc64)
Kernel: Linux 2.6.8-rc1
Locale: LANG=en_US, LC_CTYPE=sv_SE.ISO-8859-1

Versions of packages xserver-xfree86 depends on:
ii  debconf [debconf-2.0] 1.4.30 Debian configuration management sy
ii  libc6 2.3.2.ds1-15   GNU C Library: Shared libraries an
ii  xserver-common4.3.0.dfsg.1-6 files and utilities common to all 
ii  zlib1g1:1.2.1.1-5compression library - runtime

-- debconf information excluded



Bug#266684: xterm: Segmentation fault on start

2004-08-18 Thread Anton

Package: xterm

xterm crashes on start in XtToolkitThreadInitialize () from 
/usr/X11R6/lib/libXt.so.6


I am using debian sarge installed from debian-installer-rc1




X Strike Force XFree86 SVN commit: r1736 - trunk/debian

2004-08-18 Thread X Strike Force SVN Repository Admin
Author: fabbione
Date: 2004-08-18 07:16:39 -0500 (Wed, 18 Aug 2004)
New Revision: 1736

Modified:
   trunk/debian/CHANGESETS
   trunk/debian/changelog
Log:
Fix typo.


Modified: trunk/debian/CHANGESETS
===
--- trunk/debian/CHANGESETS 2004-08-13 06:43:54 UTC (rev 1735)
+++ trunk/debian/CHANGESETS 2004-08-18 12:16:39 UTC (rev 1736)
@@ -14,7 +14,7 @@
 
 Miscellaneous cosmetic fixes.
 1607, 1608, 1624, 1626, 1627, 1636, 1651, 1654, 1663, 1664, 1675, 1685,
-1690, 1713, 1715, 1716, 1718
+1690, 1713, 1715, 1716, 1718, 1736
 
 Grab latest version of XTerm (#191) from Thomas Dickey's website.
 1609

Modified: trunk/debian/changelog
===
--- trunk/debian/changelog  2004-08-13 06:43:54 UTC (rev 1735)
+++ trunk/debian/changelog  2004-08-18 12:16:39 UTC (rev 1736)
@@ -147,7 +147,7 @@
 (Closes: #259996)
 
   * Update hurd-i386 support.
-+ Update gnu.cf to delcare platform support for groff, libpng, and PAM
++ Update gnu.cf to declare platform support for groff, libpng, and PAM
   libraries in parity with Linux; also specify correct path to cpp
   executable.
 + Tell XTerm's Imakefile that openpty() needs -lutil on GNUArchitecture



Bug#266568: AT Keyboard Broken Under X

2004-08-18 Thread Harry Nicholls
Package: xserver-xfree86
Version: 4.3.0.dfsg.1-6

I have a PS/2 keyboard connected to my PC through a PS/2 to AT
adaptor. Until last night, it worked perfectly under Xfree86 on Sid
(i386). After updating to the latest packages it doesn't respond.
Everything is fine with a console login, but for some reason X just
doesn't want to recognise it. The only possibly notable line in the
log was "Generic Keyboard using legacy driver" or something along
those lines.
It may also be of note that an Apple USB keyboard works, but doesn't
work when plugged in at the same time as the PS/2 keyboard. The
problem can be replicated with kernels 2.4.26-k6 and 2.4.27-k6.



Bug#266525: xfree86-common: ssh-agent is no longer started via Xsession

2004-08-18 Thread Patrick Cornelissen
Package: xfree86-common
Version: 4.3.0.dfsg.1-6
Severity: normal

One of the last updates (I think it worked a few days ago) has broken the 
automatic start of ssh-agent.
The option is still set and I have touched no configfile except the 
XServerconfig.


-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (101, 'testing'), (99, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.26-1-k7
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED]

Versions of packages xfree86-common depends on:
ii  debconf   1.4.30 Debian configuration management sy
ii  debianutils   2.8.4  Miscellaneous utilities specific t

-- debconf information:
  xfree86-common/experimental_packages:



Re: Bug#255439: Bug#255689: Bug#255439: d-i report

2004-08-18 Thread Sven Luther
On Tue, Aug 17, 2004 at 07:31:23PM -0700, Daniel Stone wrote:
> On Tue, Jul 13, 2004 at 11:08:58AM -0500, Branden Robinson wrote:
> > There's the problem.  "radeon" is not a legal value.
> > 
> > Use "ati" instead.
> > 
> > Do not use "atimisc", "r128", or "radeon".
> 
> 'radeon' should be perfectly legal, and just sedded to 'ati' in the
> XFree86 scripts if they really want to enforce this whole 'only ever use
> the wrapper' thingo.

Problem seems to be that the ati wrapper has some troubles for some of the
Radoen 9200 cards, and doesn't load the radeon module appropriately in these
cases. I will recheck with both my 5961 and 5964 cards again and confirm this.

Friendly,

Sven Luther