[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#296023: marked as done (XF86Config-4 contains 0 bytes and doesn't change on dpkg-reconfigure)

Your message dated Tue, 13 Feb 2007 00:52:00 +0100
with message-id <45D0FDA0.3000506@ens-lyon.org>
and subject line ping timeout, but some people said it's fixed
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)
--- Begin Message --- 
Package: xserver-xfree86
Version: 4.3.0.dfsg.1-10
Severity: normal

Hi everyone,

I installed Debian on a diskless machine. I mount root and home as nfs from
another machine. The root directory only get's mounted by this machine and
is not in use by any other box.
When I install xserver-xfree86 debconf asks all the usual questions, but the
resulting XF86Config-4 file contains nothing at all. After install it
complains about not being able to remove /tmp/dexconf-tmp-12956, because it
is not empty.
I tried a couple times, removing xserver-xfree86 with dpkg -P as well as
dpkg-reconfigure xserver-xfree86 nothing changed. Only
/tmp/dexconf-tmp-xxxxx gets new numbers every time.
This problem seems to have been touched upon in bug #241532, which seems to
have been closed. In there it said to delete
/var/lib/xfree86/XF86Config-4.md5sum, but that didn't help either.

This bug leaves x completely broken. The only fix is to copy another
XF86Config-4 from another installed X on another machine. I will do this and
hope it works, if it doesn't I will write back.

-- 
Lassen Sie Ihren Gedanken freien Lauf... z.B. per FreeSMS
GMX bietet bis zu 100 FreeSMS/Monat: http://www.gmx.net/de/go/mail

--- End Message ---
--- Begin Message --- 
Closing this bug since people involved (either the submitter or some
confirmers) either did not reply to my ping a couple weeks ago, or said
that the bug is fixed for them. So this bug is probably fixed nowadays.
But, in case anybody ever reproduces this problem, feel free to reopen.

Brice

--- End Message ---
Reply to: