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

Bug#444384: marked as done (inefficient starting?)

Your message dated Fri, 05 Mar 2010 22:08:00 +0100
with message-id <4B9172B0.3040706@ens-lyon.org>
and subject line KMS rulez
has caused the Debian Bug report #444384,
regarding inefficient starting?
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
444384: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=444384
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: xdm
Version: 1:1.1.6-3
Severity: wishlist

I noticed something this time while happening to be starting at the
screen when xdm starts:

*Twice* during the oh, two seconds that xdm takes to start, the screen
has this being powered off look to it, where there is this tide of
powered off screen area that advances toward the center from the edges
of the screen, only getting about 1/4 of the way though.

Anyway, this tells me that something is being done twice at the
perhaps unfortunate wear and tear of the hardware.

If this was a simple program (like expr(1)), perhaps it would be no
big deal, but starting X windows certainly should be done with care
for using the hardware non-wastefully...

Attached log file. P.S., inform me if (EE) and (WW)'s can be helped. Thanks.

Anyway, one way to test would be to start xdm on a very slow/loaded
system and watch what was going on on the screen.

Of course I can't help, as my mountaintop equipment has no backup, and
I prefer to just report bugs and leave looking under the hood for the
experts.

P.S., xdm looks good on 800x600 now, but bevel bug is still present at
larger values.

Attachment: Xorg.0.log.bz2
Description: jidanni's X log file


--- End Message ---
--- Begin Message --- 
Fixed with KMS drivers.

Brice

--- End Message ---
Reply to: