Tom Lane wrote:
> Stefan Kaltenbrunner <[EMAIL PROTECTED]> writes:
>> seahorse just failed again with one of the dreaded "permission denied"
>> errors we seem to sporadically getting reported on the lists:
>> seahorse is just a stock windows XP box (with all patches and
>> servicepacks applied) and msys/mingw.
>> There is no other software installed or ever was - maybe there is really
>> an underlying issue that is causing those sporadic "permission denied"
>> errors ?
> How repeatable is it?

this seems two be the second time seahorse managed to trigger that
(first was a manual build a while ago) - so unfortunably not very
repeatable :-(

> It would be interesting to know the actual underlying Windows error code
> --- I see that win32error.c maps several different codes to EACCES.

yeah - is there a way to log the actual windows error code too ?


---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?


Reply via email to