emacs 30 ssh: couldn't find a proper `ls' command

  • Open
  • quality assurance status badge
Details
One participant
  • Christopher Howard
Owner
unassigned
Submitted by
Christopher Howard
Severity
normal

Debbugs page

C
C
Christopher Howard wrote on 5 Sep 09:27 -0700
(address . bug-guix@gnu.org)
87v7za83s2.fsf@librehacker.com
Hi, I've recently started using emacs 30 which I compile from source. Something that broke in the switch from emacs 29->30 is I am not able to use tramp to ssh into any of my guix servers. I get this error

```
Debugger entered--Lisp error: (file-error "Couldn't find a proper `ls' command")
```

I reported this as an Emacs bug - 72861 - and based on the data I provided -- full backtrace, etc. -- they indicated it was a guix bug. They pointed me to guix bug 64534.

However, I tried adding the appropriate directory to tramp-remote-path (/run/current-system/profile/bin) and that did not work.

If I switch back to 29.4 then I can access my servers again normally through tramp.

Here is my system information:

```
christopher@theoden
-------------------
OS: Guix System x86_64
Host: OptiPlex 9020 00
Kernel: 5.15.161-gnu
Uptime: 63 days, 19 hours, 14 mins
Packages: 167 (guix-system), 251 (guix-user)
Shell: bash 5.1.16
Resolution: 1920x1080
DE: GNOME
Theme: Adwaita [GTK2/3]
Icons: Adwaita [GTK2/3]
Terminal: guix
CPU: Intel i5-4570 (4) @ 3.600GHz
GPU: AMD ATI Radeon HD 8490 / R5 235X OEM
GPU: Intel HD Graphics
Memory: 5038MiB / 15914MiB
```

``` guix describe
Generation 143 Sep 03 2024 10:14:51 (current)
guix 82174b2
branch: master
commit: 82174b2742c2a59fd7959ba9acc80edd6f93d9f7
```

The emacs version I am testing is:

GNU Emacs 30.0.90 (build 5, x86_64-pc-linux-gnu, GTK+ Version 3.24.41, cairo version 1.18.0) of 2024-09-03


--
📛 Christopher Howard
🚀 gemini://gem.librehacker.com

בראשית ברא אלהים את השמים ואת הארץ
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 73052@patchwise.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 73052
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch