From unknown Sun Jun 22 03:46:58 2025 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Mailer: MIME-tools 5.509 (Entity 5.509) Content-Type: text/plain; charset=utf-8 From: bug#70973 <70973@debbugs.gnu.org> To: bug#70973 <70973@debbugs.gnu.org> Subject: Status: 29.1; "Unlocking file: Invalid argument" Warning saving via a softlink with stale file lock Reply-To: bug#70973 <70973@debbugs.gnu.org> Date: Sun, 22 Jun 2025 10:46:58 +0000 retitle 70973 29.1; "Unlocking file: Invalid argument" Warning saving via a= softlink with stale file lock reassign 70973 emacs submitter 70973 Duncan Greatwood severity 70973 normal thanks From debbugs-submit-bounces@debbugs.gnu.org Thu May 16 01:12:56 2024 Received: (at submit) by debbugs.gnu.org; 16 May 2024 05:12:56 +0000 Received: from localhost ([127.0.0.1]:46535 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1s7TQE-0005iZ-M0 for submit@debbugs.gnu.org; Thu, 16 May 2024 01:12:56 -0400 Received: from lists.gnu.org ([209.51.188.17]:53300) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1s7PNA-0001zC-B6 for submit@debbugs.gnu.org; Wed, 15 May 2024 20:53:34 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1s7PN6-0003xu-GD for bug-gnu-emacs@gnu.org; Wed, 15 May 2024 20:53:24 -0400 Received: from mail-lf1-x130.google.com ([2a00:1450:4864:20::130]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1s7PN3-0006lK-0y for bug-gnu-emacs@gnu.org; Wed, 15 May 2024 20:53:23 -0400 Received: by mail-lf1-x130.google.com with SMTP id 2adb3069b0e04-51fdc9af005so280304e87.3 for ; Wed, 15 May 2024 17:53:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1715820799; x=1716425599; darn=gnu.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=TKAxdKpfCmk8l5zQx2YrnBjLq95Ezv7U4GBAiIVyDgA=; b=Po4jJhO4SklYpcfF0OGghjyY08vguIOdW0/Oq1Rl1hQjb9ZCRm3wmv9Cg9Lqar0R2O ss+lJqTJH68Idfpfkha0U9SAgu44PmnbzBxJJPOcR2GWwn0yk8F6XqEwaoXgnSSSgRhJ 8tYl2E621/VBz8fctlXUx5SbsWQMmhEruU7h5ZB1G+3L1cPdla7oMo4w+mxFe2xFeV6y BnJQOqdEoutMRJuk5S/pPPJIIUz6AITZNuufy5d3MmFAV4gIj6q2kZ1wFj7nX/9Lcabk vj+FaFcs8jbp2iUCs2iyy9P6j1Q/I+DPwIoV6yWiTM950gjHN9bJqQuPGHwp2Kr8HbFS l1EA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1715820799; x=1716425599; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=TKAxdKpfCmk8l5zQx2YrnBjLq95Ezv7U4GBAiIVyDgA=; b=nxl6UNzpZcG/0LPQjmFuLZiI2YBOVnrMuufGyA7HpUrPTEgWoQ7seg7Z1xnVyL2HgV ePBp5EpnDONkWIuDvzOIrsIlhElbd5RqI8u6d6CITD2sEfbPKl51koV6tuNY6/Yb+jhl yHL6PWsCibFPp7gOhHXPpxhUU8VtH6JVczPGEF4WMQOWiPcRICI+ETsrFXKW8ZwrdIQ+ 5JTaHwi8aztmiJ243GN7kOtUGBlpIhpNfhdNaV5N9edIPSMddIDmc4qz7SKXSegArUbB Z1er1FmxncJe/kSqJL7r0GqFqrT4ssW1FmdDcrwVj4LO4kPrBA1Mj4+DOC3qr0eAibxD TMaQ== X-Gm-Message-State: AOJu0YyP3eLlGscRWSNHwfdT7dX1MEmBuodu3m7jqvEqTJ0mU5YNIvbw g+Ju94ZGMDi8FlykOuHI9Jle0m5ll8pC4zJ+VCrWMtSNFO5TGVqaKahFSrKR X-Google-Smtp-Source: AGHT+IG94zShwJLL8l9LkG7PNyb5ZkamkzPQRogrW9/5w0VYbNMOO+xoB1johIvenmpTW0iYf3b0rQ== X-Received: by 2002:a2e:9dc6:0:b0:2e6:f602:a02f with SMTP id 38308e7fff4ca-2e6f602a208mr28389111fa.52.1715820798041; Wed, 15 May 2024 17:53:18 -0700 (PDT) Received: from mail-ed1-f43.google.com (mail-ed1-f43.google.com. [209.85.208.43]) by smtp.gmail.com with ESMTPSA id 4fb4d7f45d1cf-5733bea65b5sm9906727a12.6.2024.05.15.17.53.17 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 15 May 2024 17:53:17 -0700 (PDT) Received: by mail-ed1-f43.google.com with SMTP id 4fb4d7f45d1cf-57230faeb81so1773062a12.0 for ; Wed, 15 May 2024 17:53:17 -0700 (PDT) X-Received: by 2002:a50:935b:0:b0:574:ecec:1887 with SMTP id 4fb4d7f45d1cf-574ecec19camr4515415a12.32.1715820796642; Wed, 15 May 2024 17:53:16 -0700 (PDT) MIME-Version: 1.0 From: Duncan Greatwood Date: Wed, 15 May 2024 17:53:05 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: 29.1; "Unlocking file: Invalid argument" Warning saving via a softlink with stale file lock To: bug-gnu-emacs@gnu.org Content-Type: multipart/alternative; boundary="000000000000152f79061887a9ce" Received-SPF: pass client-ip=2a00:1450:4864:20::130; envelope-from=dgreatwood@gmail.com; helo=mail-lf1-x130.google.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-Spam-Score: 1.0 (+) X-Debbugs-Envelope-To: submit X-Mailman-Approved-At: Thu, 16 May 2024 01:12:53 -0400 X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -2.3 (--) --000000000000152f79061887a9ce Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable While editing the ~/.emacs file in emacs, the machine rebooted (kernel panic I believe). This left a lock file behind. The ~/.emacs file is actually a softlink: .emacs -> /Users//Dropbox/Documents/Projects/emacs/dotemacs The fact that it's a softlink may or may not be relevant. In ~/Dropbox/Documents/Projects/emacs/, there was a file: .#dotemacs After the reboot, I started emacs, and continued with further edits to .emacs. Upon saving .emacs, had the following warning: =E2=9B=94 Warning (unlock-file): Unlocking file: Invalid argument, ~/Dropbox/Documents/Projects/emacs/dotemacs, ignored As per the warning, the save was nonetheless successful. Invoking file-locked-p directly, I saw the same error, and the following debug info: Debugger entered--Lisp error: (file-error "Testing file lock" "Invalid argument" "~/Dropbox/Documents/Projects/emacs/dotemacs") file-locked-p("~/Dropbox/Documents/Projects/emacs/dotemacs") eval((file-locked-p "~/Dropbox/Documents/Projects/emacs/dotemacs") t) eval-expression((file-locked-p "~/Dropbox/Documents/Projects/emacs/dotemacs") nil nil 127) funcall-interactively(eval-expression (file-locked-p "~/Dropbox/Documents/Projects/emacs/dotemacs") nil nil 127) call-interactively(eval-expression nil nil) command-execute(eval-expression) After removing the lock file manually, the warning on save goes away: rm ~/Dropbox/Documents/Projects/emacs/.#dotemacs Access flags on dotemacs file are as follows: -rw-r--r--@ 1 dgreatwood staff 133806 May 15 16:01 dotemacs lrwxr-xr-x 1 dgreatwood staff 59 Dec 6 2015 .emacs -> ... Thanks. ---- In GNU Emacs 29.1 (build 1, aarch64-apple-darwin21.6.0, NS appkit-2113.60 Version 12.6.6 (Build 21G646)) of 2023-08-16 built on armbob.lan Windowing system distributor 'Apple', version 10.3.2487 System Description: macOS 14.5 Configured using: 'configure --with-ns '--enable-locallisppath=3D/Library/Application Support/Emacs/${version}/site-lisp:/Library/Application Support/Emacs/site-lisp' --with-modules 'CFLAGS=3D-DFD_SETSIZE=3D10000 -DDARWIN_UNLIMITED_SELECT' --with-x-toolkit=3Dno' Configured features: ACL GLIB GMP GNUTLS JPEG JSON LIBXML2 MODULES NOTIFY KQUEUE NS PDUMPER PNG RSVG SQLITE3 THREADS TIFF TOOLKIT_SCROLL_BARS TREE_SITTER ZLIB Important settings: value of $LANG: en_US.UTF-8 locale-coding-system: utf-8-unix Major mode: Messages Minor modes in effect: server-mode: t override-global-mode: t delete-selection-mode: t tooltip-mode: t global-eldoc-mode: t show-paren-mode: t electric-indent-mode: t mouse-wheel-mode: t menu-bar-mode: t file-name-shadow-mode: t global-font-lock-mode: t font-lock-mode: t blink-cursor-mode: t buffer-read-only: t column-number-mode: t line-number-mode: t transient-mark-mode: t auto-composition-mode: t auto-encryption-mode: t auto-compression-mode: t Load-path shadows: /Users/username/.emacs.d/lisp/dash hides /Users/username/.emacs.d/elpa/dash-20221013.836/dash /Users/username/.emacs.d/elpa/use-package-20221029.1857/use-package-jump hides /Applications/Emacs.app/Contents/Resources/lisp/use-package/use-package-jum= p /Users/username/.emacs.d/elpa/use-package-20221029.1857/use-package-ensure hides /Applications/Emacs.app/Contents/Resources/lisp/use-package/use-package-ens= ure /Users/username/.emacs.d/elpa/use-package-20221029.1857/use-package-core hides /Applications/Emacs.app/Contents/Resources/lisp/use-package/use-package-cor= e /Users/username/.emacs.d/elpa/use-package-20221029.1857/use-package-delight hides /Applications/Emacs.app/Contents/Resources/lisp/use-package/use-package-del= ight /Users/username/.emacs.d/elpa/use-package-20221029.1857/use-package-diminis= h hides /Applications/Emacs.app/Contents/Resources/lisp/use-package/use-package-dim= inish /Users/username/.emacs.d/elpa/use-package-20221029.1857/use-package hides /Applications/Emacs.app/Contents/Resources/lisp/use-package/use-package /Users/username/.emacs.d/elpa/use-package-20221029.1857/use-package-bind-ke= y hides /Applications/Emacs.app/Contents/Resources/lisp/use-package/use-package-bin= d-key /Users/username/.emacs.d/elpa/bind-key-20221028.1858/bind-key hides /Applications/Emacs.app/Contents/Resources/lisp/use-package/bind-key /Users/username/.emacs.d/elpa/use-package-20221029.1857/use-package-lint hides /Applications/Emacs.app/Contents/Resources/lisp/use-package/use-package-lin= t /Users/username/.emacs.d/lisp/linum hides /Applications/Emacs.app/Contents/Resources/lisp/obsolete/linum Features: (shadow mail-extr emacsbug misearch multi-isearch help-fns radix-tree cl-print debug backtrace warnings company-oddmuse company-keywords company-etags company-gtags company-dabbrev-code company-dabbrev company-files company-clang company-capf company-cmake company-semantic company-template company-bbdb company mm-archive message sendmail yank-media dired dired-loaddefs rfc822 mml mml-sec epa derived epg rfc6068 gnus-util mailabbrev gmm-utils mailheader mm-decode mm-bodies mm-encode mail-utils sort autorevert filenotify tango-theme server cmake-mode rst persistent-todo todotxt rustic-spellcheck rustic-expand rustic-lsp rustic-playpen rustic-rustfix rustic-racer etags fileloop xref rustic-babel rustic-rustfmt project org-element org-persist org-id org-refile avl-tree generator org ob ob-tangle ob-ref ob-lob ob-table ob-exp org-macro org-src ob-comint org-pcomplete pcomplete org-list org-footnote org-faces org-entities time-date ob-emacs-lisp ob-core ob-eval org-cycle org-table ol org-fold org-fold-core org-keys oc org-loaddefs find-func cal-menu calendar cal-loaddefs org-version org-compat org-macs format-spec rustic-comint rustic-clippy rustic-doc xdg f f-shortdoc shortdoc rustic-popup rustic-cargo rustic-compile spinner s xterm-color markdown-mode color noutline outline icons rustic-interaction rustic dash pcase use-package use-package-ensure use-package-delight use-package-diminish use-package-bind-key bind-key easy-mmode use-package-core rust-utils thingatpt rust-mode rx rust-rustfmt rust-playpen rust-compile compile text-property-search comint ansi-osc ansi-color ring rust-cargo gnutls network-stream url-cache url-http url-auth mail-parse rfc2231 rfc2047 rfc2045 mm-util ietf-drums mail-prsvr url-gw nsm puny epg-config finder-inf special-scratch kmacro advice string-inflection cl-extra help-mode desktop frameset unbound cl delsel auto-complete-autoloads cmake-font-lock-autoloads cmake-mode-autoloads company-autoloads fuzzy-autoloads popup-complete-autoloads popup-autoloads info package browse-url url url-proxy url-privacy url-expand url-methods url-history url-cookie generate-lisp-file url-domsuf url-util mailcap url-handlers url-parse auth-source cl-seq eieio eieio-core cl-macs password-cache json subr-x map byte-opt gv bytecomp byte-compile url-vars cl-loaddefs cl-lib rmc iso-transl tooltip cconv eldoc paren electric uniquify ediff-hook vc-hooks lisp-float-type elisp-mode mwheel term/ns-win ns-win ucs-normalize mule-util term/common-win tool-bar dnd fontset image regexp-opt fringe tabulated-list replace newcomment text-mode lisp-mode prog-mode register page tab-bar menu-bar rfn-eshadow isearch easymenu timer select scroll-bar mouse jit-lock font-lock syntax font-core term/tty-colors frame minibuffer nadvice seq simple cl-generic indonesian philippine cham georgian utf-8-lang misc-lang vietnamese tibetan thai tai-viet lao korean japanese eucjp-ms cp51932 hebrew greek romanian slovak czech european ethiopic indian cyrillic chinese composite emoji-zwj charscript charprop case-table epa-hook jka-cmpr-hook help abbrev obarray oclosure cl-preloaded button loaddefs theme-loaddefs faces cus-face macroexp files window text-properties overlay sha1 md5 base64 format env code-pages mule custom widget keymap hashtable-print-readable backquote threads kqueue cocoa ns multi-tty make-network-process emacs) Memory information: ((conses 16 407012 134522) (symbols 48 26631 1) (strings 32 138327 48200) (string-bytes 1 3541370) (vectors 16 50914) (vector-slots 8 1424473 208168) (floats 8 298 443) (intervals 56 1081 0) (buffers 984 16)) --=20 NOTICE: This email and its attachments may contain privileged and=20 confidential information, only for the viewing and use of the intended=20 recipient. If you are not the intended recipient, you are hereby notified= =20 that any disclosure, copying, distribution, acting upon, or use of the=20 information contained in this email and its attachments is strictly=20 prohibited and that this email and its attachments must be immediately=20 returned to the sender and deleted from your system. If you received this= =20 email erroneously, please notify the sender immediately.=C2=A0 Xage Securit= y,=20 Inc. and its affiliates will never request personal information (e.g.,=20 passwords, Social Security numbers) via email.=C2=A0 Report suspicious emai= ls to=20 security-alerts@xage.com --000000000000152f79061887a9ce Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
While editing the ~/.emacs file in emacs, the machine rebo= oted (kernel panic I believe). This left a lock file behind.

