ubuntu-x-swat team mailing list archive

[David Oser <mirmos192@xxxxxxxxx>]

@Brian Rogers (#145) - I may be misunderstanding the word 'distro', but Peppermint Linux (otherwise ugh-for-me) is not affected (kernel 2.6.32-22, if I remember correctly) and rcs 5,6.7 of Mainline Lucid version is also not affected - at least, they work fine with my i855 display.
@Steve Langasek (#152) - the same basic symptom is evident on a number of intel display chipsets. Does it make sense to file them under separate bug numbers? I know programming is an iterative process, but sometimes it makes sense to take an overview.

Now for a bit of a rant, if you'll forgive me. Just a glance through the
normal forums indicates that there are many many ordinary people
affected by this bug... to the extent that they cannot upgrade from the
excellent 9.10 version without very complicated (for normal people)
workarounds, nor install Lucid cleanly for the first time. I really
think the release of Lucid before these bugs were fixed (and they
certainly were not evident in the excellent early Lucid alphas - so we
are talking of regression, here) was a serious mistake. I know open
source development is a labour of love, and many people have devoted
enormous numbers of hours to Ubuntu Lucid, without any financial reward
for their efforts. I certainly do not blame them at all, as some are
still hard at work trying to solve this particular problem. But somebody
made a decision to respect some 'magic date' for full release, and, in
my opinion, that someone made a serious error. This kind of thing tends
to bring the concept of open-source software into disrepute. Is it
intended for the masses, or just a geeky few?

Best
David

-- 
MASTER: [i855] GPU lockup (apport-crash)
https://bugs.launchpad.net/bugs/541511
You received this bug notification because you are a member of Ubuntu-X,
which is the registrant for xf86-video-intel.