Comment 1 for bug 72995

Same problem here.

I figred out two ways to work around this problem:

1) delete .nano_history (since the file doesn't exist, nano is able to create it using the user's rights. I don't know about any bad consequences this might have?)

2) change .nano_history's permissions (for some strange reason I am unable to reproduce this behavior while writing this...)

It should be possible to do both using a cron job - but there should be a better way?