=
The ~/.emacs file is actually a softlink:
.emacs -> /User= s/<username>/Dropbox/Documents/Projects/emacs/dotemacs
The = fact that it's a softlink may or may not be relevant.

In ~/Dropbox/Documents/Projects/emacs/, there was a file:=C2=A0.#do= temacs

After the reboot, I started emacs, and cont= inued with further edits to .emacs. Upon saving .emacs, had the following w= arning:
=E2=9B=94 Warning (unlock-file): Unlocking file: Invalid = argument,=C2=A0~/Dropbox/Documents/Projects/emacs/dotemacs, ignored

As per the warning, the save was nonetheless successful.<= /div>

Invoking=C2=A0file-locked-p directly, I saw the sa= me error, and the following debug info:
Debugger entered--Lisp error: (f= ile-error "Testing file lock" "Invalid argument" "= ~/Dropbox/Documents/Projects/emacs/dotemacs")
=C2=A0 file-locked-p(= "~/Dropbox/Documents/Projects/emacs/dotemacs")
=C2=A0 eval((fi= le-locked-p "~/Dropbox/Documents/Projects/emacs/dotemacs") t)
= =C2=A0 eval-expression((file-locked-p "~/Dropbox/Documents/Projects/em= acs/dotemacs") nil nil 127)
=C2=A0 funcall-interactively(eval-expre= ssion (file-locked-p "~/Dropbox/Documents/Projects/emacs/dotemacs"= ;) nil nil 127)
=C2=A0 call-interactively(eval-expression nil nil)
= =C2=A0 command-execute(eval-expression)

After removing the lock file= manually, the warning on save goes away:
rm ~/Dropbox/Documents/= Projects/emacs/.#dotemacs

Access flags on dote= macs file are as follows:
-rw-r--r--@ =C2=A01 dgreatwood =C2=A0staff =C2= =A0133806 May 15 16:01 dotemacs
lrwxr-xr-x =C2=A01 dgreatwood =C2= =A0staff =C2=A059 Dec =C2=A06 =C2=A02015 .emacs -> ...

Thanks.
----
In GNU Emacs 29.1 (build 1, aarch6= 4-apple-darwin21.6.0, NS
=C2=A0appkit-2113.60 Version 12.6.6 (Build 21G6= 46)) of 2023-08-16 built on
=C2=A0armbob.lan
Windowing system distrib= utor 'Apple', version 10.3.2487
System Description: =C2=A0macOS = 14.5

Configured using:
=C2=A0'configure --with-ns '--enab= le-locallisppath=3D/Library/Application
=C2=A0Support/Emacs/${version}/s= ite-lisp:/Library/Application
=C2=A0Support/Emacs/site-lisp' --with-= modules 'CFLAGS=3D-DFD_SETSIZE=3D10000
=C2=A0-DDARWIN_UNLIMITED_SELE= CT' --with-x-toolkit=3Dno'

Configured features:
ACL GLIB = GMP GNUTLS JPEG JSON LIBXML2 MODULES NOTIFY KQUEUE NS PDUMPER
PNG RSVG S= QLITE3 THREADS TIFF TOOLKIT_SCROLL_BARS TREE_SITTER ZLIB

Important s= ettings:
=C2=A0 value of $LANG: en_US.UTF-8
=C2=A0 locale-coding-syst= em: utf-8-unix

Major mode: Messages

Minor modes in effect:=C2=A0 server-mode: t
=C2=A0 override-global-mode: t
=C2=A0 delete-s= election-mode: t
=C2=A0 tooltip-mode: t
=C2=A0 global-eldoc-mode: t=C2=A0 show-paren-mode: t
=C2=A0 electric-indent-mode: t
=C2=A0 mou= se-wheel-mode: t
=C2=A0 menu-bar-mode: t
=C2=A0 file-name-shadow-mode= : t
=C2=A0 global-font-lock-mode: t
=C2=A0 font-lock-mode: t
=C2= =A0 blink-cursor-mode: t
=C2=A0 buffer-read-only: t
=C2=A0 column-num= ber-mode: t
=C2=A0 line-number-mode: t
=C2=A0 transient-mark-mode: t<= br>=C2=A0 auto-composition-mode: t
=C2=A0 auto-encryption-mode: t
=C2= =A0 auto-compression-mode: t

Load-path shadows:
/Users/username/.= emacs.d/lisp/dash hides /Users/username/.emacs.d/elpa/dash-20221013.836/das= h
/Users/username/.emacs.d/elpa/use-package-20221029.1857/use-package-ju= mp hides /Applications/Emacs.app/Contents/Resources/lisp/use-package/use-pa= ckage-jump
/Users/username/.emacs.d/elpa/use-package-20221029.1857/use-p= ackage-ensure hides /Applications/Emacs.app/Contents/Resources/lisp/use-pac= kage/use-package-ensure
/Users/username/.emacs.d/elpa/use-package-202210= 29.1857/use-package-core hides /Applications/Emacs.app/Contents/Resources/l= isp/use-package/use-package-core
/Users/username/.emacs.d/elpa/use-packa= ge-20221029.1857/use-package-delight hides /Applications/Emacs.app/Contents= /Resources/lisp/use-package/use-package-delight
/Users/username/.emacs.d= /elpa/use-package-20221029.1857/use-package-diminish hides /Applications/Em= acs.app/Contents/Resources/lisp/use-package/use-package-diminish
/Users/= username/.emacs.d/elpa/use-package-20221029.1857/use-package hides /Applica= tions/Emacs.app/Contents/Resources/lisp/use-package/use-package
/Users/u= sername/.emacs.d/elpa/use-package-20221029.1857/use-package-bind-key hides = /Applications/Emacs.app/Contents/Resources/lisp/use-package/use-package-bin= d-key
/Users/username/.emacs.d/elpa/bind-key-20221028.1858/bind-key hide= s /Applications/Emacs.app/Contents/Resources/lisp/use-package/bind-key
/= Users/username/.emacs.d/elpa/use-package-20221029.1857/use-package-lint hid= es /Applications/Emacs.app/Contents/Resources/lisp/use-package/use-package-= lint
/Users/username/.emacs.d/lisp/linum hides /Applications/Emacs.app/C= ontents/Resources/lisp/obsolete/linum

Features:
(shadow mail-extr= emacsbug misearch multi-isearch help-fns radix-tree
cl-print debug back= trace warnings company-oddmuse company-keywords
company-etags company-gt= ags company-dabbrev-code company-dabbrev
company-files company-clang com= pany-capf company-cmake company-semantic
company-template company-bbdb c= ompany mm-archive message sendmail
yank-media dired dired-loaddefs rfc82= 2 mml mml-sec epa derived epg
rfc6068 gnus-util mailabbrev gmm-utils mai= lheader mm-decode mm-bodies
mm-encode mail-utils sort autorevert filenot= ify tango-theme server
cmake-mode rst persistent-todo todotxt rustic-spe= llcheck rustic-expand
rustic-lsp rustic-playpen rustic-rustfix rustic-ra= cer etags fileloop
xref rustic-babel rustic-rustfmt project org-element = org-persist org-id
org-refile avl-tree generator org ob ob-tangle ob-ref= ob-lob ob-table
ob-exp org-macro org-src ob-comint org-pcomplete pcompl= ete org-list
org-footnote org-faces org-entities time-date ob-emacs-lisp= ob-core
ob-eval org-cycle org-table ol org-fold org-fold-core org-keys = oc
org-loaddefs find-func cal-menu calendar cal-loaddefs org-version
= org-compat org-macs format-spec rustic-comint rustic-clippy rustic-doc
x= dg f f-shortdoc shortdoc rustic-popup rustic-cargo rustic-compile
spinne= r s xterm-color markdown-mode color noutline outline icons
rustic-intera= ction rustic dash pcase use-package use-package-ensure
use-package-delig= ht use-package-diminish use-package-bind-key bind-key
easy-mmode use-pac= kage-core rust-utils thingatpt rust-mode rx
rust-rustfmt rust-playpen ru= st-compile compile text-property-search
comint ansi-osc ansi-color ring = rust-cargo gnutls network-stream
url-cache url-http url-auth mail-parse = rfc2231 rfc2047 rfc2045 mm-util
ietf-drums mail-prsvr url-gw nsm puny ep= g-config finder-inf
special-scratch kmacro advice string-inflection cl-e= xtra help-mode
desktop frameset unbound cl delsel auto-complete-autoload= s
cmake-font-lock-autoloads cmake-mode-autoloads company-autoloads
fu= zzy-autoloads popup-complete-autoloads popup-autoloads info package
brow= se-url url url-proxy url-privacy url-expand url-methods url-history
url-= cookie generate-lisp-file url-domsuf url-util mailcap url-handlers
url-p= arse auth-source cl-seq eieio eieio-core cl-macs password-cache
json sub= r-x map byte-opt gv bytecomp byte-compile url-vars cl-loaddefs
cl-lib rm= c iso-transl tooltip cconv eldoc paren electric uniquify
ediff-hook vc-h= ooks lisp-float-type elisp-mode mwheel term/ns-win ns-win
ucs-normalize = mule-util term/common-win tool-bar dnd fontset image
regexp-opt fringe t= abulated-list replace newcomment text-mode lisp-mode
prog-mode register = page tab-bar menu-bar rfn-eshadow isearch easymenu
timer select scroll-b= ar mouse jit-lock font-lock syntax font-core
term/tty-colors frame minib= uffer nadvice seq simple cl-generic
indonesian philippine cham georgian = utf-8-lang misc-lang vietnamese
tibetan thai tai-viet lao korean japanes= e eucjp-ms cp51932 hebrew greek
romanian slovak czech european ethiopic = indian cyrillic chinese
composite emoji-zwj charscript charprop case-tab= le epa-hook
jka-cmpr-hook help abbrev obarray oclosure cl-preloaded butt= on loaddefs
theme-loaddefs faces cus-face macroexp files window text-pro= perties
overlay sha1 md5 base64 format env code-pages mule custom widget= keymap
hashtable-print-readable backquote threads kqueue cocoa ns multi= -tty
make-network-process emacs)

Memory information:
((conses = 16 407012 134522)
=C2=A0(symbols 48 26631 1)
=C2=A0(strings 32 138327= 48200)
=C2=A0(string-bytes 1 3541370)
=C2=A0(vectors 16 50914)
= =C2=A0(vector-slots 8 1424473 208168)
=C2=A0(floats 8 298 443)
=C2=A0= (intervals 56 1081 0)
=C2=A0(buffers 984 16))



