I guess given the release date that this fix is in Raring? Should I raise a new bug since I'm getting a similar error in Raring?
I guess given the release date that this fix is in Raring? Should I raise a new bug since I'm getting a similar error in Raring?