On Wed, 2008-10-08 at 07:23 +0000, Steve Langasek wrote:
> If changing the permissions on the SetIdleHint method doesn't fix the
> problem, could it be that this is a red herring entirely? Is upstream
> confident that the permission change is a necessary and correct fix?
>
Yes, it does seem that this is a red herring for this problem. However,
upstream made the change in git after the 0.3 release, so I thought
it was worthwhile backporting.
As I can't make a convincing case for including it at this point of the
release I don't mind it being rejected.
On Wed, 2008-10-08 at 07:23 +0000, Steve Langasek wrote:
> If changing the permissions on the SetIdleHint method doesn't fix the
> problem, could it be that this is a red herring entirely? Is upstream
> confident that the permission change is a necessary and correct fix?
>
Yes, it does seem that this is a red herring for this problem. However,
upstream made the change in git after the 0.3 release, so I thought
it was worthwhile backporting.
As I can't make a convincing case for including it at this point of the
release I don't mind it being rejected.
Thanks,
James