Bug#285485: marked as done (xfree86 packages upgrade to 4.3.0.dfsg.1-9 from 4.3.0.dfsg.1-8 for 2.6.9 kernels fails nvidia driver)
Your message dated Fri, 31 Dec 2004 04:36:54 -0500
with message-id <20041231093654.GH29940@redwald.deadbeast.net>
and subject line Bug#285485: xfree86 packages upgrade to 4.3.0.dfsg.1-9 from 4.3.0.dfsg.1-8 for 2.6.9 kernels fails nvidia driver
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; 13 Dec 2004 15:43:07 +0000
>From freelsjd@ornl.gov Mon Dec 13 07:43:07 2004
Return-path: <freelsjd@ornl.gov>
Received: from emroute1.cind.ornl.gov [160.91.4.119]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CdsLr-0001e2-00; Mon, 13 Dec 2004 07:43:07 -0800
Received: from emroute1.cind.ornl.gov (localhost [127.0.0.1])
by emroute1.cind.ornl.gov (PMDF V6.2-X27 #30899)
with ESMTP id <0I8O0061H3NGCW@emroute1.cind.ornl.gov> for
submit@bugs.debian.org; Mon, 13 Dec 2004 10:43:04 -0500 (EST)
Received: from ORNLEXCHANGE.ornl.gov (ornlexchange1.ornl.gov [160.91.1.20])
by emroute1.cind.ornl.gov (PMDF V6.2-X27 #30899)
with ESMTP id <0I8O007O13N0U4@emroute1.cind.ornl.gov> for
submit@bugs.debian.org; Mon, 13 Dec 2004 10:42:36 -0500 (EST)
Received: from 160.91.145.10 ([160.91.145.10])
by ORNLEXCHANGE.ornl.gov ([160.91.1.32]) via Exchange Front-End Server
mail.ornl.gov ([160.91.4.25]) with Microsoft Exchange Server HTTP-DAV ; Mon,
13 Dec 2004 15:41:52 +0000
Received: from fea by mail.ornl.gov; Mon, 13 Dec 2004 10:42:36 -0500
Date: Mon, 13 Dec 2004 10:42:36 -0500
From: "James D. Freels" <freelsjd@ornl.gov>
Subject: xfree86 packages upgrade to 4.3.0.dfsg.1-9 from 4.3.0.dfsg.1-8 for
2.6.9 kernels fails nvidia driver
To: submit@bugs.debian.org
Reply-to: freelsjd@ornl.gov
Message-id: <[🔎] 1102952556.1812.8.camel@fea.ornl.gov>
Organization: Oak Ridge National Laboratory
MIME-version: 1.0
X-Mailer: Evolution 2.0.3
Content-type: text/plain
Content-transfer-encoding: 7bit
Delivered-To: submit@bugs.debian.org
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: xfree86
Version: 4.3.0.dfsg.1-9
With the recent upgrade in all the xfree86 packages from -8 to -9 of
Debian/Sid, I discovered a bug when using the commercial nvidia drivers.
This bug does not appear when using the xfree86 nv drivers. It also
does not appear when using the 2.4.28 kernel. Only the 2.6.9 kernel
caused the problem (I only tested 2.4.28 and 2.6.9). I have installed
the commercial nvidia drivers in vanilla fashion directly from the
vendor. I have used the "--force-tls=classic" switch which is required
for some of my legacy applications.
The symptom is that Xfree86 fails on startup. No (EE) messages are
produced. Only the following error message is produced (nvidia driver,
2.6.9 kernel).
Fatal server error:
Caught signal 11. Server aborting
I worked around the problem by using the 2.4.28 kernel. I presently
cannot use the 2.6.9 kernel.
I expect this bug will be rejected since the nvidia driver is not part
of xfree86. However, since one purpose of this new upgrade may be to
include the packages in Sarge, and since there are Debian packages for
the installation of the commercial nvidia drivers, I felt it important
to disclose this bug.
---------------------------------------
Received: (at 285485-done) by bugs.debian.org; 31 Dec 2004 09:36:55 +0000
>From branden@redwald.deadbeast.net Fri Dec 31 01:36:55 2004
Return-path: <branden@redwald.deadbeast.net>
Received: from dhcp065-026-182-085.indy.rr.com (sisyphus.deadbeast.net) [65.26.182.85]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CkJDL-0004yO-00; Fri, 31 Dec 2004 01:36:55 -0800
Received: by sisyphus.deadbeast.net (Postfix, from userid 1000)
id 3B02C68C055; Fri, 31 Dec 2004 04:36:54 -0500 (EST)
Date: Fri, 31 Dec 2004 04:36:54 -0500
From: Branden Robinson <branden@debian.org>
To: 285485-done@bugs.debian.org
Subject: Re: Bug#285485: xfree86 packages upgrade to 4.3.0.dfsg.1-9 from 4.3.0.dfsg.1-8 for 2.6.9 kernels fails nvidia driver
Message-ID: <20041231093654.GH29940@redwald.deadbeast.net>
References: <[🔎] 1102952556.1812.8.camel@fea.ornl.gov>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="9j9z4uig7ElIUlwi"
Content-Disposition: inline
In-Reply-To: <[🔎] 1102952556.1812.8.camel@fea.ornl.gov>
Mail-Copies-To: nobody
X-No-CC: I subscribe to this list; do not CC me on replies.
User-Agent: Mutt/1.5.6+20040907i
Delivered-To: 285485-done@bugs.debian.org
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:
--9j9z4uig7ElIUlwi
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Mon, Dec 13, 2004 at 10:42:36AM -0500, James D. Freels wrote:
> Package: xfree86
> Version: 4.3.0.dfsg.1-9
>=20
> With the recent upgrade in all the xfree86 packages from -8 to -9 of
> Debian/Sid, I discovered a bug when using the commercial nvidia drivers.
> This bug does not appear when using the xfree86 nv drivers. It also
> does not appear when using the 2.4.28 kernel. Only the 2.6.9 kernel
> caused the problem (I only tested 2.4.28 and 2.6.9). I have installed
> the commercial nvidia drivers in vanilla fashion directly from the
> vendor. I have used the "--force-tls=3Dclassic" switch which is required
> for some of my legacy applications.
>=20
> The symptom is that Xfree86 fails on startup. No (EE) messages are
> produced. Only the following error message is produced (nvidia driver,
> 2.6.9 kernel).
>=20
> Fatal server error:
> Caught signal 11. Server aborting
>=20
> I worked around the problem by using the 2.4.28 kernel. I presently
> cannot use the 2.6.9 kernel.
>=20
> I expect this bug will be rejected since the nvidia driver is not part
> of xfree86. However, since one purpose of this new upgrade may be to
> include the packages in Sarge, and since there are Debian packages for
> the installation of the commercial nvidia drivers, I felt it important
> to disclose this bug.
I am closing this bug, but mostly because you didn't provide important
information which is always requested when reports against xserver-xfree86
(well, you didn't file against xserver-xfree86, but rather the xfree86
source package itself, which helps matters not at all) are filed. This
requirement is documented in several places, such as the Debian X FAQ and
the XF86Config-4(5x) manual page.
[The following is a form letter.]
Hello,
You recently filed a bug report against Debian's XFree86 packages that had
so little useful information in it that it could not be meaningfully
handled.
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. A very nice
feature of reportbug is that, if the machine where you run it has network
access to the World Wide Web, it can query the Debian Bug Tracking System
and show you existing reports. This reduces the chance that you'll file a
duplicate report, and offers you the option of adding follow-up information
to an existing bug report. This is especially valuable if you have unique
information to add to an existing report, because this way information
relevant to the problem is gathered together in one place as opposed to
being scattered among multiple, duplicate bug reports where some facts may
be overlooked by the package maintainers. The reportbug program also 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, and try filing your report
again.
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 message has contained a lot of jargon
that is unfamiliar to you, you likely want to use reportbug's "novice"
mode; here's one way to do that.
$ reportbug --mode=3Dnovice
Please enter the name of the package in which you have found a problem,
or type 'other' to report a more general problem.
>
If you're more sophisticated, or if you are not using the released version
of Debian ("stable"), but instead Debian "testing" or "unstable", you
should use reportbug's standard mode.
$ reportbug
Please enter the name of the package in which you have found a problem,
or type 'other' to report a more general problem.
>
The reportbug command is extensively documented in its usage message and
manual page. Commands to view these pieces of documentation are:
$ reportbug --help | more
$ man reportbug
(The output of the above commands has been omitted from this message.)
If you don't want to use reportbug, then please see:
http://www.debian.org/Bugs/Reporting
for detailed instructions on how to file bug reports that are more
likely to be successfully resolved.
You can also view this document locally if you have the "doc-debian"
package installed:
# apt-get install doc-debian
$ pager /usr/share/doc/debian/bug-reporting.txt
Thanks for using the Debian system!
--=20
G. Branden Robinson |
Debian GNU/Linux | If encryption is outlawed, only
branden@debian.org | outlaws will @goH7Ok=3D<q4fDj]Kz?.
http://people.debian.org/~branden/ |
--9j9z4uig7ElIUlwi
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
iEYEARECAAYFAkHVHbYACgkQ6kxmHytGonxHQgCfVc3NqM2adsoWdUPew15zo/rz
Z5IAnjorVyVMZazUUBPgEHwEccbpxZy8
=74tq
-----END PGP SIGNATURE-----
--9j9z4uig7ElIUlwi--
Reply to: