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

Bug#226210: priority inflation and bad default mouse port with mdetect



On Thu, Jan 08, 2004 at 08:09:35PM -0500, Joey Hess wrote:
> Branden Robinson wrote:
> > Hmm.  I thought I did this.
> > 
> > Actually, I do.  Except I'm asking at medium, not high.  It's a "normal
> > item that has a reasonable default" (see debconf-devel(7)).  A correct
> > answer is important for the user to have a good computing experience, so
> > it cannot be low priority ("Very trivial items that have defaults that
> > will work in the vast majority of cases; only control freaks see
> > these.").
> > 
> > Perhaps you can help me find the bug in the following:
> 
> I'm not going to try to comprehend this code, but I can tell you that I
> reconfigured the package with debconf developer debugging on, and it had
> decided to ask the question at high priority. Medium priority would be
> fine.

I agree, and I have had a fresh look at the code, but I still don't see
how mdetect is working but the question is still being asked at high
priority.

Could you do a fresh install of the package with the following variable
set and exported?

# export DEBUG_XFREE86_DEBCONF=yes

There should be some chatter to stderr about the mouse, among other
things.

-- 
G. Branden Robinson                |    It was a typical net.exercise -- a
Debian GNU/Linux                   |    screaming mob pounding on a greasy
branden@debian.org                 |    spot on the pavement, where used to
http://people.debian.org/~branden/ |    lie the carcass of a dead horse.

Attachment: signature.asc
Description: Digital signature


Reply to: