Ah. I see. When I said "Problem solved", I was referring to when you said: "the original report was about a Hardy"
The problem solved was that the bug report wasn't about Gutsy, not that the bug itself was fixed, in any version. > this fglrx driver backported It's not a backport that is needed. What is needed is that the driver shipped with Gutsy be fixed to work as originally intended. On Wed, Apr 2, 2008 at 5:26 PM, Bryce Harrington <[EMAIL PROTECTED]> wrote: > @Loye, please remain civil. I had asked if the issue was still present > in Hardy, then you said "Problem solved, now fix it in Gutsy," which I > interpreted to mean as you confirming the problem is fixed and that you > wanted this fglrx driver backported to Gutsy. We do not backport l-r-m > for obvious reasons, but encourage use of Envy instead. I guess the > lesson is to not say "Fire" in a movie theater, "Bomb" in an airport, or > "Problem solved" on a bug report, unless you really mean it. ;-) > > -- > [fglrx] No DRI using fglrx through restricted driver manager > https://bugs.launchpad.net/bugs/194892 > You received this bug notification because you are a direct subscriber > of the bug. > -- Loye Young Isaac & Young Computer Company Laredo, Texas (956) 857-1172 [EMAIL PROTECTED] ** Attachment added: "unnamed" http://launchpadlibrarian.net/13079905/unnamed -- [fglrx] No DRI using fglrx through restricted driver manager https://bugs.launchpad.net/bugs/194892 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
