On Sun 21 May 2006, Martin-Éric Racine wrote: > > Upon a fresh installation of X11 7.0, dexconf produces a zero-lenght > xorg.conf, whenever automatic keyboard detection failed (debconf:high).
(I'm using 1:7.0.20) It also happened to me, when I answered "no" to automatic keyboard detection, I was not asked the question which keyboard to use; I only saw that answer after running "dpkg-reconfigure xserver-xorg". However: > A zero file is also produced at debconf:medium priority. At this priority, > dexconf DOES inform the user that configuration failed and suggests running > "dpkg-reconfigure xserver-xorg", but doing exactly that fixes nothing: the > post-install script informs that is has NOT updated the config, because it > thinks that /etc/X11/X has been modified (which is not the case). > > Trying "dpkg-reconfigure -p low xserver-xorg" does not solve it either; > the user is still left with a zero-lenght xorg.conf. I tried removing the xorg.conf and the /etc/X11/X symlink; however, the postinst _still_ refuses to create the xorg.conf (and the X symlink) because with "dpkg-reconfigure" $2 contains the current version number and this code (around line 890) sets the $UPGRADE flag: if [ "$1" = "configure" ] && [ -n "$2" ]; then UPGRADE='true' fi Then the code at line 1651: # here's a novel concept: DON'T TOUCH THE CONFIG ON UPGRADES if [ -z "$UPGRADE" ] || dpkg --compare-versions "$2" le "1:7.0.14"; then thinks it's being upgraded... while I'm still trying to get the first installed version ever to work (this is on a fresh amd64 install). The logic needs to be improved somewhat... Paul Slootman -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
