Comment 43 for bug 6367
Revision history for this message
| Scott James Remnant (Canonical) (canonical-scott) wrote | #43 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
While this bug may have been reported very early, it took a very long time to obtain enough information from the users affected to actually pinpoint what was causing the bug.
It is now clear what the bug is.
Unfortunately while fixing it may fix it for you, we have absolutely no way of knowing that it will not break somebody else's machine. That's why this fix will not go into dapper.
As has already been stated in this bug report, edgy will carry the fix from the day it opens (which has not happened yet).
At that point we will know what is broken by fixing this for you -- if nothing is broken, it is very likely that dapper will also be able to carry the fix.