[Please always cc the bug address, i.e. reply to all.] On Sun, 2012-05-13 at 14:48 -0700, Paul Zimmerman wrote: > > On Monday, May 7, 2012 7:11 PM, Ben Hutchings <b...@decadent.org.uk> wrote: > > >On Mon, 2012-05-07 at 14:51 -0700, Paul Zimmerman wrote: > >> So what is happening with this bug? It seems to be the same thing that > >> has broken what was perfectly working wifi on my laptop when I had > >> Lenny installed. But upgrading to Squeeze so I could continue to get > >> security updates has left me with no wireless connection unless I plug > >> in an external device. It doesn't seem to have been marked as fixed, > >> as it should not be if it is still present in the standard Squeeze > >> kernel, but at the end of one of the responses it says a fix has been > >> entered into the 2.6.36~rc5-1~experimental.1 kernel. > >[...] > > >The bug log is at <http://bugs.debian.org/604613> and there is no claim > >that it has been fixed. > > >Can you test Linux 3.2 from testing/unstable/squeeze-backports? Then we > >can see whether it was fixed after Linux 2.6.32. and either report the > >bug upstream or try to find that fix. > > Well, I don't claim to understand the system, but in a page linked on this > one (http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=11;bug=604613) it gives > a series of "reassigned" reports, ending with: > > reassign 586995 linux-2.6 2.6.32-24 > found 586995 linux-2.6/2.6.32-24 > fixed 586995 2.6.36~rc5-1~experimental.1 > thanks > > So it looks like the work on the bug was bounced around to various places, > perhaps because the same problem was causing more than one bug report. > The "fixed" line at the end would seem to mean that it was resolved, but > put into the experimental kernel rather than the stable one issued to users.
I reassigned a large number of bugs with a single control message, one
of which happened to be this one. I also marked another bug fixed.
> As for the backported kernel, I did try that when I first upgraded and found
> the
> wifi was broken. It would not finish loading, but froze with a black screen
> when
> it tried to start the desktop. It seems to be a little _too_ unstable for me
> at this
>
> time. :) So I simply uninstalled it. But if it has been updated since early
> March,
> I can try it again and let you know if it works now.
It's updated almost every week in unstable. I can't promise the
graphics bug has been fixed though.
Ben.
--
Ben Hutchings
Experience is directly proportional to the value of equipment destroyed.
- Carolyn Scheppner
signature.asc
Description: This is a digitally signed message part
