[Bug]: Error: Permission denied (os error 13)
Opened this issue · 12 comments
What did you expect to happen?
The search panel open.
What happened?
Recently i started getting this error when running on zsh.
The following error happens when i try run it.
Error: Permission denied (os error 13)
Location:
crates/atuin/src/command/client/search/interactive.rs:990:18
Atuin doctor output
{
"atuin": {
"version": "18.3.0",
"sync": null,
"sqlite_version": "3.44.0"
},
"shell": {
"name": "zsh",
"default": "zsh",
"plugins": [
"atuin"
],
"preexec": "built-in"
},
"system": {
"os": "Ubuntu",
"arch": "x86_64",
"version": "24.04",
"disks": [
{
"name": "/dev/sdc2",
"filesystem": "btrfs"
},
{
"name": "/dev/sdc2",
"filesystem": "btrfs"
},
{
"name": "/dev/sdc2",
"filesystem": "btrfs"
},
{
"name": "/dev/sdc1",
"filesystem": "vfat"
},
{
"name": "/dev/sda1",
"filesystem": "ext4"
},
{
"name": "/dev/sda1",
"filesystem": "ext4"
},
{
"name": "/dev/sdb1",
"filesystem": "ext4"
},
{
"name": "/dev/sdb2",
"filesystem": "ext4"
},
{
"name": "/dev/sdb1",
"filesystem": "ext4"
},
{
"name": "/dev/sdb3",
"filesystem": "ext4"
}
]
}
}
Code of Conduct
- I agree to follow this project's Code of Conduct
Same here
Atuin Doctor
Checking for diagnostics
Please include the output below with any bug reports or issues
{
"atuin": {
"version": "18.3.0",
"sync": {
"cloud": true,
"records": true,
"auto_sync": true,
"last_sync": "2024-11-05 19:37:37.40501821 +00:00:00"
},
"sqlite_version": "3.44.0"
},
"shell": {
"name": "zsh",
"default": "zsh",
"plugins": [
"atuin"
],
"preexec": "built-in"
},
"system": {
"os": "Ubuntu",
"arch": "x86_64",
"version": "24.04",
"disks": [
{
"name": "/dev/nvme1n1p2",
"filesystem": "btrfs"
},
{
"name": "/dev/nvme1n1p2",
"filesystem": "btrfs"
},
{
"name": "/dev/nvme1n1p1",
"filesystem": "vfat"
}
]
}
}
Same here
This is the output from atuin doctor
{
"atuin": {
"version": "18.3.0",
"sync": null,
"sqlite_version": "3.44.0"
},
"shell": {
"name": "zsh",
"default": "zsh",
"plugins": [
"atuin"
],
"preexec": "built-in"
},
"system": {
"os": "Ubuntu",
"arch": "x86_64",
"version": "24.04",
"disks": [
{
"name": "/dev/mapper/ubuntu--vg-ubuntu--lv",
"filesystem": "ext4"
},
{
"name": "/dev/sda2",
"filesystem": "ext4"
}
]
}
}
This is the output of ctrl+r
➜ Error: Permission denied (os error 13)
Location:
crates/atuin/src/command/client/search/interactive.rs:990:18a
What terminals are you using?
atuin/crates/atuin/src/command/client/search/interactive.rs
Lines 987 to 991 in 2e332c2
is where the error is coming from
I'm SSH'ing into a virtual machine
but with what terminal emulator?
Is xterm-256color
a terminal emulator? That's the output of echo $TERM
The same behaviour happens outside, and within tmux.
Just to rephrase - what application are you opening on your computer in order to run the ssh command?
Such as iterm2, alacritty, gnome terminal, etc
What terminals are you using?
atuin/crates/atuin/src/command/client/search/interactive.rs
Lines 987 to 991 in 2e332c2
is where the error is coming from
Alacritty
alacritty --version │
lacritty 0.13.2
iterm2
on MacOS.
I just tested and noted the same behaviour if I SSH to the VM using Windows Terminal
Is
xterm-256color
a terminal emulator? That's the output ofecho $TERM
The same behaviour happens outside, and within tmux.
I don't know why, but just as the error came, it disappeared...
The only thing I can say is that while this was happening in zsh, on the same system with bash it worked fine.
echo $TERM
xterm-256color
This was on both zsh(broken) and bash(fine) using gnome terminal
For me its solved, for now....
Am also affected — it doesn't seem to depend on which terminal emulator is used, I can reproduce when sshing from WezTerm, Zed, and the built-in macOS Terminal.
{
"atuin": {
"version": "18.3.0",
"sync": null,
"sqlite_version": "3.44.0"
},
"shell": {
"name": "zsh",
"default": "zsh",
"plugins": [
"atuin"
],
"preexec": "built-in"
},
"system": {
"os": "Debian GNU/Linux",
"arch": "x86_64",
"version": "12",
"disks": [
{
"name": "/dev/md3",
"filesystem": "ext4"
},
{
"name": "/dev/md2",
"filesystem": "ext3"
},
{
"name": "/dev/md0",
"filesystem": "vfat"
}
]
}
}
I'm happy to try repro steps / potential fixes.