Bug#253088: VT text display gets mangled with Radeon 9200 dualhead setup

[Heikki Kantola]

Package: xserver-xfree86
Version: 4.3.0.dfsg.1-4
Severity: important
Tags: sid

I just noticed that the more recent XFree86 version seem to somehow
interfere the VT text consoles on my Radeon 9200 dualhead setup: VTs
are now unusable as text is oddly striped and it looks like the texts
for both monitors are shown in one on both heads. When booting and
shutting down the system the texts on VT are displayed fine on both 
monitors, so I believe this is problem with X. Earlier this same setup 
also worked ok. I'm using gdm (Debian package version 2.4.4.7-3) to 
start X if that matters.

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

/var/lib/xfree86/X.md5sum does not exist.

X server symlink status:
lrwxrwxrwx1 root root   20 2003-11-29 20:23 /etc/X11/X -> 
/usr/bin/X11/XFree86
-rwxr-xr-x1 root root  1745132 2004-05-29 15:33 /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 RV280 [Radeon 
9200] (rev 01)
:01:00.0 Class 0300: 1002:5961 (rev 01)

/var/lib/xfree86/XF86Config-4.md5sum does not exist.

XFree86 X server configuration file status:
-rw-r--r--1 root root24713 2004-06-06 11:31 
/etc/X11/XF86Config-4

Contents of /etc/X11/XF86Config-4:
# File: XF86Config-4
# File generated by fglrxconfig (C) ATI Research, a substitute for xf86config.

# Note by ATI: the below copyright notice is there for servicing possibly
# pending third party rights on the file format and the instance of this file.
#
# Copyright (c) 1999 by The XFree86 Project, Inc.
#
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
# 
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
# 
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL
# THE XFREE86 PROJECT BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
# 
# Except as contained in this notice, the name of the XFree86 Project shall
# not be used in advertising or otherwise to promote the sale, use or other
# dealings in this Software without prior written authorization from the
# XFree86 Project.
#

# **
# Refer to the XF86Config(4/5) man page for details about the format of 
# this file.
# **

# **
# DRI Section
# **
Section "dri"
# Access to OpenGL ICD is allowed for all users:
Mode 0666
# Access to OpenGL ICD is restricted to a specific user group:
#Group 100# users
#Mode 0660
EndSection

# **
# Module section -- this  section  is used to specify
# which dynamically loadable modules to load.
# **
#
Section "Module"

# This loads the DBE extension module.

Load"dbe"   # Double buffer extension

# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
SubSection  "extmod"
  Option"omit xfree86-dga"   # don't initialise the DGA extension
EndSubSection

# This loads the Type1 and FreeType font modules
Load"type1"
Load"freetype"

# This loads the GLX module
Load"glx"   # libglx.a
Load"dri"   # libdri.a

EndSection

# **
# Files section.  This allows default font and rgb paths to be set
# **

Section "Files"

# The location of the RGB database.  Note, this is the name of the
# file minus the extension (like ".txt" or ".db").  There is normally
# no need to change the default.

RgbPath "/usr/X11R6/lib/X11/rgb"

# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination o

Bug#252214: /usr/X11R6/bin/xev: xev -id misses events

[Thomas Dickey]

On Sun, Jun 06, 2004 at 10:40:32PM -0400, Andrew Pimlott wrote:
> On Sun, Jun 06, 2004 at 10:00:51AM -0400, Andrew Pimlott wrote:
> > It must be something along these lines (note that xterm also does not
> > get motion events, which makes more sense), but in what sense is xterm
> > not listening to button presses?
> 
> BTW, I only used xterm as an example.  I originally observed the problem
> on mozilla, so I'm sure this is a systematic problem with xev (and
> whatever interfaces it uses).  So I wouldn't waste your time looking for
> the answer in xterm.  :-)

I won't (but when I review this email, I'll experiment with that ButtonMask
for the active icon so I understand better what it's doing & if it is
related to the results from xev).

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


pgp9w44W0pmUR.pgp
Description: PGP signature

Bug#253172: xserver-xfree86: Cannot install (preinst fails)

[Philipp]

Package: xserver-xfree86
Version: 4.3.0.dfsg.1-4
Severity: critical
Justification: breaks the whole system

When trying to install xserver-xfree86, the install fails with the error
message that the preinstallation script returned with error code 127.
Trying to use 4.3.0.dfsg.1-1 instead results in the same problem; however
with earlier versions (before .dfsg, but don't ask me the exact version)
i never had this problem. Purging the package (and xserver-common) does
not help.

This is a critical issue because i nowadays use X clients quite
regularly. :)

I had a quick skim through the preinst script, but did not find anything
immediately obvious. Is there a good way to debug preinst scripts ?

I should probably also mention that i use the nvidia binary drivers, but
as this doesn't seem to be a file conflict, i don't think it is related.

I would also be quite happy already if you could point me to an older
copy of xserver-xfree86 (older than what currently is in testing).

TIA,
  Philipp

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.5-fermat.03
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED]

Bug#252754:

[Chris Taylor]

I get much the same error.. DECONF_DEBUG=".*" output follows:

lexington:~# dpkg -i xserver-xfree86_4.3.0.dfsg.1-4_i386.deb
(Reading database ... 77124 files and directories currently installed.)
Unpacking xserver-xfree86 (from xserver-xfree86_4.3.0.dfsg.1-4_i386.deb) ...
debconf (db): making DbDriver of type File
debconf (db config): started; filename is /var/cache/debconf/config.dat
debconf (db config): loading database
debconf (db): making DbDriver of type File
debconf (db passwords): started; filename is
/var/cache/debconf/passwords.dat
debconf (db passwords): loading database
debconf (db): making DbDriver of type Stack
debconf (db): making DbDriver of type File
debconf (db templatedb): started; filename is
/var/cache/debconf/templates.dat
debconf (db templatedb): loading database
debconf (developer): frontend started
debconf (db configdb): trying to getfield(debconf/frontend value) ..
debconf (db configdb): getfield done by config
debconf (user): trying frontend Dialog
debconf (developer): frontend running, package name is xserver-xfree86
debconf (db configdb): trying to
addowner(xserver-xfree86/autodetect_video_card xserver-xfree86 boolean) ..
debconf (db configdb): passing to config ..
debconf (db configdb): trying to addowner(shared/no_known_x-server
xserver-xfree86 note) ..
debconf (db configdb): passing to config ..
debconf (db configdb): trying to addowner(shared/multiple_possible_x-servers
xserver-xfree86 note) ..
debconf (db configdb): passing to config ..
debconf (db configdb): trying to addowner(shared/default-x-server
xserver-xfree86 select) ..
debconf (db configdb): passing to config ..
debconf (db configdb): trying to
addowner(xserver-xfree86/config/write_files_section xserver-xfree86 boolean)
..
debconf (db configdb): passing to config ..
debconf (db configdb): trying to addowner(xserver-xfree86/config/modules
xserver-xfree86 multiselect) ..
debconf (db configdb): passing to config ..
debconf (db configdb): trying to
addowner(xserver-xfree86/multiple_possible_x-drivers xserver-xfree86 note)
..
debconf (db configdb): passing to config ..
debconf (db configdb): trying to
addowner(xserver-xfree86/config/device/identifier xserver-xfree86 string) ..
debconf (db configdb): passing to config ..
debconf (db configdb): trying to
addowner(xserver-xfree86/config/device/driver xserver-xfree86 select) ..
debconf (db configdb): passing to config ..
debconf (db configdb): trying to
addowner(xserver-xfree86/config/device/use_fbdev xserver-xfree86 boolean) ..
debconf (db configdb): passing to config ..
debconf (db configdb): trying to
addowner(xserver-xfree86/config/device/bus_id xserver-xfree86 string) ..
debconf (db configdb): passing to config ..
debconf (db configdb): trying to
addowner(xserver-xfree86/config/device/bus_id_error xserver-xfree86 note) ..
debconf (db configdb): passing to config ..
debconf (db configdb): trying to
addowner(xserver-xfree86/config/device/video_ram xserver-xfree86 string) ..
debconf (db configdb): passing to config ..
debconf (db configdb): trying to
addowner(xserver-xfree86/config/inputdevice/keyboard/internal
xserver-xfree86 string) ..
debconf (db configdb): passing to config ..
debconf (db configdb): trying to
addowner(xserver-xfree86/config/inputdevice/keyboard/rules xserver-xfree86
string) ..
debconf (db configdb): passing to config ..
debconf (db configdb): trying to
addowner(xserver-xfree86/config/inputdevice/keyboard/model xserver-xfree86
string) ..
debconf (db configdb): passing to config ..
debconf (db configdb): trying to
addowner(xserver-xfree86/config/inputdevice/keyboard/layout xserver-xfree86
string) ..
debconf (db configdb): passing to config ..
debconf (db configdb): trying to
addowner(xserver-xfree86/config/inputdevice/keyboard/variant xserver-xfree86
string) ..
debconf (db configdb): passing to config ..
debconf (db configdb): trying to
addowner(xserver-xfree86/config/inputdevice/keyboard/options xserver-xfree86
string) ..
debconf (db configdb): passing to config ..
debconf (db configdb): trying to addowner(xserver-xfree86/autodetect_mouse
xserver-xfree86 boolean) ..
debconf (db configdb): passing to config ..
debconf (db configdb): trying to
addowner(xserver-xfree86/config/inputdevice/mouse/port xserver-xfree86
select) ..
debconf (db configdb): passing to config ..
debconf (db configdb): trying to
addowner(xserver-xfree86/config/inputdevice/mouse/protocol xserver-xfree86
select) ..
debconf (db configdb): passing to config ..
debconf (db configdb): trying to
addowner(xserver-xfree86/config/inputdevice/mouse/emulate3buttons
xserver-xfree86 boolean) ..
debconf (db configdb): passing to config ..
debconf (db configdb): trying to
addowner(xserver-xfree86/config/inputdevice/mouse/zaxismapping
xserver-xfree86 boolean) ..
debconf (db configdb): passing to config ..
debconf (db configdb): trying to addowner(xserver-xfree86/autodetect_monitor
xserver-xfree86 boolean) ..
debconf (db configdb): passing to config ..
debconf (db configdb): trying to addowner(xserver

Processed: Re: Bug#253172: xserver-xfree86: Cannot install (preinst fails)

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> # bts control commands
> package xserver-xfree86
Ignoring bugs not assigned to: xserver-xfree86

> severity 253172 normal
Bug#253172: xserver-xfree86: Cannot install (preinst fails)
Severity set to `normal'.

> merge 253172 249447
Bug#249447: xserver-xfree86: Problem when upgrading from 4.3.0-7 to 
4.3.0.dfsg.1-1 on Unstable
Bug#253172: xserver-xfree86: Cannot install (preinst fails)
Bug#251690: xserver-xfree86: config script exits with status 127
Bug#252379: xserver-xfree86: fails to reinstall
Bug#252570: xserver-xfree86 doesn't upgrade anymore
Bug#252584: xserver-xfree68 4.3.0.dfsg.1-4_i386 failed to preconfigure, with 
exit status 127
Merged 249447 251690 252379 252570 252584 253172.

> thanks
Stopping processing here.

Please contact me if you need assistance.

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

Bug#253172: xserver-xfree86: Cannot install (preinst fails)

[Adam D. Barratt]

# bts control commands
package xserver-xfree86
severity 253172 normal
merge 253172 249447
thanks

On Mon, 2004-06-07 at 18:03, Philipp wrote:
> Package: xserver-xfree86
> Version: 4.3.0.dfsg.1-4
> Severity: critical
> Justification: breaks the whole system

Hi,

> When trying to install xserver-xfree86, the install fails with the error
> message that the preinstallation script returned with error code 127.
> Trying to use 4.3.0.dfsg.1-1 instead results in the same problem; however
> with earlier versions (before .dfsg, but don't ask me the exact version)
> i never had this problem. Purging the package (and xserver-common) does
> not help.

This issue has already been reported five times (see bug #249447 and the
reports merged to it).

The exit status 127 is returned by the `discover' program, which
xserver-xfree86 calls to try and auto-detect your hardware.
Unfortunately, a recent upload of one of the libraries used by discover
(libcurl2, to be precise) incorrectly broke backward compatibility,
hence discover fails.

There's a patch in Debian's X SVN repository to workaround the issue
(http://lists.debian.org/debian-x/2004/06/msg00123.html) which will be
included in the next release. However, the easiest workaround is to
make sure that your curl / libcurl2 packages are not the version that
caused the issue (7.12.0-1); any other version should work fine.

> This is a critical issue because i nowadays use X clients quite
> regularly. :)

IMHO, this bug is not at all critical according to the definition given
on . `important' would
potentially be justifiable, but would still be too high imo as the
problem is not caused by this package and installing it from either
current testing (`sarge') or current unstable (`sid') will work fine.

Downgrading this report to `normal' in order to merge it with the other
reports.

Regards,

Adam

Processed: your mail

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> #their titles look the similar, so
> merge 201855 204307
Bug#201855: xdm: would like autologin feature
Bug#204307: xdm: want auto-login feature that bypasses greeter
Merged 201855 204307.

> #though no pressing need at the moment for implementation
>
End of message, stopping processing here.

Please contact me if you need assistance.

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

Bug#204378: Debian version number (sid[?] vs. woody etc.)

[Dan Jacobson]

Ah, what the login square is missing is the Debian version number, 3.0 etc.

Bug#253172: [Fwd: Mail delivery failed: returning message to sender]

[Adam D. Barratt]

FYI, the submitter's e-mail is currently bouncing due to being over
quota. *sigh*

-Forwarded Message-
From: Mail Delivery System <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Mail delivery failed: returning message to sender
Date: Mon, 07 Jun 2004 11:00:11 -0700

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  [EMAIL PROTECTED]
(generated from [EMAIL PROTECTED])
SMTP error from remote mailer after RCPT TO:<[EMAIL PROTECTED]>:
host mx0.gmx.de [213.165.64.100]: 552 5.2.2 {mx024} <[EMAIL PROTECTED]> The 
user's mailbox is full

-- This is a copy of the message, including all the headers. --

X Strike Force XFree86 SVN commit: r1520 - in trunk/debian: . patches

[X Strike Force SVN Repository Admin]

Author: branden
Date: 2004-06-07 16:24:29 -0500 (Mon, 07 Jun 2004)
New Revision: 1520

Added:
   trunk/debian/patches/089_xkb_fix_symbols_pc_lt.diff
Modified:
   trunk/debian/CHANGESETS
   trunk/debian/TODO
   trunk/debian/changelog
Log:
Fix problem with numbers and symbols being un-typable in the Lithuanian
keymap (patch by Mantas Kriau?\196?\141i?\197?\171nas via Vytautas Lukenskas).
(Closes: #247387)


Modified: trunk/debian/CHANGESETS
===
--- trunk/debian/CHANGESETS 2004-06-06 19:57:21 UTC (rev 1519)
+++ trunk/debian/CHANGESETS 2004-06-07 21:24:29 UTC (rev 1520)
@@ -136,4 +136,9 @@
 ship into port.  (Closes: #229785)
 1519
 
+Fix problem with numbers and symbols being un-typable in the Lithuanian
+keymap (patch by Mantas Kriaučiūnas via Vytautas Lukenskas).
+(Closes: #247387)
+1520
+
 vim:set ai et sts=4 sw=4 tw=80:

Modified: trunk/debian/TODO
===
--- trunk/debian/TODO   2004-06-06 19:57:21 UTC (rev 1519)
+++ trunk/debian/TODO   2004-06-07 21:24:29 UTC (rev 1520)
@@ -20,9 +20,6 @@
 * #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...
   (Ben Collins pinged for status on 2004-06-03.)
-* #247387: xlibs: Can't type numbers with AltGr with /etc/X11/xkb/symbols/pc/lt
-  key map
-  + Apply patch by Mantas Kriaučiūnas via Vytautas Lukenskas.
 * #201737: fix U.K. Macintosh keyboard support
 * #251310: xlibs: implement compose:caps
 

Modified: trunk/debian/changelog
===
--- trunk/debian/changelog  2004-06-06 19:57:21 UTC (rev 1519)
+++ trunk/debian/changelog  2004-06-07 21:24:29 UTC (rev 1520)
@@ -130,8 +130,12 @@
 Jenkins.  Thanks also to Margarita Manterola for helping to steer this
 ship into port.  (Closes: #229785)
 
- -- Branden Robinson <[EMAIL PROTECTED]>  Sun,  6 Jun 2004 14:52:37 -0500
+  * Fix problem with numbers and symbols being un-typable in the Lithuanian
+keymap (patch by Mantas Kriaučiūnas via Vytautas Lukenskas).
+(Closes: #247387)
 
+ -- Branden Robinson <[EMAIL PROTECTED]>  Mon,  7 Jun 2004 15:58:55 -0500
+
 xfree86 (4.3.0.dfsg.1-4) unstable; urgency=medium
 
   * The "thanks for the 'testing'" release.

Added: trunk/debian/patches/089_xkb_fix_symbols_pc_lt.diff
===
--- trunk/debian/patches/089_xkb_fix_symbols_pc_lt.diff 2004-06-06 19:57:21 UTC 
(rev 1519)
+++ trunk/debian/patches/089_xkb_fix_symbols_pc_lt.diff 2004-06-07 21:24:29 UTC 
(rev 1520)
@@ -0,0 +1,139 @@
+$Id$
+
+Fix problem with numbers and symbols being un-typable in the Lithuanian keymap.
+
+Part of this file is encoded in ISO 8859-13, and part in UTF-8.
+Do not recode it (Vim users beware!).
+
+This patch by Mantas Kriaučiūnas.
+
+Not submitted to XFree86.
+
+--- xc/programs/xkbcomp/symbols/pc/lt~ 2004-06-06 15:23:11.0 -0500
 xc/programs/xkbcomp/symbols/pc/lt  2004-06-06 15:27:27.0 -0500
+@@ -1,7 +1,8 @@
+-
+ // based on
+-// Lithuanian keyboard map by Ri�ardas �epas <[EMAIL PROTECTED]>
+-// merged into one file by Nerijus Bali�nas
++// Lithuanian keyboard map by Ričardas Čepas <[EMAIL PROTECTED]>
++// merged into one file by Nerijus Baliūnas
++// Added number and special characters writing in basic lt layout with RAlt by
++// Mantas Kriaučiūnas <[EMAIL PROTECTED]>, 2004
+ //
+ // $XFree86: xc/programs/xkbcomp/symbols/pc/lt,v 1.4 2003/04/19 12:22:12 
pascal Exp $
+ 
+@@ -16,17 +17,17 @@
+ 
+ name[Group1]="Lithuanian";
+ 
+-key { [   aogonek,  Aogonek ]   };
+-key { [ccaron,   Ccaron ]   };
+-key { [   eogonek,  Eogonek ]   };
+-key { [ eabovedot,Eabovedot ]   };
+-key { [   iogonek,  Iogonek ]   };
+-key { [scaron,   Scaron ]   };
+-key { [   uogonek,  Uogonek ]   };
+-key { [   umacron,  Umacron ]   };
+-key { [doublelowquotemark,  parenleft ] };
+-key { [leftdoublequotemark,parenright ] };
+-key { [zcaron,   Zcaron ]   };
++key { [   aogonek,  Aogonek,1,  exclam ]
};
++key { [ccaron,   Ccaron,2,  at ]
};
++key { [   eogonek,  Eogonek,3,  numbersign ]
};
++key { [ eabovedot,Eabovedot,4,  dollar ]
};
++key { [   iogonek,  Iogonek,5, percent ]
};
++key { [scaron,   Scaron,6, asciicircum ]
};
++key { [   uogonek,  Uogonek,7,   ampersand ]
};
++key { [   umacron,  Umacron,8,asterisk ]
};
++key { [doublelowquotemark,  parenleft,  9,   parenleft ]
};
++key { [

Bug#225526: Bug#246782: [davem@redhat.com: Fw: Re: Kernel 2.6.x breaks X on blade 100]

[Branden Robinson]

On Fri, Jun 04, 2004 at 07:32:19AM -0400, Ben Collins wrote:
> On Thu, Jun 03, 2004 at 11:13:32PM -0500, Branden Robinson wrote:
> > How's this coming?  I'm ready for it, and Fabio and I would both like to
> > have it in 4.3.0.dfsg.1-5.
> 
> I think it's ready. I'm going to let dave test the debs (since I don't
> have a sunffb card) before I let you guys have the patch. When's the
> latest you'll accept the patch?

That's up to Fabio, as he is the release manager.  I will say that I am
running out of things on the TODO list for -5, apart from this item.

Has Dave been able to test yet?

-- 
G. Branden Robinson| Notions like Marxism and
Debian GNU/Linux   | Freudianism belong to the history
[EMAIL PROTECTED] | of organized religion.
http://people.debian.org/~branden/ | -- Noam Chomsky


signature.asc
Description: Digital signature

Bug#201737: map LWIN to Mode_switch

[Branden Robinson]

On Wed, Jun 02, 2004 at 09:33:37AM +0200, Sebastian Henschel wrote:
> * Branden Robinson <[EMAIL PROTECTED]> [2004-06-02 09:02 +0200]:
> > Well, that's the downside to this solution.  You have to know by
> > convention or by reading XKB configuration, as Macintosh keyboards are
> > not engraved with any such keycap.
> 
> so you do not know either? playing around, i found out that fn+alt seems
> to be RALT. note that it is important to hit fn first.

Ah; I didn't know that.

> though i personally do not like it that much this way. this might not be
> part of your responsibilities, but the default configuration of the
> keyboard is to use alt+fn to use the F-keys, where it is important to hit
> alt first. this is a tad irritating.

Fn+ is implemented in hardware; there is no way to change it or
disable it that I know of.

A good way to find out what's done in hardware is to use the "xev" X
client (from xbase-clients) or the "showkey" command at the Linux
virtual console.

> anyway, your british keymap works when you know which RALT is. thank you
> very much. :)

Glad to hear it!

[...]
> > You're looking for a file called "group", with a section "switch", as
> > pasted above.
> 
> okay, found it.

Good!

Thanks for your help figuring out what's going on with UK Macintosh
keyboards.  :)

-- 
G. Branden Robinson| The more ridiculous a belief
Debian GNU/Linux   | system, the higher the probability
[EMAIL PROTECTED] | of its success.
http://people.debian.org/~branden/ | -- Wayne R. Bartz


signature.asc
Description: Digital signature

Processed: retitle 225526 to xserver-xfree86: [core server] domain-based PCI probing doesn't work on UltraSPARCs running Linux 2.6

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.7.95.1
> retitle 225526 xserver-xfree86: [core server] domain-based PCI probing 
> doesn't work on UltraSPARCs running Linux 2.6
Bug#225526: xserver-xfree86: PCI probing doesn't work on UltraSPARCs running 
Linux 2.6
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)

Processed: [clemens.brunner@tugraz.at: Re: Bug#248619: xserver-xfree86: X reports errors when kdm is started on bootup]

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> reassign 248619 kernel-image-2.6.6-1-k7
Bug#248619: xserver-xfree86: X reports errors when kdm is started on bootup
Bug reassigned from package `xserver-xfree86' to `kernel-image-2.6.6-1-k7'.

> thanks
Stopping processing here.

Please contact me if you need assistance.

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

Bug#248619: [clemens.brunner@tugraz.at: Re: Bug#248619: xserver-xfree86: X reports errors when kdm is started on bootup]

[Branden Robinson]

reassign 248619 kernel-image-2.6.6-1-k7
thanks

Reassigning per information below.

I don't think the XFree86 X server should have to tell the kernel to
load modules.  Shouldn't hotplug or something take care of this?

- Forwarded message from Clemens Brunner <[EMAIL PROTECTED]> -

From: Clemens Brunner <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: Bug#248619: xserver-xfree86: X reports errors when kdm is started
 on bootup
Date: Fri, 04 Jun 2004 16:13:54 +0200
Message-ID: <[EMAIL PROTECTED]>
User-Agent: Thunderbird 0.6 (Windows/20040502)
X-Spam-Status: No, hits=-4.9 required=4.0 tests=BAYES_00 autolearn=ham 
version=2.63

Hi!

I had exactly the same problem, but it's definitely not the mouse being 
misconfigured.
The problem occurs only with the 2.6 kernel images (afaik), and it seems the 
mouse module doesn't get loaded automatically during the boot process. 
Instead, I added "psmouse" to /etc/modules, and now everything's working.

Maybe this bug should be reassigned to the kernel-image-2.6.x package 
(currently x = 6-1-k7 on my machine).

HTH
Clemens Brunner

- End forwarded message -

-- 
G. Branden Robinson| No math genius, eh?  Then perhaps
Debian GNU/Linux   | you could explain to me where you
[EMAIL PROTECTED] | got these...   PENROSE TILES!
http://people.debian.org/~branden/ | -- Stephen R. Notley


signature.asc
Description: Digital signature

Re: Support for VIA driver, patch against SVN HEAD

[Branden Robinson]

On Wed, Jun 02, 2004 at 08:30:00PM -0400, Nathanael Nerode wrote:
> Branden Robinson wrote:
> 
> > This leaves a few questions open:
> > 
> > A) What does David Dawes regard as "attribution to [him]"?[1]  If the
> >responsibility for the CVS commit is attributed to him, as it appears
> >to be in several of the above, does he consider the XFree86 1.1
> >license to attach to those changes?
> I would really like to know this.  I have not included such commits in my
> most recent summary of potential XFree86 1.1 license issues in X.org.

I don't know the answer.  Perhaps you could ask him, as my efforts over
the past or so to obtain useful information from Mr. Dawes have been in
vain.

> The changes would generally be copyright their authors.

I would think so, yes.

> If the authors were contacted directly and released the patches, Dawes
> could be ignored.

I would think so, yes.

> > B) What is Marc La France's policy regarding the application of the
> >XFree86 1.1 license to modifications he makes to files that bear no
> >copyright notice by him or by the XFree86 Project, Inc.?
> Maybe someone could ask him personally?  (Or is he not responding to your
> mail either?) There were quite a lot of these, and likewise I have not
> included them in that summary.

I haven't asked Mr. La France personally, but given some of his
messages[1][2] to the X.Org Foundation list, which are vigorously in
favor of the new XFree86 license policy, I would wager he has adopted a
policy similar to Mr. Dawes's.

> > C) Does the XFree86 Project, Inc., consider patches submitted to their
> >Bugzilla system to have any applicable copyrights therein assigned to
> >them?
> 
> It had better not; to my knowledge, that doesn't actually happen under US
> law.  There's no way that a voluntarily submitted thing from an outsider is
> a "work for hire", and copyright assignments have to be signed and on
> paper, last time I checked.

That's the best of your and my knowledge; it has not been established
that The XFree86 Project, Inc., its Board of Directors, or its President
knows this.

> > Is there someone who'd like to broach these questions with the XFree86
> > Project?  My mails seem to go unanswered.
> Don't mail them.  Mail the individual authors, perhaps?

Sure; it could be done.

> > At any rate, for any of the above where we can get the licensing
> > straightened out, I'd be happly to apply the relevant patches.  It may
> > be worth contacting Thomas Hellström and Luc Verhaegen to inquire as to
> > the provenance of their patches.
> Would it be worth contacting the others?

Given a few anecdotes since the relicensing, I'd say yes.

[1] Message-ID: <[EMAIL PROTECTED]>

http://www.opengroup.org/sophocles/show_mail.tpl?source=L&listname=xorg_foundation&id=100
[2] Message-ID: <[EMAIL PROTECTED]>

http://www.opengroup.org/sophocles/show_mail.tpl?source=L&listname=xorg_foundation&id=140

-- 
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

Re: Bug#250915: installation-report

[Branden Robinson]

On Thu, Jun 03, 2004 at 08:52:34PM +0100, Jason Dobbs wrote:
> >> 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. 
> 
> >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
> 
> http://www.xfree86.org/4.3.0/Status29.html states :-
> "Support (accelerated) for the 964 (revisions 0 and 1), 968, Trio32,
> Trio64, Trio64, Trio64V+, Trio64UV+, Aurora64V+, Trio64V2, and
> PLATO/PX is provided by the "s3" driver (however, only models using
> the IBM RGB 524, Texas Instruments 3025, or an internal TrioDAC RAMDAC
> chip are supported)."
> 
> I tried to figure out what RAMDAC was in this card, but didn't reach a
> definite conclusion.

Well, your logs from 3.3.6 seem to indicate an internal RAMDAC:

> (--) S3: Ramdac type: s3_trio64
> (--) S3: Ramdac speed: 135 MHz

...though I admit the Status document could have been much more clear
and explicit in this respect.

> I did try for quite some time  (several evenings,
> googling, reading xfree86 documentation and trying things out) to get
> 4.3 to go, but to no avail. My  conclusion was that 3.3.6 works for
> me, but 4.3 does not. I think it's inevitable that this scenario will
> be hit for older hardware, hence my comment about it would be nice if
> sarge could support it

Have you tried the "vga" or "vesa" drivers in 4.3 instead?

-- 
G. Branden Robinson|   The only way to get rid of a
Debian GNU/Linux   |   temptation is to yield to it.
[EMAIL PROTECTED] |   -- Oscar Wilde
http://people.debian.org/~branden/ |


signature.asc
Description: Digital signature

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

[X Strike Force SVN Repository Admin]

Author: branden
Date: 2004-06-07 18:32:24 -0500 (Mon, 07 Jun 2004)
New Revision: 1521

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


Modified: trunk/debian/TODO
===
--- trunk/debian/TODO   2004-06-07 21:24:29 UTC (rev 1520)
+++ trunk/debian/TODO   2004-06-07 23:32:24 UTC (rev 1521)
@@ -116,6 +116,13 @@
 * Stop building fonts (and possibly docs?) when building binary-arch target.
   [Fabio, you're going to drag me into this kicking and screaming, aren't you?]
 * #233551: add SELinux support to xdm
+* Backport s3 driver from sanitized XFree86 4.4.0-pre-RC3 tree; fairly small
+  changes, but fixes bugs and adds support for Trio64UV+ and Trio64V2/DX/GX
+  chipsets.  Note that the same REGION_EQUAL and REGION_NULL hacks used for the
+  ATI driver backport will also need to be applied here.  There may also be 
some
+  XVideo stuff to cope with: new symbols xf86XVClipVideoHelper(),
+  xf86XVCopyYUV12ToPacked(), xf86XVCopyPacked(), and xf86XVFillKeyHelper() are
+  used.  Closes: #192365, likely among others.
 
 Do opportunistically, only in conjuction with other fixes
 -

Bug#29194: Bug #29194: xfree86: have all XFree86 packages symlink to xfree86-common for copyright and changelog(s)

[Branden Robinson]

On Thu, Jun 03, 2004 at 01:26:06AM +0200, Elrond wrote:
> On Wed, Jun 02, 2004 at 01:51:57AM -0500, Branden Robinson wrote:
> > [I don't know that Joey Hess really needs to be CCed on this, so I have
> 
> Some year ago or so, the submitter of a bug didn't get mail
> for [EMAIL PROTECTED],
[...]

That was true and remains true.  I did not and do not see what relevant
our discussion has to him.

People talk about implementing new debhelper features all the time; he'd
probably become more interested once you have a working design or
prototype.

> > I think if you had actually read the file, this would have been clear to
> > you.
> 
> Well, "but you know better, I presume" was intended to say:
> "Let's stop this discussion here, I'm 99% sure, you know,
> what you're doing there." ;)

You could go to the trouble of reading the xfree86 package's
debian/copyright file just once for yourself.

> Well, I wanted to explain, what the idea _was_.
> 
> Anyway, I think, we should stop this discussion here and
> hope for Joey to say anything.
> 
> (I don't see a point in coding debhelper stuff like mad for
> realising at the end, that Joey has much better plans.)

You could ask him, but I am not sure this bug report is the best place
to do so.

-- 
G. Branden Robinson|The best place to hide something is
Debian GNU/Linux   |in documentation.
[EMAIL PROTECTED] |-- Ethan Benson
http://people.debian.org/~branden/ |


signature.asc
Description: Digital signature

Bug#236256: xbase-clients: installer fails

[Branden Robinson]

On Wed, Jun 02, 2004 at 04:23:47AM -0500, Branden Robinson wrote:
> Sorry.  I've now attached a version that should work.

It's been a few days.  Do either of you gentlemen have anything to
report?

If not, I will have to close this report as being unreproducible, and
having a submitter unresponsive to requests for further information.

-- 
G. Branden Robinson|
Debian GNU/Linux   |   "Bother," said Pooh, as he was
[EMAIL PROTECTED] |   assimilated by the Borg.
http://people.debian.org/~branden/ |


signature.asc
Description: Digital signature

Processed: retitle 252045 to xfonts-base: [ClearlyU] off-by-one error with some glyphs, tagging 252045

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.7.95.1
> retitle 252045 xfonts-base: [ClearlyU] off-by-one error with some glyphs
Bug#252045: xfonts-base: ClearlyU font: Off-by-one error with some glyphs
Changed Bug title.

> tags 252045 + upstream
Bug#252045: xfonts-base: [ClearlyU] off-by-one error with some glyphs
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#249239: DRM

[Branden Robinson]

On Tue, Jun 01, 2004 at 10:21:05AM +0200, Ralf Hildebrandt wrote:
> I thought that DRM may be the issue due to the fact that disabling DRI
> makes the crashes go away. But you are the true X11 master, so what do
> I know :)

If disabling DRI makes the problem go away, then the problem is most
likely on the chipset-specific Mesa side of things (package:
xlibmesa-dri), or the chipset-specific kernel DRM module (package:
kernel).

-- 
G. Branden Robinson|  The greatest productive force is
Debian GNU/Linux   |  human selfishness.
[EMAIL PROTECTED] |  -- Robert Heinlein
http://people.debian.org/~branden/ |


signature.asc
Description: Digital signature

Bug#249399: DRI

[Branden Robinson]

On Tue, Jun 01, 2004 at 10:22:50AM +0200, Ralf Hildebrandt wrote:
> > Have you tried going back to kernel 2.4.x?
> 
> No.

Please try that.

> > (Why do you keep filing bugs specific to the XFree86 X server against
> > xserver-common?  Is there a file in the xserver-common package you
> > believe to be the cause of your problems?)
> 
> The EIP was generated by a binary that belonged into the
> xserver-common package, so Ithought it would be reasonable.

Which binary was that?

-- 
G. Branden Robinson|I reverse the phrase of Voltaire,
Debian GNU/Linux   |and say that if God really existed,
[EMAIL PROTECTED] |it would be necessary to abolish
http://people.debian.org/~branden/ |him. -- Mikhail Bakunin


signature.asc
Description: Digital signature

Re: Does not use the whole screen.

[Branden Robinson]

On Wed, Jun 02, 2004 at 09:45:31PM -0600, Marvin Aguero wrote:
> Hi guys,
> 
> I guess this is an FAQ, but here I go anyway.

[The following is a form letter.]

Hello,

You recently sent an off-charter message to the debian-x mailing list.
First, I will offer an explanation of what this mailing list's purpose is;
I will then suggest some alternative forums for your message or concern.

The full charter of the mailing list follows.

  This list is for the discussion and support of the X Window System within
  Debian.  Issues of maintenance and porting of Debian's XFree86 packages are
  germane here, as are discussions of possible Debian policy mechanisms for
  ensuring the smooth interoperation of packages that use the X Window
  System, particularly widget sets, desktop environments, window managers,
  display managers, and packages that provide fonts for the X Window System.
  In particular, individuals involved with building official Debian XFree86
  packages for any architecture are invited to join, as are those with
  various graphics hardware who seek to reproduce and/or fix bugs in the X
  server.  This is not a user support list; this list is intended for those
  who deal with the source code of any of the X Window System components
  mentioned above.

If you are experiencing a problem, the first thing to check is the Debian X
FAQ.  This FAQ is available on the World Wide Web:

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

The FAQ is also available on any Debian system that has the
"xfree86-common" package installed.

You can use the command "dpkg --status xfree86-common" at a shell prompt to
determine whether you have the xfree86-common package installed (this
technique works with any other package name as well).  For instance, when I
run this command I see the following:

  $ dpkg --status xfree86-common
  Package: xfree86-common
  Status: install ok installed

(followed by additional information about the package)

If xfree86-common is installed, you can view the Debian X FAQ in a variety of
ways, since it is a gzipped (compressed) text file.  The path to the FAQ is
/usr/share/doc/xfree86-common/FAQ.gz.  Here's one method for viewing it:

  $ zmore /usr/share/doc/xfree86-common/FAQ.gz
  Debian X Window System Frequently Asked Questions (FAQ) List

  Copyright 1998-2002 Branden Robinson.  This document is licensed under the
  GNU General Public License, version 2 (see /usr/share/common-licenses/GPL).

  By its nature, this document is not complete.  If your question is not
  answered here, try /usr/share/doc//README.Debian (and other files
  in the package's doc directory), manual pages, and the debian-user mailing
  list.  See http://www.debian.org/ for more information about the Debian
  mailing lists.

(followed by the rest of the FAQ)

If the FAQ does not satisfactorily answer your question, the primary Debian
users' support forum is the debian-user mailing list.  You can learn more about
this list at:

  http://lists.debian.org/debian-user/

If you have already tried that mailing list, and/or your machine does *NOT*
use an Intel-x86 compatible CPU (such as a Pentium or AMD Athlon chip), you
may also want to peruse one of Debian's architecture-specific mailing
lists:

  http://lists.debian.org/debian-alpha/
  http://lists.debian.org/debian-arm/
  http://lists.debian.org/debian-hppa/
  http://lists.debian.org/debian-ia64/
  http://lists.debian.org/debian-m68k/
  http://lists.debian.org/debian-mips/
  http://lists.debian.org/debian-powerpc/
  http://lists.debian.org/debian-sparc/
  http://lists.debian.org/debian-superh/

Before sending a message to one of the mailing lists, it's wise to try
using the search interface; in many cases, your problem has been
experienced before by other people, and a solution, workaround, or
explanation may already be available!

  http://lists.debian.org/search.html

If the search engine turns up nothing, you should know whether or not
you're subscribed to a mailing list before sending a message to it.  If you
are not subscribed, make *certain* that you ask for private copies of
replies to your message.  Debian's standard practice is to reply only to
mailing lists (this cuts down on Internet traffic and annoying bounce
messages).  If you want people to deviate from this standard practice you
should ask them to do so.  (Advanced mail users should set a
Mail-Followup-To header that includes both the list address and their own
address.)

Finally, if you have found a problem in Debian's XFree86 packages (and
especially if Debian experts on one or more of the above mailing lists
agree), you should file a bug report with the Debian Bug Tracking System.
One of the best ways to do this is with the "reportbug" package and command
of the same name.  One way to install reportbug is with "apt-get"; for
example:

  # apt-get install reportbug

The "reportbug" command has a few different modes that cater to different
levels of user expertise.  If this messag

Processed: Re: Bug#252068: xbase-clients: [xkb] Problem using different layouts

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> retitle 252068 xlibs: some layout combinations under xfree86/pc105 do not 
> work ('us,us_intl', 'us,ca_enhanced')
Bug#252068: xbase-clients: [xkb] Problem using different layouts
Changed Bug title.

> tag 252068 + upstream moreinfo unreproducible help
Bug#252068: xlibs: some layout combinations under xfree86/pc105 do not work 
('us,us_intl', 'us,ca_enhanced')
There were no tags set.
Tags added: upstream, moreinfo, unreproducible, help

> reassign 252068 xlibs
Bug#252068: xlibs: some layout combinations under xfree86/pc105 do not work 
('us,us_intl', 'us,ca_enhanced')
Bug reassigned from package `xbase-clients' to `xlibs'.

> thanks
Stopping processing here.

Please contact me if you need assistance.

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

Processed: Re: Bug#252326: can't login using xdm

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> retitle 252326 xdm: user cannot log in
Bug#252326: can't login using xdm 
Changed Bug title.

> tag 252326 + moreinfo unreproducible
Bug#252326: xdm: user cannot log in
There were no tags set.
Tags added: moreinfo, unreproducible

> thanks
Stopping processing here.

Please contact me if you need assistance.

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

Bug#251690: Possibly discover problem?

[Branden Robinson]

