* pinentry start report error ‘/tmp/emacs1000’ is not a safe directory
@ 2019-08-08 11:06 numbchild
2019-08-08 12:06 ` Noam Postavsky
0 siblings, 1 reply; 3+ messages in thread
From: numbchild @ 2019-08-08 11:06 UTC (permalink / raw)
To: emacs-help
I configure pinentry:
#+begin_src emacs-lisp
(use-package pinentry
:ensure t
:init (pinentry-start))
#+end_src
But Emacs raise error:
#+begin_example
Debugger entered--Lisp error: (error "‘/tmp/emacs1000’ is not a safe
directory because i...")
signal(error ("‘/tmp/emacs1000’ is not a safe directory because i..."))
error("`%s' is not a safe directory because %s" "/tmp/emacs1000" "it is a
symlink")
server-ensure-safe-dir("/tmp/emacs1000")
pinentry-start()
eval((pinentry-start) nil)
elisp--eval-last-sexp(nil)
eval-last-sexp(nil)
eros-eval-last-sexp(nil)
funcall-interactively(eros-eval-last-sexp nil)
call-interactively(eros-eval-last-sexp nil nil)
command-execute(eros-eval-last-sexp)
#+end_example
- My Emacs version (compiled from master branch source code):
GNU Emacs 27.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.10) of
2019-07-09
- pinentry version: 0.1 from GNU ELPA
[stardiviner] <Hack this world!> GPG key ID: 47C32433
IRC(freeenode): stardiviner Twitter: @numbchild
Key fingerprint = 9BAA 92BC CDDD B9EF 3B36 CB99 B8C4 B8E5 47C3 2433
Blog: http://stardiviner.github.io/
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: pinentry start report error ‘/tmp/emacs1000’ is not a safe directory
2019-08-08 11:06 pinentry start report error ‘/tmp/emacs1000’ is not a safe directory numbchild
@ 2019-08-08 12:06 ` Noam Postavsky
2019-08-09 0:28 ` [SOLVED] " numbchild
0 siblings, 1 reply; 3+ messages in thread
From: Noam Postavsky @ 2019-08-08 12:06 UTC (permalink / raw)
To: numbchild@gmail.com; +Cc: emacs-help
On Thu, 8 Aug 2019 at 07:07, numbchild@gmail.com <numbchild@gmail.com> wrote:
> error("`%s' is not a safe directory because %s" "/tmp/emacs1000" "it is a
> symlink")
> - My Emacs version (compiled from master branch source code):
>
> GNU Emacs 27.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.10) of
> 2019-07-09
This sounds like Bug#36599, update master to something later than
2019-07-18, and then delete the /tmp/emacs1000 symlink.
https://debbugs.gnu.org/36598
^ permalink raw reply [flat|nested] 3+ messages in thread
* [SOLVED] Re: pinentry start report error ‘/tmp/emacs1000’ is not a safe directory
2019-08-08 12:06 ` Noam Postavsky
@ 2019-08-09 0:28 ` numbchild
0 siblings, 0 replies; 3+ messages in thread
From: numbchild @ 2019-08-09 0:28 UTC (permalink / raw)
To: Noam Postavsky; +Cc: emacs-help
Thanks, using your method, I recompiled the latest `master` branch source
code. And deleted `/tmp/emacs1000` symlink. Not the warning is gone.
[stardiviner] <Hack this world!> GPG key ID: 47C32433
IRC(freeenode): stardiviner Twitter: @numbchild
Key fingerprint = 9BAA 92BC CDDD B9EF 3B36 CB99 B8C4 B8E5 47C3 2433
Blog: http://stardiviner.github.io/
On Thu, Aug 8, 2019 at 8:06 PM Noam Postavsky <npostavs@gmail.com> wrote:
> On Thu, 8 Aug 2019 at 07:07, numbchild@gmail.com <numbchild@gmail.com>
> wrote:
>
> > error("`%s' is not a safe directory because %s" "/tmp/emacs1000" "it
> is a
> > symlink")
>
> > - My Emacs version (compiled from master branch source code):
> >
> > GNU Emacs 27.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.10)
> of
> > 2019-07-09
>
> This sounds like Bug#36599, update master to something later than
> 2019-07-18, and then delete the /tmp/emacs1000 symlink.
>
> https://debbugs.gnu.org/36598
>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2019-08-09 0:28 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-08-08 11:06 pinentry start report error ‘/tmp/emacs1000’ is not a safe directory numbchild
2019-08-08 12:06 ` Noam Postavsky
2019-08-09 0:28 ` [SOLVED] " numbchild
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).