dnkl/foot
41
2.0k
Fork
You've already forked foot
243

"WARNING: terminal is not fully functional" when elevate privileges with opendoas #692

Closed
opened 2021年08月27日 19:21:34 +02:00 by langtudeplao · 8 comments

After updating to 1.9.0 release, some commands are not executed properly when run with doas.

E.g.
$ doas systemctl status bluetooth
Output: "WARNING: terminal is not fully functional"
$ doas vi /path/to/file
Output: file is not displayed properly, only the first line of file is displayed
$ doas dmesg
Output: is not colorized

These problems only happen after updating to 1.9.0. I'm using sway.

// Thank you for this awesome terminal emulator.

After updating to 1.9.0 release, some commands are not executed properly when run with doas. E.g. $ doas systemctl status bluetooth Output: "WARNING: terminal is not fully functional" $ doas vi /path/to/file Output: file is not displayed properly, only the first line of file is displayed $ doas dmesg Output: is not colorized These problems only happen after updating to 1.9.0. I'm using sway. // Thank you for this awesome terminal emulator.
Contributor
Copy link

This is most likely because doas doesn't inherit TERMINFO from the user environment and foot's terminfo is installed in a non-standard location since 1.9.0. See also #673 for background.

There are multiple possible workarounds: You could teach doas to inherit TERMINFO or install foot's terminfo in the standard location manually, for example.

This is most likely because `doas` doesn't inherit `TERMINFO` from the user environment and foot's terminfo is installed in a non-standard location since 1.9.0. See also #673 for background. There are multiple possible workarounds: You could teach doas to inherit `TERMINFO` or install foot's terminfo in the standard location manually, for example.
Owner
Copy link

I'm not familiar with doas, but sounds like this: #691

Note that once the next ncurses release is out, this will be a much much smaller problem, since we'll then gracefully fall back to its version of foot's terminfo.

I'm not familiar with doas, but sounds like this: https://codeberg.org/dnkl/foot/issues/691 Note that once the next ncurses release is out, this will be a much much smaller problem, since we'll then gracefully fall back to its version of foot's terminfo.
Owner
Copy link

I will also happily add information on how to workaround this with doas to the man pages, just like sudo and ssh had already been documented.

I just need someone to tell me what the workaround is :)

I will also happily add information on how to workaround this with doas to the man pages, just like sudo and ssh had already been documented. I just need someone to tell me what the workaround is :)

Thank both of you for godspeed answers. Tbh, I have no idea how to get that workaround. Either @sterni provides a more detailed instruction or I will do my own search based on his/her suggestions. Knowing the cause and there are solutions out there, feel free to close my issue.

Thank both of you for godspeed answers. Tbh, I have no idea how to get that workaround. Either @sterni provides a more detailed instruction or I will do my own search based on his/her suggestions. Knowing the cause and there are solutions out there, feel free to close my issue.
Owner
Copy link
https://man.openbsd.org/doas.conf.5#setenv looks right

@dnkl You're right. I never use this function before.
Setting: permit setenv { -ENV TERMINFO=/usr/share/foot/terminfo } :wheel
solve the problem. Thanks a ton.

@dnkl You're right. I never use this function before. Setting: permit setenv { -ENV TERMINFO=/usr/share/foot/terminfo } :wheel solve the problem. Thanks a ton.
Owner
Copy link

Thanks for the feedback!

One more question if I may; does it also work with { -ENV TERMINFO }? I.e without assigning to it?

Thanks for the feedback! One more question if I may; does it also work with { -ENV TERMINFO }? I.e without assigning to it?

Yes, it works. Great, now my favorite terminal emu is back to action.

Yes, it works. Great, now my favorite terminal emu is back to action.
Sign in to join this conversation.
No Branch/Tag specified
master
osc-5522
sixel-heap-buffer-overflow
releases/1.27
releases/1.26
releases/1.25
releases/1.24
multi-cursor
releases/1.23
pixman-16f-2
releases/1.22
releases/1.21
releases/1.20
releases/1.19
releases/1.18
releases/1.17
releases/1.16
releases/1.15
releases/1.14
releases/1.13
releases/1.12
releases/1.11
releases/1.10
releases/1.9
releases/1.8
releases/1.7
releases/1.6
releases/1.5
releases/1.4
releases/1.3
releases/1.2
releases/1.1
releases/1.0
1.27.0
1.26.1
1.26.0
1.25.0
1.24.0
1.23.1
1.23.0
1.22.3
1.22.2
1.22.1
1.22.0
1.21.0
1.20.2
1.20.1
1.20.0
1.19.0
1.18.1
1.18.0
1.17.2
1.17.1
1.17.0
1.16.2
1.16.1
1.16.0
1.15.3
1.15.2
1.15.1
1.15.0
1.14.0
1.13.1
1.13.0
1.12.1
1.12.0
1.11.0
1.10.3
1.10.2
1.10.1
1.10.0
1.9.2
1.9.1
1.9.0
1.8.2
1.8.1
1.8.0
1.7.2
1.7.1
1.7.0
1.6.4
1.6.3
1.6.2
1.6.1
1.6.0
1.5.4
1.5.3
1.5.2
1.5.1
1.5.0
1.4.4
1.4.3
1.4.2
1.4.1
1.4.0
1.3.0
1.2.3
1.2.2
1.2.1
1.2.0
1.1.0
1.0.0
0.9.0
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
dnkl/foot#692
Reference in a new issue
dnkl/foot
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?