This bug does not appear in the list of ~80 current bugs for Dapper on https://launchpad.net/distros/ubuntu/dapper/+bugs (or the next page). But I believe this is a current Dapper bug, and so anyone wanting to know the status of Dapper should see it. Strangely, when I type 47775 in the search field on that page, I get the page for this bug, i.e., the search doesn't limit itself to the list of ~80 current Dapper bugs. My guess is that this bug should still be listed on https://launchpad.net/distros/ubuntu/dapper/+bugs, and hopefully quite high (just below bug #1) on the list so that the upstream patch gets incorporated into Dapper. If I understand correctly, this is the only other "confirmed critical" bug on Dapper.
Thanks.
PS: I have been bitten by this bug on a Thinkpad A31p with ATI FireGL 7800 (which is similar to a Radeon 7500 mobility). I'm currently using gentoo (with much maintenance fatigue) and this bug is the only barrier to my switching to Dapper.
This bug does not appear in the list of ~80 current bugs for Dapper on https:/ /launchpad. net/distros/ ubuntu/ dapper/ +bugs (or the next page). But I believe this is a current Dapper bug, and so anyone wanting to know the status of Dapper should see it. Strangely, when I type 47775 in the search field on that page, I get the page for this bug, i.e., the search doesn't limit itself to the list of ~80 current Dapper bugs. My guess is that this bug should still be listed on https:/ /launchpad. net/distros/ ubuntu/ dapper/ +bugs, and hopefully quite high (just below bug #1) on the list so that the upstream patch gets incorporated into Dapper. If I understand correctly, this is the only other "confirmed critical" bug on Dapper.
Thanks.
PS: I have been bitten by this bug on a Thinkpad A31p with ATI FireGL 7800 (which is similar to a Radeon 7500 mobility). I'm currently using gentoo (with much maintenance fatigue) and this bug is the only barrier to my switching to Dapper.