NOTICE: This email and its attachmen= ts may contain privileged and confidential information, only for the viewin= g and use of the intended recipient. If you are not the intended recipient,= you are hereby notified that any disclosure, copying, distribution, acting= upon, or use of the information contained in this email and its attachment= s is strictly prohibited and that this email and its attachments must be im= mediately returned to the sender and deleted from your system. If you recei= ved this email erroneously, please notify the sender immediately.=C2=A0 Xag= e Security, Inc. and its affiliates will never request personal information= (e.g., passwords, Social Security numbers) via email.=C2=A0 Report suspici= ous emails to security= -alerts@xage.com
--000000000000152f79061887a9ce-- From debbugs-submit-bounces@debbugs.gnu.org Thu May 16 04:44:00 2024 Received: (at 70973) by debbugs.gnu.org; 16 May 2024 08:44:00 +0000 Received: from localhost ([127.0.0.1]:47503 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1s7WiW-0008Ko-C9 for submit@debbugs.gnu.org; Thu, 16 May 2024 04:44:00 -0400 Received: from eggs.gnu.org ([209.51.188.92]:54646) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1s7WiV-0008Ki-6k for 70973@debbugs.gnu.org; Thu, 16 May 2024 04:43:59 -0400 Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1s7WiL-0004XG-Hd; Thu, 16 May 2024 04:43:50 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-version:References:Subject:In-Reply-To:To:From: Date; bh=sh9lnUxy3TU9HmNhyu2Ysqt6Y6sSV3vgFDB6xBHPuOc=; b=Yje3MbKs0Lzh89m/Anfi Vrw3wWW1vVZcQujGZQhaTAKCvjqjWVinA1Df0XjAX2k/Hyw3GoTke474FtcpvCao/RwMmjzVGWIRR xjyfDkWfe38BMO6ZmZplIDwlf6/c98e6t97CJeJuhe2v9Ow0uXQD6gpzcq4KW18Zzhb7fMcR3eMWi H8XuSjo77ufUsJGzxj4owz7ifbjSa+HRRsW9CmsoDZvdMPfJ0za/hDPrKvpHf9IWR7OtYLFkjN3Oq BXxde/OxWcBHBWTWHtyM2cKZi9iYBPakstTxFhLMs9CV4yIeI8fOhSwV0WKhpaC7iivpRRJDPPCFX R3rxyT1cRm/RxQ==; Date: Thu, 16 May 2024 11:43:45 +0300 Message-Id: <867cfujge6.fsf@gnu.org> From: Eli Zaretskii To: Duncan Greatwood In-Reply-To: (message from Duncan Greatwood on Wed, 15 May 2024 17:53:05 -0700) Subject: Re: bug#70973: 29.1; "Unlocking file: Invalid argument" Warning saving via a softlink with stale file lock References: MIME-version: 1.0 Content-type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Spam-Score: -2.3 (--) X-Debbugs-Envelope-To: 70973 Cc: 70973@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -3.3 (---) > From: Duncan Greatwood > Date: Wed, 15 May 2024 17:53:05 -0700 > > While editing the ~/.emacs file in emacs, the machine rebooted (kernel panic I believe). This left a lock file > behind. > > The ~/.emacs file is actually a softlink: > .emacs -> /Users//Dropbox/Documents/Projects/emacs/dotemacs > The fact that it's a softlink may or may not be relevant. > > In ~/Dropbox/Documents/Projects/emacs/, there was a file: .#dotemacs > > After the reboot, I started emacs, and continued with further edits to .emacs. Upon saving .emacs, had the > following warning: > ⛔ Warning (unlock-file): Unlocking file: Invalid argument, ~/Dropbox/Documents/Projects/emacs/dotemacs, > ignored > > As per the warning, the save was nonetheless successful. > > Invoking file-locked-p directly, I saw the same error, and the following debug info: > Debugger entered--Lisp error: (file-error "Testing file lock" "Invalid argument" > "~/Dropbox/Documents/Projects/emacs/dotemacs") > file-locked-p("~/Dropbox/Documents/Projects/emacs/dotemacs") > eval((file-locked-p "~/Dropbox/Documents/Projects/emacs/dotemacs") t) > eval-expression((file-locked-p "~/Dropbox/Documents/Projects/emacs/dotemacs") nil nil 127) > funcall-interactively(eval-expression (file-locked-p "~/Dropbox/Documents/Projects/emacs/dotemacs") nil nil > 127) > call-interactively(eval-expression nil nil) > command-execute(eval-expression) > > After removing the lock file manually, the warning on save goes away: > rm ~/Dropbox/Documents/Projects/emacs/.#dotemacs > > Access flags on dotemacs file are as follows: > -rw-r--r--@ 1 dgreatwood staff 133806 May 15 16:01 dotemacs > lrwxr-xr-x 1 dgreatwood staff 59 Dec 6 2015 .emacs -> ... Thanks. However, this doesn't provide enough information to investigate the issue and its causes. If you can reproduce the problem, please tell what does ls -l ~/Dropbox/Documents/Projects/emacs/.#dotemacs produce when you see the warnings, because that is the immediate trigger for the "invalid argument". From debbugs-submit-bounces@debbugs.gnu.org Thu May 16 10:19:28 2024 Received: (at 70973) by debbugs.gnu.org; 16 May 2024 14:19:28 +0000 Received: from localhost ([127.0.0.1]:48996 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1s7bx9-0007By-Kd for submit@debbugs.gnu.org; Thu, 16 May 2024 10:19:28 -0400 Received: from mail-lf1-f47.google.com ([209.85.167.47]:52587) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1s7bx4-0007Bo-LE for 70973@debbugs.gnu.org; Thu, 16 May 2024 10:19:26 -0400 Received: by mail-lf1-f47.google.com with SMTP id 2adb3069b0e04-523b017a5c6so1348542e87.1 for <70973@debbugs.gnu.org>; Thu, 16 May 2024 07:19:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1715869093; x=1716473893; darn=debbugs.gnu.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=/fXn4vnw1BoPMua50i1kt0mZiyoBxkLGqUcki/w+TE8=; b=mP5cB/aqeGe+AvlvR7xjNF5G1PsuUuE4qcViZEnTWpCgtNV+FjIncwVO80K3H1y1Ft RryIHS4ASeuxZw8wFhJK4vNK8RhUuWI9yag3HA7s6cy4+U8qB/mK8Qltiox4KU7epJ3N 3CU40ojMWaauDBgK8hC0dhU7q+zUGEKQ9dgIkdWwP2VIjQDtP2NAqlRp8RoxKs+oWgEG pk8/wnTep1lu5zl2BPHBt939ACdit47Dk0REVcSOSxwD7nVeaU9cNmnTIGGaGjoyhemc XmjApCBsUxJemtdyFI3OpKmf/NY5RUJRCQVBUwdg9G6aD+aQZZNMMFvWYyNeskeL76eQ gK1w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1715869093; x=1716473893; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=/fXn4vnw1BoPMua50i1kt0mZiyoBxkLGqUcki/w+TE8=; b=XX9oGFl07W00lTw8PZq7MRnJQsi9a7AvS4QletnkTcvcmurwEd55oVUfAAgQLpVue0 P3oe99E+MCAe8qcVXk+b6aYBsTYafSB88k9ijRXbDPVv21IImRIjiJx6RCid983ut4S7 MRVf5IfreF6woYvN8IlZJDF8D6hpQ9wP1hT4HrmXRzIFj9Puul5XbCvcmLbPHSvPIkRb xg3bnIb0NN7wumlasRi080Ef/Q1cZoIee7Nw/88OM3dWoOh1yg15oHhsw3ji8O+k+SfV t2yYDtAw2v4FjLpc1BMD7EPFcN8M2WsPtPkQjr8mjM2pcy021yJ0Md5+V7s+CTNG5xl0 3Qkw== X-Gm-Message-State: AOJu0YwmvSxlkmtwE4HfqMy00SzSAqDFaXfKNKQ1THMwsJSF2derpD0r nhtkMo+7XWDH7dMmxkgik5y7H72W49AfJyB8hPtpaR+Rx7asGxaWMLK2hoaO X-Google-Smtp-Source: AGHT+IETuBBluCUEKZmJ88gZmY/1bfHT8DN+ea28sJ6UJmk55+cVZWk6FVjl0I873VXFzXz0Vu41/w== X-Received: by 2002:a19:5f47:0:b0:523:9515:4b74 with SMTP id 2adb3069b0e04-52395154c9bmr4120497e87.14.1715869093233; Thu, 16 May 2024 07:18:13 -0700 (PDT) Received: from mail-lj1-f182.google.com (mail-lj1-f182.google.com. [209.85.208.182]) by smtp.gmail.com with ESMTPSA id 2adb3069b0e04-521f35ad41dsm2968366e87.22.2024.05.16.07.18.12 for <70973@debbugs.gnu.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 16 May 2024 07:18:12 -0700 (PDT) Received: by mail-lj1-f182.google.com with SMTP id 38308e7fff4ca-2e1fa1f1d9bso14739441fa.0 for <70973@debbugs.gnu.org>; Thu, 16 May 2024 07:18:12 -0700 (PDT) X-Received: by 2002:a2e:8847:0:b0:2dd:2bd8:a4c1 with SMTP id 38308e7fff4ca-2e51fc3406cmr170905831fa.10.1715869091668; Thu, 16 May 2024 07:18:11 -0700 (PDT) MIME-Version: 1.0 References: <867cfujge6.fsf@gnu.org> In-Reply-To: <867cfujge6.fsf@gnu.org> From: Duncan Greatwood Date: Thu, 16 May 2024 07:17:59 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: bug#70973: 29.1; "Unlocking file: Invalid argument" Warning saving via a softlink with stale file lock To: Eli Zaretskii Content-Type: multipart/alternative; boundary="000000000000b0daad061892e703" X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 70973 Cc: 70973@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) --000000000000b0daad061892e703 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable > If you can reproduce the problem, please tell what does > > ls -l ~/Dropbox/Documents/Projects/emacs/.#dotemacs > > produce when you see the warnings As follows: $ ls -l ~/Dropbox/Documents/Projects/emacs/.#dotemacs -rw-r--r--@ 1 username staff 0 May 16 07:13 /Users/username/Dropbox/Documents/Projects/emacs/.#dotemacs On Thu, May 16, 2024 at 1:43=E2=80=AFAM Eli Zaretskii wrote: > > From: Duncan Greatwood > > Date: Wed, 15 May 2024 17:53:05 -0700 > > > > While editing the ~/.emacs file in emacs, the machine rebooted (kernel > panic I believe). This left a lock file > > behind. > > > > The ~/.emacs file is actually a softlink: > > .emacs -> /Users//Dropbox/Documents/Projects/emacs/dotemacs > > The fact that it's a softlink may or may not be relevant. > > > > In ~/Dropbox/Documents/Projects/emacs/, there was a file: .#dotemacs > > > > After the reboot, I started emacs, and continued with further edits to > .emacs. Upon saving .emacs, had the > > following warning: > > =E2=9B=94 Warning (unlock-file): Unlocking file: Invalid argument, > ~/Dropbox/Documents/Projects/emacs/dotemacs, > > ignored > > > > As per the warning, the save was nonetheless successful. > > > > Invoking file-locked-p directly, I saw the same error, and the followin= g > debug info: > > Debugger entered--Lisp error: (file-error "Testing file lock" "Invalid > argument" > > "~/Dropbox/Documents/Projects/emacs/dotemacs") > > file-locked-p("~/Dropbox/Documents/Projects/emacs/dotemacs") > > eval((file-locked-p "~/Dropbox/Documents/Projects/emacs/dotemacs") t) > > eval-expression((file-locked-p > "~/Dropbox/Documents/Projects/emacs/dotemacs") nil nil 127) > > funcall-interactively(eval-expression (file-locked-p > "~/Dropbox/Documents/Projects/emacs/dotemacs") nil nil > > 127) > > call-interactively(eval-expression nil nil) > > command-execute(eval-expression) > > > > After removing the lock file manually, the warning on save goes away: > > rm ~/Dropbox/Documents/Projects/emacs/.#dotemacs > > > > Access flags on dotemacs file are as follows: > > -rw-r--r--@ 1 dgreatwood staff 133806 May 15 16:01 dotemacs > > lrwxr-xr-x 1 dgreatwood staff 59 Dec 6 2015 .emacs -> ... > > Thanks. > > However, this doesn't provide enough information to investigate the > issue and its causes. If you can reproduce the problem, please tell > what does > > ls -l ~/Dropbox/Documents/Projects/emacs/.#dotemacs > > produce when you see the warnings, because that is the immediate > trigger for the "invalid argument". > --=20 NOTICE: This email and its attachments may contain privileged and=20 confidential information, only for the viewing and use of the intended=20 recipient. If you are not the intended recipient, you are hereby notified= =20 that any disclosure, copying, distribution, acting upon, or use of the=20 information contained in this email and its attachments is strictly=20 prohibited and that this email and its attachments must be immediately=20 returned to the sender and deleted from your system. If you received this= =20 email erroneously, please notify the sender immediately.=C2=A0 Xage Securit= y,=20 Inc. and its affiliates will never request personal information (e.g.,=20 passwords, Social Security numbers) via email.=C2=A0 Report suspicious emai= ls to=20 security-alerts@xage.com --000000000000b0daad061892e703 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
> If you can reproduce the problem, please tell wh= at does
>
> =C2=A0 ls -l ~/Dropbox/Documents/Projects/emacs/.#= dotemacs
>
> produce when you see the warnings
<= br>
As follows:
$ ls -l ~/Dropbox/Documents/Projects/em= acs/.#dotemacs
-rw-r--r--@ 1 username =C2=A0staff =C2=A00 May 16 07:13 /= Users/username/Dropbox/Documents/Projects/emacs/.#dotemacs

On Thu, May 16, 2024 at 1:43=E2=80=AFAM Eli Zaretskii <eliz@gnu.org> wrote:
> From: Duncan Greatwood <dgreatwood@gmail.com>
> Date: Wed, 15 May 2024 17:53:05 -0700
>
> While editing the ~/.emacs file in emacs, the machine rebooted (kernel= panic I believe). This left a lock file
> behind.
>
> The ~/.emacs file is actually a softlink:
> .emacs -> /Users/<username>/Dropbox/Documents/Projects/emacs/= dotemacs
> The fact that it's a softlink may or may not be relevant.
>
> In ~/Dropbox/Documents/Projects/emacs/, there was a file: .#dotemacs >
> After the reboot, I started emacs, and continued with further edits to= .emacs. Upon saving .emacs, had the
> following warning:
> =E2=9B=94 Warning (unlock-file): Unlocking file: Invalid argument, ~/D= ropbox/Documents/Projects/emacs/dotemacs,
> ignored
>
> As per the warning, the save was nonetheless successful.
>
> Invoking file-locked-p directly, I saw the same error, and the followi= ng debug info:
> Debugger entered--Lisp error: (file-error "Testing file lock"= ; "Invalid argument"
> "~/Dropbox/Documents/Projects/emacs/dotemacs")
>=C2=A0 =C2=A0file-locked-p("~/Dropbox/Documents/Projects/emacs/dot= emacs")
>=C2=A0 =C2=A0eval((file-locked-p "~/Dropbox/Documents/Projects/ema= cs/dotemacs") t)
>=C2=A0 =C2=A0eval-expression((file-locked-p "~/Dropbox/Documents/P= rojects/emacs/dotemacs") nil nil 127)
>=C2=A0 =C2=A0funcall-interactively(eval-expression (file-locked-p "= ;~/Dropbox/Documents/Projects/emacs/dotemacs") nil nil
> 127)
>=C2=A0 =C2=A0call-interactively(eval-expression nil nil)
>=C2=A0 =C2=A0command-execute(eval-expression)
>
> After removing the lock file manually, the warning on save goes away:<= br> > rm ~/Dropbox/Documents/Projects/emacs/.#dotemacs
>
> Access flags on dotemacs file are as follows:
> -rw-r--r--@=C2=A0 1 dgreatwood=C2=A0 staff=C2=A0 133806 May 15 16:01 d= otemacs
> lrwxr-xr-x=C2=A0 1 dgreatwood=C2=A0 staff=C2=A0 59 Dec=C2=A0 6=C2=A0 2= 015 .emacs -> ...

Thanks.

However, this doesn't provide enough information to investigate the
issue and its causes.=C2=A0 If you can reproduce the problem, please tell what does

=C2=A0 ls -l ~/Dropbox/Documents/Projects/emacs/.#dotemacs

produce when you see the warnings, because that is the immediate
trigger for the "invalid argument".

NOTICE: This email and its attachmen= ts may contain privileged and confidential information, only for the viewin= g and use of the intended recipient. If you are not the intended recipient,= you are hereby notified that any disclosure, copying, distribution, acting= upon, or use of the information contained in this email and its attachment= s is strictly prohibited and that this email and its attachments must be im= mediately returned to the sender and deleted from your system. If you recei= ved this email erroneously, please notify the sender immediately.=C2=A0 Xag= e Security, Inc. and its affiliates will never request personal information= (e.g., passwords, Social Security numbers) via email.=C2=A0 Report suspici= ous emails to security= -alerts@xage.com
--000000000000b0daad061892e703-- From debbugs-submit-bounces@debbugs.gnu.org Thu May 16 11:47:19 2024 Received: (at 70973) by debbugs.gnu.org; 16 May 2024 15:47:20 +0000 Received: from localhost ([127.0.0.1]:49423 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1s7dKB-0008Lp-J9 for submit@debbugs.gnu.org; Thu, 16 May 2024 11:47:19 -0400 Received: from eggs.gnu.org ([209.51.188.92]:50932) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1s7dK6-0008Lf-DV for 70973@debbugs.gnu.org; Thu, 16 May 2024 11:47:17 -0400 Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1s7dJv-0002fy-67; Thu, 16 May 2024 11:47:06 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=u+NYc/I+Cd2htZxzKnm+X4uvGDg8wU2TSjM7Jk/YFOs=; b=jLoF3ZVlO1Mu GFJK957HGtnWjlUNiLIrgY0Jn55WavdCi/60TZPXK+TlgqQJlo0RSJIzjtKklzXXHRmNCcUs/A0Ki 2nRpo2kl6bK9wyCmMEHiWC6A1XBX/YNwfeW6CBHqJtfhQZBXxCfmfQ2KVL4E/75OQtrIsa1YBEv6i +Zkfm7JNvhwGLSwLHccXZXwNoKdq/sj70xddLPR+8O01fePayyG9DuOp4HXnBJN7UH99T3iow9Xn6 ibk/UDmPUHzenfklmFIcrz6QhyeVBZicrDw4GzidPu0ZfmTI+EBK5ehe82+ppBW5ET5ki0dEnm626 jqlIaYWG98Q+DSsIGNV59Q==; Date: Thu, 16 May 2024 18:46:51 +0300 Message-Id: <86fruhiwt0.fsf@gnu.org> From: Eli Zaretskii To: Duncan Greatwood In-Reply-To: (message from Duncan Greatwood on Thu, 16 May 2024 07:17:59 -0700) Subject: Re: bug#70973: 29.1; "Unlocking file: Invalid argument" Warning saving via a softlink with stale file lock References: <867cfujge6.fsf@gnu.org> X-Spam-Score: -2.3 (--) X-Debbugs-Envelope-To: 70973 Cc: 70973@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -3.3 (---) > From: Duncan Greatwood > Date: Thu, 16 May 2024 07:17:59 -0700 > Cc: 70973@debbugs.gnu.org > > > If you can reproduce the problem, please tell what does > > > > ls -l ~/Dropbox/Documents/Projects/emacs/.#dotemacs > > > > produce when you see the warnings > > As follows: > $ ls -l ~/Dropbox/Documents/Projects/emacs/.#dotemacs > -rw-r--r--@ 1 username staff 0 May 16 07:13 > /Users/username/Dropbox/Documents/Projects/emacs/.#dotemacs Sorry, that doesn't help. I thought "ls -l" will show the target of the symlink, but maybe it doesn't on macOS? In that case, you should be able to use the Emacs function file-symlink-p: when called with the lock file as its argument, it should return the target of the symlink as a string. From debbugs-submit-bounces@debbugs.gnu.org Thu May 16 11:56:41 2024 Received: (at 70973) by debbugs.gnu.org; 16 May 2024 15:56:41 +0000 Received: from localhost ([127.0.0.1]:49472 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1s7dTF-0008Tn-Ao for submit@debbugs.gnu.org; Thu, 16 May 2024 11:56:41 -0400 Received: from mail-ed1-f52.google.com ([209.85.208.52]:59774) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1s7dTC-0008Tf-UB for 70973@debbugs.gnu.org; Thu, 16 May 2024 11:56:40 -0400 Received: by mail-ed1-f52.google.com with SMTP id 4fb4d7f45d1cf-572a93890d1so3908357a12.3 for <70973@debbugs.gnu.org>; Thu, 16 May 2024 08:56:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1715874930; x=1716479730; darn=debbugs.gnu.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=OiyCbIufc3u/1Ax4vPoaw8/AtWs5/Y9u9q3LEMnKqls=; b=cy2SWYOX+tdF3Yndqj2woLcTS2Ii83htBQ6Yf3zgiHz74lqtpD8OvPaKQ3/RL7rx9A CkIdaqgeG1ifqlRkmcK/6u3ZVemZF60gnYoOCeKUo6Y80Bb5Zg99gBDhQeAxW47CAyef LblsL9Mrp+iD6ODLGD5LQq66ORBQW0YGXOAN6UUw8KJ7p6ZHcjKLx9RuqUSWCB9jdsal zpbg/5R/nfwtqWgE6HAep0WfsYK3axcaycoyrIf1AtNC2CY/pPqqrkU2fubHFWk0pGbM 3gwC2DVWNalccdSQpzkSchBZkk2e3PXUWFMpFwkriEZcB7pqvqCLyEFDzT6/tp1g72wP Pa7Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1715874930; x=1716479730; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=OiyCbIufc3u/1Ax4vPoaw8/AtWs5/Y9u9q3LEMnKqls=; b=k2UTWqlq1kH8adWUd/s5T1IkiTAZZlVpARNaH9kTdF1PytwgSFUO518ntk7RotKT71 aPHlCPJ1puIIcZA6QPzE7aiSm9o8ithfnOCllnhsrFMkjRhYxl1T0ASnHBE4ZWfzwqbK SsAd2yEWh8yLHwedOsteH3+9OTMT82Mk1PYRBRjOflOmEu8vYTAq9cDtoooNPu7UEEEk kwaqP1FdgZptD66dj6ruTU8zJNxUXWNbhPZO/Qiwb35XOEJyjOQ2O3vIe2A+ISaFpla2 7euwkX0xjXkyzjG6qeDGbnarU9zh9feokMvRMjKAytexvvoBySps1Vlnt7bI5/VTPKIG oflA== X-Gm-Message-State: AOJu0YykHpv83nfjH1NFDsGnV5QxN/DQB/6foCNIg5OMyeGkHwR7R5GE GWe4jKEVNFsoAHi2u/bT9YnRySIRfo4R48mv7L27xVM74W5sBEh9O75XgHPmBNs= X-Google-Smtp-Source: AGHT+IHQjIa8c1pTZQVoZcsj30wracvSLJZFYhJW4fbrOWQd6UQUlBfVMrEH5xJLWoCj+pOBInJreA== X-Received: by 2002:a50:c317:0:b0:575:c1a:4948 with SMTP id 4fb4d7f45d1cf-5750c1a5334mr1782186a12.4.1715874929966; Thu, 16 May 2024 08:55:29 -0700 (PDT) Received: from mail-ed1-f44.google.com (mail-ed1-f44.google.com. [209.85.208.44]) by smtp.gmail.com with ESMTPSA id 4fb4d7f45d1cf-574ec273185sm3259297a12.42.2024.05.16.08.55.29 for <70973@debbugs.gnu.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 16 May 2024 08:55:29 -0700 (PDT) Received: by mail-ed1-f44.google.com with SMTP id 4fb4d7f45d1cf-56e1bbdb362so2944133a12.1 for <70973@debbugs.gnu.org>; Thu, 16 May 2024 08:55:29 -0700 (PDT) X-Received: by 2002:a50:ab0c:0:b0:572:459f:c7ab with SMTP id 4fb4d7f45d1cf-5734d6f004bmr18870978a12.28.1715874929002; Thu, 16 May 2024 08:55:29 -0700 (PDT) MIME-Version: 1.0 References: <867cfujge6.fsf@gnu.org> <86fruhiwt0.fsf@gnu.org> In-Reply-To: <86fruhiwt0.fsf@gnu.org> From: Duncan Greatwood Date: Thu, 16 May 2024 08:55:17 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: bug#70973: 29.1; "Unlocking file: Invalid argument" Warning saving via a softlink with stale file lock To: Eli Zaretskii Content-Type: multipart/alternative; boundary="0000000000009f6dc50618944313" X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 70973 Cc: 70973@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) --0000000000009f6dc50618944313 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable > I thought "ls -l" will show the target of > the symlink, but maybe it doesn't on macOS? It does indeed do that, even on macOS However, it is the .emacs that is a symlink. $ ls -l ~/.emacs lrwxr-xr-x 1 username staff 59 Dec 6 2015 .emacs -> /Users/username/Dropbox/Documents/Projects/emacs/dotemacs The lock file is not a link. On Thu, May 16, 2024 at 8:47=E2=80=AFAM Eli Zaretskii wrote: > > From: Duncan Greatwood > > Date: Thu, 16 May 2024 07:17:59 -0700 > > Cc: 70973@debbugs.gnu.org > > > > > If you can reproduce the problem, please tell what does > > > > > > ls -l ~/Dropbox/Documents/Projects/emacs/.#dotemacs > > > > > > produce when you see the warnings > > > > As follows: > > $ ls -l ~/Dropbox/Documents/Projects/emacs/.#dotemacs > > -rw-r--r--@ 1 username staff 0 May 16 07:13 > > /Users/username/Dropbox/Documents/Projects/emacs/.#dotemacs > > Sorry, that doesn't help. I thought "ls -l" will show the target of > the symlink, but maybe it doesn't on macOS? In that case, you should > be able to use the Emacs function file-symlink-p: when called with the > lock file as its argument, it should return the target of the symlink > as a string. > --=20 NOTICE: This email and its attachments may contain privileged and=20 confidential information, only for the viewing and use of the intended=20 recipient. If you are not the intended recipient, you are hereby notified= =20 that any disclosure, copying, distribution, acting upon, or use of the=20 information contained in this email and its attachments is strictly=20 prohibited and that this email and its attachments must be immediately=20 returned to the sender and deleted from your system. If you received this= =20 email erroneously, please notify the sender immediately.=C2=A0 Xage Securit= y,=20 Inc. and its affiliates will never request personal information (e.g.,=20 passwords, Social Security numbers) via email.=C2=A0 Report suspicious emai= ls to=20 security-alerts@xage.com --0000000000009f6dc50618944313 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
> I thought "ls -l" will show the target of> the symlink, but maybe it doesn't on macOS?
It does inde= ed do that, even on macOS

However, it is the .emac= s that is a symlink.

$ ls -l ~/.emacs
lrwxr-xr-= x =C2=A01 username =C2=A0staff =C2=A059 Dec =C2=A06 =C2=A02015 .emacs ->= /Users/username/Dropbox/Documents/Projects/emacs/dotemacs
The lock file is not a link.

On Thu, May 16, 2024 at = 8:47=E2=80=AFAM Eli Zaretskii <eliz@gnu.= org> wrote:
> From: Duncan Greatwood <dgreatwood@gmail.com>
> Date: Thu, 16 May 2024 07:17:59 -0700
> Cc: 70973@d= ebbugs.gnu.org
>
> > If you can reproduce the problem, please tell what does
> >
> >=C2=A0 =C2=A0ls -l ~/Dropbox/Documents/Projects/emacs/.#dotemacs > >
> > produce when you see the warnings
>
> As follows:
> $ ls -l ~/Dropbox/Documents/Projects/emacs/.#dotemacs
> -rw-r--r--@ 1 username=C2=A0 staff=C2=A0 0 May 16 07:13
> /Users/username/Dropbox/Documents/Projects/emacs/.#dotemacs

Sorry, that doesn't help.=C2=A0 I thought "ls -l" will show t= he target of
the symlink, but maybe it doesn't on macOS?=C2=A0 In that case, you sho= uld
be able to use the Emacs function file-symlink-p: when called with the
lock file as its argument, it should return the target of the symlink
as a string.

NOTICE: This email and its attachmen= ts may contain privileged and confidential information, only for the viewin= g and use of the intended recipient. If you are not the intended recipient,= you are hereby notified that any disclosure, copying, distribution, acting= upon, or use of the information contained in this email and its attachment= s is strictly prohibited and that this email and its attachments must be im= mediately returned to the sender and deleted from your system. If you recei= ved this email erroneously, please notify the sender immediately.=C2=A0 Xag= e Security, Inc. and its affiliates will never request personal information= (e.g., passwords, Social Security numbers) via email.=C2=A0 Report suspici= ous emails to security= -alerts@xage.com
--0000000000009f6dc50618944313-- From debbugs-submit-bounces@debbugs.gnu.org Thu May 16 12:10:13 2024 Received: (at 70973) by debbugs.gnu.org; 16 May 2024 16:10:13 +0000 Received: from localhost ([127.0.0.1]:49574 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1s7dgD-0000Io-Tv for submit@debbugs.gnu.org; Thu, 16 May 2024 12:10:12 -0400 Received: from eggs.gnu.org ([209.51.188.92]:55524) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1s7dgB-0000IJ-U6 for 70973@debbugs.gnu.org; Thu, 16 May 2024 12:10:04 -0400 Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1s7dg4-0000Cv-7t; Thu, 16 May 2024 12:09:56 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=1u94Bq/KAakinG8WxX0qkdsR82jxrDLsvO8CKsLw1aE=; b=Dc8Kt57BFWgW +xWYTIjUnWBywPgMRyCRcWvdn/iOx6CCNZKfj62o3L17vyVm9ryy4h7t17jrG/RxGHubwynzSjT6/ E8PAvwiE+sZ3cNUxL+5MutAyTkV2RLfM0T0OwjU4myTvk3pns7NUwuxuuZFLctpHkbvCQWThMMeHZ UF3+0sNB5OJhc2jLKADxjpPhMlZ7ahgKQECPgqs1+C7HjUE8zXEDljzsQUeJ3ZLXwNWEyRpdNfBqb lN7m7Zt12MsZuJrhWEMu5mXiLxOtvvauuQIZhQhM4v9wBuEu7ecTqXddvrXIET/nhQHuZ9JWQUD6V C0w2CX4VSoGwnb7KPBn3Zw==; Date: Thu, 16 May 2024 19:09:52 +0300 Message-Id: <868r09ivqn.fsf@gnu.org> From: Eli Zaretskii To: Duncan Greatwood In-Reply-To: (message from Duncan Greatwood on Thu, 16 May 2024 08:55:17 -0700) Subject: Re: bug#70973: 29.1; "Unlocking file: Invalid argument" Warning saving via a softlink with stale file lock References: <867cfujge6.fsf@gnu.org> <86fruhiwt0.fsf@gnu.org> X-Spam-Score: -2.3 (--) X-Debbugs-Envelope-To: 70973 Cc: 70973@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -3.3 (---) > From: Duncan Greatwood > Date: Thu, 16 May 2024 08:55:17 -0700 > Cc: 70973@debbugs.gnu.org > > > I thought "ls -l" will show the target of > > the symlink, but maybe it doesn't on macOS? > It does indeed do that, even on macOS > > However, it is the .emacs that is a symlink. > > $ ls -l ~/.emacs > lrwxr-xr-x 1 username staff 59 Dec 6 2015 .emacs -> > /Users/username/Dropbox/Documents/Projects/emacs/dotemacs > > The lock file is not a link. Is that normal on macOS? Or is that something specific to DropBox? If you edit a file elsewhere on your system, does Emacs create lock files that are symlinks? From debbugs-submit-bounces@debbugs.gnu.org Thu May 16 12:22:10 2024 Received: (at 70973) by debbugs.gnu.org; 16 May 2024 16:22:10 +0000 Received: from localhost ([127.0.0.1]:49672 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1s7dru-0000UK-2W for submit@debbugs.gnu.org; Thu, 16 May 2024 12:22:10 -0400 Received: from mail-ed1-f41.google.com ([209.85.208.41]:59747) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1s7drr-0000U1-DR for 70973@debbugs.gnu.org; Thu, 16 May 2024 12:22:08 -0400 Received: by mail-ed1-f41.google.com with SMTP id 4fb4d7f45d1cf-572a93890d1so3949953a12.3 for <70973@debbugs.gnu.org>; Thu, 16 May 2024 09:22:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1715876459; x=1716481259; darn=debbugs.gnu.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=rvcX8+N8hT7PlH1BfSC+a+4sJjdOeRdf4T4MvJYsrvI=; b=b5StdSh88NXQz22L8gl8tXK+ROWGd1qOps3o2E/FKqAm7U/lxlHeEYAy19X/2X39BG 4d8iVhCNYuRBbase5PSYHJ+ca2k8yDSqeyjQuDxMajKGuzFFkPWGAacWIGKmhc/LsXbe ht7Gzd14FuHnL5XlmKFbwC2iGta5UgHzjs4JDIByiQNlBO/r4+dixCjk45UMTEvIkrn3 HhZRxda7OBngNnnp40j5OZOqzlITYdKKu3cgj3XdWKmk5CC/IT53/8m1+MkuhsvEQN3h nZ+c+zP3CcyOv0b2B2pBqD+cjh4tEhln/uRCXNjCKi9oKHQRjHnDX+7oe2m5giEgIllX goyw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1715876459; x=1716481259; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=rvcX8+N8hT7PlH1BfSC+a+4sJjdOeRdf4T4MvJYsrvI=; b=m1PHml1Nt3V3nIeq94/6X79V8Js9TNSI6VVbJtFkP1p4xliaficiJuX5kbSy3wsmp1 JgDxJIjiRxEL//unF68tY6VzzUsC+YqJa7o1jYw+6LHtYbaNb0n/fujdxntwmCmvlNuI d1nqf6gxwEnZoCpTS5Cs0M3GDJmLKxM98NmCmlV7sonPFwOy1E0d2j/G5+mCzkrdCUZg Y8Y+DgHuQ0bRc0bhPCjiB40sduUQD+mshjKjLveSkYFdzO9PWxczDjEESZQzTKD/5xFK 1Vyrkv+8lTCDMD/hGEWzsnyFgqMTVnlMM/3c4WBCGQ38eHQ3o6vpfOdpCbLBI/zwPpnA jtzQ== X-Gm-Message-State: AOJu0Yxqb2RBO5nhV+6p2ap4nlkStWHbfQBa1embh+WBWThva7RdKUZp IqdLK7Nci2skwxtMNr625Ofc4J5g7DD8iS6IcmFDrivOROSJFQUo1VEubE3DRhA= X-Google-Smtp-Source: AGHT+IFcC5K+T4mkT/Qkrwz/RQLc1rEqNWYohANEWvouaBw5/jBic8NL+9+vCG6tmST2yqmNg65whA== X-Received: by 2002:a17:907:720c:b0:a5a:5b23:c150 with SMTP id a640c23a62f3a-a5a5b23c18amr1573506866b.41.1715876458531; Thu, 16 May 2024 09:20:58 -0700 (PDT) Received: from mail-ed1-f41.google.com (mail-ed1-f41.google.com. [209.85.208.41]) by smtp.gmail.com with ESMTPSA id a640c23a62f3a-a5a17892471sm997027466b.84.2024.05.16.09.20.57 for <70973@debbugs.gnu.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 16 May 2024 09:20:57 -0700 (PDT) Received: by mail-ed1-f41.google.com with SMTP id 4fb4d7f45d1cf-5708d8beec6so3651606a12.0 for <70973@debbugs.gnu.org>; Thu, 16 May 2024 09:20:57 -0700 (PDT) X-Received: by 2002:a17:906:3c7:b0:a5c:e031:faf2 with SMTP id a640c23a62f3a-a5ce03210e7mr279366066b.77.1715876457462; Thu, 16 May 2024 09:20:57 -0700 (PDT) MIME-Version: 1.0 References: <867cfujge6.fsf@gnu.org> <86fruhiwt0.fsf@gnu.org> <868r09ivqn.fsf@gnu.org> In-Reply-To: <868r09ivqn.fsf@gnu.org> From: Duncan Greatwood Date: Thu, 16 May 2024 09:20:46 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: bug#70973: 29.1; "Unlocking file: Invalid argument" Warning saving via a softlink with stale file lock To: Eli Zaretskii Content-Type: multipart/alternative; boundary="000000000000b9e3e00618949e3d" X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 70973 Cc: 70973@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) --000000000000b9e3e00618949e3d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable AFAIK, there is nothing about the symlink that is macOS or DropBox specific= . Again, ~/.emacs is a symlink to the file in the subfolder of ~/Dropbox. The lock file is not a symlink. Emacs does not create lock files that are symlinks AFAIK. On Thu, May 16, 2024 at 9:09=E2=80=AFAM Eli Zaretskii wrote: > > From: Duncan Greatwood > > Date: Thu, 16 May 2024 08:55:17 -0700 > > Cc: 70973@debbugs.gnu.org > > > > > I thought "ls -l" will show the target of > > > the symlink, but maybe it doesn't on macOS? > > It does indeed do that, even on macOS > > > > However, it is the .emacs that is a symlink. > > > > $ ls -l ~/.emacs > > lrwxr-xr-x 1 username staff 59 Dec 6 2015 .emacs -> > > /Users/username/Dropbox/Documents/Projects/emacs/dotemacs > > > > The lock file is not a link. > > Is that normal on macOS? Or is that something specific to DropBox? > If you edit a file elsewhere on your system, does Emacs create lock > files that are symlinks? > --=20 NOTICE: This email and its attachments may contain privileged and=20 confidential information, only for the viewing and use of the intended=20 recipient. If you are not the intended recipient, you are hereby notified= =20 that any disclosure, copying, distribution, acting upon, or use of the=20 information contained in this email and its attachments is strictly=20 prohibited and that this email and its attachments must be immediately=20 returned to the sender and deleted from your system. If you received this= =20 email erroneously, please notify the sender immediately.=C2=A0 Xage Securit= y,=20 Inc. and its affiliates will never request personal information (e.g.,=20 passwords, Social Security numbers) via email.=C2=A0 Report suspicious emai= ls to=20 security-alerts@xage.com --000000000000b9e3e00618949e3d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
AFAIK, there is nothing about the symlink that is macOS or= DropBox specific.

Again, ~/.emacs is a symlink to the f= ile in the subfolder of ~/Dropbox.

The lock file i= s not a symlink.

Emacs does not create lock files = that are symlinks AFAIK.

On Thu, May 16, 2024 at 9:09=E2=80=AFAM Eli Z= aretskii <eliz@gnu.org> wrote:
> From: Duncan = Greatwood <dgr= eatwood@gmail.com>
> Date: Thu, 16 May 2024 08:55:17 -0700
> Cc: 70973@d= ebbugs.gnu.org
>
> > I thought "ls -l" will show the target of
> > the symlink, but maybe it doesn't on macOS?
> It does indeed do that, even on macOS
>
> However, it is the .emacs that is a symlink.
>
> $ ls -l ~/.emacs
> lrwxr-xr-x=C2=A0 1 username=C2=A0 staff=C2=A0 59 Dec=C2=A0 6=C2=A0 201= 5 .emacs ->
> /Users/username/Dropbox/Documents/Projects/emacs/dotemacs
>
> The lock file is not a link.

Is that normal on macOS?=C2=A0 Or is that something specific to DropBox? If you edit a file elsewhere on your system, does Emacs create lock
files that are symlinks?

NOTICE: This email and its attachmen= ts may contain privileged and confidential information, only for the viewin= g and use of the intended recipient. If you are not the intended recipient,= you are hereby notified that any disclosure, copying, distribution, acting= upon, or use of the information contained in this email and its attachment= s is strictly prohibited and that this email and its attachments must be im= mediately returned to the sender and deleted from your system. If you recei= ved this email erroneously, please notify the sender immediately.=C2=A0 Xag= e Security, Inc. and its affiliates will never request personal information= (e.g., passwords, Social Security numbers) via email.=C2=A0 Report suspici= ous emails to security= -alerts@xage.com
--000000000000b9e3e00618949e3d-- From debbugs-submit-bounces@debbugs.gnu.org Thu May 16 14:19:07 2024 Received: (at 70973) by debbugs.gnu.org; 16 May 2024 18:19:08 +0000 Received: from localhost ([127.0.0.1]:50189 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1s7fh4-0001v6-Ub for submit@debbugs.gnu.org; Thu, 16 May 2024 14:19:07 -0400 Received: from eggs.gnu.org ([209.51.188.92]:53266) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1s7fgx-0001ua-4s for 70973@debbugs.gnu.org; Thu, 16 May 2024 14:19:05 -0400 Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1s7fgo-000647-GC; Thu, 16 May 2024 14:18:50 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=xM3j4wXpuLLsFdybrOf89qyYgUU7Ssar7k7QPy+aXYA=; b=N8zWFeO1/Grh 9RHGvuXmITNB0Z6hXKcz9Cfq6eSzdU7ENnYOEVTWmCZiYKpHwLiG2oo5EgihrWV8Rx4oUBqkW2KfG pTGJhk3m5nG0XdKe5jn8nkT1D/anyIjZjR41k0nb48jU+uqEXunrzKvTbwB8ZoleheiBQC5FiUY4y +QghGll+QtJ8YCr1AS9wr8J/GA5t7Jr6JgtMzOPfJ2f9vnciTzySCTFTPScvyX5wfB6BaWYrnlH/I SbePt2n2scm60uuTAOiR2wR+JTcTMMSNX8/QJMafpQdObcOznaA4OZ0DvfA33L8LVEL8ioQlKi5dt aVREqmYe5IktXINEkQSGyg==; Date: Thu, 16 May 2024 21:18:46 +0300 Message-Id: <867cftiprt.fsf@gnu.org> From: Eli Zaretskii To: Duncan Greatwood In-Reply-To: (message from Duncan Greatwood on Thu, 16 May 2024 09:20:46 -0700) Subject: Re: bug#70973: 29.1; "Unlocking file: Invalid argument" Warning saving via a softlink with stale file lock References: <867cfujge6.fsf@gnu.org> <86fruhiwt0.fsf@gnu.org> <868r09ivqn.fsf@gnu.org> X-Spam-Score: -0.0 (/) X-Debbugs-Envelope-To: 70973 Cc: 70973@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -3.3 (---) > From: Duncan Greatwood > Date: Thu, 16 May 2024 09:20:46 -0700 > Cc: 70973@debbugs.gnu.org > > AFAIK, there is nothing about the symlink that is macOS or DropBox specific. > > Again, ~/.emacs is a symlink to the file in the subfolder of ~/Dropbox. > > The lock file is not a symlink. > > Emacs does not create lock files that are symlinks AFAIK. That is not true. lock files are normally dangling symlinks, i.e. their target does not exist. On a few systems where lock files are not symlinks (I knew about only one: MS-Windows), lock files are regular files, but then they are not empty. And your reports indicate that it is a regular and empty file: > As follows: > $ ls -l ~/Dropbox/Documents/Projects/emacs/.#dotemacs > -rw-r--r--@ 1 username staff 0 May 16 07:13 /Users/username/Dropbox/Documents/Projects/emacs/.#dotemacs This is unusual, because it means the information that a lock file should record: the user and the process ID that locked the file -- is not recorded anywhere. It is usually recorded either in the name of the symlink's target or (if the lock file is a regular file) in the file's contents. So something here is not "normal". If indeed on macOS lock files are not symlinks, they should be regular files which are not empty. If you could step with a debugger through the code of the C function create_lock_file and see what happens there when Emacs locks a file you edit, we could make some progress in investigating this bug. From debbugs-submit-bounces@debbugs.gnu.org Thu May 16 15:28:33 2024 Received: (at 70973) by debbugs.gnu.org; 16 May 2024 19:28:33 +0000 Received: from localhost ([127.0.0.1]:50531 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1s7gmG-0002oX-Eu for submit@debbugs.gnu.org; Thu, 16 May 2024 15:28:33 -0400 Received: from mail-lf1-f42.google.com ([209.85.167.42]:60751) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1s7gmC-0002oN-70 for 70973@debbugs.gnu.org; Thu, 16 May 2024 15:28:31 -0400 Received: by mail-lf1-f42.google.com with SMTP id 2adb3069b0e04-52327368e59so1236828e87.1 for <70973@debbugs.gnu.org>; Thu, 16 May 2024 12:28:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1715887639; x=1716492439; darn=debbugs.gnu.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=KgP6gN85SbRHk2GSv67ihbPiT0GTtpzGQQYZgt84jCw=; b=c1TSA5fPzNhg0/oBJb5MqQk/LTzGgFxxeP66bI3a/XvawgLCtLFO3BuEEG805lJpJd KqWncg7nSBXGl0LgsQQ+Iv3y0Peg5+1nQsePEW9MMIxRhZdlpptubkM1uxuPY8VVbl9N bCwB2R22ieYl6aXLzMhWbhoVo8oWu5nFB2O6um255v5u3JapcztGkMcYjaNZb2Fa8PmD whqganMG7kOkmgRlN+CvZvGAhPd6xqVceCnruiR3GRaU0aZ0suPPmZNaTPo/szMsrkMz ObJQlk5y3vxbbdSZyMlskTrcggkfx3IqelsUoEBVuGqeHhIXeME5rbFDQBdv4BWdyF+P PKyQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1715887639; x=1716492439; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=KgP6gN85SbRHk2GSv67ihbPiT0GTtpzGQQYZgt84jCw=; b=f2nhUSb9kNIBgpj5wT8lTXiwc+cFgU+QpqtHRPloyPhzupeNKl3Bol0fGJvnzWpgDM /wtAPDYZZWSJ4eQBbkArXBW00N9dCzAwSjqH0jlTDD67KfSCinGVrcSHiKnlHRFxgJ1Z KtvkB+/qvSATNgRXgmRL3f3NKaFxfCFs8ksayIj5RTZW7Wi0zvAKATJnQwCRximZhsLW 416uQA8GiX+pNOyMq4DvydWLe5KzE2D0+ZZwRjyCpDwGxdZnZ3YMIdCxg9CYnjvW6DMB E/E5ZGoQGfD0CM3eE27MmlcK+lSQrAxv4LmcsSiy3rU7326YaPFbs4BK3QdB7s+FS8se Ty0A== X-Gm-Message-State: AOJu0YzspcMci2bZWIGOQ3zuSQWzuuXjfk5kcRrUnYRxoajaPfgVyQfn xEpOOVe/CpT9MPgic6qV/aX3InKGOjsqt7ZAeBoPiW7yPz7S3gEGayKALdQ1Hu4= X-Google-Smtp-Source: AGHT+IEMhtOa0LirESwIKHAId+g5guZDrHBYP2mvSVVOxhlCjXdo4BjQKU5eiZBaklJjlBdVvsWsgQ== X-Received: by 2002:ac2:596a:0:b0:523:a5b3:5e1d with SMTP id 2adb3069b0e04-523a5b35f2amr3089126e87.10.1715887638387; Thu, 16 May 2024 12:27:18 -0700 (PDT) Received: from mail-lj1-f177.google.com (mail-lj1-f177.google.com. [209.85.208.177]) by smtp.gmail.com with ESMTPSA id 2adb3069b0e04-521f38d340dsm3060579e87.175.2024.05.16.12.27.17 for <70973@debbugs.gnu.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 16 May 2024 12:27:17 -0700 (PDT) Received: by mail-lj1-f177.google.com with SMTP id 38308e7fff4ca-2e6792ea67fso15078571fa.1 for <70973@debbugs.gnu.org>; Thu, 16 May 2024 12:27:17 -0700 (PDT) X-Received: by 2002:a2e:22c6:0:b0:2e0:eb96:7b53 with SMTP id 38308e7fff4ca-2e5205ec950mr114680741fa.44.1715887637084; Thu, 16 May 2024 12:27:17 -0700 (PDT) MIME-Version: 1.0 References: <867cfujge6.fsf@gnu.org> <86fruhiwt0.fsf@gnu.org> <868r09ivqn.fsf@gnu.org> <867cftiprt.fsf@gnu.org> In-Reply-To: <867cftiprt.fsf@gnu.org> From: Duncan Greatwood Date: Thu, 16 May 2024 12:27:05 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: bug#70973: 29.1; "Unlocking file: Invalid argument" Warning saving via a softlink with stale file lock To: Eli Zaretskii Content-Type: multipart/alternative; boundary="000000000000156014061897394d" X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 70973 Cc: 70973@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) --000000000000156014061897394d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable >> Emacs does not create lock files that are symlinks AFAIK. >That is not true. lock files are normally dangling symlinks, >i.e. their target does not exist. Ah, I see. I just tried editing a different file, client.cc, causing a lockfile to be created. Sure enough, just as you say, that lockfile is a dangling symlink: ls -al .#client.cc lrwxr-xr-x@ 1 username staff 40 May 16 11:39 .#client.cc -> username@DMG-MB-Air-15-2024.local.3071 Then, returning to editing ~/.emacs (which, being a symlink, is actually editing ~/Dropbox/Documents/Projects/emacs/dotemacs). Again, this creates a dangling symlink as you would expect: ls -l .#dotemacs lrwxr-xr-x@ 1 username staff 40 May 16 11:43 .#dotemacs -> username@DMG-MB-Air-15-2024.local.3071 At this point, I tried doing a hard reboot (power cycle) to simulate the kernel crash I mentioned before. But (not surprisingly) after the reboot the lock file still looks as you would expect. ls -l .#dotemacs lrwxr-xr-x@ 1 username staff 40 May 16 11:43 .#dotemacs -> username@DMG-MB-Air-15-2024.local.3071 Noting that, in the bad case, the lock file was not only *not* a dangling symlink as it should be, but was also of zero size, I would speculate that the kernel crash happened right as emacs was part way through writing the lockfile to disk. Taking a quick look at the emacs source, the C function create_lock_file calls emacs_symlink which in turn calls the OS function symlink. The OS function symlink is commonly assumed to be atomic I believe (e.g. see https://rcrowley.org/2010/01/06/things-unix-can-do-atomically.html). However in this case I would suspect that *the kernel crash terminated the symlink write before it could fully complete*. To fix, perhaps emacs needs to check purported lock files and handle the case where they are not symlinks and/or are of zero size, avoiding the need to remove the partially-written lock file manually. On Thu, May 16, 2024 at 11:18=E2=80=AFAM Eli Zaretskii wrote= : > > From: Duncan Greatwood > > Date: Thu, 16 May 2024 09:20:46 -0700 > > Cc: 70973@debbugs.gnu.org > > > > AFAIK, there is nothing about the symlink that is macOS or DropBox > specific. > > > > Again, ~/.emacs is a symlink to the file in the subfolder of ~/Dropbox. > > > > The lock file is not a symlink. > > > > Emacs does not create lock files that are symlinks AFAIK. > > That is not true. lock files are normally dangling symlinks, > i.e. their target does not exist. On a few systems where lock files > are not symlinks (I knew about only one: MS-Windows), lock files are > regular files, but then they are not empty. And your reports indicate > that it is a regular and empty file: > > > As follows: > > $ ls -l ~/Dropbox/Documents/Projects/emacs/.#dotemacs > > -rw-r--r--@ 1 username staff 0 May 16 07:13 > /Users/username/Dropbox/Documents/Projects/emacs/.#dotemacs > > This is unusual, because it means the information that a lock file > should record: the user and the process ID that locked the file -- is > not recorded anywhere. It is usually recorded either in the name of > the symlink's target or (if the lock file is a regular file) in the > file's contents. > > So something here is not "normal". If indeed on macOS lock files are > not symlinks, they should be regular files which are not empty. If > you could step with a debugger through the code of the C function > create_lock_file and see what happens there when Emacs locks a file > you edit, we could make some progress in investigating this bug. > --=20 NOTICE: This email and its attachments may contain privileged and=20 confidential information, only for the viewing and use of the intended=20 recipient. If you are not the intended recipient, you are hereby notified= =20 that any disclosure, copying, distribution, acting upon, or use of the=20 information contained in this email and its attachments is strictly=20 prohibited and that this email and its attachments must be immediately=20 returned to the sender and deleted from your system. If you received this= =20 email erroneously, please notify the sender immediately.=C2=A0 Xage Securit= y,=20 Inc. and its affiliates will never request personal information (e.g.,=20 passwords, Social Security numbers) via email.=C2=A0 Report suspicious emai= ls to=20 security-alerts@xage.com --000000000000156014061897394d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
>> Emacs does not= create lock files that are symlinks AFAIK.
>That is not true.= =C2=A0 lock files are normally dangling symlinks,
>i.e. their target = does not exist.

Ah, I see.

= I just tried editing a different file, client.cc, causing a lockfile to be = created. Sure enough, just as you say, that lockfile is a dangling symlink:=
ls -al .#client.cc
lrwxr-xr-x@ 1 username =C2=A0staff =C2=A04= 0 May 16 11:39 .#client.cc -> username@DMG-MB-Air-15-2024.local.3071
=

Then, returning to editing ~/.emacs (which, being= a symlink, is actually editing ~/Dropbox/Documents/Projects/emacs/dotemacs= ).
Again, this creates a dangling symlink as you would expect:
ls -l .#dotemacs
lrwxr-xr-x@ 1 username =C2=A0staff =C2=A040 May= 16 11:43 .#dotemacs -> username@DMG-MB-Air-15-2024.local.3071
=

At this point, I tried doing a hard reboot (power cycle= ) to simulate the kernel crash I mentioned before. But (not surprisingly) a= fter the reboot the lock file still looks as you would expect.
ls= -l .#dotemacs
lrwxr-xr-x@ 1 username =C2=A0staff =C2=A040 May 16 11:43 = .#dotemacs -> username@DMG-MB-Air-15-2024.local.3071

<= /div>
Noting that, in the bad case, the lock file was not only not=C2=A0a dangling symlink as it should be, but was also of zero size, I wo= uld speculate that the kernel crash happened right as emacs was part way th= rough writing the lockfile to disk.

Taking a quick= look at the emacs source, the C function create_lock_file calls=C2=A0emacs= _symlink which in turn calls the OS function=C2=A0symlink.=C2=A0
=
The OS function symlink is commonly assumed to be atomic I b= elieve (e.g. see=C2=A0https://rcrowley.org/2010/01/06/things-unix-can-d= o-atomically.html). However in this case I would suspect that the ke= rnel crash terminated the symlink write before it could fully complete.=

To fix, perhaps emacs needs to check purported lo= ck files and handle the case where they are not symlinks and/or are of zero= size, avoiding the need to remove the partially-written lock file manually= .




On Thu, May 16, 2024 at= 11:18=E2=80=AFAM Eli Zaretskii <eliz@gnu.org> wrote:
> From: Duncan Greatwood <dgreatwood@gmail.com>
> Date: Thu, 16 May 2024 09:20:46 -0700
> Cc: 70973@d= ebbugs.gnu.org
>
> AFAIK, there is nothing about the symlink that is macOS or DropBox spe= cific.
>
> Again, ~/.emacs is a symlink to the file in the subfolder of ~/Dropbox= .
>
> The lock file is not a symlink.
>
> Emacs does not create lock files that are symlinks AFAIK.

That is not true.=C2=A0 lock files are normally dangling symlinks,
i.e. their target does not exist.=C2=A0 On a few systems where lock files are not symlinks (I knew about only one: MS-Windows), lock files are
regular files, but then they are not empty.=C2=A0 And your reports indicate=
that it is a regular and empty file:

> As follows:
> $ ls -l ~/Dropbox/Documents/Projects/emacs/.#dotemacs
> -rw-r--r--@ 1 username=C2=A0 staff=C2=A0 0 May 16 07:13 /Users/usernam= e/Dropbox/Documents/Projects/emacs/.#dotemacs

This is unusual, because it means the information that a lock file
should record: the user and the process ID that locked the file -- is
not recorded anywhere.=C2=A0 It is usually recorded either in the name of the symlink's target or (if the lock file is a regular file) in the
file's contents.

So something here is not "normal".=C2=A0 If indeed on macOS lock = files are
not symlinks, they should be regular files which are not empty.=C2=A0 If you could step with a debugger through the code of the C function
create_lock_file and see what happens there when Emacs locks a file
you edit, we could make some progress in investigating this bug.

NOTICE: This email and its attachmen= ts may contain privileged and confidential information, only for the viewin= g and use of the intended recipient. If you are not the intended recipient,= you are hereby notified that any disclosure, copying, distribution, acting= upon, or use of the information contained in this email and its attachment= s is strictly prohibited and that this email and its attachments must be im= mediately returned to the sender and deleted from your system. If you recei= ved this email erroneously, please notify the sender immediately.=C2=A0 Xag= e Security, Inc. and its affiliates will never request personal information= (e.g., passwords, Social Security numbers) via email.=C2=A0 Report suspici= ous emails to security= -alerts@xage.com
--000000000000156014061897394d-- From debbugs-submit-bounces@debbugs.gnu.org Thu May 16 15:52:24 2024 Received: (at 70973) by debbugs.gnu.org; 16 May 2024 19:52:24 +0000 Received: from localhost ([127.0.0.1]:50647 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1s7h9M-00034r-0H for submit@debbugs.gnu.org; Thu, 16 May 2024 15:52:24 -0400 Received: from eggs.gnu.org ([209.51.188.92]:52092) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1s7h9J-00034j-IQ for 70973@debbugs.gnu.org; Thu, 16 May 2024 15:52:23 -0400 Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1s7h9B-00036l-Mk; Thu, 16 May 2024 15:52:13 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=YuPYJcc53WzCzhSsN/o5FSod9UVxp8HGDIfHD/XWHW8=; b=Jx9tQpgHZBmH /drfoX1s3dIKCJcaGc99W9BQdjsIyzaTbkCbxQsD+pwVghMrU+Qu1i9zWmTSST0lQ0w7yBjDytBKu C7jUcW0GCnXtoMWQf0OAfB66wYWBbc8VujQ65bxAl7+wqrNelY90K1GzsawzdPJMC/SwYy1VEJ3pa VPsM9vcIFms6myYBXy/s0ee7LVk0EBtySHEKCj5IULTgJL0jaJQUD7e9XLOe0Nhg6noq75ZX0GJJG U3LpOvpgu/ZuPiHEDdR3ZG7uYK9jtiMyr9lDKt9et0eTqHqvdsott1X7ma4wd4G27H4cwqErwlFjt kqc6J6Vn3qp0SmJH/jYwVA==; Date: Thu, 16 May 2024 22:51:30 +0300 Message-Id: <86msoph6wt.fsf@gnu.org> From: Eli Zaretskii To: Duncan Greatwood In-Reply-To: (message from Duncan Greatwood on Thu, 16 May 2024 12:27:05 -0700) Subject: Re: bug#70973: 29.1; "Unlocking file: Invalid argument" Warning saving via a softlink with stale file lock References: <867cfujge6.fsf@gnu.org> <86fruhiwt0.fsf@gnu.org> <868r09ivqn.fsf@gnu.org> <867cftiprt.fsf@gnu.org> X-Spam-Score: -2.3 (--) X-Debbugs-Envelope-To: 70973 Cc: 70973@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -3.3 (---) > From: Duncan Greatwood > Date: Thu, 16 May 2024 12:27:05 -0700 > Cc: 70973@debbugs.gnu.org > > I just tried editing a different file, client.cc, causing a lockfile to be created. Sure enough, just as you say, that > lockfile is a dangling symlink: > ls -al .#client.cc > lrwxr-xr-x@ 1 username staff 40 May 16 11:39 .#client.cc -> username@DMG-MB-Air-15-2024.local.3071 > > Then, returning to editing ~/.emacs (which, being a symlink, is actually editing ~ > /Dropbox/Documents/Projects/emacs/dotemacs). > Again, this creates a dangling symlink as you would expect: > ls -l .#dotemacs > lrwxr-xr-x@ 1 username staff 40 May 16 11:43 .#dotemacs -> username@DMG-MB-Air-15-2024.local.3071 > > At this point, I tried doing a hard reboot (power cycle) to simulate the kernel crash I mentioned before. But > (not surprisingly) after the reboot the lock file still looks as you would expect. > ls -l .#dotemacs > lrwxr-xr-x@ 1 username staff 40 May 16 11:43 .#dotemacs -> username@DMG-MB-Air-15-2024.local.3071 > > Noting that, in the bad case, the lock file was not only not a dangling symlink as it should be, but was also of > zero size, I would speculate that the kernel crash happened right as emacs was part way through writing the > lockfile to disk. > > Taking a quick look at the emacs source, the C function create_lock_file calls emacs_symlink which in turn > calls the OS function symlink. > > The OS function symlink is commonly assumed to be atomic I believe (e.g. see > https://rcrowley.org/2010/01/06/things-unix-can-do-atomically.html). However in this case I would suspect that > the kernel crash terminated the symlink write before it could fully complete. > > To fix, perhaps emacs needs to check purported lock files and handle the case where they are not symlinks > and/or are of zero size, avoiding the need to remove the partially-written lock file manually. I'm not sure we should silently sweep these rare and special cases under the carpet. The warning is just a warning, and manually deleting the lock file fixes even that. So I'm not sure we should do anything here, as long as the conclusion is that this happened due to a system crash in an opportune moment. From debbugs-submit-bounces@debbugs.gnu.org Thu May 16 17:38:03 2024 Received: (at 70973) by debbugs.gnu.org; 16 May 2024 21:38:03 +0000 Received: from localhost ([127.0.0.1]:51145 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1s7inb-0004dL-5z for submit@debbugs.gnu.org; Thu, 16 May 2024 17:38:03 -0400 Received: from mail-lj1-f180.google.com ([209.85.208.180]:56752) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1s7inY-0004cq-F8 for 70973@debbugs.gnu.org; Thu, 16 May 2024 17:38:01 -0400 Received: by mail-lj1-f180.google.com with SMTP id 38308e7fff4ca-2df848f9325so15328581fa.1 for <70973@debbugs.gnu.org>; Thu, 16 May 2024 14:37:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1715895411; x=1716500211; darn=debbugs.gnu.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=83e8fCh+acjISgYuxLTphVPz5VpTufxDpH+3ydhhjiQ=; b=ZRuVi6ZpfxCXZTqExu0+ilJLGtSzGXqaUgk59JNabsZ81bLCtNhT/YmpITe2Xpp7oU fmXz1KzNNBdPh5TaYxXLCXgPxRDd49ZUaiJ/XXx6s9gISRg2tSEAqJ3nBO1H7Pr9RUGn O1p3snElhzHkRMAFW/LUu1aNL/bGBz/XkUVD6vulEpHf1o8Oe7bHH/N6pMR7gA5KGuOl ZefDwkpsbblGTYrRKy5gJo+CLDY65fgLFc8X0YvYoSJ+T0z287/fr5gHtLp5uEqPQZZE 6sGAnzoEiubaOVPP3m4ybCjie2Okx2zQDoklqKQtcNiyKHSEu+dvUEl7N591VgXF47gJ cVjQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1715895411; x=1716500211; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=83e8fCh+acjISgYuxLTphVPz5VpTufxDpH+3ydhhjiQ=; b=iaoKn1fKlZF5dOQFYzWfVnJH16gEkGL1T+kpLoK05JZurSEdUtvdR2Hv40KpsT6j4h ZoP7U9hhvFJPFo5MzfuIM8Nuho4km9liylzvZjX19lewd8vco26fqKB/SaB+t0vpy7sz Yjua+3NPTgV17OhnyKdZI4lFPxioJvaMqSa0U/zw7jkDc3S6eYnshZnv34L0tbtrrl7q jmsqdQ/J9XjT9n7Gd+P6lKnCrRiPYOSAoEFVmwEaGufzX1YBvjFxRxXjbX+k8frE5KYd +wReZeOR3MdmdDKs7FcbnsA1TmWOTReIlo1RopdZTCayxs0OT5eR4vxbSbf+DwpsM9hZ I0dA== X-Gm-Message-State: AOJu0Yx/S2BWs8SgGbwQ25WkbpoXbA2n1KvJRFBNCgzMxt7Z00bArMyR iFuRZ4oRYCJegwUYtJ6bE2arRsIiCf01defiThW9vPqizaSLAvBg5gZ4LabMV/8= X-Google-Smtp-Source: AGHT+IFSSz6v9xHdhZIG11BQ8KPRQO9a/DWfg9OlybJTu5I4wHLURehVwJlR78twbYodRyZEMbX7AA== X-Received: by 2002:a05:651c:78e:b0:2e0:a39b:2b25 with SMTP id 38308e7fff4ca-2e5204b2d6bmr114341731fa.48.1715895410902; Thu, 16 May 2024 14:36:50 -0700 (PDT) Received: from mail-ed1-f50.google.com (mail-ed1-f50.google.com. [209.85.208.50]) by smtp.gmail.com with ESMTPSA id 4fb4d7f45d1cf-574eaace761sm3892385a12.91.2024.05.16.14.36.49 for <70973@debbugs.gnu.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 16 May 2024 14:36:49 -0700 (PDT) Received: by mail-ed1-f50.google.com with SMTP id 4fb4d7f45d1cf-572d2461001so4154068a12.0 for <70973@debbugs.gnu.org>; Thu, 16 May 2024 14:36:49 -0700 (PDT) X-Received: by 2002:a50:9f21:0:b0:572:6249:96bc with SMTP id 4fb4d7f45d1cf-5734d67eea4mr14607869a12.32.1715895408990; Thu, 16 May 2024 14:36:48 -0700 (PDT) MIME-Version: 1.0 References: <867cfujge6.fsf@gnu.org> <86fruhiwt0.fsf@gnu.org> <868r09ivqn.fsf@gnu.org> <867cftiprt.fsf@gnu.org> <86msoph6wt.fsf@gnu.org> In-Reply-To: <86msoph6wt.fsf@gnu.org> From: Duncan Greatwood Date: Thu, 16 May 2024 14:36:37 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: bug#70973: 29.1; "Unlocking file: Invalid argument" Warning saving via a softlink with stale file lock To: Eli Zaretskii Content-Type: multipart/alternative; boundary="00000000000053416806189908ba" X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 70973 Cc: 70973@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) --00000000000053416806189908ba Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I would agree that the issue was likely due to a system crash at an inopportune moment. Of course, if emacs did detect a bad lock file, it could prompt the user for confirmation before removing / replacing it. No need to be silent. The status quo, requiring a user to find and remove the lock file manually, seems burdensome to my eye, albeit the issue is presumably rare. But certainly it is a matter of taste. On Thu, May 16, 2024 at 12:52=E2=80=AFPM Eli Zaretskii wrote= : > > From: Duncan Greatwood > > Date: Thu, 16 May 2024 12:27:05 -0700 > > Cc: 70973@debbugs.gnu.org > > > > I just tried editing a different file, client.cc, causing a lockfile to > be created. Sure enough, just as you say, that > > lockfile is a dangling symlink: > > ls -al .#client.cc > > lrwxr-xr-x@ 1 username staff 40 May 16 11:39 .#client.cc -> > username@DMG-MB-Air-15-2024.local.3071 > > > > Then, returning to editing ~/.emacs (which, being a symlink, is actuall= y > editing ~ > > /Dropbox/Documents/Projects/emacs/dotemacs). > > Again, this creates a dangling symlink as you would expect: > > ls -l .#dotemacs > > lrwxr-xr-x@ 1 username staff 40 May 16 11:43 .#dotemacs -> > username@DMG-MB-Air-15-2024.local.3071 > > > > At this point, I tried doing a hard reboot (power cycle) to simulate th= e > kernel crash I mentioned before. But > > (not surprisingly) after the reboot the lock file still looks as you > would expect. > > ls -l .#dotemacs > > lrwxr-xr-x@ 1 username staff 40 May 16 11:43 .#dotemacs -> > username@DMG-MB-Air-15-2024.local.3071 > > > > Noting that, in the bad case, the lock file was not only not a dangling > symlink as it should be, but was also of > > zero size, I would speculate that the kernel crash happened right as > emacs was part way through writing the > > lockfile to disk. > > > > Taking a quick look at the emacs source, the C function create_lock_fil= e > calls emacs_symlink which in turn > > calls the OS function symlink. > > > > The OS function symlink is commonly assumed to be atomic I believe (e.g= . > see > > https://rcrowley.org/2010/01/06/things-unix-can-do-atomically.html). > However in this case I would suspect that > > the kernel crash terminated the symlink write before it could fully > complete. > > > > To fix, perhaps emacs needs to check purported lock files and handle th= e > case where they are not symlinks > > and/or are of zero size, avoiding the need to remove the > partially-written lock file manually. > > I'm not sure we should silently sweep these rare and special cases > under the carpet. The warning is just a warning, and manually > deleting the lock file fixes even that. > > So I'm not sure we should do anything here, as long as the conclusion > is that this happened due to a system crash in an opportune moment. > --=20 NOTICE: This email and its attachments may contain privileged and=20 confidential information, only for the viewing and use of the intended=20 recipient. If you are not the intended recipient, you are hereby notified= =20 that any disclosure, copying, distribution, acting upon, or use of the=20 information contained in this email and its attachments is strictly=20 prohibited and that this email and its attachments must be immediately=20 returned to the sender and deleted from your system. If you received this= =20 email erroneously, please notify the sender immediately.=C2=A0 Xage Securit= y,=20 Inc. and its affiliates will never request personal information (e.g.,=20 passwords, Social Security numbers) via email.=C2=A0 Report suspicious emai= ls to=20 security-alerts@xage.com --00000000000053416806189908ba Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I would agree that the issue was likely due to a system cr= ash at an inopportune moment.

Of course, if emacs did de= tect a bad lock file, it could prompt the user for confirmation before remo= ving / replacing it. No need to be silent.

The sta= tus quo, requiring a user to find and remove the=C2=A0lock file manually, s= eems burdensome to my eye, albeit the issue is presumably rare. But certain= ly it is a matter of taste.



On Thu, May = 16, 2024 at 12:52=E2=80=AFPM Eli Zaretskii <eliz@gnu.org> wrote:
> From: Duncan Greatwood <dgreatwood@gmail.com>
> Date: Thu, 16 May 2024 12:27:05 -0700
> Cc: 70973@d= ebbugs.gnu.org
>
> I just tried editing a different file, client.cc, causing a lockfile t= o be created. Sure enough, just as you say, that
> lockfile is a dangling symlink:
> ls -al .#client.cc
> lrwxr-xr-x@ 1 username=C2=A0 staff=C2=A0 40 May 16 11:39 .#client.cc -= > username@DMG-MB-Air-15-2024.local.3071
>
> Then, returning to editing ~/.emacs (which, being a symlink, is actual= ly editing ~
> /Dropbox/Documents/Projects/emacs/dotemacs).
> Again, this creates a dangling symlink as you would expect:
> ls -l .#dotemacs
> lrwxr-xr-x@ 1 username=C2=A0 staff=C2=A0 40 May 16 11:43 .#dotemacs -&= gt; username@DMG-MB-Air-15-2024.local.3071
>
> At this point, I tried doing a hard reboot (power cycle) to simulate t= he kernel crash I mentioned before. But
> (not surprisingly) after the reboot the lock file still looks as you w= ould expect.
> ls -l .#dotemacs
> lrwxr-xr-x@ 1 username=C2=A0 staff=C2=A0 40 May 16 11:43 .#dotemacs -&= gt; username@DMG-MB-Air-15-2024.local.3071
>
> Noting that, in the bad case, the lock file was not only not a danglin= g symlink as it should be, but was also of
> zero size, I would speculate that the kernel crash happened right as e= macs was part way through writing the
> lockfile to disk.
>
> Taking a quick look at the emacs source, the C function create_lock_fi= le calls emacs_symlink which in turn
> calls the OS function symlink.
>
> The OS function symlink is commonly assumed to be atomic I believe (e.= g. see
> https://rcrowley.org/2010/01/= 06/things-unix-can-do-atomically.html). However in this case I would su= spect that
> the kernel crash terminated the symlink write before it could fully co= mplete.
>
> To fix, perhaps emacs needs to check purported lock files and handle t= he case where they are not symlinks
> and/or are of zero size, avoiding the need to remove the partially-wri= tten lock file manually.

I'm not sure we should silently sweep these rare and special cases
under the carpet.=C2=A0 The warning is just a warning, and manually
deleting the lock file fixes even that.

So I'm not sure we should do anything here, as long as the conclusion is that this happened due to a system crash in an opportune moment.

NOTICE: This email and its attachmen= ts may contain privileged and confidential information, only for the viewin= g and use of the intended recipient. If you are not the intended recipient,= you are hereby notified that any disclosure, copying, distribution, acting= upon, or use of the information contained in this email and its attachment= s is strictly prohibited and that this email and its attachments must be im= mediately returned to the sender and deleted from your system. If you recei= ved this email erroneously, please notify the sender immediately.=C2=A0 Xag= e Security, Inc. and its affiliates will never request personal information= (e.g., passwords, Social Security numbers) via email.=C2=A0 Report suspici= ous emails to security= -alerts@xage.com
--00000000000053416806189908ba-- From debbugs-submit-bounces@debbugs.gnu.org Sat Jun 01 10:04:50 2024 Received: (at 70973-done) by debbugs.gnu.org; 1 Jun 2024 14:04:50 +0000 Received: from localhost ([127.0.0.1]:56947 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1sDPLl-0006gq-Qx for submit@debbugs.gnu.org; Sat, 01 Jun 2024 10:04:50 -0400 Received: from eggs.gnu.org ([209.51.188.92]:39402) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1sDPLk-0006ge-LZ for 70973-done@debbugs.gnu.org; Sat, 01 Jun 2024 10:04:48 -0400 Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sDPLT-00007E-LH; Sat, 01 Jun 2024 10:04:31 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=5sXB4A61LoyJTFDUtI6OVlYJlH5GCaSjSnfxkkUEuTU=; b=KKnZvV0oD76C bVjwclEkVLvgEPrh4Yd35BcHYDBB0ZymUrIWifoeow5iPkDXanJuzcmZZDtHONBeyKQCVI8Q2J7+F gQr8a/OKTU+S9xlhxXTmUmHt5Asp5NjYu3vRVdp2N8e+A6mJ06R23tsvlkOnnTWpfhtqdMi3aaFkH eHa+P9qBZ9GZQOlAOKBRE/AG/e8d8fb3mF3UA7nELTS1BgB4OEWH0YxEXzWVQMruHG1rw/HWPZ9Fe uePNKph9FTVUmORmW/025IiNMpJEZtESKr37OeWYRHLyVIA6hN/GVP+fIqBOptpi0YskVt0pFDiDe 7tgrzI4eimmTO8BHqb+TVA==; Date: Sat, 01 Jun 2024 17:04:29 +0300 Message-Id: <86wmn8oj2q.fsf@gnu.org> From: Eli Zaretskii To: Duncan Greatwood In-Reply-To: (message from Duncan Greatwood on Thu, 16 May 2024 14:36:37 -0700) Subject: Re: bug#70973: 29.1; "Unlocking file: Invalid argument" Warning saving via a softlink with stale file lock References: <867cfujge6.fsf@gnu.org> <86fruhiwt0.fsf@gnu.org> <868r09ivqn.fsf@gnu.org> <867cftiprt.fsf@gnu.org> <86msoph6wt.fsf@gnu.org> X-Spam-Score: -2.3 (--) X-Debbugs-Envelope-To: 70973-done Cc: 70973-done@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -3.3 (---) > From: Duncan Greatwood > Date: Thu, 16 May 2024 14:36:37 -0700 > Cc: 70973@debbugs.gnu.org > > I would agree that the issue was likely due to a system crash at an inopportune moment. > > Of course, if emacs did detect a bad lock file, it could prompt the user for confirmation before removing / > replacing it. No need to be silent. > > The status quo, requiring a user to find and remove the lock file manually, seems burdensome to my eye, > albeit the issue is presumably rare. But certainly it is a matter of taste. No further comments, so I'm now closing this bug. From unknown Sun Jun 22 03:46:58 2025 Received: (at fakecontrol) by fakecontrolmessage; To: internal_control@debbugs.gnu.org From: Debbugs Internal Request Subject: Internal Control Message-Id: bug archived. Date: Sun, 30 Jun 2024 11:24:09 +0000 User-Agent: Fakemail v42.6.9 # This is a fake control message. # # The action: # bug archived. thanks # This fakemail brought to you by your local debbugs # administrator From debbugs-submit-bounces@debbugs.gnu.org Thu Aug 15 13:44:57 2024 Received: (at control) by debbugs.gnu.org; 15 Aug 2024 17:44:57 +0000 Received: from localhost ([127.0.0.1]:49700 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1seeWu-0004c6-NY for submit@debbugs.gnu.org; Thu, 15 Aug 2024 13:44:56 -0400 Received: from mail.cs.ucla.edu ([131.179.128.66]:52184) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1seeWs-0004br-Bn for control@debbugs.gnu.org; Thu, 15 Aug 2024 13:44:55 -0400 Received: from localhost (localhost [127.0.0.1]) by mail.cs.ucla.edu (Postfix) with ESMTP id 7F9813C0140A0 for ; Thu, 15 Aug 2024 10:44:11 -0700 (PDT) Received: from mail.cs.ucla.edu ([127.0.0.1]) by localhost (mail.cs.ucla.edu [127.0.0.1]) (amavis, port 10032) with ESMTP id WOcm67wxc3oN for ; Thu, 15 Aug 2024 10:44:11 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.cs.ucla.edu (Postfix) with ESMTP id 401363C0140A4 for ; Thu, 15 Aug 2024 10:44:11 -0700 (PDT) DKIM-Filter: OpenDKIM Filter v2.10.3 mail.cs.ucla.edu 401363C0140A4 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cs.ucla.edu; s=9D0B346E-2AEB-11ED-9476-E14B719DCE6C; t=1723743851; bh=E5QhuQPqcH/2CwHCebvVYqc1NqK5nN1IIWvT/nsoxeY=; h=Message-ID:Date:MIME-Version:To:From; b=mI5xn+Mt5Q6MWUZuTsdRz3Fmbki31XLk4Ty8J+6vQwjfqCJBAHS9N2ofD7no4XFQN 87OtDDTulyRt2S5+ZnQxeE8poFkSYgmwS+enTXuTWAHndqkG/pEUvO2AW9dQo0cS7U hWODyjQsAKQZ/cKcD+8dJVz/rSCniiwHAbsEKd+rUk6HmoWb28bZeqjlIewCk2kMDH p/1WNA5aAom2O351XmxLS4K5UmTRyRI/naW8DFCKEBuVPxFuDZcZXbzx10jNJ2uN/E HyRzCDDr/NHDpIKeqttrJnKBHgXkss0QShiYN0B5snnWV1xJZQxo665DZoNs8WgVqX avn5yssE7VNxQ== X-Virus-Scanned: amavis at mail.cs.ucla.edu Received: from mail.cs.ucla.edu ([127.0.0.1]) by localhost (mail.cs.ucla.edu [127.0.0.1]) (amavis, port 10026) with ESMTP id m6L5VcxSRPkM for ; Thu, 15 Aug 2024 10:44:11 -0700 (PDT) Received: from [192.168.254.12] (unknown [47.150.137.250]) by mail.cs.ucla.edu (Postfix) with ESMTPSA id 294F53C0140A0 for ; Thu, 15 Aug 2024 10:44:11 -0700 (PDT) Message-ID: Date: Thu, 15 Aug 2024 10:44:10 -0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Content-Language: en-US To: control@debbugs.gnu.org From: Paul Eggert Subject: unarchive 70973 Organization: UCLA Computer Science Department Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: control X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) unarchive 70973 From unknown Sun Jun 22 03:46:58 2025 Received: (at fakecontrol) by fakecontrolmessage; To: internal_control@debbugs.gnu.org From: Debbugs Internal Request Subject: Internal Control Message-Id: Did not alter fixed versions and reopened. Date: Thu, 15 Aug 2024 17:54:02 +0000 User-Agent: Fakemail v42.6.9 # This is a fake control message. # # The action: # Did not alter fixed versions and reopened. thanks # This fakemail brought to you by your local debbugs # administrator From debbugs-submit-bounces@debbugs.gnu.org Thu Aug 15 13:53:05 2024 Received: (at control) by debbugs.gnu.org; 15 Aug 2024 17:53:05 +0000 Received: from localhost ([127.0.0.1]:49719 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1seeen-0004qC-FO for submit@debbugs.gnu.org; Thu, 15 Aug 2024 13:53:05 -0400 Received: from mail.cs.ucla.edu ([131.179.128.66]:51676) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1seeel-0004pi-FY for control@debbugs.gnu.org; Thu, 15 Aug 2024 13:53:03 -0400 Received: from localhost (localhost [127.0.0.1]) by mail.cs.ucla.edu (Postfix) with ESMTP id A401B3C00E405 for ; Thu, 15 Aug 2024 10:52:21 -0700 (PDT) Received: from mail.cs.ucla.edu ([127.0.0.1]) by localhost (mail.cs.ucla.edu [127.0.0.1]) (amavis, port 10032) with ESMTP id wMljpu_v24Re for ; Thu, 15 Aug 2024 10:52:21 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.cs.ucla.edu (Postfix) with ESMTP id 680BF3C0140A4 for ; Thu, 15 Aug 2024 10:52:21 -0700 (PDT) DKIM-Filter: OpenDKIM Filter v2.10.3 mail.cs.ucla.edu 680BF3C0140A4 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cs.ucla.edu; s=9D0B346E-2AEB-11ED-9476-E14B719DCE6C; t=1723744341; bh=m3g1wSDdmmhp/3eQ1Zvy9oCQxMVJlP8rzLU8nE5DRZM=; h=Message-ID:Date:MIME-Version:To:From; b=br/ZwadxZJ9uCgQww68ff10rSi3OhBUdKAVzwKOrfhRjbABNGUblKXpibTUQS0kVz CfURvbOHxR2JfbXP9AOHYcmh1/bujmVMjvNyFj2q9WOo81ufs2nwNdmYwPEC6lK/AK g6fWuIdvI6hfkXdcpRLF5YX7l9dxrLvcZ8VvejUxMOafIIBAmFSeJDFBbrNAzjRh80 uCQZdah25CjXhaXDu/eDD9OVVE3Gq6FQhMKUQRJp7u2ZZV0+Jy+hpjHA99pZoDIrFe ycT1krQvcPBjJHSv4DYsjxNBYMsDr0GZe/WmjXbZBFNq2IG14DFC+n0BBed3MNGQ26 ppV2aLsA0tupQ== X-Virus-Scanned: amavis at mail.cs.ucla.edu Received: from mail.cs.ucla.edu ([127.0.0.1]) by localhost (mail.cs.ucla.edu [127.0.0.1]) (amavis, port 10026) with ESMTP id r1qDYb2pIPnW for ; Thu, 15 Aug 2024 10:52:21 -0700 (PDT) Received: from [192.168.254.12] (unknown [47.150.137.250]) by mail.cs.ucla.edu (Postfix) with ESMTPSA id 506EB3C0140A0 for ; Thu, 15 Aug 2024 10:52:21 -0700 (PDT) Message-ID: <602894da-c475-4b84-9b96-a0a51fd63635@cs.ucla.edu> Date: Thu, 15 Aug 2024 10:52:21 -0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Content-Language: en-US To: control@debbugs.gnu.org From: Paul Eggert Subject: two bug reports for same bug in Emacs Organization: UCLA Computer Science Department Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: control X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) reopen 70973 merge 70973 72641 From unknown Sun Jun 22 03:46:58 2025 Received: (at fakecontrol) by fakecontrolmessage; To: internal_control@debbugs.gnu.org From: Debbugs Internal Request Subject: Internal Control Message-Id: bug archived. Date: Mon, 16 Sep 2024 11:24:06 +0000 User-Agent: Fakemail v42.6.9 # This is a fake control message. # # The action: # bug archived. thanks # This fakemail brought to you by your local debbugs # administrator