Bug#257302: xfree86: general complaint about XFree86 on Dell Latitude D400
Hi, About 3 years ago, you reported a bug to the Debian BTS regarding general problems with XFree86 on a Dell Latitude D400. Do you still have problems running X on this laptop? If not, I will close this bug in the next weeks. Thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#257302: xfree86: general complaint about XFree86 on Dell Latitude D400
On Tue, Jul 13, 2004 at 01:22:09PM -0400, Joey Hess wrote: > Branden Robinson wrote: > > The debconf reorg is scheduled, but I *don't* have plans to introduce a > > spurious dependency of xserver-xfree86 on discover, mdetect, or read-edid. > > Have you considered doing an xfree86-config package that is separate > from X and depends on the right set of tools? I like this, because it > allows for a xfree86-knoppix-config or whatever. > > > I thought it was agreed a long time ago that it really was the installer's > > job to get hardware autodetection tools onto the system. > > That's fine for general purpose hardware detection tools, but for things > like read-edid and mdetect, we either end up bloating systems with no X > with these tools, or we end up with unresolvable bugs like #250422. On Tue, Jul 13, 2004 at 09:00:21PM +0200, Michael Banck wrote: > On Tue, Jul 13, 2004 at 01:22:09PM -0400, Joey Hess wrote: [...] > Did the d-i team consider using the xdebconfigurator package? > > Description: A script used with debconf to autoconfigure xserver-xfree86 > A script-package used in conjunction with debconf to autoconfigure > xserver-xfree86. This script is supposed to help setup X correctly > even with DEBIAN_FRONTEND set to noninteractive. > > Just a thought, I haven't really seen it in action. I have no objection to this proposal. I'd be happy to work with the xdebconfigurator maintainer to ensure smooth interoperation. -- G. Branden Robinson| Software engineering: that part of Debian GNU/Linux | computer science which is too [EMAIL PROTECTED] | difficult for the computer http://people.debian.org/~branden/ | scientist. signature.asc Description: Digital signature
Bug#257302: xfree86: general complaint about XFree86 on Dell Latitude D400
On Tue, Jul 13, 2004 at 01:22:09PM -0400, Joey Hess wrote: > Branden Robinson wrote: > > The debconf reorg is scheduled, but I *don't* have plans to introduce a > > spurious dependency of xserver-xfree86 on discover, mdetect, or read-edid. > > Have you considered doing an xfree86-config package that is separate > from X and depends on the right set of tools? I like this, because it > allows for a xfree86-knoppix-config or whatever. Did the d-i team consider using the xdebconfigurator package? Description: A script used with debconf to autoconfigure xserver-xfree86 A script-package used in conjunction with debconf to autoconfigure xserver-xfree86. This script is supposed to help setup X correctly even with DEBIAN_FRONTEND set to noninteractive. Just a thought, I haven't really seen it in action. Michael
Bug#257302: xfree86: general complaint about XFree86 on Dell Latitude D400
Branden Robinson wrote: > The debconf reorg is scheduled, but I *don't* have plans to introduce a > spurious dependency of xserver-xfree86 on discover, mdetect, or read-edid. Have you considered doing an xfree86-config package that is separate from X and depends on the right set of tools? I like this, because it allows for a xfree86-knoppix-config or whatever. > I thought it was agreed a long time ago that it really was the installer's > job to get hardware autodetection tools onto the system. That's fine for general purpose hardware detection tools, but for things like read-edid and mdetect, we either end up bloating systems with no X with these tools, or we end up with unresolvable bugs like #250422. -- see shy jo signature.asc Description: Digital signature
Bug#257302: xfree86: general complaint about XFree86 on Dell Latitude D400
On Sun, Jul 11, 2004 at 04:22:35PM -0400, Joey Hess wrote: > No, read-edid and mdetect are installed by base-config (but see bug #258690), > prior to package installation. They are later removed, iff X was not > installed. [...] > Since X doesn't declare a dependency on them, selecting them for install > at the same time as X does not even guarantee they'll be _unpacked_ when > X is conigured. And they will certianly not be available when it's > preconfigured. This is why base-config is complicated with the need to > mess with read-edid and mdetect itself, and why I'm left with bugs such > as #250422 which I cannot fix. > > There are other, better ways this could be done, but they all require > reorganising how X's configuration is done. The debconf reorg is scheduled, but I *don't* have plans to introduce a spurious dependency of xserver-xfree86 on discover, mdetect, or read-edid. I thought it was agreed a long time ago that it really was the installer's job to get hardware autodetection tools onto the system. Has that thinking changed? If so, why? Should Debian's kernel-image packages start depending on hardware detection tools as well? -- 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#257302: xfree86: general complaint about XFree86 on Dell Latitude D400
Frans Pop wrote: > On Saturday 10 July 2004 19:23, Branden Robinson wrote: > > Doesn't d-i install mdetect to autodetect the mouse? > > D-i does install both read-edid and mdetect during first stage installation. > However, they are both _uninstalled_ somewhere during base-config. > (See also #250422) No, read-edid and mdetect are installed by base-config (but see bug #258690), prior to package installation. They are later removed, iff X was not installed. > I have noticed myself that if read-edid and mdetect are installed at the same > time as xfree-xserver86 (e.g. by selecting them from the "suggests" list), > they may not be used during X configuration (as they are not yet set up at > that time). Since X doesn't declare a dependency on them, selecting them for install at the same time as X does not even guarantee they'll be _unpacked_ when X is conigured. And they will certianly not be available when it's preconfigured. This is why base-config is complicated with the need to mess with read-edid and mdetect itself, and why I'm left with bugs such as #250422 which I cannot fix. There are other, better ways this could be done, but they all require reorganising how X's configuration is done. -- see shy jo signature.asc Description: Digital signature
Bug#257302: xfree86: general complaint about XFree86 on Dell Latitude D400
On Saturday 10 July 2004 19:23, Branden Robinson wrote: > Doesn't d-i install mdetect to autodetect the mouse? D-i does install both read-edid and mdetect during first stage installation. However, they are both _uninstalled_ somewhere during base-config. (See also #250422) I have noticed myself that if read-edid and mdetect are installed at the same time as xfree-xserver86 (e.g. by selecting them from the "suggests" list), they may not be used during X configuration (as they are not yet set up at that time). Cheers, FJP
