GNU bug report logs - #36598
26.1; (error "‘/tmp/emacs1000’ is not a safe directory because it is a symlink")

Previous Next

Package: emacs;

Reported by: mah <at> everybody.org (Mark A. Hershberger)

Date: Thu, 11 Jul 2019 14:12:01 UTC

Severity: normal

Tags: fixed

Found in version 26.1

Done: Noam Postavsky <npostavs <at> gmail.com>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: phillip.lord <at> russet.org.uk
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: bug-gnu-emacs <bug-gnu-emacs-bounces+phillip.lord=russet.org.uk <at> gnu.org>, mah <at> everybody.org, 36598 <at> debbugs.gnu.org
Subject: bug#36598: 26.1; (error "‘/tmp/emacs1000’ is not a safe directory because it is a symlink")
Date: Sat, 13 Jul 2019 15:30:50 +0100
On 2019-07-13 05:38, Lars Ingebrigtsen wrote:
> mah <at> everybody.org (Mark A. Hershberger) writes:
> 
>> $ ls -l /tmp/emacs1000
>> lrwxrwxrwx 1 mah mah 20 Jul 11 09:53 /tmp/emacs1000 -> 
>> /run/user/1000/emacs
>> 
>> Whoever set up the symlink for /tmp/emacs1000 should also change the
>> value of server-socket-dir.
> 
> I'm unable to reproduce this error -- do you have a recipe starting 
> from
> "emacs -Q"?
> 
> What is it that triggers the "is not a safe directory because it is a
> symlink" error?  Do you have a backtrace?


I discovered the cause of this the other day.

Launch emacs-27, start the server. Now launch emacs-26 and start the 
server with a different. The problem is that
emacs-27 creates the file /tmp/emacs($PID) as a symlink, while emacs-26 
doesn't like it.

Probably created by

b663c837249 (Stefan Monnier          2019-05-03  538)

Phil




This bug report was last modified 5 years and 356 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.