Bug#233883: xterm and gnome-session, still

2004-05-29 Thread Wolfgang Pfeiffer
On Fri, 2004-05-28 at 11:40, Branden Robinson wrote:
> On Tue, May 25, 2004 at 04:48:49AM -0400, Thomas Dickey wrote:
> > On Tue, May 25, 2004 at 08:56:11AM +0200, Josselin Mouette wrote:
> > > tag 233883 fixed-upstream
> > > tag 233883 - help
> > > reassign 233883 xterm
> > > thanks
> > > 
> > > Le dim 09/05/2004  20:10, [EMAIL PROTECTED] a crit :
> > > >Debian Bug report logs - #233883
> > > > >   gnome-session: very slow to shut down (checkpoint?) xterm 
> > > > > windows
> > > > someone sent me a patch for xterm which seems to fix this problem (it'll
> > > > be in xterm patch #188).
> > > 
> > > Thanks for the fix.
> > > 
> > > XSF, could you please update 000_stolen_from_author_xterm.diff to
> > > version #188 or #189? That should do the trick.
> > 
> > my impression is that Branden's intention is to update to current xterm
> > source at some time (soon).  At the moment, #189 looks stable (no new
> > bugs noticed past that point - the fixes I'm working on now seem to be
> > as in the session code: present in older versions).
> 
> An update to XTerm #190 is planned, but the actual scheduling is up to
> Fabio Massimo di Nitto, the package release manager.

Some hours ago I found some xterm source: #190, as it seems, on (IIRC)


I compiled it on ppc/Titanium4. Played with it a bit this evening. No
problems, as it seems, when logging out of Gnome any more. Except the
very first time after the first compile. But after this first "accident"
(might be related to other Gnome stuff), logging in and out of Gnome,
without the need to close down xterms manually before the logout, worked
like a charm.

To make sure you know what I'm talking about, here's an excerpt from 
version.h 
from the source directory of the xterm above

---
/* $XTermId: version.h,v 1.221 2004/05/26 01:19:55 tom Exp $ */
/* $XFree86: xc/programs/xterm/version.h,v 3.101 2004/05/26 01:19:55
dickey Exp $ */

/*
 * These definitions are used to build the string that's printed in
response to
 * "xterm -version", or embedded in "xterm -help".  It usually indicates
the
 * version of X to which this version of xterm has been built.  The
number in
 * parentheses is my patch number (T.Dickey).
 */
#define XTERM_PATCH   190



Official Debian ppc/unstable doesn't have #190, yet, IINM.

Thanks to everyone involved. You'll hear from me if there are xterm
issues you might want to know about.

And if you please let me know in case you want to know more.

Nice weekend to everyone, and again:
Thanks a lot for your work. I'm glad xterm is running again without
problems here, as it seems. 

Best Regards
Wolfgang
-- 
Profile, links: http://profiles.yahoo.com/wolfgangpfeiffer





Bug#251307: xserver-xfree86: X crashes when using Xine

2004-05-29 Thread Rob Bochan
On Sat, 29 May 2004 04:16:26 -0500, Branden Robinson wrote:

>Please see the message I sent to the bug submitter, and supply this bug
>with the same information I requested of him:
>
>http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=251307

Unfortunately, I didn't get your reply until after upgrades had gone through 
this evening (to xserver-xfree86_4.3.0.dfsg.1-4), however, the problem 
persists even with the most recent upgrade.

$ objdump --dynamic-syms /usr/X11R6/bin/XFree86 | grep xf86XVCopyYUV12ToPacked
080aefa0 gDF .text  0151  Basexf86XVCopyYUV12ToPacked

If there's any more info I can provide, let me know.

-- 
Rob Bochan




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

2004-05-29 Thread X Strike Force SVN Repository Admin
Author: branden
Date: 2004-05-29 18:48:30 -0500 (Sat, 29 May 2004)
New Revision: 1479

Modified:
   trunk/debian/TODO
Log:
Add item.

Fabio, we didn't have a chance to discuss this one, so please move it down
to the unscheduled list if you disagree with it.


Modified: trunk/debian/TODO
===
--- trunk/debian/TODO   2004-05-29 23:21:43 UTC (rev 1478)
+++ trunk/debian/TODO   2004-05-29 23:48:30 UTC (rev 1479)
@@ -29,6 +29,10 @@
 * #245246: Apply hot pokers to Ben Collins until we extract a working patch for
   XAA and Render support for the sunffb driver.  Mmmm, burning manflesh...
 * Apply "other half" of SPARC 64-bit avoidance patch to Mesa; see #241331.
+* #251307: xserver-xfree86: [ati/atimisc] XVideo apps crash X server; 
complaints
+  of unresolved symbol xf86XVCopyYUV12ToPacked on 3D Rage IIC AGP rev 122
+  Michel Dänzer reports that this is due to failure to export that symbol
+  via SYMFUNC() in xc/programs/Xserver/hw/xfree86/loader/xf86sym.c.
 
 4.3.0.dfsg.1-6
 --



Bug#251534: marked as done (xserver-xfree86_4.3.0.dfsg.1-3_i386.deb fails to install.)

