Bug#251690: apparently the same problem with 1-4
-----BEGIN PGP SIGNED MESSAGE-----
apparently the update of libcurl2 which has just been uploaded
(version 7.12.0.is.7.11.2-1 ) has fixed the problem for me.
Adam D. Barratt wrote:
> On Fri, 2004-06-04 at 18:52, Fedor Karpelevitch wrote:
> > I am getting the same problem with 4.3.0.dfsg.1-4 and there is no
> > helpful output as to what the root cause is. I followed
> > instructions for setting env vars but that does not produce any
> > more output.
> > Is there any way to find the root cause?
> 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. Short-term, the easiest
> workaround is to revert libcurl2 to the previous package version
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
-----END PGP SIGNATURE-----