Comment 17 for bug 1111459

v1nce (vincent-pennec) wrote :

Yes.

> there are no issues with the (most recent) patch in regards to this bug

I don't know what is the latest patch version.
I tested with 1:0.48+devel+12226+35~precise1.

When I opened 1122495 someone (JazzyNico) suggested 1122495 could be closely related to (if not a duplicate of) 1111459.
For me it looks like your patch fixes 1111459 (with no side effect as much as I can tell) but not the 1122495.

Sorry for reporting stuff about 1122495 here. It introduces confusion.