2004-05-29 Thread Debian Bug Tracking System
Your message dated Sat, 29 May 2004 18:24:31 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#251534: xserver-xfree86_4.3.0.dfsg.1-3_i386.deb fails to 
install.
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; 28 May 2004 22:53:18 +
>From [EMAIL PROTECTED] Fri May 28 15:53:18 2004
Return-path: <[EMAIL PROTECTED]>
Received: from smtp10.wanadoo.fr (mwinf1001.wanadoo.fr) [193.252.22.21] 
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1BTqE1-0004VM-00; Fri, 28 May 2004 15:53:17 -0700
Received: from camus.celestiadust (ca-bordeaux-32-41.w80-8.abo.wanadoo.fr 
[80.8.202.41])
by mwinf1001.wanadoo.fr (SMTP Server) with ESMTP
id 254DA1C0004A; Sat, 29 May 2004 00:52:44 +0200 (CEST)
Received: by camus.celestiadust (Postfix, from userid 1000)
id 98EFE84C002; Sat, 29 May 2004 00:55:11 +0200 (CEST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: eLShaman <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: xserver-xfree86_4.3.0.dfsg.1-3_i386.deb fails to install.
X-Mailer: reportbug 2.60
Date: Sat, 29 May 2004 00:55:10 +0200
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 

Package: xserver-xfree86
Version: 4.3.0.dfsg.1-2
Severity: normal
Tags: sid


Hello,


xserver-xfree86_4.3.0.dfsg.1-3_i386.deb fails to install.
When I try to install it whith "dpkg -i" it never finishes, I have to 
kill dpkg.



I have lauched the installation with strace, this is the result:

camus:/home/elshaman/# strace dpkg -i 
xserver-xfree86_4.3.0.dfsg.1-3_i386.deb
[...]
rename("/var/lib/dpkg/updates/tmp.i", "/var/lib/dpkg/updates/0002") = 0
open("/var/lib/dpkg/updates/tmp.i", 
O_WRONLY|O_CREAT|O_TRUNC|O_LARGEFILE, 0666) = 4
fcntl64(4, F_GETFD) = 0
fcntl64(4, F_SETFD, FD_CLOEXEC) = 0
fstat64(4, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 
0) = 0x4048c000
write(4, "#padding\n#padding\n#padding\n#padd"..., 4096) = 4096
write(4, "padding\n#padding\n#padding\n#paddi"..., 512) = 512
_llseek(4, 0, [0], SEEK_SET)= 0
stat64("/var/lib/dpkg/tmp.ci/preinst", {st_mode=S_IFREG|0755, 
st_size=26210, ...}) = 0
clone(child_stack=0, 
flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, 
child_tidptr=0x401692e8) = 15798
rt_sigaction(SIGQUIT, {SIG_IGN}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGINT, {SIG_IGN}, {SIG_DFL}, 8) = 0
waitpid(15798,


Here, dpkg is waiting and I have to kill it.


After, I have extract the preinst file and I have launched it, it 
seems that the line which breaks the script is:
. /usr/share/debconf/confmodule   (line ~31)
If I comment this line, the script finishes.


So, I think that is a debconf problem.




Thanks,

Lolo.


-- Package-specific info:
Contents of /var/lib/xfree86/X.roster:
xserver-xfree86

/etc/X11/X target unchanged from checksum in /var/lib/xfree86/X.md5sum.

X server symlink status:
lrwxrwxrwx1 root root   20 2003-10-04 21:14 /etc/X11/X -> 
/usr/bin/X11/XFree86
-rwxr-xr-x1 root root  1745132 2004-05-25 23:30 /usr/bin/X11/XFree86

Contents of /var/lib/xfree86/XF86Config-4.roster:
xserver-xfree86

VGA-compatible devices on PCI bus:
:01:00.0 VGA compatible controller: nVidia Corporation NV10 [GeForce 256 
SDR] (rev 10)
:01:00.0 Class 0300: 10de:0100 (rev 10)

/etc/X11/XF86Config-4 does not match checksum in 
/var/lib/xfree86/XF86Config-4.md5sum.

XFree86 X server configuration file status:
-rw-r--r--1 root root 3084 2004-04-12 17:40 
/etc/X11/XF86Config-4

Contents of /etc/X11/XF86Config-4:
# XF86Config-4 (XFree86 X server configuration file) generated by dexconf, the
# Debian X Configuration tool, using values from the debconf database.
#
# Edit this file with caution, and see the XF86Config-4 manual page.
# (Type "man XF86Config-4" at the shell prompt.)
#
# This file is automatically updated on xserver-xfree86 package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xfree86
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, ru

Processed: tagging 251509

2004-05-29 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.7.95.1
>  # fixed in Debian X Strike Force XFree86 repository; to view, run "svn diff 
> -r 1477:1478 svn://necrotic.deadbeast.net/xfree86"
> tags 251509 + pending
Bug#251509: file:/home/markos/pics/Conferences[INTL:el] Please include updated 
Greek debconf translation
Tags were: l10n patch
Tags added: pending

>
End of message, stopping processing here.

Please contact me if you need assistance.

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



Re: Problem during xserver-xfree86_4.3.0.dfsg.1-3 installation

2004-05-29 Thread Branden Robinson
On Sat, May 29, 2004 at 12:55:51AM +0200, jjluza wrote:
> It seems there is a problem with the preinst script of this package.
> I get it from incoming.debian.org
> When I try to install it, it freezes like that :
> 
> # dpkg -i xserver-xfree86_4.3.0.dfsg.1-3_i386.deb
> (Lecture de la base de données... 151846 fichiers et répertoires déjà 
> installés.)
> Préparation du remplacement de xserver-xfree86 4.3.0.dfsg.1-2 (en utilisant 
> xserver-xfree86_4.3.0.dfsg.1-3_i386.deb) ...
> 
> If I run "ps aux", I get these lines :
> 
> root  5464 30.0  7.1 38596 37044 pts/7   S+   00:46   0:00 dpkg -i 
> xserver-xfree86_4.3.0.dfsg.1-3_i386.deb
> root  5483 39.0  1.8 11288 9492 pts/7S+   00:46   0:00 /usr/bin/perl 
> -w /usr/share/debconf/frontend /var/lib/dpkg/tmp.ci/preinst u
> root  5489  0.0  0.2  2996 1544 pts/7S+   00:46   
> 0:00 /bin/sh /var/lib/dpkg/tmp.ci/config configure 4.3.0.dfsg.1-2
> root  5518  0.0  0.1  2060  768 pts/7S+   00:46   0:00 grep -q system 
> type.*:.*SGI Indigo2
> 
> I can't tell more, but ask me if you need more information.

This was fixed in 4.3.0.dfsg.1-4.

  xfree86 (4.3.0.dfsg.1-4) unstable; urgency=medium

* The "thanks for the 'testing'" release.

Changes by Branden Robinson:

* Fix hang in xserver-xfree86 config script by telling grep what file to
  search.

   -- Branden Robinson <[EMAIL PROTECTED]>  Fri, 28 May 2004 21:49:53 -0500

I apologize for the inconvenience.

-- 
G. Branden Robinson| If you're handsome, it's flirting.
Debian GNU/Linux   | If you're a troll, it's sexual
[EMAIL PROTECTED] | harassment.
http://people.debian.org/~branden/ | -- George Carlin


signature.asc
Description: Digital signature


Bug#251037: Strange xdmcp behavior, maybe a trojan horse?

2004-05-29 Thread Bartłomiej Ochman

Branden Robinson wrote:
Hello,


That's probably a bug.  It may have something to do with:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1985

*That* bug has been open for over 8 years. :(

[and from another mail]:

> Does it sound like this one?:
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=4757

First thing first, in my opinion xdm works perfectly well in all those 
situations. I think I understand now *why* it behaves this way. And what's 
worst, it can be assumed as the right behavior. :-(


As far as I can understand the situation, the problem is caused by Xserver 
and RFC1122, where "weak end host" is defined. During connection setup, 
Xserver sends its IP address in a XDMCP packet to a xdm process on a remote 
host. But which IP should be sent by a multihomed Xserver? The logic says, 
the IP of the interface which leads to a remote xdm. But in a consequence of 
RFC1122, all host's IPs are local on every interface (for incomming packets, 
of course). One can easily check it's true, just traceroute to a box with 
more than one interface:


[EMAIL PROTECTED]:~$ traceroute 192.168.1.254
traceroute to 192.168.1.254 (192.168.1.254), 30 hops max, 38 byte packets
 1  chlew-wifi.home.fback.net (192.168.1.254)  2.649 ms  1.878 ms  1.961 ms

[EMAIL PROTECTED]:~$ traceroute 192.168.0.1
traceroute to 192.168.0.1 (192.168.0.1), 30 hops max, 38 byte packets
 1  192.168.0.1 (192.168.0.1)  2.221 ms  2.474 ms  1.974 ms

[EMAIL PROTECTED]:~$ traceroute chlew
traceroute to chlew.home.fback.net (80.53.236.154), 30 hops max, 38 byte packets
 1  chlew.home.fback.net (80.53.236.154)  2.232 ms  1.744 ms  2.751 ms

I can even add some public IP to a chlew's loopback interface and:

chlew:~# ifconfig lo:1 204.255.235.118 netmask 255.255.255.255 broadcast 
204.255.235.118


[EMAIL PROTECTED]:~$ traceroute 204.255.235.118
traceroute to 204.255.235.118 (204.255.235.118), 30 hops max, 38 byte packets
 1  204.255.235.118 (204.255.235.118)  2.216 ms  2.327 ms  2.360 ms

So Xserver takes all the local IPs and sends them to a remote xdm process, 
allowing him to choose the best. When it's in the same subnet, it will 
choose local address (and that's why it worked for me within the same 
subnet), but what when all IPs are non-local? It will take the first one and 
will try to connect to it.


Everything is OK according to RFCs. But on the other hand, loopback is only 
a local interface, which never sends packets to a network. So in my opinion, 
Xserver should never advertise its loopbacks. As far as I checked, it 
doesn't send 127.0.0.1, except the situation when connecting to it 
explicitely. I think it should never send *any* IP assigned to a loopback 
[sub]interface(s). Unfortunately, I'm not sure there's easy way to check, if 
an address is assigned to a loopback.


Sending loopback would make sense only in a situation, when the Xserver is 
running on a multihomed box, with 2 (or more) interfaces which are available 
through different paths. But who runs Xserver on a BGP router? ;-)


I guess, that a scenario in #4757 was as follow:
First interface up was eth0, possibly with a private IP. Second interface up 
was ppp0 (so Xserver advertised private IP as the first one, and public as 
the second). It caused remote xdm connects to an unavailable IP.


Would configuring interfaces in some explicit order solve my (and all other) 
problems? I'll try this next week.


Regards,
BO

PS. Sorry for my english. :(




X Strike Force XFree86 SVN commit: r1478 - in trunk/debian: . po

2004-05-29 Thread X Strike Force SVN Repository Admin
Author: branden
Date: 2004-05-29 18:21:43 -0500 (Sat, 29 May 2004)
New Revision: 1478

Modified:
   trunk/debian/CHANGESETS
   trunk/debian/changelog
   trunk/debian/po/el.po
Log:
Update Greek debconf template translations (thanks, Konstantinos
Margaritis).  (Closes: #251509)


Modified: trunk/debian/CHANGESETS
===
--- trunk/debian/CHANGESETS 2004-05-29 23:19:32 UTC (rev 1477)
+++ trunk/debian/CHANGESETS 2004-05-29 23:21:43 UTC (rev 1478)
@@ -12,4 +12,8 @@
 debconf template changes in 4.3.0.dfsg.1-3.
 1475
 
+Update Greek debconf template translations (thanks, Konstantinos
+Margaritis).  (Closes: #251509)
+1478
+
 vim:set ai et sts=4 sw=4 tw=80:

Modified: trunk/debian/changelog
===
--- trunk/debian/changelog  2004-05-29 23:19:32 UTC (rev 1477)
+++ trunk/debian/changelog  2004-05-29 23:21:43 UTC (rev 1478)
@@ -5,8 +5,11 @@
   * Re-run debconf-updatepo to get templates.pot and po files in sync with
 debconf template changes in 4.3.0.dfsg.1-3.
 
- -- Branden Robinson <[EMAIL PROTECTED]>  Sat, 29 May 2004 18:01:05 -0500
+  * Update Greek debconf template translations (thanks, Konstantinos
+Margaritis).  (Closes: #251509)
 
+ -- Branden Robinson <[EMAIL PROTECTED]>  Sat, 29 May 2004 18:12:00 -0500
+
 xfree86 (4.3.0.dfsg.1-4) unstable; urgency=medium
 
   * The "thanks for the 'testing'" release.

Modified: trunk/debian/po/el.po
===
--- trunk/debian/po/el.po   2004-05-29 23:19:32 UTC (rev 1477)
+++ trunk/debian/po/el.po   2004-05-29 23:21:43 UTC (rev 1478)
@@ -27,13 +27,13 @@
 "Project-Id-Version: el\n"
 "Report-Msgid-Bugs-To: [EMAIL PROTECTED]"
 "POT-Creation-Date: 2004-05-29 16:56-0500\n"
-"PO-Revision-Date: 2004-01-27 23:37EEST\n"
+"PO-Revision-Date: 2004-05-27 21:10EEST\n"
 "Last-Translator: Konstantinos Margaritis <[EMAIL PROTECTED]>\n"
 "Language-Team: Greek \n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"X-Generator: KBabel 1.0.2\n"
+"X-Generator: KBabel 1.3.1\n"
 
 #. Type: select
 #. Description
@@ -454,7 +454,6 @@
 #. Type: multiselect
 #. Description
 #: ../xserver-xfree86.templates:66
-#, fuzzy
 msgid ""
 "The vbe and ddc modules enable support for VESA BIOS Extensions and Data "
 "Display Channel, respectively.  These modules are used to query monitor "
@@ -898,6 +897,12 @@
 "symbols), you likely have a \"pc102\" or \"pc105\" model; if you choose "
 "\"pc101\" or \"pc104\" instead, your \"< >\" key might not work."
 msgstr ""
+"Τα μοντέλα \"pc102\" και \"pc105\" είναι ευρωπαϊκές εκδόσεις των μοντέλων "
+"pc101 και pc104, αντίστοιχα.  Αν το πληκτρολόγιό σας έχει ένα πλήκτρο \"< >"
+"\" (ένα μονάδικό πλήκτρο με τα σύμβολα \"μικρότερο\" και \"μεγαλύτερο\"), "
+"μάλλον έχετε ένα μοντέλο πληκτρολογίου \"pc102\" ή \"pc105\", και αν "
+"επιλέξετε μοντέλο \"pc101\" ή \"pc104\" το πλήκτρο \"< >\" πιθανόν να μη "
+"λειτουργεί."
 
 #. Type: string
 #. Description
@@ -1711,10 +1716,3 @@
 #: ../xserver-xfree86.templates:533
 msgid "Characters other than digits are not allowed in the entry."
 msgstr "Άλλοι χαρακτήρες εκτός από ψηφία δεν είναι αποδεκτοί."
-
-#~ msgid ""
-#~ "The \"pc102\" and \"pc105\" models are versions of the pc101 and pc104 "
-#~ "keyboards, respectively, often found in Europe."
-#~ msgstr ""
-#~ "Τα μοντέλα \"pc102\" και \"pc105\" είναι εκδόσεις των pc101 και pc104, "
-#~ "αντίστοιχα, που απαντώνται συχνά στην Ευρώπη."



X Strike Force XFree86 SVN commit: r1477 - tags

2004-05-29 Thread X Strike Force SVN Repository Admin
Author: branden
Date: 2004-05-29 18:19:32 -0500 (Sat, 29 May 2004)
New Revision: 1477

Added:
   tags/4.3.0.dfsg.1-4/
Log:
Tag 4.3.0.dfsg.1-4 release.


Copied: tags/4.3.0.dfsg.1-4 (from rev 1470, branches/4.3.0/sid)



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

2004-05-29 Thread X Strike Force SVN Repository Admin
Author: branden
Date: 2004-05-29 18:17:02 -0500 (Sat, 29 May 2004)
New Revision: 1476

Modified:
   trunk/debian/CHANGESETS
Log:
Update to reflect previous commit.


Modified: trunk/debian/CHANGESETS
===
--- trunk/debian/CHANGESETS 2004-05-29 23:02:28 UTC (rev 1475)
+++ trunk/debian/CHANGESETS 2004-05-29 23:17:02 UTC (rev 1476)
@@ -8,8 +8,8 @@
 (It should always be safe to merge the latest version of TODO or CHANGESETS
 files anywhere.)
 
-Fix hang in xserver-xfree86 config script by telling grep what file to
-search.
-1468
+Re-run debconf-updatepo to get templates.pot and po files in sync with
+debconf template changes in 4.3.0.dfsg.1-3.
+1475
 
 vim:set ai et sts=4 sw=4 tw=80:



Bug#251453: marked as done (xlibs-data: syntax error in /usr/X11R6/lib/X11/locale/locale.alias ?)

2004-05-29 Thread Debian Bug Tracking System
Your message dated Sat, 29 May 2004 16:31:21 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#251453: xlibs-data: syntax error in 
/usr/X11R6/lib/X11/locale/locale.alias ?
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; 28 May 2004 16:07:22 +
>From [EMAIL PROTECTED] Fri May 28 09:07:22 2004
Return-path: <[EMAIL PROTECTED]>
Received: from mail2.webmessenger.it (mail2a.webresidence.it) [193.70.193.55] 
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1BTivv-0006e7-00; Fri, 28 May 2004 08:06:07 -0700
Received: from bohr.pisa.iol.it (193.76.233.84) by mail2a.webresidence.it 
(7.0.027-DD01)
id 40A0FB9D7196; Fri, 28 May 2004 17:05:33 +0200
Received: from giuseppe by bohr.pisa.iol.it with local (Exim 4.32)
id 1BTivN-00035f-AF; Fri, 28 May 2004 17:05:33 +0200
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: giuseppe bonacci <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: xlibs-data: syntax error in /usr/X11R6/lib/X11/locale/locale.alias ?
X-Mailer: reportbug 2.60
Date: Fri, 28 May 2004 17:05:33 +0200
Message-Id: <[EMAIL PROTECTED]>
Sender: peppe <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 

Package: xlibs-data
Version: 4.3.0.dfsg.1-1
Severity: normal

I did not succeed in finding out the exact syntax for this file.  
Apparently, the file is the result of a concatenation of two files with
different formats.

The header states that lines should be like

alias-name  target-name

but it also contains lines of the form 

alias-name: target-name

According to my experiments, the first form is ignored, while the
second works smoothly: adding

en_US.ISO-8859-15: en_US.ISO8859-15

allows me to set LANG=en_US.ISO-8859-15 and launch xterm with Xlib
honouring my locale. (see #251000, and possibly merge)

best regards. 
g.bonacci

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.4.26-1-686
Locale: LANG=C, LC_CTYPE=C

-- no debconf information

---
Received: (at 251453-done) by bugs.debian.org; 29 May 2004 21:31:23 +
>From [EMAIL PROTECTED] Sat May 29 14:31:23 2004
Return-path: <[EMAIL PROTECTED]>
Received: from dhcp065-026-182-085.indy.rr.com (redwald.deadbeast.net) 
[65.26.182.85] 
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1BUBQI-00012V-00; Sat, 29 May 2004 14:31:23 -0700
Received: by redwald.deadbeast.net (Postfix, from userid 1000)
id F403564275; Sat, 29 May 2004 16:31:21 -0500 (EST)
Date: Sat, 29 May 2004 16:31:21 -0500
From: Branden Robinson <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: Bug#251453: xlibs-data: syntax error in 
/usr/X11R6/lib/X11/locale/locale.alias ?
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="6tPipYVl+OcoAvSh"
Content-Disposition: inline
In-Reply-To: <[EMAIL PROTECTED]>
Mail-Copies-To: nobody
X-No-CC: I subscribe to this list; do not CC me on replies.
User-Agent: Mutt/1.5.6i
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 


--6tPipYVl+OcoAvSh
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, May 28, 2004 at 05:05:33PM +0200, giuseppe bonacci wrote:
> Package: xlibs-data
> Version: 4.3.0.dfsg.1-1
> Severity: normal
>=20
> I did not succeed in finding out the exact syntax for this file. =20
> Apparently, the file is the result of a concatenation of two files with
> different formats.
>=20
> The header states that lines should be like
>=20
> alias-nametarget-name
>=20
> but it also contains lines of the form=20
>=20
> alias-name:   target-name

This is deliberate.  I can't find the reference right now, b

Processed: retitle 251506 to xserver-xfree86: [ati/radeon] Xinerama malfunctions on Radeon 9000/PRO If [regression from 4.3.0.dfsg.1-1] ...

2004-05-29 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.7.95.1
> retitle 251506 xserver-xfree86: [ati/radeon] Xinerama malfunctions on Radeon 
> 9000/PRO If [regression from 4.3.0.dfsg.1-1]
Bug#251506: xserver-xfree86: xinerama (radeon) broken with 4.3.0.dfsg.1-2
Changed Bug title.

> tags 251506 + upstream
Bug#251506: xserver-xfree86: [ati/radeon] Xinerama malfunctions on Radeon 
9000/PRO If [regression from 4.3.0.dfsg.1-1]
There were no tags set.
Tags added: upstream

>
End of message, stopping processing here.

Please contact me if you need assistance.

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



Bug#251449: Dual head addition to FAQ

2004-05-29 Thread Branden Robinson
reassign 251449 xfree86-common
retitle 251449 xfree86-common: please add instructions on configuring multiple 
displays to FAQ
severity 251449 wishlist
thanks

On Fri, May 28, 2004 at 03:42:27PM +0100, Chris Walker wrote:
> Package: xserver-xfree86
> Version: 4.3.0.dfsg.1-1
> 
> Please can you add an entry to the FAQ on how to configure two displays.
> 
> Here is a starting point:
> 
>Q) Using more than one monitor (Dual head)
>   
>   
>   If you are using the nvidia driver, and wish to use the "TwinView"
>   feature, then more detailed instructions can be found in
>   /usr/share/doc/nvidia-glx/README.gz
>   
>   An example using two video cards to drive two displays can be found in
>   ***insert example filename here***.
>   
>   An example using a video card capable of driving two displays can be
>   found in ***insert example filename here***.
>   
> 
> What I struggled to work out from the instructions - though it now
> seems obvious from the example in the nvidia readme.  You need to have
> two "Device" entries identical except that the first should have have
> the command Screen 0, and the second Screen 1. (I have in fact not
> tried this as I got the Twinview setup working - but I think that this
> was my problem).

Thank you for your report.  This will need to be fleshed out before it
can be added to the FAQ; also, a migration of the FAQ to XHTML is
pending, and so this will probably wait until after that has occurred to
be included.

-- 
G. Branden Robinson|  "I came, I saw, she conquered."
Debian GNU/Linux   |  The original Latin seems to have
[EMAIL PROTECTED] |  been garbled.
http://people.debian.org/~branden/ |  -- Robert Heinlein


signature.asc
Description: Digital signature


Bug#229785: Fwd: Re: Hash function

2004-05-29 Thread Branden Robinson
Mr. Jenkins,

Hello,

I am a member of the XFree86 packaging team for the Debian Project, and
I'm the root cause of this nagging about the license of your hash
algorithm.

There is no problem with your statement that you have placed it in the
public domain, and I also have no problem preserving identification of
you as the author.

I wanted to offer that assurance along with a (lengthy) explanation of
why this was even an issue.

The reason I've been a stickler about this is that the Debian Project
has learned over the years that not all jurisdictions, particularly
those in Europe, have a concept of "placing in public domain" that is
directly analogous to that in the United States.  Many European
jurisdictions have a concept called "droit d'auteur" ("authorial rights"
or sometimes "moral rights") which are distinct from copyright, and
whose application to digital works is unclear.

It is conceivable, for instance, that despite disclaiming copyright
protection, in Europe you could compel the removal of your name from a
work that accurately credited you if you found that work distasteful.
E.g., imagine your hash algorithm being used in an industrial control
application for factory farming, a practice which some people find
ethically objectionable.

In the U.S., as far as I know, you would have no such cause of action.
People still have to be careful not to imply that you endorse their
work, and they have no right in any case to use your name or likeness in
promotional or advertising materials without your consent, but in Europe
-- as I understand it -- "moral rights" permit you to dissociate your
name from a work that includes or is derived from yours, even when your
name is used accurately.

So, in much more than a nutshell, that is why Debian sweats this sort of
thing.

Please feel free to contact me if you have any questions or concerns
about our use of your work.

Thank you again for your clarifying statement, and for your
contribution.

Margarita,

Thanks for helping me to understand the provenance of the code you've
contributed!

On Fri, May 28, 2004 at 09:58:27AM -0300, Margarita Manterola wrote:
> About the licence of the hash algorithm:
> 
> - Forwarded message from Bob Jenkins <[EMAIL PROTECTED]> -
> 
> From: Bob Jenkins <[EMAIL PROTECTED]>
> Date: Thu, 27 May 2004 22:33:06 -0700
> To: Margarita Manterola <[EMAIL PROTECTED]>
> Subject: Re: Hash function
> 
> Margarita Manterola wrote:
> >Hi!
> >
> >Sorry to bother you, I hope you still have this email.
> >
> >I'm wishing to use or hash() algorithm, from the lookup2.c in a piece of
> >XFree86 code. In order to be able to do this legally and properly, the
> >code needs to be licenced with some specific licence :|...  Stating that
> >it is free seems not to be enough. :|
> >
> >Could you state that the code is covered under the GPL, or BSD Licences,
> >or some other licence you like, but that is written somewhere, pretty
> >pretty please?
> >
> >Thanks for the great algorithm and for making it free.
> >
> >Love,
> >Margarita Manterola.
> >
> 
> The algorithm is public domain.  I ask that I be referenced as the 
> source of the algorithm, but I can't enforce that, since being public 
> domain means I've reserved no rights at all.
> 
> 
> - End forwarded message -
> 
> So, is public domain enough?  I know the text does not state it's public
> domain, but the author is stating it here...

-- 
G. Branden Robinson|Of two competing theories or
Debian GNU/Linux   |explanations, all other things
[EMAIL PROTECTED] |being equal, the simpler one is to
http://people.debian.org/~branden/ |be preferred.  -- Occam's Razor


signature.asc
Description: Digital signature


Processed: tagging 246398

2004-05-29 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.7.95.1
> tags 246398 - d-i
Bug#246398: xterm: uxterm should fail if en_US.UTF-8 locale not supported on 
system
There were no tags set.
Tags removed: d-i

>
End of message, stopping processing here.

Please contact me if you need assistance.

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



Processed: Re: Bug#251449: Dual head addition to FAQ

2004-05-29 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

> reassign 251449 xfree86-common
Bug#251449: Dual head addition to FAQ
Bug reassigned from package `xserver-xfree86' to `xfree86-common'.

> retitle 251449 xfree86-common: please add instructions on configuring 
> multiple displays to FAQ
Bug#251449: Dual head addition to FAQ
Changed Bug title.

> severity 251449 wishlist
Bug#251449: xfree86-common: please add instructions on configuring multiple 
displays to FAQ
Severity set to `wishlist'.

> thanks
Stopping processing here.

Please contact me if you need assistance.

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



Processed: tagging 246398

2004-05-29 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.7.95.1
> tags 246398 - d-i
Bug#246398: xterm: uxterm should fail if en_US.UTF-8 locale not supported on 
system
Tags were: d-i
Tags removed: d-i

>
End of message, stopping processing here.

Please contact me if you need assistance.

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



Bug#233933: Heads up?

2004-05-29 Thread James Young
Now that I've switched the gpm repeater to ms3, switching from console to 
X is a lot faster.  Thanks for pointing that out.  But could you configure 
that package to, say, pop up a warning dialog about this before you throw 
the previous X config away?  This can silently break X in such a way that 
downgrading doesn't help.

-- 
[EMAIL PROTECTED]



Bug#251611: xlibs: Most XKB operations fail, including GNOME.

2004-05-29 Thread Adam D. Barratt
package xlibs
severity 251611 important
merge 251511 251119
thanks

On Sat, 2004-05-29 at 19:46, Harald Nordgård-Hansen wrote:
> Package: xlibs
> Version: 4.3.0.dfsg.1-2
> Severity: critical
> Tags: sid
> Justification: breaks unrelated software
> 
> For some reason, the latest xlibs package has replaced the standard
> /etc/X11/xkb/types/basic file with what seems to be a X Consortium
> version from '94 or something.
[...]
> Please fix the package with the correct file from XFree86.

The reason in question was the same as that described in #251119, and
the six other reports of the bug merged with it.

As can be seen from looking at the xlibs bts page, all of those bugs
were fixed in the upload of 4.3.0.dfsg.1-3, almost 24 hours *before* you
filed this report.

This report should be closed, imho, but I'll leave that to the
maintainers.

Regards,

Adam




Processed: Re: Bug#251611: xlibs: Most XKB operations fail, including GNOME.

2004-05-29 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

> package xlibs
Ignoring bugs not assigned to: xlibs

> severity 251611 important
Bug#251611: xlibs: Most XKB operations fail, including GNOME.
Severity set to `important'.

> merge 251511 251119
Bug#251119: xlibs: version 4.3.0.dfsg.1-2 breaks NumLock, CapsLock and 
gnome-settings-daemon
Bug#251511: libxml-dev: conflict on libxml2-dev too strict
Mismatch - only Bugs in same state can be merged:
Values for `package' don't match:
 #251119 has `xlibs';
 #251511 has `libxml-dev'

> thanks
Stopping processing here.

Please contact me if you need assistance.

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



Bug#251611: xlibs: Most XKB operations fail, including GNOME.

2004-05-29 Thread Harald Nordgård-Hansen
Package: xlibs
Version: 4.3.0.dfsg.1-2
Severity: critical
Tags: sid
Justification: breaks unrelated software

For some reason, the latest xlibs package has replaced the standard
/etc/X11/xkb/types/basic file with what seems to be a X Consortium
version from '94 or something.

The result is that any program that tries to do things with XKB fails
with a BadValue error on a XKEYBOARD/XkbSetMap call, which is causing
errors all over the place.  There is a whole slew of critical errors
reported on the capplets package, as well as other gnome packages that
is caused by this.

In bug #245848, there is a patch to fix this, which just returns the
file to the version from 4.3.0.dfsg.1-1 or earlier.

Please fix the package with the correct file from XFree86.

-Harald

-- Package-specific info:
Keyboard-related contents of XFree86 X server log file
/var/log/XFree86.0.log:
(==) ServerLayout "Server Layout"
(**) |-->Screen "Screen0" (0)
(**) |   |-->Monitor "Monitor0"
(**) |   |-->Device "ATI Graphics Adapter"
(**) |-->Input Device "Mouse1"
(**) |-->Input Device "Keyboard1"
(**) Option "AutoRepeat" "500 30"
(**) Option "XkbRules" "xfree86"
(**) XKB: rules: "xfree86"
(**) Option "XkbModel" "pc105"
(**) XKB: model: "pc105"
(**) Option "XkbLayout" "no"
(**) XKB: layout: "no"
(==) Keyboard: CustomKeycode disabled
(**) FontPath set to 
"/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/75dpi/:unscaled,/usr/X11R6/lib/X11/fonts/100dpi/:unscaled,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/"
(**) RgbPath set to "/usr/X11R6/lib/X11/rgb"
(==) ModulePath set to "/usr/X11R6/lib/modules"
(++) using VT number 7

--
(==) RandR enabled
(II) Setting vga for screen 0.
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension LBX
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFree86-Bigfont
--
(**) Mouse1: Core Pointer
(**) Option "Device" "/dev/mouse"
(**) Option "Emulate3Buttons"
(**) Mouse1: Emulate3Buttons, Emulate3Timeout: 50
(==) Mouse1: Buttons: 3
(II) Keyboard "Keyboard1" handled by legacy driver
(II) XINPUT: Adding extended input device "Mouse1" (type: MOUSE)
(II) Mouse1: ps2EnableDataReporting: succeeded
Could not init font path element /usr/X11R6/lib/X11/fonts/Speedo/, removing 
from list!
GetModeLine - scrn: 0 clock: 108000
GetModeLine - hdsp: 1400 hbeg: 1432 hend: 1464 httl: 1600

XFree86 X server log files on system:
-rw-r--r--1 root root33233 May 29 20:08 /var/log/XFree86.0.log


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (499, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.6
Locale: LANG=C, LC_CTYPE=no_NO.ISO8859-1

Versions of packages xlibs depends on:
ii  libice6   4.3.0.dfsg.1-2 Inter-Client Exchange library
ii  libsm64.3.0.dfsg.1-2 X Window System Session Management
ii  libx11-6  4.3.0.dfsg.1-2 X Window System protocol client li
ii  libxext6  4.3.0.dfsg.1-2 X Window System miscellaneous exte
ii  libxft1   4.3.0.dfsg.1-2 FreeType-based font drawing librar
ii  libxi64.3.0.dfsg.1-2 X Window System Input extension li
ii  libxmu6   4.3.0.dfsg.1-2 X Window System miscellaneous util
ii  libxmuu1  4.3.0.dfsg.1-2 lightweight X Window System miscel
ii  libxp64.3.0.dfsg.1-2 X Window System printing extension
ii  libxpm4   4.3.0.dfsg.1-2 X pixmap library
ii  libxrandr24.3.0.dfsg.1-2 X Window System Resize, Rotate and
ii  libxt64.3.0.dfsg.1-2 X Toolkit Intrinsics
ii  libxtrap6 4.3.0.dfsg.1-2 X Window System protocol-trapping 
ii  libxtst6  4.3.0.dfsg.1-2 X Window System event recording an
ii  xlibs-data4.3.0.dfsg.1-2 X Window System client data

-- no debconf information



Bug#248940: Processed: Re: Bug#248940: xlibs: strange caps lock lag

2004-05-29 Thread John Belmonte

Branden Robinson wrote:

Mr. Belmonte, you may want to take your concern directly to the
linux-kernel mailing list, as Mr. Xu is likely, given his past behavior,
to blockade any efforts to resolve this in Debian's kernel.


I've filed a kernel bug, see 
.






Bug#201737: map LWIN to Mode_switch

2004-05-29 Thread Mark Brown
On Fri, May 28, 2004 at 04:38:27AM -0500, Branden Robinson wrote:

> XkbRules  xfree86
> XkbModel  macintosh
> XkbLayout gb
> XkbOptionsgroup:lwin_switch

> Mark, between this and the modification to /etc/X11/xkb/symbols/macintosh/gb I
> sent you last July, are your problems resolved?

Turning on that option I still can't seem to generate a number symbol
(or, I notice the Euro symbol which is the third character on 2).  My
keyboard configuration is:

Section "InputDevice"
Identifier  "Generic Keyboard"
Driver  "keyboard"
Option  "CoreKeyboard"
Option  "XkbRules"  "xfree86"
Option  "XkbModel"  "macintosh"
Option  "XkbLayout" "gb"
Option  "XkbOptions""ctrl:nocaps,group:lwin_switch"
EndSection

I've tried all the modifier keys I can think of but this could still be
user error.

-- 
"You grabbed my hand and we fell into it, like a daydream - or a fever."




Re: d-i beta & x configuration

2004-05-29 Thread Andree Leidenfrost
On Fri, 2004-05-21 at 15:06, Branden Robinson wrote:
> On Sun, May 02, 2004 at 12:36:32PM +1000, Andree Leidenfrost wrote:
> > I've just done a testrun of d-i installer beta4 which worked just fine.
> > 
> > There were three issues with the x windows setup though:
> > 
> > Apparently, if one only has one video card, the PCI ID field must be
> > empty for things to work.
> 
> Not true.  At least with earlier versions of XFree86 (and maybe still
> today), some machines need this parameter just to work with a single
> video card.  Most, however, do not.
> 
> > I did not find this obvious from the dialog and it was prefilled with
> > the ID from my videocard. It took me some experimenting to realise it
> > had to be empty for things to work.
> 
> Unfortunately, I cannot offer the user much guidance in the dialog box,
> as I do not myself know exactly when the PCI ID field is required.  I
> know only that sometimes you need it, as I do with my Blue&White
> Macintosh G3.
> 
> It puzzles me that the autodetected value did not work, however.
> 
> Could you try purging and reinstalling the XFree86 package, or running
> through d-i again, and leaving the pre-filled value in, so that you can
> file a bug report against xserver-xfree86 with "reportbug"?  That will
> automatically include the config file and server logs so we can take a
> closer look at the problem.

Done. I've reinstalled from scratch using d-i daily 040528. Bug number
is 251568.

> > Secondly, the setup offered to auto-detect my monitor which apparently
> > worked as I got the correct monitor description prefilled when doing a
> > dpkg-reconfigure xserver-xfree86 later on. However, the initial setup
> > configures a suboptimal resolution. Shouldn't the auto-detection see
> > that the monitor is an LCD and therefore operate it @ 60Hz with the
> > monitor's native resolution?
> 
> In a word, yes.  This is being worked on as part of the "debconf
> overhaul".

Cool. As an intermediate measure, would it be possible to add an entry
[EMAIL PROTECTED] to the Medium monitor configuration screen?

> > Last thing I'd like to bring up is the fact that I had to to specify the
> > brand of my videocard. Can this not be autodetected? (lspci knows that
> > vendor ID 1002 is 'ATI Technologies Inc', maybe that could be used? But
> > maybe it's not as simple...)
> 
> The config script *does* make an attempt to autodetect the video card's
> brand:
> 
>   # card identifier; try to set a sensible default
>   DEFAULT=
>   if [ -n "$(echo $NDRIVERS)" ] && [ $NDRIVERS -eq 1 -a $NCARDS -eq 1 ]; then
> if which discover > /dev/null 2>&1; then
>   if [ "$AUTODETECT_VIDEO_CARD" = "true" ]; then
> DEFAULT=$(echo "$DISCOVERED_VIDEO" | awk 'BEGIN { FS="\t" } {print 
> $1}')
>   fi
> fi
>   fi
>   if [ -z "$DEFAULT" ]; then
> # fall back to some language-specific generic text
> case "${LC_ALL:-${LC_MESSAGES:-$LANG}}" in
>   ca_*) DEFAULT="Targeta de vídeo genèrica" ;;
>   # da
>   de_*) DEFAULT="Standardgrafikkarte" ;;
>   es_*) DEFAULT="Tarjeta de vídeo genérica" ;;
>   fr_*) DEFAULT="Carte vidéo générique" ;;
>   gl_*) DEFAULT="Tarxeta de Video Xenérica" ;;
>   it_*) DEFAULT="Scheda video generica" ;;
>   # ja
>   # nl
>   pt_BR) DEFAULT="Placa de Vídeo Genérica" ;;
>   # ru
>   # sv
>   *) DEFAULT="Generic Video Card" ;;
> esac
>   fi
>   # this question requires input validation
>   MAY_BE_NULL= auto_answer validate_string_db_input "$(priority_ceil low)" 
> xserver-xfree86/config/device/identifier "$DEFAULT"
> 
> Needless to say, this only works if discover is installed, and
> recognizes the video card.  You might try installing the discover
> package and running the "discover" command without arguments.

Right. d-i currently comes with discover1 as far as I can tell. When I
run the discover command I get no output at all, this is both as root
and as a normal user. What am I supposed to see/do? The manpage sounds
like running discover should produce output. Then again, the manpage
mentions optins -h and -v which don't seem to exist...hm.

> > Other than that I completely acknowledge that it must be incredibly
> > hard to support a complex system like x windows on so many platforms.
> > So maybe it is just not possible. But from a user experience it would
> > probably be quite helpful.
> 
> I think we can probably make some improvements in all three of the areas
> you noted.

Sounds good. Is there any other information I can gather that would
possibly help?

Cheers
Andree
-- 
Andree Leidenfrost
Sydney - Australia



xfree86_4.3.0.dfsg.1-4_powerpc.changes ACCEPTED

2004-05-29 Thread Debian Installer

Accepted:
lbxproxy_4.3.0.dfsg.1-4_powerpc.deb
  to pool/main/x/xfree86/lbxproxy_4.3.0.dfsg.1-4_powerpc.deb
libdps-dev_4.3.0.dfsg.1-4_powerpc.deb
  to pool/main/x/xfree86/libdps-dev_4.3.0.dfsg.1-4_powerpc.deb
libdps1-dbg_4.3.0.dfsg.1-4_powerpc.deb
  to pool/main/x/xfree86/libdps1-dbg_4.3.0.dfsg.1-4_powerpc.deb
libdps1_4.3.0.dfsg.1-4_powerpc.deb
  to pool/main/x/xfree86/libdps1_4.3.0.dfsg.1-4_powerpc.deb
libice-dev_4.3.0.dfsg.1-4_powerpc.deb
  to pool/main/x/xfree86/libice-dev_4.3.0.dfsg.1-4_powerpc.deb
libice6-dbg_4.3.0.dfsg.1-4_powerpc.deb
  to pool/main/x/xfree86/libice6-dbg_4.3.0.dfsg.1-4_powerpc.deb
libice6_4.3.0.dfsg.1-4_powerpc.deb
  to pool/main/x/xfree86/libice6_4.3.0.dfsg.1-4_powerpc.deb
libsm-dev_4.3.0.dfsg.1-4_powerpc.deb
  to pool/main/x/xfree86/libsm-dev_4.3.0.dfsg.1-4_powerpc.deb
libsm6-dbg_4.3.0.dfsg.1-4_powerpc.deb
  to pool/main/x/xfree86/libsm6-dbg_4.3.0.dfsg.1-4_powerpc.deb
libsm6_4.3.0.dfsg.1-4_powerpc.deb
  to pool/main/x/xfree86/libsm6_4.3.0.dfsg.1-4_powerpc.deb
libx11-6-dbg_4.3.0.dfsg.1-4_powerpc.deb
  to pool/main/x/xfree86/libx11-6-dbg_4.3.0.dfsg.1-4_powerpc.deb
libx11-6_4.3.0.dfsg.1-4_powerpc.deb
  to pool/main/x/xfree86/libx11-6_4.3.0.dfsg.1-4_powerpc.deb
libx11-dev_4.3.0.dfsg.1-4_powerpc.deb
  to pool/main/x/xfree86/libx11-dev_4.3.0.dfsg.1-4_powerpc.deb
libxaw6-dbg_4.3.0.dfsg.1-4_powerpc.deb
  to pool/main/x/xfree86/libxaw6-dbg_4.3.0.dfsg.1-4_powerpc.deb
libxaw6-dev_4.3.0.dfsg.1-4_powerpc.deb
  to pool/main/x/xfree86/libxaw6-dev_4.3.0.dfsg.1-4_powerpc.deb
libxaw6_4.3.0.dfsg.1-4_powerpc.deb
  to pool/main/x/xfree86/libxaw6_4.3.0.dfsg.1-4_powerpc.deb
libxaw7-dbg_4.3.0.dfsg.1-4_powerpc.deb
  to pool/main/x/xfree86/libxaw7-dbg_4.3.0.dfsg.1-4_powerpc.deb
libxaw7-dev_4.3.0.dfsg.1-4_powerpc.deb
  to pool/main/x/xfree86/libxaw7-dev_4.3.0.dfsg.1-4_powerpc.deb
libxaw7_4.3.0.dfsg.1-4_powerpc.deb
  to pool/main/x/xfree86/libxaw7_4.3.0.dfsg.1-4_powerpc.deb
libxext-dev_4.3.0.dfsg.1-4_powerpc.deb
  to pool/main/x/xfree86/libxext-dev_4.3.0.dfsg.1-4_powerpc.deb
libxext6-dbg_4.3.0.dfsg.1-4_powerpc.deb
  to pool/main/x/xfree86/libxext6-dbg_4.3.0.dfsg.1-4_powerpc.deb
libxext6_4.3.0.dfsg.1-4_powerpc.deb
  to pool/main/x/xfree86/libxext6_4.3.0.dfsg.1-4_powerpc.deb
libxft1-dbg_4.3.0.dfsg.1-4_powerpc.deb
  to pool/main/x/xfree86/libxft1-dbg_4.3.0.dfsg.1-4_powerpc.deb
libxft1_4.3.0.dfsg.1-4_powerpc.deb
  to pool/main/x/xfree86/libxft1_4.3.0.dfsg.1-4_powerpc.deb
libxi-dev_4.3.0.dfsg.1-4_powerpc.deb
  to pool/main/x/xfree86/libxi-dev_4.3.0.dfsg.1-4_powerpc.deb
libxi6-dbg_4.3.0.dfsg.1-4_powerpc.deb
  to pool/main/x/xfree86/libxi6-dbg_4.3.0.dfsg.1-4_powerpc.deb
libxi6_4.3.0.dfsg.1-4_powerpc.deb
  to pool/main/x/xfree86/libxi6_4.3.0.dfsg.1-4_powerpc.deb
libxmu-dev_4.3.0.dfsg.1-4_powerpc.deb
  to pool/main/x/xfree86/libxmu-dev_4.3.0.dfsg.1-4_powerpc.deb
libxmu6-dbg_4.3.0.dfsg.1-4_powerpc.deb
  to pool/main/x/xfree86/libxmu6-dbg_4.3.0.dfsg.1-4_powerpc.deb
libxmu6_4.3.0.dfsg.1-4_powerpc.deb
  to pool/main/x/xfree86/libxmu6_4.3.0.dfsg.1-4_powerpc.deb
libxmuu-dev_4.3.0.dfsg.1-4_powerpc.deb
  to pool/main/x/xfree86/libxmuu-dev_4.3.0.dfsg.1-4_powerpc.deb
libxmuu1-dbg_4.3.0.dfsg.1-4_powerpc.deb
  to pool/main/x/xfree86/libxmuu1-dbg_4.3.0.dfsg.1-4_powerpc.deb
libxmuu1_4.3.0.dfsg.1-4_powerpc.deb
  to pool/main/x/xfree86/libxmuu1_4.3.0.dfsg.1-4_powerpc.deb
libxp-dev_4.3.0.dfsg.1-4_powerpc.deb
  to pool/main/x/xfree86/libxp-dev_4.3.0.dfsg.1-4_powerpc.deb
libxp6-dbg_4.3.0.dfsg.1-4_powerpc.deb
  to pool/main/x/xfree86/libxp6-dbg_4.3.0.dfsg.1-4_powerpc.deb
libxp6_4.3.0.dfsg.1-4_powerpc.deb
  to pool/main/x/xfree86/libxp6_4.3.0.dfsg.1-4_powerpc.deb
libxpm-dev_4.3.0.dfsg.1-4_powerpc.deb
  to pool/main/x/xfree86/libxpm-dev_4.3.0.dfsg.1-4_powerpc.deb
libxpm4-dbg_4.3.0.dfsg.1-4_powerpc.deb
  to pool/main/x/xfree86/libxpm4-dbg_4.3.0.dfsg.1-4_powerpc.deb
libxpm4_4.3.0.dfsg.1-4_powerpc.deb
  to pool/main/x/xfree86/libxpm4_4.3.0.dfsg.1-4_powerpc.deb
libxrandr-dev_4.3.0.dfsg.1-4_powerpc.deb
  to pool/main/x/xfree86/libxrandr-dev_4.3.0.dfsg.1-4_powerpc.deb
libxrandr2-dbg_4.3.0.dfsg.1-4_powerpc.deb
  to pool/main/x/xfree86/libxrandr2-dbg_4.3.0.dfsg.1-4_powerpc.deb
libxrandr2_4.3.0.dfsg.1-4_powerpc.deb
  to pool/main/x/xfree86/libxrandr2_4.3.0.dfsg.1-4_powerpc.deb
libxt-dev_4.3.0.dfsg.1-4_powerpc.deb
  to pool/main/x/xfree86/libxt-dev_4.3.0.dfsg.1-4_powerpc.deb
libxt6-dbg_4.3.0.dfsg.1-4_powerpc.deb
  to pool/main/x/xfree86/libxt6-dbg_4.3.0.dfsg.1-4_powerpc.deb
libxt6_4.3.0.dfsg.1-4_powerpc.deb
  to pool/main/x/xfree86/libxt6_4.3.0.dfsg.1-4_powerpc.deb
libxtrap-dev_4.3.0.dfsg.1-4_powerpc.deb
  to pool/main/x/xfree86/libxtrap-dev_4.3.0.dfsg.1-4_powerpc.deb
libxtrap6-dbg_4.3.0.dfsg.1-4_powerpc.deb
  to pool/main/x/xfree86/libxtrap6-dbg_4.3.0.dfsg.1-4_powerpc.deb
libxtrap6_4.3.0.dfsg.1-4_powerpc.deb
  to pool/main/x/xfree86/libxtrap6_4.3.0.dfsg.1-4_powerpc.deb
libxtst-dev_4.3.0.dfsg.1-4_powerpc.deb
  to pool/main/x/xfree86/libxtst-dev_4.3.0.dfsg.1-4_powerpc.deb
libxtst6-dbg_4.3.0.dfsg.1-4_powerpc.deb
  to pool/main/x/xfree86/libxtst6-dbg_4

xfree86 override disparity

2004-05-29 Thread Debian Installer
There are disparities between your recently accepted upload and the
override file for the following file(s):

x-window-system-dev_4.3.0.dfsg.1-4_powerpc.deb: package says priority is extra, 
override says optional.

Either the package or the override file is incorrect.  If you think
the override is correct and the package wrong please fix the package
so that this disparity is fixed in the next upload.  If you feel the
override is incorrect then please reply to this mail and explain why.

[NB: this is an automatically generated mail; if you replied to one
like it before and have not received a response yet, please ignore
this mail.  Your reply needs to be processed by a human and will be in
due course, but until then the installer will send these automated
mails; sorry.]

--
Debian distribution maintenance software

(This message was generated automatically; if you believe that there
is a problem with it please contact the archive administrators by
mailing [EMAIL PROTECTED])



Accepted xfree86 4.3.0.dfsg.1-4 (powerpc all source)

2004-05-29 Thread Branden Robinson
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Fri, 28 May 2004 21:49:53 -0500
Source: xfree86
Binary: libx11-6-dbg libxtst6-dbg xserver-common xlibs-static-dev libxp6-dbg 
xbase-clients xlibmesa3-dbg libxtrap6-dbg xfonts-75dpi libxt6 libice6-dbg xmh 
libxaw6-dbg x-dev libxv1 libxext6-dbg xlibmesa-dev libxpm4 libxtst6 
xlibmesa-gl-dev xfonts-cyrillic libx11-6 libsm6-dbg xlibs-pic xlibs-data 
x-window-system xfree86-common xlibmesa-dri xlibmesa3 libxv1-dbg libxrandr2 
xlibmesa-glu libxaw7-dev xnest libxaw6 xterm libxp6 xlibmesa-dri-dbg 
libxrandr2-dbg libxmu6 xlibmesa-glu-dbg libx11-dev xlibs-static-pic libxpm4-dbg 
libxaw7-dbg libxmu6-dbg xlibmesa-glu-dev libxmuu-dev pm-dev libxext6 
libxft1-dbg libxtst-dev libxv-dev libxp-dev twm x-window-system-dev libsm-dev 
xfonts-scalable libdps1-dbg libxmuu1-dbg xfwp libice6 libxmu-dev xlibs 
libdps-dev xserver-xfree86-dbg libxrandr-dev libsm6 xserver-xfree86 libdps1 
proxymngr xfonts-base-transcoded libxaw6-dev lbxproxy x-window-system-core 
xutils xspecs libxtrap6 libice-dev libxt-dev xfs libxmuu1 libxi6-dbg 
xfonts-base xlibs-dbg libxpm-de
 v xlibmesa-gl xfonts-100dpi-transcoded libxtrap-dev xfonts-100dpi libxext-dev 
xfonts-75dpi-transcoded xlibosmesa4-dbg libxft1 xprt libxi-dev xlibosmesa-dev 
xlibosmesa4 xvfb libxaw7 xlibmesa-gl-dbg xdm xlibs-dev libxi6 libxt6-dbg
Architecture: source powerpc all
Version: 4.3.0.dfsg.1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force 
Changed-By: Branden Robinson <[EMAIL PROTECTED]>
Description: 
 lbxproxy   - Low Bandwidth X (LBX) proxy server
 libdps-dev - Display PostScript (DPS) client library development files
 libdps1- Display PostScript (DPS) client library
 libdps1-dbg - Display PostScript (DPS) client library (unstripped)
 libice-dev - Inter-Client Exchange library development files
 libice6- Inter-Client Exchange library
 libice6-dbg - Inter-Client Exchange library (unstripped)
 libsm-dev  - X Window System Session Management library development files
 libsm6 - X Window System Session Management library
 libsm6-dbg - X Window System Session Management library (unstripped)
 libx11-6   - X Window System protocol client library
 libx11-6-dbg - X Window System protocol client library (unstripped)
 libx11-dev - X Window System protocol client library development files
 libxaw6- X Athena widget set library (version 6)
 libxaw6-dbg - X Athena widget set library (version 6, unstripped)
 libxaw6-dev - X Athena widget set library development files (version 6)
 libxaw7- X Athena widget set library
 libxaw7-dbg - X Athena widget set library (unstripped)
 libxaw7-dev - X Athena widget set library development files
 libxext-dev - X Window System miscellaneous extension library development files
 libxext6   - X Window System miscellaneous extension library
 libxext6-dbg - X Window System miscellaneous extension library (unstripped)
 libxft1- FreeType-based font drawing library for X (version 1)
 libxft1-dbg - FreeType-based font drawing library for X (version 1, unstripped)
 libxi-dev  - X Window System Input extension library development files
 libxi6 - X Window System Input extension library
 libxi6-dbg - X Window System Input extension library (unstripped)
 libxmu-dev - X Window System miscellaneous utility library development files
 libxmu6- X Window System miscellaneous utility library
 libxmu6-dbg - X Window System miscellaneous utility library (unstripped)
 libxmuu-dev - lightweight X Window System miscellaneous utility library develop
 libxmuu1   - lightweight X Window System miscellaneous utility library
 libxmuu1-dbg - lightweight X Window System miscellaneous utility library 
