On 12-01-12 12:21 PM, Chow Loong Jin wrote: > > Looks like the libproxy/webkit bug you mentioned.
Shouldn't be per http://code.google.com/p/libproxy/issues/detail?id=153#c9 (comment #9) which is the work-around I have implemented here locally and it resolves the issue with gnome-clock (so as a work-around, it works).
> Is there a bug filed in > Launchpad for this?
Yup. https://bugs.launchpad.net/ubuntu/+source/libproxy/+bug/547106 and going on 2 years old now.
> Also, I think http://code.google.com/p/libproxy/issues/detail?id=153 is the > relevant upstream bug for that issue.
It is, and as you can see in that bug, upstream is not going to address the very old version of libproxy that Ubuntu is still carrying.
b.
On 12-01-12 12:21 PM, Chow Loong Jin wrote:
>
> Looks like the libproxy/webkit bug you mentioned.
Shouldn't be per code.google. com/p/libproxy/ issues/ detail? id=153# c9 (comment #9)
http://
which is the work-around I have implemented here locally and it resolves
the issue with gnome-clock (so as a work-around, it works).
> Is there a bug filed in
> Launchpad for this?
Yup. https:/ /bugs.launchpad .net/ubuntu/ +source/ libproxy/ +bug/547106 and
going on 2 years old now.
> Also, I think http:// code.google. com/p/libproxy/ issues/ detail? id=153 is the
> relevant upstream bug for that issue.
It is, and as you can see in that bug, upstream is not going to address
the very old version of libproxy that Ubuntu is still carrying.
b.