-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 03/07/2013 01:57 PM, Jean-David Beyer wrote:
> On 03/07/2013 01:44 PM, Ludwig Hügelschäfer wrote:
>> On 07.03.13 17:02, Jean-David Beyer wrote:
>>> I seem to be getting stuff like this in my .xsession-errors 
>>> file.
>>> 
>>> .xsession-errors:2013-03-07 10:17:27.796 [DEBUG] enigmail.js: 
>>> WriteFileContents: file=/jome/jeandavid8/Desktop/enigout.txt
>>> 
>>> .xsession-errors:2013-03-07 10:17:27.797 [ERROR] enigmail.js: 
>>> CreateFileStream: Failed to create 
>>> /jome/jeandavid8/Desktop/enigout.txt
>>> 
>>> .xsession-errors:2013-03-07 10:17:27.797 [ERROR] enigmail.js: 
>>> WriteFileContents: Failed to write to 
>>> /jome/jeandavid8/Desktop/enigout.txt
>>> 
>>> 
>>> Obviously, I must have typed jome instead of home in some 
>>> configuration file, but I cannot find it. It does not seem to
>>> be in my .xsession file (I do not even have one). Or in any of
>>> the files in /home/jeandavid8.
>>> 
>>> There is no /jome directory.
>>> 
>>> Any idea where I have this error?
> 
>> Looks like the path for your Enigmail debug logs is set wrong. 
>> Please look at OpenPGP -> Preferences, select Debug and set the
>> Log directory path correctly.
> 
> Hey! That is it! I just fixed it. I will see tomorrow if that
> fixed the problem, but I am pretty sure it will.
> 
> Thanks very much.
> 
>> Don't know why these error messages are written into 
>> .xsession-errors, but I'm not too fit in Linux/Unix ;-)
> 
>> HTH
> 
> I do not know why it is trying to write any messages, since as far
> as I can tell, enigmail is working correctly. But I assume much
> less will be written to .xsession-errors and I will be able to
> figure it all out.
> 
> Let's see what happens if I try to sign this.
> 
OK. Now it can write what it wanted to write, and it has written several
files to /home/jeandavid8/Desktop. Like this (you probably do not care
what is in them):

$ cat enigcmd.txt
/usr/bin/gpg2 --charset utf-8 --display-charset utf-8 --batch --no-tty
[snip]

$ cat enigenv.txt
DISPLAY=:0.0,HOME=/home
[snip]

$ cat enigout.txt
tru::1:1362669409:1451579252:3:1:5
[snip]

I hope setting the log path to null will turn it off completely.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJROPLOAAoJEBZthAoMYQyL6M4H/iDA1x/xTR/DfV9NCPARvTr2
JcwEIvAS2/9cgq9NPE58qnpkwubLsKUdUsTniiQMP/rY/PxsWnb+JukYAkmRQZke
K/tuTYh5Z9kpGHRbR3ha5PKx4/JzPNDwQn6kSpUJ89yXz3ibyfkLVVECQRItliQr
DcRqZQj8NA4MY4zB8Pv299lgEMFUTnQTOjVMniRCRK7oVbG/urtL5ygvKb9XHZa1
+N5e2YjKYkgIqHMihyD/PuXet9tO0JEijtR3tJEFLi7pqoTMbo1APmu/BxH2mLb/
wcoCkLFs/cZZQ0m5dYhfU2b8YW+MU9mKdaSyzYes5U7SYrtTBjKftMOo4m+4+iA=
=igLR
-----END PGP SIGNATURE-----


_______________________________________________
enigmail-users mailing list
[email protected]
https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net

Reply via email to