(unstri
 libxp-dev  - X Window System printing extension library development files
 libxp6 - X Window System printing extension library
 libxp6-dbg - X Window System printing extension library (unstripped)
 libxpm-dev - X pixmap library development files
 libxpm4- X pixmap library
 libxpm4-dbg - X pixmap library (unstripped)
 libxrandr-dev - X Window System Resize, Rotate and Reflection extension 
library d
 libxrandr2 - X Window System Resize, Rotate and Reflection extension library
 libxrandr2-dbg - X Window System Resize, Rotate and Reflection extension 
library (
 libxt-dev  - X Toolkit Intrinsics development files
 libxt6 - X Toolkit Intrinsics
 libxt6-dbg - X Toolkit Intrinsics (unstripped)
 libxtrap-dev - X Window System protocol-trapping extension library development 
f
 libxtrap6  - X Window System protocol-trapping extension library
 libxtrap6-dbg - X Window System protocol-trapping extension library 
(unstripped)
 libxtst-dev - X Window System event recording and testing extension library dev
 libxtst6   - X Window System event recording and testing extension library
 libxtst6-dbg - X Window System event recording and testing extension library 
(un
 libxv-dev  - X Window System video extension library development files
 libxv1 - X Window System video

Processing of xfree86_4.3.0.dfsg.1-4_powerpc.changes

2004-05-29 Thread Archive Administrator
xfree86_4.3.0.dfsg.1-4_powerpc.changes uploaded successfully to localhost
along with the files:
  xfree86_4.3.0.dfsg.1-4.dsc
  xfree86_4.3.0.dfsg.1-4.diff.gz
  lbxproxy_4.3.0.dfsg.1-4_powerpc.deb
  libdps1_4.3.0.dfsg.1-4_powerpc.deb
  libdps1-dbg_4.3.0.dfsg.1-4_powerpc.deb
  libdps-dev_4.3.0.dfsg.1-4_powerpc.deb
  libice6_4.3.0.dfsg.1-4_powerpc.deb
  libice6-dbg_4.3.0.dfsg.1-4_powerpc.deb
  libice-dev_4.3.0.dfsg.1-4_powerpc.deb
  libsm6_4.3.0.dfsg.1-4_powerpc.deb
  libsm6-dbg_4.3.0.dfsg.1-4_powerpc.deb
  libsm-dev_4.3.0.dfsg.1-4_powerpc.deb
  libx11-6_4.3.0.dfsg.1-4_powerpc.deb
  libx11-6-dbg_4.3.0.dfsg.1-4_powerpc.deb
  libx11-dev_4.3.0.dfsg.1-4_powerpc.deb
  libxaw6_4.3.0.dfsg.1-4_powerpc.deb
  libxaw6-dbg_4.3.0.dfsg.1-4_powerpc.deb
  libxaw6-dev_4.3.0.dfsg.1-4_powerpc.deb
  libxaw7_4.3.0.dfsg.1-4_powerpc.deb
  libxaw7-dbg_4.3.0.dfsg.1-4_powerpc.deb
  libxaw7-dev_4.3.0.dfsg.1-4_powerpc.deb
  libxext6_4.3.0.dfsg.1-4_powerpc.deb
  libxext6-dbg_4.3.0.dfsg.1-4_powerpc.deb
  libxext-dev_4.3.0.dfsg.1-4_powerpc.deb
  libxft1_4.3.0.dfsg.1-4_powerpc.deb
  libxft1-dbg_4.3.0.dfsg.1-4_powerpc.deb
  libxi6_4.3.0.dfsg.1-4_powerpc.deb
  libxi6-dbg_4.3.0.dfsg.1-4_powerpc.deb
  libxi-dev_4.3.0.dfsg.1-4_powerpc.deb
  libxmu6_4.3.0.dfsg.1-4_powerpc.deb
  libxmu6-dbg_4.3.0.dfsg.1-4_powerpc.deb
  libxmu-dev_4.3.0.dfsg.1-4_powerpc.deb
  libxmuu1_4.3.0.dfsg.1-4_powerpc.deb
  libxmuu1-dbg_4.3.0.dfsg.1-4_powerpc.deb
  libxmuu-dev_4.3.0.dfsg.1-4_powerpc.deb
  libxp6_4.3.0.dfsg.1-4_powerpc.deb
  libxp6-dbg_4.3.0.dfsg.1-4_powerpc.deb
  libxp-dev_4.3.0.dfsg.1-4_powerpc.deb
  libxpm4_4.3.0.dfsg.1-4_powerpc.deb
  libxpm4-dbg_4.3.0.dfsg.1-4_powerpc.deb
  libxpm-dev_4.3.0.dfsg.1-4_powerpc.deb
  libxrandr2_4.3.0.dfsg.1-4_powerpc.deb
  libxrandr2-dbg_4.3.0.dfsg.1-4_powerpc.deb
  libxrandr-dev_4.3.0.dfsg.1-4_powerpc.deb
  libxt6_4.3.0.dfsg.1-4_powerpc.deb
  libxt6-dbg_4.3.0.dfsg.1-4_powerpc.deb
  libxt-dev_4.3.0.dfsg.1-4_powerpc.deb
  libxtrap6_4.3.0.dfsg.1-4_powerpc.deb
  libxtrap6-dbg_4.3.0.dfsg.1-4_powerpc.deb
  libxtrap-dev_4.3.0.dfsg.1-4_powerpc.deb
  libxtst6_4.3.0.dfsg.1-4_powerpc.deb
  libxtst6-dbg_4.3.0.dfsg.1-4_powerpc.deb
  libxtst-dev_4.3.0.dfsg.1-4_powerpc.deb
  libxv1_4.3.0.dfsg.1-4_powerpc.deb
  libxv1-dbg_4.3.0.dfsg.1-4_powerpc.deb
  libxv-dev_4.3.0.dfsg.1-4_powerpc.deb
  proxymngr_4.3.0.dfsg.1-4_powerpc.deb
  twm_4.3.0.dfsg.1-4_powerpc.deb
  xbase-clients_4.3.0.dfsg.1-4_powerpc.deb
  xdm_4.3.0.dfsg.1-4_powerpc.deb
  xfs_4.3.0.dfsg.1-4_powerpc.deb
  xfwp_4.3.0.dfsg.1-4_powerpc.deb
  xlibmesa-dri_4.3.0.dfsg.1-4_powerpc.deb
  xlibmesa-dri-dbg_4.3.0.dfsg.1-4_powerpc.deb
  xlibmesa-gl_4.3.0.dfsg.1-4_powerpc.deb
  xlibmesa-gl-dbg_4.3.0.dfsg.1-4_powerpc.deb
  xlibmesa-gl-dev_4.3.0.dfsg.1-4_powerpc.deb
  xlibmesa-glu_4.3.0.dfsg.1-4_powerpc.deb
  xlibmesa-glu-dbg_4.3.0.dfsg.1-4_powerpc.deb
  xlibmesa-glu-dev_4.3.0.dfsg.1-4_powerpc.deb
  xlibosmesa4_4.3.0.dfsg.1-4_powerpc.deb
  xlibosmesa4-dbg_4.3.0.dfsg.1-4_powerpc.deb
  xlibosmesa-dev_4.3.0.dfsg.1-4_powerpc.deb
  xlibs-static-dev_4.3.0.dfsg.1-4_powerpc.deb
  xlibs-static-pic_4.3.0.dfsg.1-4_powerpc.deb
  xmh_4.3.0.dfsg.1-4_powerpc.deb
  xnest_4.3.0.dfsg.1-4_powerpc.deb
  xprt_4.3.0.dfsg.1-4_powerpc.deb
  xserver-common_4.3.0.dfsg.1-4_powerpc.deb
  xserver-xfree86_4.3.0.dfsg.1-4_powerpc.deb
  xserver-xfree86-dbg_4.3.0.dfsg.1-4_powerpc.deb
  xterm_4.3.0.dfsg.1-4_powerpc.deb
  xutils_4.3.0.dfsg.1-4_powerpc.deb
  xvfb_4.3.0.dfsg.1-4_powerpc.deb
  x-window-system-core_4.3.0.dfsg.1-4_powerpc.deb
  x-window-system-dev_4.3.0.dfsg.1-4_powerpc.deb
  xlibmesa3_4.3.0.dfsg.1-4_powerpc.deb
  pm-dev_4.3.0.dfsg.1-4_all.deb
  x-dev_4.3.0.dfsg.1-4_all.deb
  xfonts-100dpi_4.3.0.dfsg.1-4_all.deb
  xfonts-100dpi-transcoded_4.3.0.dfsg.1-4_all.deb
  xfonts-75dpi_4.3.0.dfsg.1-4_all.deb
  xfonts-75dpi-transcoded_4.3.0.dfsg.1-4_all.deb
  xfonts-base_4.3.0.dfsg.1-4_all.deb
  xfonts-base-transcoded_4.3.0.dfsg.1-4_all.deb
  xfonts-cyrillic_4.3.0.dfsg.1-4_all.deb
  xfonts-scalable_4.3.0.dfsg.1-4_all.deb
  xfree86-common_4.3.0.dfsg.1-4_all.deb
  xlibs_4.3.0.dfsg.1-4_all.deb
  xlibs-data_4.3.0.dfsg.1-4_all.deb
  xspecs_4.3.0.dfsg.1-4_all.deb
  x-window-system_4.3.0.dfsg.1-4_all.deb
  xlibmesa3-dbg_4.3.0.dfsg.1-4_all.deb
  xlibmesa-dev_4.3.0.dfsg.1-4_all.deb
  xlibs-dbg_4.3.0.dfsg.1-4_all.deb
  xlibs-dev_4.3.0.dfsg.1-4_all.deb
  xlibs-pic_4.3.0.dfsg.1-4_all.deb

Greetings,

Your Debian queue daemon



Bug#250655: xterm: crashes on paste from abiword

2004-05-29 Thread Thomas Dickey
On Fri, May 28, 2004 at 10:27:16PM -0500, Branden Robinson wrote:
> On Fri, May 28, 2004 at 06:45:39AM -0400, Thomas Dickey wrote:
> > On Fri, May 28, 2004 at 05:17:45AM -0500, Branden Robinson wrote:
> > > On Wed, May 26, 2004 at 05:03:43PM -0400, Thomas Dickey wrote:
> > > > On Wed, May 26, 2004 at 03:10:08AM +0200, Thomas Dickey wrote:
> > > > 
> > > > Running xterm against current XFree86, this problem does not appear.
> > > 
> > > By "current XFree86", do you mean Debian's latest packages of it,
> > > XFree86 4.4.0, or XFree86 CVS HEAD?
> > 
> > I was looking at the latter.  (I do have a build tree for 4.4.0, but since I
> > made a few fixes for Xt, was looking at the current code, partly to see if
> > there were other fixes I might make).
> 
> Okay, I will be patient while you explore this.

no problem (just a lot of things to work through).
 
-- 
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net


pgpdpVopYEdyp.pgp
Description: PGP signature


Bug#251319: acknowledged by developer (Re: Bug#251319: [xbase-clients] /etc/X11/xinit/xserverrc calls X the wrong way)

2004-05-29 Thread Daniel
Hm, I still disagree with you about whether the commandline of the
Xserver is the right place to put hardware-specific information and
wether a default value should be put there. But if you insist on doing
that, what about showing a notice to that effect during the
installation? Would have saved me half an hour of finding the culprit.

regards,
Daniel



Bug#251307: xserver-xfree86: A problem with the new ATI driver: XVideo apps crash X server (on ATI Range IIc (Mach64) card)

2004-05-29 Thread Michel Dänzer
tags 251307 - moreinfo upstream
thanks

On Sat, 2004-05-29 at 04:09 -0500, Branden Robinson wrote:
> 
> On Fri, May 28, 2004 at 12:50:28AM +0300, Modestas Vainius wrote:
> > 
> > Symbol xf86XVCopyYUV12ToPacked from module 
> > /usr/X11R6/lib/modules/drivers/atimisc_drv.o is unresolved!
> > 
> > which yields the following error on crash:
> > 
> > This should not happen!
> > An unresolved function was called!
> 
> This is quite strange.  According to objdump:
> 
> % objdump --dynamic-syms /usr/X11R6/bin/XFree86 | grep xf86XVCopyYUV12ToPacked
> 10070394 gDF .text  01ac  Basexf86XVCopyYUV12ToPacked
> 
> What does this command say for you?
> 
> I've looked over the sources and this is not a symbol that has to be
> imported; it, along with the rest of XVideo appears to be in the part of
> the XFree86 X server that is resident in memory all the time (else it
> wouldn't appear in objdump).

X server symbols aren't automatically visible to modules though; they
need to be exported with SYMFUNC() in
xc/programs/Xserver/hw/xfree86/loader/xf86sym.c . It looks like that
file was overlooked in the patch.


-- 
Earthling Michel Dänzer  | Debian (powerpc), X and DRI developer
Libre software enthusiast|   http://svcs.affero.net/rm.php?r=daenzer





Processed: Re: Bug#251307: xserver-xfree86: A problem with the new ATI driver: XVideo apps crash X server (on ATI Range IIc (Mach64) card)

2004-05-29 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

> tags 251307 - moreinfo upstream
Bug#251307: xserver-xfree86: [ati/atimisc] XVideo apps crash X server; 
complaints of unresolved symbol xf86XVCopyYUV12ToPacked on 3D Rage IIC AGP rev 
122
Tags were: upstream moreinfo sid
Tags removed: moreinfo, upstream

> thanks
Stopping processing here.

Please contact me if you need assistance.

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



Incomplete upload found in Debian upload queue

2004-05-29 Thread Archive Administrator
Probably you are the uploader of the following file(s) in
the Debian upload queue directory:
  xfree86_4.3.0.dfsg.1-4.diff.gz
  xfree86_4.3.0.dfsg.1-4.dsc
This looks like an upload, but a .changes file is missing, so the job
cannot be processed.

If no .changes file arrives within 23:08:25, the files will be deleted.

If you didn't upload those files, please just ignore this message.

Greetings,

Your Debian queue daemon



Re: dexconf should default to PCI:1:0:0 ?

2004-05-29 Thread Bill Allombert
On Sat, May 29, 2004 at 03:56:03AM -0500, Branden Robinson wrote:
> On Thu, May 27, 2004 at 11:03:24AM +0200, Bill Allombert wrote:
> > Hello X Strike Force,
> > 
> > I have just made a sarge install and I found that
> > dexconf default to PCI:0:1:0. 
> 
> That's just about completely incorrect.
> 
> More accurately, it defaults to:
>   1) whatever lspci says the first VGA compatible device is, if lspci is
>  available, returns information, and (if you have more than one video
>  card or if you're on a PowerPC);

This is not the case here. dexconf default to PCI:0:1:0, but I have
:00:01.0 PCI bridge: Intel Corp. 82865G/PE/P PCI to AGP Controller (rev 02)
:01:00.0 VGA compatible controller: ATI Technologies Inc Radeon RV250 If 
[Radeon 9000] (rev 01)

> Let's look at the code, shall we?
> 
> VIDEO_CARD=$(LC_ALL=C lspci -n | grep "Class 0300:" | head -n 1 | cut -d\ 
>  -f1)
> if [ -n "$VIDEO_CARD" ]; then
>   # we now have an entry in "hex:hex.hex" format, need 
> "PCI:decimal:decimal:decimal"
>   BUS=$(printf "%d" 0x$(echo $VIDEO_CARD | cut -d: -f1) )
>   DEVICE=$(printf "%d" 0x$(echo $VIDEO_CARD | cut -d: -f2 | cut -d. -f1) )
>   FUNCTION=$(printf "%d" 0x$(echo $VIDEO_CARD | cut -d. -f2) )
>   DEFAULT=PCI:$BUS:$DEVICE:$FUNCTION
> fi
>   fi
> fi

OK, that settle it: VIDEO_CARD is :01:00.0, which is the correct device, 
but then DEFAULT is set incorrectly, apparently it expects a different lspci
format.

As a matter of fact:

$ VIDEO_CARD="0:1:2.3"
$ BUS=$(printf "%d" 0x$(echo $VIDEO_CARD | cut -d: -f1) )
$ DEVICE=$(printf "%d" 0x$(echo $VIDEO_CARD | cut -d: -f2 | cut -d. -f1) )
$ FUNCTION=$(printf "%d" 0x$(echo $VIDEO_CARD | cut -d. -f2)
$ DEFAULT=PCI:$BUS:$DEVICE:$FUNCTION
$ echo $DEFAULT
PCI:0:1:3

I have done a straight d-i sarge install:
ii  pciutils   2.1.11-8   Linux PCI Utilities (for 2.*.* kernels)

> > I expect most box to have a video adapter on the AGP port nowadays, so
> > PCI:1:0:0 seems a better default.
> 
> I think you're proceeding from an invalid assumption; namely that
> "PCI:0:1:0" is some sort of hard-coded default.

This is true, because "PCI:0:1:0" seemed like an hardcoded value. 

> > Also it is unfortunate XFree86 and lspci does not use the same exact
> > format for PCI ids, (lspci give :01:00.0, but XFree86 want
> > PCI:1:0:0) so I ended up slighlty confused...
> 
> The debconf template explains the format, and cautions about the
> difference between decimal and hexadecimal.

The template explains the old lspci format, not the new one.
But anyway I did a similar mistake than your script by assuming
the old behaviour.

> I am unwilling to change the format of the BusID parameter that the
> XFree86 X server accepts.  To do would render people's XF86Config-4
> files incompatible between distributions.
> 
> If you have suggestions for how the following can be improved, please
> offer them.

Maybe a -X option to lspci that output XF86Config compatible ids would
be nice. Also this would allow lspci -n to change output without
breaking dexconf. Especially since lspci -n format is not documented.

Cheers,
-- 
Bill. <[EMAIL PROTECTED]>

Imagine a large red swirl here. 



Bug#246869: xserver-xfree86: some keyboard buttons are not functioning properly after dist-upgrade

2004-05-29 Thread Branden Robinson
On Fri, May 28, 2004 at 08:05:07AM +0100, Eddie Baker wrote:
> > Can you please downgrade xlibs to 4.3.0-7 (no need to downgrade other
> > packages) and see if this bug still occurs?
> 
> Having a similar problem here, present in dfsg.1-1 and dfsg.1-2 (not
> related to the numlock problem in dfsg.1-2).
> 
> Downgrading xlibs to 4.3.0-7 fixes it.

If you still experience this problem in dfsg.1-3, please file a new bug,
using the "reportbug" command from the package of the same name, against
the "xlibs" package.

-- 
G. Branden Robinson|It's extremely difficult to govern
Debian GNU/Linux   |when you control all three branches
[EMAIL PROTECTED] |of government.
http://people.debian.org/~branden/ |-- John Feehery


signature.asc
Description: Digital signature


Bug#251568: xserver-xfree86: X startup fails with PCI ID specified in XF86Config-4

2004-05-29 Thread Andree Leidenfrost
Package: xserver-xfree86
Version: 4.3.0.dfsg.1-1
Severity: normal

This is on a virgin Sarge installation after initial X configuration. It
happens reproducibly using d-i beta4 and daily 040528.

If the BusID line is commented out in the Device section, X starts
successfully (albeit with a suboptimal resolution of 800x600).

Cheers
Andree


-- Package-specific info:
Contents of /var/lib/xfree86/X.roster:
xserver-xfree86

/etc/X11/X target unchanged from checksum in /var/lib/xfree86/X.md5sum.

X server symlink status:
lrwxrwxrwx1 root root   20 2004-05-29 17:57 /etc/X11/X
-> /usr/bin/X11/XFree86
-rwxr-xr-x1 root root  1743788 2004-04-29 04:23
/usr/bin/X11/XFree86

Contents of /var/lib/xfree86/XF86Config-4.roster:
xserver-xfree86

VGA-compatible devices on PCI bus:
:01:00.0 VGA compatible controller: ATI Technologies Inc Radeon
RV250 If [Radeon 9000] (rev 01)
:01:00.0 Class 0300: 1002:4966 (rev 01)

/etc/X11/XF86Config-4 unchanged from checksum in
/var/lib/xfree86/XF86Config-4.md5sum.

XFree86 X server configuration file status:
-rw-r--r--1 root root 2891 2004-05-29 17:57
/etc/X11/XF86Config-4

Contents of /etc/X11/XF86Config-4:
# XF86Config-4 (XFree86 X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool,
using
# values from the debconf database.
#
# Edit this file with caution, and see the XF86Config-4 manual page.
# (Type "man XF86Config-4" at the shell prompt.)
#
# This file is automatically updated on xserver-xfree86 package upgrades
*only*
# if it has not been modified since the last upgrade of the
xserver-xfree86
# package.
#
# If you have edited this file but would like it to be automatically
updated
# again, run the following commands as root:
#
#   cp /etc/X11/XF86Config-4 /etc/X11/XF86Config-4.custom
#   md5sum /etc/X11/XF86Config-4 > /var/lib/xfree86/XF86Config-4.md5sum
#   dpkg-reconfigure xserver-xfree86
Section "Files"
FontPath"unix/:7100"# local font server
# if the local font server has problems, we can fall back on these
FontPath"/usr/lib/X11/fonts/misc"
FontPath"/usr/lib/X11/fonts/cyrillic"
FontPath"/usr/lib/X11/fonts/100dpi/:unscaled"
FontPath"/usr/lib/X11/fonts/75dpi/:unscaled"
FontPath"/usr/lib/X11/fonts/Type1"
FontPath"/usr/lib/X11/fonts/CID"
FontPath"/usr/lib/X11/fonts/Speedo"
FontPath"/usr/lib/X11/fonts/100dpi"
FontPath"/usr/lib/X11/fonts/75dpi"
EndSection
Section "Module"
Load"GLcore"
Load"bitmap"
Load"dbe"
Load"ddc"
Load"dri"
Load"extmod"
Load"freetype"
Load"glx"
Load"int10"
Load"record"
Load"speedo"
Load"type1"
Load"vbe"
EndSection
Section "InputDevice"
Identifier  "Generic Keyboard"
Driver  "keyboard"
Option  "CoreKeyboard"
Option  "XkbRules"  "xfree86"
Option  "XkbModel"  "pc104"
Option  "XkbLayout" "us"
EndSection
Section "InputDevice"
Identifier  "Configured Mouse"
Driver  "mouse"
Option  "CorePointer"
Option  "Device""/dev/input/mice"
Option  "Protocol"  "ImPS/2"
Option  "Emulate3Buttons"   "true"
Option  "ZAxisMapping"  "4 5"
EndSection
Section "Device"
Identifier  "Generic Video Card"
Driver  "ati"
BusID   "PCI:0:1:0"
EndSection
Section "Monitor"
Identifier  "Philips 170B2PHL"
HorizSync   28-50
VertRefresh 43-75
Option  "DPMS"
EndSection
Section "Screen"
Identifier  "Default Screen"
Device  "Generic Video Card"
Monitor "Philips 170B2PHL"
DefaultDepth24
SubSection "Display"
Depth   1
Modes   "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth   4
Modes   "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth   8
Modes   "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth   15
Modes   "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth   16
Modes   "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth   24
Modes   "800x600" "640x480"
EndSubSection
EndSection
Section "ServerLayout"
Identifier  "Default La

Bug#251307: xserver-xfree86: X crashes when using Xine

2004-05-29 Thread Branden Robinson
On Thu, May 27, 2004 at 08:18:17PM -0400, Rob Bochan wrote:
> Package: xserver-xfree86
> Version: 4.3.0.dfsg.1-2
> Severity: normal
> Followup-For: Bug #251307
> 
> Since the most recent upgrade to xserver-xfree86_4.3.0.dfsg.1-2 (i386), X
> crashes when trying to view a video file with Xine (xine-ui 0.99.1-1,
> libxine1 1-rc4a-1). This was not the case until this most recent upgrade of
> the xserver packages.
> 
> Machine info: HP Omnibook 6000 Laptop, P-III 700/384 meg RAM, ATI Mobility 3D
> graphics w/8 meg video RAM
[...]
> (--) PCI:*(1:0:0) ATI Technologies Inc Rage Mobility P/M AGP 2x rev 100, Mem 
> @ 0xf500/24, 0xf410/12, I/O @ 0x9000/8
[...]
> Symbol xf86XVCopyYUV12ToPacked from module 
> /usr/X11R6/lib/modules/drivers/atimisc_drv.o is unresolved!

Please see the message I sent to the bug submitter, and supply this bug
with the same information I requested of him:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=251307

-- 
G. Branden Robinson|To Republicans, limited government
Debian GNU/Linux   |means not assisting people they
[EMAIL PROTECTED] |would sooner see shoveled into mass
http://people.debian.org/~branden/ |graves.  -- Kenneth R. Kahn


signature.asc
Description: Digital signature


Bug#251359: xserver-xfree86: xmodmap not supported anymore

2004-05-29 Thread Branden Robinson
tag 251359 + moreinfo
thanks

On Fri, May 28, 2004 at 09:48:23AM +0200, Didrik Pinte wrote:
> Package: xserver-xfree86
> Version: 4.3.0.dfsg.1-2
> Severity: normal
> Tags: sid
> 
> Hi, since i've update my Sid system to xfree86-4.3.0.dfsg.1-2, the 
> mapping i've defined in the file /etc/X11/Xmodmap is not supported 
> anymore.

xmodmap has been deprecated for literally years.

If you would send us a copy of your /etc/X11/Xmodmap, perhaps we can
help you come up with a way to achieve what you want using XKB.

-- 
G. Branden Robinson| When I die I want to go peacefully
Debian GNU/Linux   | in my sleep like my ol' Grand
[EMAIL PROTECTED] | Dad...not screaming in terror like
http://people.debian.org/~branden/ | his passengers.


signature.asc
Description: Digital signature


Processed: Re: Bug#251359: xserver-xfree86: xmodmap not supported anymore

2004-05-29 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

> tag 251359 + moreinfo
Bug#251359: xserver-xfree86: xmodmap not supported anymore
Tags were: sid
Tags added: moreinfo

> thanks
Stopping processing here.

Please contact me if you need assistance.

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



Bug#251037: More info on strange xdmcp behavior

2004-05-29 Thread Branden Robinson
On Thu, May 27, 2004 at 08:12:30PM +0200, Bartłomiej Ochman wrote:
> I've discovered, what are those IPs, they were on my lo:1...lo:5 set by 
> some software I use to block access from there. But then, why has it used 
> them instead of outgoing eth0?
> 
> I'd consider it still a bug.

Does it sound like this one?:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=4757

-- 
G. Branden Robinson|
Debian GNU/Linux   |Yeah, that's what Jesus would do.
[EMAIL PROTECTED] |Jesus would bomb Afghanistan. Yeah.
http://people.debian.org/~branden/ |


signature.asc
Description: Digital signature


Bug#251319: marked as done ([xbase-clients] /etc/X11/xinit/xserverrc calls X the wrong way)

2004-05-29 Thread Debian Bug Tracking System
Your message dated Sat, 29 May 2004 04:14:01 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#251319: [xbase-clients] /etc/X11/xinit/xserverrc calls X 
the wrong way
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 May 2004 23:59:56 +
>From [EMAIL PROTECTED] Thu May 27 16:59:56 2004
Return-path: <[EMAIL PROTECTED]>
Received: from nat-ph3-wh.rz.uni-karlsruhe.de (localhost) [129.13.73.33] 
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1BTUmy-Zy-00; Thu, 27 May 2004 16:59:56 -0700
Received: from daniel by localhost with local (Exim 4.32)
id 1BTUe8-00010v-Bo
for [EMAIL PROTECTED]; Fri, 28 May 2004 01:50:48 +0200
Date: Fri, 28 May 2004 01:50:48 +0200
To: [EMAIL PROTECTED]
Subject: [xbase-clients] /etc/X11/xinit/xserverrc calls X the wrong way
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.5.1+cvs20040105i
From: Daniel <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 

Package: xbase-clients
Version: 4.3.0.dfsg.1-1

/etc/X11/xinit/xserverrc calls X like that:
'exec /usr/bin/X11/X -dpi 100 -nolisten tcp'

The '-dpi 100' bit is wrong. It overrides anything you might have
written in the config file, which is very annoying. The config file has a
way to specify the screen size. The config file is the correct place to
put this information. The commandline in some script is _not_.

---
Received: (at 251319-done) by bugs.debian.org; 29 May 2004 09:14:02 +
>From [EMAIL PROTECTED] Sat May 29 02:14:02 2004
Return-path: <[EMAIL PROTECTED]>
Received: from dhcp065-026-182-085.indy.rr.com (redwald.deadbeast.net) 
[65.26.182.85] 
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1BTzuk-0002D4-00; Sat, 29 May 2004 02:14:02 -0700
Received: by redwald.deadbeast.net (Postfix, from userid 1000)
id 9DB19649DC; Sat, 29 May 2004 04:14:01 -0500 (EST)
Date: Sat, 29 May 2004 04:14:01 -0500
From: Branden Robinson <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: Bug#251319: [xbase-clients] /etc/X11/xinit/xserverrc calls X the 
wrong way
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="W/D3X8sky0X3AmG5"
Content-Disposition: inline
In-Reply-To: <[EMAIL PROTECTED]>
Mail-Copies-To: nobody
X-No-CC: I subscribe to this list; do not CC me on replies.
User-Agent: Mutt/1.5.6i
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 


--W/D3X8sky0X3AmG5
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, May 28, 2004 at 01:50:48AM +0200, Daniel wrote:
> Package: xbase-clients
> Version: 4.3.0.dfsg.1-1
>=20
> /etc/X11/xinit/xserverrc calls X like that:
> 'exec /usr/bin/X11/X -dpi 100 -nolisten tcp'
>=20
> The '-dpi 100' bit is wrong. It overrides anything you might have
> written in the config file, which is very annoying. The config file has a
> way to specify the screen size. The config file is the correct place to
> put this information. The commandline in some script is _not_.

The issue is significantly more complex than you imply.

Permit me to refer you to the Debian X FAQ.

http://necrotic.deadbeast.net/xsf/XFree86/trunk/debian/local/FAQ

  *) Why are some fonts (or graphical rulers) sized incorrectly?

  Programs that try to optimize font sizes for better screen output (such as
  FontConfig-based applications) and those that try to show real-world geom=
etry
  (like inch/centimeter scales in the GIMP) need to know the pixel density =
of
  the display to be accurate.  This value is the ratio of the display's pix=
el
  resolution to the physical size of your monitor -- generally between 70 a=
nd
  120 DPI (dots per inch).  If the DPI value used by the X server does not

thank you, Andreas Metzler

2004-05-29 Thread Branden Robinson
Andreas,

Thanks for handling the merges of the duplicate reports of XKB trouble
caused by xfree86 4.3.0.dfsg.1-2.

Your machine-gun-like efficiency has helped preserve what little sanity
I have left.

Interestingly, I found out where that backwards-time-warping diff came
from.

It came straight out of a CVS diff command.  But not one you might
expect:

xc/programs/xkbcomp % cvs diff -N -r xf-4_3-branch -D "2003/04/30" types/basic
Index: types/basic
===
RCS file: /cvs/xc/programs/xkbcomp/types/basic,v
retrieving revision 1.1.1.4
retrieving revision 1.1
diff -u -r1.1.1.4 -r1.1
--- types/basic 16 Jan 2001 23:00:29 -  1.1.1.4
+++ types/basic 27 Apr 1994 07:21:51 -  1.1
@@ -1,39 +1,28 @@

Huh?

[0] [EMAIL PROTECTED]:~/packages/xfree86/cvs % diff -u 
{xf-4_3-branch,xfree86-CVS-pre-4.4.0-RC3-new-license-sanitized}/xc/programs/xkbcomp/types/basic
--- xf-4_3-branch/xc/programs/xkbcomp/types/basic   2001-01-16 
18:00:29.0 -0500
+++ 
xfree86-CVS-pre-4.4.0-RC3-new-license-sanitized/xc/programs/xkbcomp/types/basic 
2003-11-03 00:36:35.0 -0500
@@ -1,4 +1,5 @@
 // $Xorg: basic,v 1.3 2000/08/17 19:54:48 cpqbld Exp $
+// $XFree86: xc/programs/xkbcomp/types/basic,v 1.3 2003/11/03 05:36:35 tsi Exp 
$
 default xkb_types "basic" {

 // Fairly standard definitions for
@@ -20,11 +21,11 @@
 };

 type "ALPHABETIC" {
-   modifiers = Shift+Lock;
-   map[Shift] = Level2;
-   preserve[Lock]= Lock;
-   level_name[Level1] = "Base";
-   level_name[Level2] = "Caps";
+modifiers = Shift+Lock;
+map[Shift] = Level2;
+map[Lock] = Level2;
+level_name[Level1] = "Base";
+level_name[Level2] = "Caps";
 };

 type "KEYPAD" {

As far as I can tell -- and I looked carefully -- this was the only file that
exhibited this crazy behavior.

Bizarre.  Completely bizarre.

-- 
G. Branden Robinson| Eternal vigilance is the price of
Debian GNU/Linux   | liberty.
[EMAIL PROTECTED] | -- Wendell Phillips
http://people.debian.org/~branden/ |


signature.asc
Description: Digital signature


Bug#251307: xserver-xfree86: A problem with the new ATI driver: XVideo apps crash X server (on ATI Range IIc (Mach64) card)

2004-05-29 Thread Branden Robinson
tag 251307 + moreinfo upstream
retitle 251307 xserver-xfree86: [ati/atimisc] XVideo apps crash X server; 
complaints of unresolved symbol xf86XVCopyYUV12ToPacked on 3D Rage IIC AGP rev 
122
thanks

On Fri, May 28, 2004 at 12:50:28AM +0300, Modestas Vainius wrote:
> Package: xserver-xfree86
> Version: 4.3.0.dfsg.1-2
> Severity: important
> Tags: sid
> 
> Hello,
> 
> First of all, thank you for including the new ATI driver. I have used
> the driver from http://gatos.sf.net for a year or so to get Xv support
> for my video card. Finally, the xserver-xfree86 is supposed to support
> XVideo on my pretty old video card out of the box.

Yes, I was hoping this would make some people happy.

> However, there is one problem currently. It seems that any XVideo app
> (I have tested mplayer and kaffeine (xine)) brings the X server down.
> /var/log/XFree86.0.log.old provides good hints though. I have attached this
> file it doesn't get included in the report automatically.
> /var/log/XFree86.0.log.old has the log of the X server instance which was 
> crashed by mplayer. /var/log/XFree86.0.log (automatically included)
> is from the currently running X server instance. I think, the cause of
> my problem is the unresolved symbol:
> 
> Symbol xf86XVCopyYUV12ToPacked from module 
> /usr/X11R6/lib/modules/drivers/atimisc_drv.o is unresolved!
> 
> which yields the following error on crash:
> 
>   This should not happen!
>   An unresolved function was called!

This is quite strange.  According to objdump:

% objdump --dynamic-syms /usr/X11R6/bin/XFree86 | grep xf86XVCopyYUV12ToPacked
10070394 gDF .text  01ac  Basexf86XVCopyYUV12ToPacked

What does this command say for you?

I've looked over the sources and this is not a symbol that has to be
imported; it, along with the rest of XVideo appears to be in the part of
the XFree86 X server that is resident in memory all the time (else it
wouldn't appear in objdump).

For that matter:

% objdump --dynamic-syms /usr/X11R6/bin/XFree86 | grep xf86XV
1006c808 gDF .text  0080  Basexf86XVRegisterGenericAdaptorDriver
10070394 gDF .text  01ac  Basexf86XVCopyYUV12ToPacked
1006c9c0 gDF .text  002c  Basexf86XVQueryOffscreenImages
1006c9ec gDF .text  0024  Basexf86XVAllocateVideoAdaptorRec
1006fd98 gDF .text  05fc  Basexf86XVClipVideoHelper
1006ca30 gDF .text  0248  Basexf86XVScreenInit
10070540 gDF .text  009c  Basexf86XVCopyPacked
1006ca10 gDF .text  0020  Basexf86XVFreeVideoAdaptorRec
1006c888 gDF .text  0108  Basexf86XVListGenericAdaptors
1006fbdc gDF .text  01bc  Basexf86XVFillKeyHelper
1006c990 gDF .text  0030  Basexf86XVRegisterOffscreenImages

> Feel free to ask for more information. You may send patches to me.
> I will test them shortly!

Try using xserver-xfree86-dbg instead.  What happens then?

If the symbol were truly unresolved, the package build would fail when the
gigantic, static XFree86 debug binary were linked.  But that doesn't happen.

-- 
G. Branden Robinson|   If atheism is a religion, then
Debian GNU/Linux   |   health is a disease.
[EMAIL PROTECTED] |   -- Clark Adams
http://people.debian.org/~branden/ |


signature.asc
Description: Digital signature


Processed: Re: Bug#251307: xserver-xfree86: A problem with the new ATI driver: XVideo apps crash X server (on ATI Range IIc (Mach64) card)

2004-05-29 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

> tag 251307 + moreinfo upstream
Bug#251307: xserver-xfree86: A problem with the new ATI driver: XVideo apps 
crash X server (on ATI Range IIc (Mach64) card)
Tags were: sid
Tags added: moreinfo, upstream

> retitle 251307 xserver-xfree86: [ati/atimisc] XVideo apps crash X server; 
> complaints of unresolved symbol xf86XVCopyYUV12ToPacked on 3D Rage IIC AGP 
> rev 122
Bug#251307: xserver-xfree86: A problem with the new ATI driver: XVideo apps 
crash X server (on ATI Range IIc (Mach64) card)
Changed Bug title.

> thanks
Stopping processing here.

Please contact me if you need assistance.

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



Processed: Re: Bug#251281: xlibmesa-gl-dev: Uninstalable

2004-05-29 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

> reassign 251281 nvidia-glx
Bug#251281: xlibmesa-gl-dev: Uninstalable
Bug reassigned from package `xlibmesa-gl-dev' to `nvidia-glx'.

> severity 251281 normal
Bug#251281: xlibmesa-gl-dev: Uninstalable
Severity set to `normal'.

> merge 251281 246590
Bug#246590: xlibmesa-gl-dev: install fails while trying to create 
/usr/lib/libGL.so symbolic link
Bug#251281: xlibmesa-gl-dev: Uninstalable
Merged 246590 251281.

> thanks
Stopping processing here.

Please contact me if you need assistance.

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



Inexpenive domain registration,metamorphosis

2004-05-29 Thread Dorothy
Reilly,|

Need affordable but reliable web hosting for only $5/month?

-800 MB Disk Space
-Unlimited email accounts
-FREE Shopping Cart... and much more! 

Please contact us to take advantage of this new offer at  

http://rrunae.thebiggestand.com/amite/host.htm


debauch 


Re: Bug#250915: installation-report

2004-05-29 Thread Branden Robinson
On Thu, May 27, 2004 at 12:30:32PM -0300, Martin Michlmayr wrote:
> * Jason Dobbs <[EMAIL PROTECTED]> [2004-05-25 21:18]:
> > Unfortunately, I could not get the graphics card working
> > for the version of XFree86 (4.3.0.dfsg.1-1) currently in sarge. It's a PCI
> > Diamond Multimedia Stealth 64 Video 2001 Series card with 1MB ram, which
> > has a S3 Trio 64V+ chipset. I tried S3, VESA & VGA drivers, but the best I
> > could come up with was a 640x480 VESA mode. So I installed Woody and got 
> > Xfree86 version 3.3.6 running just fine with a 800x600 16bpp mode. However, 
> > Sarge no longer supports Xfree86 3.3.6, and I would really prefer to be 
> > running
> > Sarge. So I reinstalled Sarge, and tried to build Xfree86 3.3.6 from source.
> > This effort failed, for various reasons (compiler related, I suspect). 
> 
> There are some cards which are no longer supported in 4.x, but I don't
> know if the S3 Trio is one of them.  I'm CCing the debian-x list for
> more comments.  Can you please send the XFree86 logs from 3.3.6?

Please see:

  http://www.xfree86.org/4.3.0/Status29.html

-- 
G. Branden Robinson| The Rehnquist Court has never
Debian GNU/Linux   | encountered a criminal statute it
[EMAIL PROTECTED] | did not like.
http://people.debian.org/~branden/ | -- John Dean


signature.asc
Description: Digital signature


Re: dexconf should default to PCI:1:0:0 ?

2004-05-29 Thread Branden Robinson
On Thu, May 27, 2004 at 11:03:24AM +0200, Bill Allombert wrote:
> Hello X Strike Force,
> 
> I have just made a sarge install and I found that
> dexconf default to PCI:0:1:0. 

That's just about completely incorrect.

More accurately, it defaults to:
  1) whatever lspci says the first VGA compatible device is, if lspci is
 available, returns information, and (if you have more than one video
 card or if you're on a PowerPC);
  2) "1", if you're on an SGI Indigo2 machine;
  3) blank, if neither of the above apply

Let's look at the code, shall we?

# BusID
PRIORITY=low
DEFAULT=

# Some PowerPCs need to be told where to find the video card even if there is
# only one in the machine (broken PCI bus code in the XFree86 X server, most
# likely).  If there are multiple video cards, we need to configure one as the
# primary head.
if [ "$ARCH" = "powerpc" -o "$MULTIHEAD" = "yes" ]; then
  if [ "$ARCH" = "powerpc" ]; then
PRIORITY=medium
  fi
  if [ "$MULTIHEAD" = "yes" ]; then
PRIORITY=high
  fi
  if which lspci > /dev/null 2>&1; then
# try to guess the correct BusID
VIDEO_CARD=$(LC_ALL=C lspci -n | grep "Class 0300:" | head -n 1 | cut -d\  
-f1)
if [ -n "$VIDEO_CARD" ]; then
  # we now have an entry in "hex:hex.hex" format, need 
"PCI:decimal:decimal:decimal"
  BUS=$(printf "%d" 0x$(echo $VIDEO_CARD | cut -d: -f1) )
  DEVICE=$(printf "%d" 0x$(echo $VIDEO_CARD | cut -d: -f2 | cut -d. -f1) )
  FUNCTION=$(printf "%d" 0x$(echo $VIDEO_CARD | cut -d. -f2) )
  DEFAULT=PCI:$BUS:$DEVICE:$FUNCTION
fi
  fi
fi

# SGI Indigo2 XLs require a special hack, per Guido Guenther (see Debian
# #249614).
if [ -e /proc/cpuinfo ]; then
  if grep -q "system type.*:.*SGI Indigo2" /proc/cpuinfo; then
PRIORITY=medium
DEFAULT=1
  fi
fi

> I expect most box to have a video adapter on the AGP port nowadays, so
> PCI:1:0:0 seems a better default.

I think you're proceeding from an invalid assumption; namely that
"PCI:0:1:0" is some sort of hard-coded default.

> Also it is unfortunate XFree86 and lspci does not use the same exact
> format for PCI ids, (lspci give :01:00.0, but XFree86 want
> PCI:1:0:0) so I ended up slighlty confused...

The debconf template explains the format, and cautions about the
difference between decimal and hexadecimal.

I am unwilling to change the format of the BusID parameter that the
XFree86 X server accepts.  To do would render people's XF86Config-4
files incompatible between distributions.

If you have suggestions for how the following can be improved, please
offer them.

Template: xserver-xfree86/config/device/bus_id
Type: string
_Description: Please enter the video card's bus identifier.
 Users of PowerPC machines, and users of any computer with multiple video
 devices, should specify the BusID of the video card in the format:
 .
 PCI:nn:nn:nn
 .
 (where each nn is a decimal number referring to the card's bus, device, and
 function number, respectively).
 .
 For users of multi-head setups, this option will configure only one of the
 heads.  Further configuration will have to be done manually in the X server
 configuration file, /etc/X11/XF86Config-4.
 .
 Users of SGI Indigo2 XL machines should specify simply "1" here.
 .
 You may wish to use the "lspci" command to determine the bus location of your
 PCI or AGP video card.  Keep in mind that lspci reports the bus, device, and
 function numbers in hexadecimal, not decimal.
 .
 When possible, this question has been pre-answered for you and you should
 accept the default unless you know it doesn't work.
 .
 Users of machines other than PowerPCs or SGI Indigo2 XLs with only one video
 card should leave this entry blank.

Does anybody actually read the template descriptions I write?  You're
from France -- is the French translation badly out of date?

#. Type: string
#. Description
#: ../xserver-xfree86.templates:147
msgid "Please enter the video card's bus identifier."
msgstr "Identifiant du bus de la carte vidéo :"

#. Type: string
#. Description
#: ../xserver-xfree86.templates:147
msgid ""
"Users of PowerPC machines, and users of any computer with multiple video "
"devices, should specify the BusID of the video card in the format:"
msgstr ""
"Les utilisateurs de machines PowerPC et les utilisateurs d'ordinateurs avec "
"plusieurs cartes vidéo, doivent préciser l'identifiant du bus de la carte "
"vidéo au format suivant :"

#. Type: string
#. Description
#: ../xserver-xfree86.templates:147
msgid "PCI:nn:nn:nn"
msgstr "PCI:nn:nn:nn"

#. Type: string
#. Description
#: ../xserver-xfree86.templates:147
msgid ""
"(where each nn is a decimal number referring to the card's bus, device, and "
"function number, respectively)."
msgstr ""
"où chaque nn est un nombre décimal qui désigne le numéro, respectivement, du "
"bus, du périphérique et de la fonction."

#. Type: string
#. Description
#: ../xserver-xfree86.templates:147
msgid ""
"For users of multi-head setups, this option will configure only one of the "
"head

Bug#251000: acknowledged by developer (Re: Bug#251000: xlibs-data: keeping /usr/share/i18n/SUPPORTED and /usr/X11R6/lib/X11/locale/locale.alias in sync.)

2004-05-29 Thread Branden Robinson
On Fri, May 28, 2004 at 05:05:04PM +0200, peppe wrote:
> The point is:  why xlibs-data and glibc use the same env
> vars but interpret them differently? That is: why must I set
> LANG="en_US.ISO-8859-15" for libc and LANG="en_US.ISO8859-15" for
> xlibs-data? (Notice the subtle difference, and the impossibility)

Because Xlib's locale handling was implemented before many C libraries
supported locales at all.

I am still stumped as to why you think the lanuage and territory part of
the LC_CTYPE variable are significant.

-- 
G. Branden Robinson|  Mob rule isn't any prettier just
Debian GNU/Linux   |  because you call your mob a
[EMAIL PROTECTED] |  government.
http://people.debian.org/~branden/ |


signature.asc
Description: Digital signature


Re: Start preparing -3

2004-05-29 Thread Branden Robinson
On Fri, May 28, 2004 at 05:33:00AM -0500, Branden Robinson wrote:
> > + #249614: xserver-xfree86: [debconf] autodetect SGI Indy and Indigo2
> >systems
> > 
> > Branden, i would really love to fix this problem ASAP. We have a SGI Indy
> > here at debconf4 that we can use to build and test the fix. If you think
> > that we can't make it in time for debconf4 than we wil include with all
> > the other debconf fixes (that are anyway in this plan).
> 
> Per our discussions today in IRC, this is now on the SVN trunk.

Well, this turned out to be a total abortion.

Please convey my thanks to the "SGI" people who "tested" this change.

:-P

-- 
G. Branden Robinson| If the jury can count higher than
Debian GNU/Linux   | two, the case will fail.
[EMAIL PROTECTED] | -- Tom Lane, on Forgent's claim of
http://people.debian.org/~branden/ |a patent on JPEG


signature.asc
Description: Digital signature


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

2004-05-29 Thread X Strike Force SVN Repository Admin
Author: branden
Date: 2004-05-29 03:13:45 -0500 (Sat, 29 May 2004)
New Revision: 1474

Modified:
   trunk/debian/changelog
Log:
Merge revision 1470 from branches/4.3.0/sid.


Modified: trunk/debian/changelog
===
--- trunk/debian/changelog  2004-05-29 06:07:34 UTC (rev 1473)
+++ trunk/debian/changelog  2004-05-29 08:13:45 UTC (rev 1474)
@@ -1,4 +1,4 @@
-xfree86 (4.3.0.dfsg.1-3+SVN) unstable; urgency=medium
+xfree86 (4.3.0.dfsg.1-4) unstable; urgency=medium
 
   * The "thanks for the 'testing'" release.
 



Bug#250629: xlibs: AltGr stopped working

2004-05-29 Thread deblst
> Check for the existence of the following files:
> 
> $HOME/.Xmodmap
> /etc/X11/Xmodmap

There is neither an /etc/X11/Xmodmap nor any $HOME/.Xmodmap.

Regards
Klaus




Great Software at Great Prices!

2004-05-29 Thread Lackey, Elias


Debian-x,

Are you or your company looking for up to date software?

We sell O E M Software at lowest possible price.

Don't pay the department store markups, buy on the internet.

http://progsforpc.com/index.php?s=


manatee fungus female charlesinscribe tarry kin
hysterectomy yourpc.biz/soft/chair.p hp paraxial rufus sheen half. countersunk 
provost stationmaster indentation lint velvet. gerundial eminent
matinal eclogue commendatory correlate. anger ferment comedian
melcher architectonic frame.wearied tablet doris? dugout tragicomic
hurt amphetamine chloroplast jackson?



[no subject]

2004-05-29 Thread Waleed Al-Hassan








X Strike Force XFree86 SVN commit: r1473 - trunk/debian/patches

2004-05-29 Thread X Strike Force SVN Repository Admin
Author: branden
Date: 2004-05-29 01:07:34 -0500 (Sat, 29 May 2004)
New Revision: 1473

Modified:
   trunk/debian/patches/000_stolen_from_HEAD_xkb_data.diff
Log:
(cosmetic) Update patch annotation.


Modified: trunk/debian/patches/000_stolen_from_HEAD_xkb_data.diff
===
--- trunk/debian/patches/000_stolen_from_HEAD_xkb_data.diff 2004-05-29 
04:58:07 UTC (rev 1472)
+++ trunk/debian/patches/000_stolen_from_HEAD_xkb_data.diff 2004-05-29 
06:07:34 UTC (rev 1473)
@@ -1,8 +1,9 @@
 $Id$
 
 This file is for XKB data.  This basically means any subdirectory of
-xc/programs/xkbcomp.  Changes within xc/program/xkbcomp itself should not
-be here, nor should changes elsewhere in the tree.
+xc/programs/xkbcomp (except xc/programs/xkbcomp/cross).  Changes within
+xc/program/xkbcomp itself should not be here, nor should changes elsewhere
+in the tree.
 
 NOTE: Be careful not to re-code this file!  For instance, I got burned by
 using Vim to edit it in a UTF-8 environment.



Processed: retitle 135692 to xdm: manpage should reference xdm.options manpage in SEE ALSO section

2004-05-29 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.7.95.1
> retitle 135692 xdm: manpage should reference xdm.options manpage in SEE ALSO 
> section
Bug#135692: xdm manpage should reference xdm.options mangpage in SEE ALSO
Changed Bug title.

>
End of message, stopping processing here.

Please contact me if you need assistance.

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



Bug#248940: Processed: Re: Bug#248940: xlibs: strange caps lock lag

2004-05-29 Thread Branden Robinson
[Mr. Xu not mailed directly because his mail server has my mail host
blacklisted.]

retitle 248940 kernel: caps lock key events delayed on Toshiba Libretto L5 
laptop [BUG STALLED BECAUSE HERBERT XU WILL NOT PERMIT IT TO BE REASSIGNED TO 
THE KERNEL; cf. #121335]
thanks

On Sat, May 29, 2004 at 02:08:43PM +1000, Herbert Xu wrote:
> reassign 248940 xlibs
> quit
> 
> On Fri, May 28, 2004 at 09:03:04PM -0700, Debian Bug Tracking System wrote:
> > Processing commands for [EMAIL PROTECTED]:
> > 
> > > reassign 248940 kernel
> > Bug#248940: xlibs: caps lock takes time to disengage with 
> > xfree86/pc101/dvorak on Toshiba Libretto L5 laptop
> > Bug reassigned from package `xlibs' to `kernel'.
> 
> Please cc @packages.debian.org when reassigning.

I did.

  From: Branden Robinson <[EMAIL PROTECTED]>
  To: [EMAIL PROTECTED], [EMAIL PROTECTED]
  Cc: [EMAIL PROTECTED]
  ^^
  Subject: Re: Bug#248940: xlibs: strange caps lock lag
  Date: Fri, 28 May 2004 22:59:58 -0500
  Message-ID: <[EMAIL PROTECTED]>

> In the BTS entry I've found no evidence to indicate that this is a kernel
> bug.

No, it's been suggested that it's a hardware bug, and the OS is the
abstraction layer for the hardware.

> In fact, in raw mode it is up to the user-space appliation to keep track
> of things like caps-lock state.

That's not what's being complained about.  Please read the original
report carefully.

> Therefore it is mostly likely to be an X bug a priori.

Raw mode is supposed to expose an abstract keyboard interface unseasoned
by terminal-related concerns, not every defect in the underlying
hardware.

As the 2.6 kernel likes to tell people, "XFree86 should not access the
hardware directly."  Raw mode is not "accessing the hardware directly".

It's not XFree86's job to work around hardware bugs.  It's the kernel's.

However, I am supremely disinterested in playing your favorite sport
(bug tennis), so I guess this bug will languish until a kernel
person can be troubled to look at it, just like the last Toshiba laptop
keyboard problem you insisted wasn't the kernel's business to deal
with[1][2].  As you said, "There is no way that this patch can be
accepted...Don't bother reassigning it back to me because I will simply
reassign it again with no warning."[3]

Mr. Belmonte, you may want to take your concern directly to the
linux-kernel mailing list, as Mr. Xu is likely, given his past behavior,
to blockade any efforts to resolve this in Debian's kernel.  That his
conception of the meaning of "raw mode" differs from that of the
upstream kernel maintainers does not stop him from imposing his vision
of it on Debian's kernel packages, even after his resignation from the
Debian Project[4].

I apologize for the inconvenience his uncooperative attitude is causing
you.

[1] http://lists.debian.org/debian-x/2003/01/msg00197.html
[2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=121335
[3] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=121335&msg=39
[4] http://lists.debian.org/debian-boot/2004/05/msg00568.html

-- 
G. Branden Robinson|   The software said it required
Debian GNU/Linux   |   Windows 3.1 or better, so I
[EMAIL PROTECTED] |   installed Linux.
http://people.debian.org/~branden/ |


signature.asc
Description: Digital signature


Processed: Re: Processed: Re: Bug#248940: xlibs: strange caps lock lag

2004-05-29 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

> [Mr. Xu not mailed directly because his mail server has my mail host
Unknown command or malformed arguments to command.

> blacklisted.]
Unknown command or malformed arguments to command.

> retitle 248940 kernel: caps lock key events delayed on Toshiba Libretto L5 
> laptop [BUG STALLED BECAUSE HERBERT XU WILL NOT PERMIT IT TO BE REASSIGNED TO 
> THE KERNEL; cf. #121335]
Bug#248940: kernel: caps lock takes time to disengage in raw mode
Changed Bug title.

> thanks
Stopping processing here.

Please contact me if you need assistance.

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