On Wed, Jun 02, 2004 at 05:25:43PM -0400, Kevin B. McCarty wrote:
> Hi Branden,
> 
> I just finished debugging a very similar issue to bug 251690, where the
> preinst of xserver-xfree86 failed with exit code 127.  As in the
> submitter's case, there was no useful debugging output, even with variables
> DEBUG_XFREE86_PACKAGE=true and DEBIAN_FRONTEND=readline
> exported as you requested.  The problem turned out to be that discover
> crashed silently in the xserver-xfree86 config script.
> 
> In my case, this was due to libcurl2 abruptly changing soname (I've just
> filed a grave bug against libcurl2, #252348), but since the broken libcurl2
> package only entered unstable today, the submitter likely has a different
> problem.  Still, I suggest investigating discover as a first possible
> culprit.  Maybe in the X inst/config/rm scripts, you could output debugging
> messages before and after calls to discover when DEBUG_XFREE86_PACKAGE is
> set, to aid in catching these problems?

Mr. McCarty,

Thanks very much for the research and the suggestion.  I have taken your
advice.

% svn log -v -r 1511 svn://necrotic.deadbeast.net/xfree86

r1511 | branden | 2004-06-03 22:36:07 -0500 (Thu, 03 Jun 2004) | 9 lines
Changed paths:
   M /trunk/debian/CHANGESETS
   M /trunk/debian/changelog
   M /trunk/debian/xserver-xfree86.config.in

Modify xserver-xfree86's config script to be more paranoid and mistrustful
of Discover.  Store standard error from checking for the installed version
of Discover instead of discarding it, and if this fails, report Discover's
error output to the user and trap the failure instead of permitting it to
break us.  (Thanks to Kevin B. McCarty for identifying the cause of these
mysterious failures; see #251690 and #252348.  Thanks also to the libcurl2
maintainer for the reminder that "The issue isn't whether you're
paranoid...The issue is whether you're paranoid *enough*." [Max Peltier])



-- 
G. Branden Robinson|  When dogma enters the brain, all
Debian GNU/Linux   |  intellectual activity ceases.
[EMAIL PROTECTED] |  -- Robert Anton Wilson
http://people.debian.org/~branden/ |


signature.asc
Description: Digital signature

Bug#252068: xbase-clients: [xkb] Problem using different layouts

[Branden Robinson]

retitle 252068 xlibs: some layout combinations under xfree86/pc105 do not work 
('us,us_intl', 'us,ca_enhanced')
tag 252068 + upstream moreinfo unreproducible help
reassign 252068 xlibs
thanks

On Tue, Jun 01, 2004 at 05:59:42AM -0400, Sylvain Ageneau wrote:
> Package: xbase-clients
> Version: 4.3.0.dfsg.1-4
> Severity: normal
> 
> I wanted to use the us,us_intl and fr layouts and be able to switch 
> between them (using setxkbmap or the gnome applet). It seems some 
> combinations are impossible. 
> 
> $ setxkbmap -layout "us"
> $ setxkbmap -layout "us_intl"
> $ setxkbmap -layout "us,fr"
> $ setxkbmap -layout "us,us_intl"
> Error loading new keyboard description
> $ setxkbmap -layout "us,ca_enhanced"
> Error loading new keyboard description 
> 
> Same bug in Fedora (there's a patch):
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=116669

This patch was already applied to Debian's XFree86 packages in
4.3.0.dfsg.1-2, which is two revisions prior to the one against which
you reported the bug.

Also, I am using 4.3.0.dfsg.1-4, and I cannot exactly reproduce your
problem:

[0] [EMAIL PROTECTED]:~ % setxkbmap -layout "us"
[0] [EMAIL PROTECTED]:~ % setxkbmap -layout "us_intl"
Error loading new keyboard description
[251] [EMAIL PROTECTED]:~ % setxkbmap -layout "us,fr"
[0] [EMAIL PROTECTED]:~ % setxkbmap -layout "us,us_intl"
Error loading new keyboard description
[251] [EMAIL PROTECTED]:~ % setxkbmap -layout "us,ca_enhanced"
Error loading new keyboard description
[251] [EMAIL PROTECTED]:~ % setxkbmap -layout "us"
[0] [EMAIL PROTECTED]:~ %

-- 
G. Branden Robinson| There's nothing an agnostic can't
Debian GNU/Linux   | do if he doesn't know whether he
[EMAIL PROTECTED] | believes in it or not.
http://people.debian.org/~branden/ | -- Graham Chapman


signature.asc
Description: Digital signature

Bug#252379: xserver-xfree86: fails to reinstall

[Branden Robinson]

On Fri, Jun 04, 2004 at 06:35:16PM +0100, Adam D. Barratt wrote:
> This looks like another case of bug 251690. The exit status 127 is
> returned by the `discover' program, which xserver-xfree86 calls to try
> and auto-detect your hardware. Unfortunately, a recent upload of one of
> the libraries used by discover (libcurl2, to be precise) incorrectly
> broke backward compatibility, hence discover fails.
> 
> Merging this with #251690.

Mr. Barratt,

Thanks for helping to keep my blood pressure down by disciplining the
duplicate reports.

I appreciate it greatly.

-- 
G. Branden Robinson|If I recall correctly, devfs went
Debian GNU/Linux   |straight from being marked as
[EMAIL PROTECTED] |EXPERIMENTAL to OBSOLETE in the
http://people.debian.org/~branden/ |kernel config. -- Tore Anderson


signature.asc
Description: Digital signature

Bug#252326: can't login using xdm

[Branden Robinson]

retitle 252326 xdm: user cannot log in
tag 252326 + moreinfo unreproducible
thanks

On Wed, Jun 02, 2004 at 08:56:17PM +0200, Andreas Messer wrote:
> Package: xdm
> Version: 4.3.0.dfsg.1-1
> 
> Hello, 
> i am not able to login local using xdm. With kdm everything works fine. I 
> think there ist some problem verifying the passwort, because 
> my /var/log/auth.log says:
> 
> Jun  2 19:19:03 hermes  : (pam_unix) authentication failure; logname= 
> uid=0 euid=0 tty=:0 ruser= rhost= user=satura

The above is probably a red herring.  xdm fine works for me, and I
always get lines like this in auth.log myself.

> I have also completely purged and reinstalled the xdm Package but this
> did'nt solve the problem. 

I wonder if the session is just exiting normally because it has nothing
to do.  See the Debian X FAQ:

/usr/share/doc/xfree86-commom/FAQ.gz
http://necrotic.deadbeast.net/xsf/XFree86/trunk/debian/local/FAQ

  *) How can I tell if it's the X server crashing, or my X session exiting
 abnormally?

  Generally, when the X server has no more clients to manage, it will exit
  immediately.  This can look a lot like a "crash" to the uninitiated, 
especially
  when the clients themselves crash.

  It's easy to determine whether the X server itself works.  As root, simply run
  the command "X".  If that brings up the little root window weave and the X
  cursor, then *you do not have a fatal X server configuration problem*.  The X
  server is working.  Use CTRL-ALT-BACKSPACE to kill it.

  Alternatively, if you're using a display manager and you can see the greeter
  (login screen), then the X server is running: *you do not have a fatal X 
server
  configuration problem*.  Most failures after that point are client-side
  problems.  (Yes, there are bugs in the X server that can cause it 
spontaneously
  crash, but if the X server "crashes" immediately upon logging in to your X
  session, it's probably a client side problem.)

  If the X server doesn't start with the command "X", but you get a message like
  "Server already active for display 0", then you're probably already running X
  somewhere.  See the "The X server log says there was an error opening my 'core
  pointer'..." question above for more information on how to deal with this.

  Alternatively, if you're using a display manager and you can see the
  greeter (login screen), then the X server is running: *you do not have a
  fatal X server configuration problem*.  Most failures after that point
  are client-side problems.  (Yes, there are bugs in the X server that can
  cause it spontaneously crash, but if the X server "crashes" immediately
  upon logging in to your X session, it's probably a client side problem.)

-- 
G. Branden Robinson| That's the saving grace of humor:
Debian GNU/Linux   | if you fail, no one is laughing at
[EMAIL PROTECTED] | you.
http://people.debian.org/~branden/ | -- A. Whitney Brown


signature.asc
Description: Digital signature

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

[X Strike Force SVN Repository Admin]

Author: branden
Date: 2004-06-07 19:11:28 -0500 (Mon, 07 Jun 2004)
New Revision: 1522

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


Modified: trunk/debian/TODO
===
--- trunk/debian/TODO   2004-06-07 23:32:24 UTC (rev 1521)
+++ trunk/debian/TODO   2004-06-08 00:11:28 UTC (rev 1522)
@@ -19,7 +19,7 @@
 
 * #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...
-  (Ben Collins pinged for status on 2004-06-03.)
+  (Ben Collins pinged for status on 2004-06-03, and again on 2004-06-07.)
 * #201737: fix U.K. Macintosh keyboard support
 * #251310: xlibs: implement compose:caps
 

Processed: retitle 252558 to xserver-xfree86: [ati/atimisc] XVideo apps crash X server; complaints of unresolved symbols xf86XVCopyYUV12ToPacked and xf86XVCopyPacked on Rage Mobility L AGP 2x rev 100

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.7.95.1
> retitle 252558 xserver-xfree86: [ati/atimisc] XVideo apps crash X server; 
> complaints of unresolved symbols xf86XVCopyYUV12ToPacked and xf86XVCopyPacked 
> on Rage Mobility L AGP 2x rev 100
Bug#252558: xserver-xfree86: [ati/atimisc] XVideo apps crash X server; 
complaints of unresolved symbols xf86XVCopyYUV12ToPacked and xf86XVCopyPacked 
on ATI 3D Rage Mobility
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)

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

[X Strike Force SVN Repository Admin]

Author: branden
Date: 2004-06-07 19:18:45 -0500 (Mon, 07 Jun 2004)
New Revision: 1523

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


Modified: trunk/debian/TODO
===
--- trunk/debian/TODO   2004-06-08 00:11:28 UTC (rev 1522)
+++ trunk/debian/TODO   2004-06-08 00:18:45 UTC (rev 1523)
@@ -123,6 +123,10 @@
   XVideo stuff to cope with: new symbols xf86XVClipVideoHelper(),
   xf86XVCopyYUV12ToPacked(), xf86XVCopyPacked(), and xf86XVFillKeyHelper() are
   used.  Closes: #192365, likely among others.
+* Examine Marc Haber's Xsession suggestions:
+  + #252585: xfree86-common: Xsession.options parsing fragile
+  + #252592: xfree86-common: please consider adding a local hook for Xsession
+handling
 
 Do opportunistically, only in conjuction with other fixes
 -

Processed: tagging 252631

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.7.95.1
> tags 252631 + upstream
Bug#252631: xbase-clients: [setxkbmap] man page doesn't describe all switches
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)

Processed: tagging 253029

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.7.95.1
> tags 253029 + upstream
Bug#253029: xmessage: could check if -default args are valid
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)

Processed: retitle 252895 to xbase-clients: [xfontsel] crashes with BadValue error on X_OpenFont request ...

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.7.95.1
> retitle 252895 xbase-clients: [xfontsel] crashes with BadValue error on 
> X_OpenFont request
Bug#252895: /usr/X11R6/bin/xfontsel: [xfontsel] crash
Changed Bug title.

> severity 252895 important
Bug#252895: xbase-clients: [xfontsel] crashes with BadValue error on X_OpenFont 
request
Severity set to `important'.

>
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#252895: /usr/X11R6/bin/xfontsel: [xfontsel] crash

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> tag 252895 + unreproducible
Bug#252895: xbase-clients: [xfontsel] crashes with BadValue error on X_OpenFont 
request
There were no tags set.
Tags added: unreproducible

> thanks
Stopping processing here.

Please contact me if you need assistance.

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

Bug#192365: [patch] [s3] Bresenham line drawing accel fixed

[Branden Robinson]

On Sat, Jun 05, 2004 at 09:39:55PM +0200, Németh Márton wrote:
> Hi!
> 
> The same problem in xserver-xfree86 Debian package version 4.3.0.dfsg.1-1
> Applying the attached patch solves the problem, this patch already have
> the current XFree86 mainstream.
> http://cvsweb.xfree86.org/cvsweb/xc/programs/Xserver/hw/xfree86/drivers/s3/s3_accel.c?rev=1.3&content-type=text/vnd.viewcvs-markup
> 
> See the file xc/programs/Xserver/hw/xfree86/xaa/XAA.HOWTO Section 2.3
> (Solid Lines), void SubsequentSolidBresenhamLine(...)
> The file is also accessible at
> http://cvsweb.xfree86.org/cvsweb/xc/programs/Xserver/hw/xfree86/xaa/XAA.HOWTO?rev=1.13&content-type=text/vnd.viewcvs-markup
> 
>   NMarci

Excellent; thanks for following up.

I have added a TODO item for a backport of the driver from my 4.4.0-RC3
"sanitized" CVS checkout.  This will not only fix this bug, it will
collect other fixes, add support for a couple more pre-ViRGE S3
chipsets, and may even improve the driver's XVideo performance.

-- 
G. Branden Robinson|
Debian GNU/Linux   |  Please do not look directly into
[EMAIL PROTECTED] |  laser with remaining eye.
http://people.debian.org/~branden/ |


signature.asc
Description: Digital signature

Bug#220675: xserver-common: Bug #220675 - Having same problem; Additional info included

[Branden Robinson]

On Sat, Jun 05, 2004 at 03:50:26PM -0400, Adam Aube wrote:
> Package: xserver-common
> Version: 4.3.0.dfsg.1-4
> Severity: normal
> Followup-For: Bug #220675
> 
> I am having the same problem - dpkg-reconfigure xserver-common does not
> change nice value in /etc/X11/Xwrapper.config. Had not edited file
> manually before trying dpkg-reconfigure. Also noticed that the file would not 
> be
> created by dpkg-reconfigure or apt-get install --reinstall if it is removed.
> 
> Checking /var/lib/dpkg/info/xserver-common.md5sums and 
> xserver-common.conffiles
> showed no entry for the file. Are these the correct places to check?
> 
> I eventually had to resort to editing the file manually. Additional info
> can be provided if needed.

Please supply the information I requested of the submitter:

Please mail me the output of the command after doing this:

export DEBUG_XFREE86_PACKAGE=YES
export DEBIAN_FRONTEND=readline
dpkg-reconfigure xserver-common

(I've added the DEBIAN_FRONTEND line so that you're more sure to get
unclobbered text output.)

-- 
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

Bug#252566: xbase-clients: [xkbcomp] Type "TWO_LEVEL" has 2 levels, but has 4 symbols

[Branden Robinson]

retitle 252566 xlibs: xkbcomp complains 'Warning: Type 'TWO_LEVEL' has 2 
levels, but  has 4 symbols; Ignoring extra symbols'
reassign 252566 xlibs
tag 252566 + moreinfo
thanks

On Fri, Jun 04, 2004 at 09:03:32AM +0200, David Liontooth wrote:
> Package: xbase-clients
> Version: 4.3.0.dfsg.1-4
> Severity: minor
> 
> After upgrading to xfree86 4.3.0.dfsg.1-4, I get this xkbcomp warning:
> 
> The XKEYBOARD keymap compiler (xkbcomp) reports:
> > Warning:  Type "TWO_LEVEL" has 2 levels, but  has 4 symbols
> >   Ignoring extra symbols
> 
> Is this something I can fix?

Possibly, but you reported the bug against the wrong package, so vital
information was omitted from your report.

Please run the following commands from a shell prompt to gather and
deliver this information to us:

$ /usr/share/bug/xlibs > /tmp/output 3>&1
$ mailx -s "Re: Bug#252566" [EMAIL PROTECTED] < /tmp/output

If you do not have a "mailx" command on your system, you can get by
installing the "mailx" Debian package; for example, with the "aptitude
install mailx" or "apt-get install mailx" commands as root.  Alternatively,
you can also use a mail command that is compatible with mailx's
command-line syntax, such as "mutt".

Thank you!

-- 
G. Branden Robinson|People are equally horrified at
Debian GNU/Linux   |hearing the Christian religion
[EMAIL PROTECTED] |doubted, and at seeing it
http://people.debian.org/~branden/ |practiced. -- Samuel Butler


signature.asc
Description: Digital signature

Bug#252570: Solved (sort of) : free86-xserver doesn't install anymore

[Branden Robinson]

On Fri, Jun 04, 2004 at 09:45:48AM +0200, Emmanuel Charpentier wrote:
> I reported that an upgrade hosed my system because xfree86-xserver failed 
> to install.
> 
> Well, a bit *more* perusing the bugs list (yes, I *did* look before 
> reporting, but failed to find the relevant bug ...) led me to create the 
> symlink /usr/lib/libcurl.so.2 --> /usr/lib/so.3.0.0, which unlocked the 
> install and un-hosed me.
> 
> I sort-of apologize for the report, but I think the *large* number of bugs 
> in the xfree86-xserver is somehow an extenuating cirumstance for this false 
> report ...

This is why reportbug's "f" (filter) feature exists.

-- 
G. Branden Robinson|The errors of great men are
Debian GNU/Linux   |venerable because they are more
[EMAIL PROTECTED] |fruitful than the truths of little
http://people.debian.org/~branden/ |men. -- Friedrich Nietzsche


signature.asc
Description: Digital signature

Bug#252895: /usr/X11R6/bin/xfontsel: [xfontsel] crash

[Branden Robinson]

tag 252895 + unreproducible
thanks

On Sat, Jun 05, 2004 at 09:14:01PM +0200, Markus Schaber wrote:
> Package: xbase-clients
> Version: 4.3.0.dfsg.1-4
> Severity: normal
> File: /usr/X11R6/bin/xfontsel
> 
> Hello,
> 
> I start xfontsel, and then klick on sWdth menu and select monospaced,
> then xfontsel crashes with the following error message:
> 
> X Error of failed request:  BadValue (integer parameter out of range for 
> operation)
>   Major opcode of failed request:  45 (X_OpenFont)
>   Value in failed request:  0x380005d
>   Serial number of failed request:  4308
>   Current serial number in output stream:  4309
> 
> Can anyone reproduce this?

I cannot, but that may have something to do with the fact that when I
start xfontsel, "monospaced" is not a choice under the sWdth menu.

Instead, I have:

*
(nil)
normal
semicondensed

You probably have different fonts installed that I do.

Can you please mail this bug report the output of the following
commands?:

1) grep FontPath /etc/X11/XF86Config-4
2) dpkg -S /usr/X11R6/lib/X11/fonts

-- 
G. Branden Robinson|No executive devotes much effort to
Debian GNU/Linux   |proving himself wrong.
[EMAIL PROTECTED] |-- Laurence J. Peter
http://people.debian.org/~branden/ |


signature.asc
Description: Digital signature

Processed: Re: Bug#252947: X screen not restored correctly after monitor unsuspend

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> tag 252947 + moreinfo
Bug#252947: X screen not restored correctly after monitor unsuspend
There were no tags set.
Tags added: moreinfo

> thanks
Stopping processing here.

Please contact me if you need assistance.

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

Processed: reassign 252949 to xlibs ..., tagging 252949

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.7.95.1
> reassign 252949 xlibs
Bug#252949: xserver-xfree86: [xkb] modifiers get messed up when using multiple 
layouts
Bug reassigned from package `xserver-xfree86' to `xlibs'.

> retitle 252949 xlibs: modifiers get messed up when using multiple layouts
Bug#252949: xserver-xfree86: [xkb] modifiers get messed up when using multiple 
layouts
Changed Bug title.

> tags 252949 + upstream
Bug#252949: xlibs: modifiers get messed up when using multiple layouts
Tags were: sid
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#252947: X screen not restored correctly after monitor unsuspend

[Branden Robinson]

tag 252947 + moreinfo
thanks

On Sat, Jun 05, 2004 at 09:18:11PM -0700, Yvoe Ywon wrote:
> Package: xserver-xfree86
> Version: not sure
> 
> sorry i could not figure out against which package
> should i file this bug:

[The following is a form letter.]

Dear bug submitter,

Since the XFree86 X server is a large and complex piece of software, some
more information is required of you before this bug can be handled.  Please
run the following commands from a shell prompt to gather and deliver this
information to us:

$ /usr/share/bug/xserver-xfree86 > /tmp/output 3>&1
$ mailx -s "Re: Bug#252947" [EMAIL PROTECTED] < /tmp/output

If you do not have a "mailx" command on your system, you can get by
installing the "mailx" Debian package; for example, with the "aptitude
install mailx" or "apt-get install mailx" commands as root.  Alternatively,
you can also use a mail command that is compatible with mailx's
command-line syntax, such as "mutt".

One very good way to file bugs with the Debian Bug Tracking System is to
use the "reportbug" package and command of the same name.  The reportbug
program does a lot of automatic information-gathering that helps package
maintainers to understand your system configuration, and also ensures that
your message to the Debian Bug Tracking System is well-formed so that it is
processed correctly by the automated tools that manage the reports.  (If
you've ever gotten a "bounce" message from the Debian Bug Tracking System
that tells you your message couldn't be processed, you might appreciate
this latter feature.)

Therefore, I strongly urge you to give "reportbug" a try as your primary
bug reporting tool for the Debian System in the future.

If you *did* use reportbug to file your report, then you'r receiving this
message because the information we expected to see was not present.

If you deliberately deleted this information from the report, please don't
do that in the future, even if it seems like it makes the mail too large.
50 kB (kilobytes) of configuration and log data is typical.  Only if the
included information greatly exceeds this amount (more than 100 kB) should
you consider omitting it; instead, put it up on the World Wide Web
somewhere and provide URLs to it in your report, or in subsequent followup
by mailing <[EMAIL PROTECTED]>.

Thank you!

-- 
G. Branden Robinson| Never attribute to human stupidity
Debian GNU/Linux   | that which can be adequately
[EMAIL PROTECTED] | explained by GNU Libtool.
http://people.debian.org/~branden/ | -- Scott James Remnant


signature.asc
Description: Digital signature

Bug#236256: xbase-clients: installer fails

[Einar Jørgensen]

Dear Branden,

I managed to install xbase-clients after a lot of trials on the previous
version.

Peaceful regards Einar

mandag 7. juni 2004, 18:19, skrev du :
> On Wed, Jun 02, 2004 at 04:23:47AM -0500, Branden Robinson wrote:
> > Sorry.  I've now attached a version that should work.
>
> It's been a few days.  Do either of you gentlemen have anything to
> report?
>
> If not, I will have to close this report as being unreproducible, and
> having a submitter unresponsive to requests for further information.

-- 
Peaceful regards from Einar

--
Kari Fiskum and Einar Joergensen
1000 Univ. Manor Drive Unit 23
Fairfield, IA 52556, USA
+1-641-472-3429, [EMAIL PROTECTED]


Peaceful regards Einar

Kari and Einar Joergensen
1000 University Manor Drive Unit 23A
Fairfield, Iowa 52556, USA
Tel +1-641-472-3429, email [EMAIL PROTECTED]

Bug#220675: xserver-common: Providing requested info

[Adam Aube]

On Monday 07 June 2004 08:29 pm, Branden Robinson wrote:
> On Sat, Jun 05, 2004 at 03:50:26PM -0400, Adam Aube wrote:
> > I am having the same problem - dpkg-reconfigure xserver-common does
> > not change nice value in /etc/X11/Xwrapper.config.

> > I eventually had to resort to editing the file manually. Additional
> > info can be provided if needed.

> Please supply the information I requested of the submitter:
>
> Please mail me the output of the command after doing this:
>
> export DEBUG_XFREE86_PACKAGE=YES
> export DEBIAN_FRONTEND=readline
> dpkg-reconfigure xserver-common

*** BEGIN CONSOLE TRANSCRIPT ***

$ export DEBUG_XFREE86_PACKAGE=YES
$ export DEBIAN_FRONTEND=readline
$ sudo dpkg-reconfigure xserver-common
Password:
xserver-common config note: Linux kernel > 2.5 detected; using 0 as 
default nice value
xserver-common config note: setting xserver-common/xwrapper/allowed_users
   from configuration file
xserver-common config note: setting xserver-common/xwrapper/nice_value
   from configuration file
Configuring xserver-common
--

Because the X server runs with superuser privileges, it may be unwise to 
permit any user to start it, for security reasons.  On the other hand, it 
is even more unwise to run general-purpose X client programs as root, 
which is what may happen if only root is permitted to start the X server.  
A good compromise is to permit the X server to be started only by users 
logged in to one of the virtual consoles.

  1. Root Only  2. Console Users Only  3. Anybody

Select what type of user has permission to start the X server. 2


When using operating system kernels with a particular scheduling strategy, 
it has been widely noted that the X server's performance improves when it 
is run at a higher process priority than the default; a process's 
priority is known as its "nice" value.  They range from -20 (extremely 
high priority, or "not nice" to other processes) to 19 (extremely low 
priority).  The default nice value for ordinary processes is 0.  -10 is a 
good default for a single-user workstation; 0 is a good default for a 
machine that has duties other than interacting with the console user 
(such as a web server).

The above is not true of Linux kernel version 2.6 (nor of the 2.5 series 
after the "O(1) scheduler" was included); on such systems, the nice value 
of the X server should be set to 0.

Values outside the range of -10 to 0 are not recommended; too negative, 
and the X server will interfere with important system tasks.  Too 
positive, and the X server will be sluggish and unresponsive.

Enter the desired nice value for the X server to use. -10


xserver-common postinst note: not updating /etc/X11/Xwrapper.config; no
   stored checksum available

*** END CONSOLE TRANSCRIPT ***

The output from the console commands was edited for formatting only; no 
content was changed. A cat of /etc/X11/Xwrapper.config confirms the file 
has not been changed.

Adam