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

Bug#233933: acknowledged by developer (closing 233933 :-])



reopen 233933
thanks

On Sun, Feb 22, 2004 at 09:48:15PM -0800, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> #233933: X server 4.3 stalls for a few seconds when switching from console back to X,
> which was filed against the xserver-xfree86 package.
> 
> It has been marked as closed by one of the developers, namely
> Raphael Zimmerer <killekulla@rdrz.de>.

Umm, this bug was improperly closed here, I never got Branden's initial
message to -done, but that wasn't a proper closing either.

After wading through the obnoxiously long bug log due to extraneous log
files attached inline (d'oh), I'll note that I'm using X mouse protocol
"ImPS/2" for my /dev/gpmdata and GPM is set to repeat "raw" from "imps2".

Further, it's entirely bollocks to say that a problem like this can be
easily closed as a "user configuration error" when the exact same thing
works perfectly with the same version of gpm and an older version of X, and
neither of the programs/packages provided any clue whatsoever that they
could have a problem.

I am also entirely unimpressed by mindless rants from the gpm maintainer
about how he's "said it MANY times, and [he] will say it again" when his
very package has continuously offered this configuration option over the
last several years (cf. gpm(8)), and it has actually worked well until the
latest X. I have no reason to believe that the problem is due to anything
other but an minor, possibly revertible, change in the behaviour of the X
server.

That said, I didn't even verify that it's the same bug as the other
submitters have said, and my settings happen to be (slightly) different than
theirs. It wouldn't have killed either of you Debian maintainers to show
some common courtesy towards the initial submitters and get them to ACK that
they don't indeed still exhibit the problem before dismissing the bug report
as an error on the part of those people.

I'll test the 4.3.0-2 package shortly and then see if I should rephrase the
bug report's title into a request for proper documentation and/or clone
another copy over to gpm with similar intent. Heck, who are we to say that
the behaviour shouldn't actually try to be *gasp* fixed upstream?
It would still be a normal bug in any event.

-- 
     2. That which causes joy or happiness.



Reply to: