hstr stops working on linux >=6.2.0 (depending on kernel config)

Question

hstr stops working on linux >=6.2.0 (depending on kernel config)

leapfog opened this issue 2 years ago · 63 comments

Just wanted to leave a note, that hstr stops working with linux kernel 6.2.0, when CONFIG_LEGACY_TIOCSTI isn't set. So maybe you want to add that information to a trouble shooting guide or FAQ or something.

(re: "stops working": the history can still be browsed, but cannot be inserted anymore)

Answer 1 · 2023-02-28T19:00:01.000Z

Edit: Never mind, probably only switchable with CONFIG_LEGACY_TIOCSTI=y.

~~How is this meant to be done?~~

This functionality can be changed at runtime with the dev.tty.legacy_tiocsti sysctl. This configuration option sets the default value of the sysctl.
https://cateee.net/lkddb/web-lkddb/LEGACY_TIOCSTI.html

It can't be set though.

# sysctl -w dev.tty.legacy_tiocsti=1
sysctl: setting key "dev.tty.legacy_tiocsti": Invalid argument
# echo 1 > /proc/sys/dev/tty/legacy_tiocsti
bash: echo: write error: Invalid argument

Arch Linux 6.2.1

Answer 2 · 2023-03-02T12:36:58.000Z

I came here as well cause hstr stopped working.
Could we get an official reply on how this situation will be handled? Will hstr be adjusted to work without it?
I would rather not enable a legacy option.

Cheers

Answer 3 · 2023-03-02T15:39:27.000Z

❯ uname -r
6.2.1-arch1-1

❯ date
Thu Mar 2 10:38:30 AM EST 2023

Hstr is confirmed NOT working on the above kernel as of the time above.

Answer 4 · 2023-03-02T15:54:27.000Z

If you run zgrep CONFIG_LEGACY_TIOCSTI /proc/config.gz you can see CONFIG_LEGACY_TIOCSTI is not set for 6.2.1-arch1-1. If indeed hstr insertion is not working because CONFIG_LEGACY_TIOCSTI is not set then this is why for 6.2.1-arch1-1.

Answer 5 · 2023-03-02T18:16:51.000Z

I can confirm that it's the CONFIG_LEGACY_TIOCSTI option. I had the same problem after I updated my Gentoo to 6.2, and after reenabling that option in my Kernel, it started to work again with 6.2.

Answer 6 · 2023-03-03T08:31:01.000Z

Seems fzf's history search is still working, even without CONFIG_LEGACY_TIOCSTI, so there is a way.

Answer 7 · 2023-03-04T12:42:28.000Z

Seems fzf's history search is still working, even without CONFIG_LEGACY_TIOCSTI, so there is a way.

fzf has a bash function around it for the history function, that sets the readline input buffer with the history line that was selected in fzf. The same can be done with hstr!

What I did:

Build hstr with DEBUG_NO_TIOCSTI set. You just need to uncomment this line and recompile hstr: https://github.com/dvorka/hstr/blob/master/src/hstr_utils.c#L29. With DEBUG_NO_TIOCSTI set hstr doesn't use the insecure TIOCSTI and instead prints the selected history line to stderr. On Arch Linux I did this with:

auracle download hstr
cd hstr
makepkg -so
sed -i -r 's|//(#define DEBUG_NO_TIOCSTI)|\1|' src/hstr-*/src/hstr_utils.c
makepkg -e
sudo pacman -U hstr-*.zst

We don't want the selected history line on stderr, we want it in the readline input buffer. I couldn't fully follow how fzf was doing that but on the wiki there is an example for bash: https://github.com/junegunn/fzf/wiki/Examples#with-write-to-terminal-capabilities. I used the 3rd example, the one starting with # re-wrote the script above, and adjusted it a bit for hstr. Basically: call hstr, redirect its stderr to a file so that can be read back into a variable and then pass that variable to the function from the wiki that sets the readline input buffer. Add this to your ~/.bashrc:

bind '"\C-r": "\C-x1\e^\er"'
bind -x '"\C-x1": __hstr';

__hstr ()
{
	hstr 2> ~/.hstr.tmp
	hstr_tmp=$(< ~/.hstr.tmp)
	__ehc "$hstr_tmp"
}

__ehc()
{
if
        [[ -n $1 ]]
then
        bind '"\er": redraw-current-line'
        bind '"\e^": magic-space'
        READLINE_LINE=${READLINE_LINE:+${READLINE_LINE:0:READLINE_POINT}}${1}${READLINE_LINE:+${READLINE_LINE:READLINE_POINT}}
        READLINE_POINT=$(( READLINE_POINT + ${#1} ))
else
        bind '"\er":'
        bind '"\e^":'
fi
}

And you need to disable the default hstr keybindings in your ~/.bashrc so comment out these lines:

# if this is interactive shell, then bind hstr to Ctrl-r (for Vi mode check doc)
if [[ $- =~ .*i.* ]]; then bind '"\C-r": "\C-a hstr -- \C-j"'; fi
# if this is interactive shell, then bind 'kill last command' to Ctrl-x k
if [[ $- =~ .*i.* ]]; then bind '"\C-xk": "\C-a hstr -k \C-j"'; fi

Now if I open a new terminal, press Ctrl+R, hstr works again and the selected history line is placed on the readline input.

I don't fully understand all of the above — and it can probably be cleaned up and made nicer — but at least I have a working hstr again.

Answer 8 · 2023-03-04T16:54:53.000Z

CopyQ is another candidate that still works. I'm not sure but i think they load the clipboard and send a keystroke via X11 to paste the text.

Answer 9 · 2023-03-04T16:57:06.000Z

Thanks @jakedane for the workaround. It works!
There is a small issue - pressing Enter on selected command in history places the command into input buffer but without automatic execution. I have to press Enter again, but this is very small issue.

Answer 10 · 2023-03-08T14:56:07.000Z

I am on debian sid and stopped working too with 6.2.2-2-siduction-amd64 #1 SMP PREEMPT_DYNAMIC siduction 6.2-2.1 (2023-03-06) x86_64 GNU/Linux

apt source hstr
sed -i -r 's|//(#define DEBUG_NO_TIOCSTI)|\1|' src/hstr_utils.c
debuild -uc -us

Compiled with the patch, it still not work. I just get the command in the terminal after the selection compared to before.

Answer 11 · 2023-03-08T15:40:54.000Z

Compiled with the patch, it still not work. I just get the command in the terminal after the selection compared to before.

That sounds like you did step 1 from #478 (comment) but didn't proceed with step 2 and 3 to modify your .bashrc file (and open a new terminal after).

Answer 12 · 2023-03-09T10:47:35.000Z

So I tried that bash changes and in this way works only Ctrl+r not hh as example (I tried changing the bash-completion script):

#
# Copyright (C) 2014-2022  Martin Dvorak <martin.dvorak@mindforger.com>
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
#    http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.

# Bash completion support for HSTR

# Source this file or install it to /usr/share/bash-completion/completions or /etc/bash_completion.d/
# See https://iridakos.com/tutorials/2018/03/01/bash-programmable-completion-tutorial.html
# help complete
# complete -W "--favorites --kill-last-command --non-interactive --show-configuration --show-zsd-configuration --show-blacklist --version --help" hstr

bind '"\C-r": "\C-x1\e^\er"'
bind -x '"\C-x1": _hstr';

#_hstr()
#{
#        local cur prev OPTS
#        COMPREPLY=()
#        cur="${COMP_WORDS[COMP_CWORD]}"
#        prev="${COMP_WORDS[COMP_CWORD-1]}"
#        case $prev in
#                '-h'|'--help'|'-v'|'--version')
#                        return 0
#                        ;;
#        esac
#        case $cur in
#                -*)
#                        OPTS="--favorites --kill-last-command --non-interactive --show-configuration --show-zsd-configuration --show-blacklist --version --help"
#                        COMPREPLY=( $(compgen -W "${OPTS[*]}" -- $cur) )
#                        return 0
#                        ;;
#        esac
#        compopt -o bashdefault
#        COMPREPLY=( $(compgen -c -- $cur) )
#        return 0
#}

_hstr ()
{
	hstr 2> /tmp/.hstr.tmp
	hstr_tmp=$(< /tmp/.hstr.tmp)
	__ehc "$hstr_tmp"
}

__ehc()
{
if
        [[ -n $1 ]]
then
        bind '"\er": redraw-current-line'
        bind '"\e^": magic-space'
        READLINE_LINE=${READLINE_LINE:+${READLINE_LINE:0:READLINE_POINT}}${1}${READLINE_LINE:+${READLINE_LINE:READLINE_POINT}}
        READLINE_POINT=$(( READLINE_POINT + ${#1} ))
else
        bind '"\er":'
        bind '"\e^":'
fi
}
complete -F _hstr hstr
complete -F _hstr hh

# eof

Answer 13 · 2023-03-14T08:31:24.000Z

While I still hope for hstr to be modified to work without CONFIG_LEGACY_TIOCSTI, kernel 6.2.x has been fixed, so re-enabling it at runtime is now possible:

# sysctl -w dev.tty.legacy_tiocsti=1 # fix hstr
dev.tty.legacy_tiocsti = 1

I only confirmed that with linux-6.2.6 today, but it might also have worked earlier.

Answer 14 · 2023-03-15T15:47:37.000Z

I can confirm that with 6.2.5-arch1-1 re-enabling sysctl -w dev.tty.legacy_tiocsti=1 is now also works.

Answer 15 · 2023-03-16T09:56:25.000Z

I can confirm too on Debian sid (siduction) with 6.2.6-1 the hstr package from debian repository works again.

Answer 16 · 2023-03-16T21:41:46.000Z

Re-enabling sysctl -w dev.tty.legacy_tiocsti=1 also works on OpenSUSE Tumbleweed (6.2.4-1-default) with hstr from the lemmy04 repo.

Answer 17 · 2023-03-18T17:56:32.000Z

@Mte90 @chrischmo @karlovskiy @leapfog @jakedane @papavlos @mmeier86 thank you all for detailed descriptions of the problem, root cause identification and proposed solutions!

I worked on a version of HSTR for Cygwin and WSL where TIOCSTI is not available in the past. If you are able to build HSTR and you use Bash, can you please try #481?

The PR just enables existing HSTR functionality to work w/o TIOCSTI w/ the new define. I did not used it in the past because it requires shell command (and many users will not (be able to) do such configuration).

Anyway if the PR will work for you, I will fix it also for zsh (which I use on 90% of my machines) and release a new version.

Do you think that it would make sense to release HSTR with a TIOCSTI parameter allowing to run version with or without TIOCSTI use? Is there any way how to safely detect TIOCSTI availability? Will it compile on systems with new kernel?

Thank you all your interest in HSTR and your help!

Answer 18 · 2023-03-18T19:27:02.000Z

@dvorka I built hstr with #481 and with LINUX_KERNEL_6 defined, I put the new config in my .bashrc and with that Ctrl+R works properly in Bash. Thank you!

I'm on Arch Linux with kernel 6.2.6. No issue compiling.

I don't know how to safely detect TIOCSTI is available. Probably too hacky and not portable but on Linux if sysctl -ne dev.tty.legacy_tiocsti prints 0 (zero) that means TIOCSTI is disabled.

Answer 19 · 2023-03-18T20:10:23.000Z

Preliminary TIOCSTI design:

.bashrc/.zshrc function:
- detects TIOCSTI and based on that:
  - call the right Bash/zsh function which binds to the shortcut
  - hstr command w/ or w/o --no-tiocsti parameter
hstr binary:
- detects TIOCSTI and based on that it either uses it or not
  - hstr binary supports both modes
  - #define is not used to compile only one option

.bashrc

detect whether TIOCSTI is supported by the kernel @ Bash
based on whether TIOCSTI is available bind keyword shortcuts
either to hstr command or hstrcygwin Bash function

# detect TIOCSTI
function is_tiocsti {
    if test -w /dev/tty && { stty -echo; echo -n a | tioctl TIOCSTI; stty echo; } >/dev/null 2>&1; then
        echo "TIOCSTI is supported by the kernel."
    else
        echo "TIOCSTI is not supported by the kernel."
    fi
}

# command binding
if is_tiocsti
then
    # if this is interactive shell, then bind hstr to Ctrl-r (for Vi mode check doc)
    if [[ $- =~ .*i.* ]]; then bind '"\C-r": "\C-a hstr -- \C-j"'; fi
    # if this is interactive shell, then bind 'kill last command' to Ctrl-x k
    if [[ $- =~ .*i.* ]]; then bind '"\C-xk": "\C-a hstr -k \C-j"'; fi
else
    if [[ $- =~ .*i.* ]]; then bind -x '"\C-r": "hstrcygwin"'; fi
fi

Detect TIOCSTI from C:

#include <stdio.h>
#include <stdlib.h>
#include <fcntl.h>
#include <unistd.h>
#include <termios.h>
#include <sys/ioctl.h>

int main() {
   int fd;
   struct termios t;
   fd = open("/dev/tty", O_RDWR);
   if (fd < 0) {
      perror("open /dev/tty");
      exit(1);
   }
   if (tcgetattr(fd, &t) < 0) {
      perror("tcgetattr");
      exit(1);
   }
   if (!ioctl(fd, TIOCSTI, "a")) {
      printf("TIOCSTI supported\n");
   } else {
      printf("TIOCSTI not supported\n");
   }
   close(fd);
   return 0;
}

Answer 20 · 2023-03-18T20:26:39.000Z

The C code detects TIOCSTI correctly. I tested it both with dev.tty.legacy_tiocsti=0 and dev.tty.legacy_tiocsti=1.

The bash code does not detect it correctly. is_tiocsti always responds "TIOCSTI is supported by the kernel."

Edit: ah, removing the redirect to /dev/null I get tioctl: command not found.

Answer 21 · 2023-03-19T16:24:05.000Z

@jakedane thank you for testing the code! It really helped. As tioctl command does not have to be present on the system, I will always hstr - I will create a hstr parameter which will make the test (and use it in .bashrc/.zshrc).

Answer 22 · 2023-03-19T18:01:38.000Z

FYI working on the fix @ dev-2.7.0 branch.

Answer 23 · 2023-03-28T22:56:00.000Z

Hi!

I'd like to add some information regarding TIOCSTI ioctl that I didn't see mentioned above (from a quick look):

Allowing use of TIOCSTI has security consequences, e.g. see ttyjack to see trivial privilege escalation through command injection using TIOCSTI in action.
TIOCSTI is enabled by default in upstream Linux but disabled by default in Arch Linux.
The sysctl variable dev.tty.legacy_tiocsti could not be set successfully in the past on some systems, including Arch Linux. There was a kernel module built in the mean time to bring it back at https://github.com/kauruus/legacy_tiocsti to workaround the issue but by now it is no longer needed and sysctl should work fine.

Best, Sebastian

Answer 24 · 2023-04-04T06:56:59.000Z

PROGRESS UPDATE: I apologize that the fix is not out yet (busy days). It was a bit painful process, but I finally have the solution for both Bash and Zsh which enables HSTR to work w/o TIOCSTI 😌

Zsh:

hstr_notiocsti() {
    zle -I
    { HSTR_OUT="$( { </dev/tty hstr ${BUFFER}; } 2>&1 1>&3 3>&- )"; } 3>&1;
    BUFFER="${HSTR_OUT}"
    CURSOR=${#BUFFER}
    zle redisplay
}
zle -N hstr_notiocsti
bindkey '\C-r' hstr_notiocsti

Bash:

function hstrnotiocsti {
    { HSTR_OUT="$( { </dev/tty hstr ${READLINE_LINE}; } 2>&1 1>&3 3>&- )"; } 3>&1;
    READLINE_LINE="${HSTR_OUT}"
    READLINE_POINT=${#READLINE_LINE}
}
if [[ $- =~ .*i.* ]]; then bind -x '"\C-r": "hstrnotiocsti"'; fi

Having the solution, I just need to polish it a bit and do the release. Stay tuned please.

Answer 25 · 2023-04-04T10:14:52.000Z

Posted hstr_notiocsti() function does not work for me, still does nothing after selecting the history entry. Don't know if I am doing something wrong. I already verified that it is actually being executed on CTRL+R.

fedora 37, kernel 6.2.8-200.fc37.x86_64

sysctl -w dev.tty.legacy_tiocsti=1 is making it work.

Answer 26 · 2023-04-04T16:46:07.000Z

@krossekrabbe apologies for confusion - I shared the function, however, it will work with new version of HSTR. Anyway thank you for your interest in this issue!

Answer 27 · 2023-04-15T16:08:38.000Z

Fixed by aa14f03 and released by f370a80. Please report any problems!

Answer 28 · 2023-04-21T15:42:17.000Z

The fix only seems to work to some extent. After entering the hstr_notiocsti() function in my .bashrc, the history can be opened via CTRL+R but the selected command now appears in the console and is not executed until ENTER is pressed. This corresponds more to the function of the right cursor key (->) - to display the command and to be able to change it if necessary.

Answer 29 · 2023-04-23T08:45:50.000Z

Imo the fix is not working as expected.
This means I can display bash history and select any line item.
However when I hit ENTER the line item will only be copied to console, but not executed.

I'm running Arch Linux with hstr version "3.1.0" (2023-04-18T08:50:00) and Linux Kernel 6.2.12-arch1-1.
TIOCSTI is disabled (dev.tty.legacy_tiocsti = 0).

My understanding was that hstr should work /w and w/o TIOCSTI.

Answer 30 · 2023-04-23T09:01:26.000Z

Yes can confirm on fedora, ENTER writes to console but not executes.

But I can live with that for now, close enough 😂 Thanks for the fix @dvorka

Answer 31 · 2023-04-23T10:20:34.000Z

My error I think. Where I wrote for the earlier patch "with that Ctrl+R works properly in Bash" I meant it works the same as my workaround, which has this behavior (which I actually prefer), and should have clarified with the patch Enter puts the command on the console and Enter is needed again to execute it. Sorry @dvorka if I put you on wrong footing here!

Answer 32 · 2023-04-23T11:26:12.000Z

Is the version 3.1.0 supposed to fix selecting command from running hstr command directly as well (not using Ctrl + R)? If so, it is not working for me with bash on Arch Linux with kernel version 6.2.12-arch1-1. The interactive history shows and I can search, but selecting a command using tab or enter returns to the prompt with the selected command on its own line and the prompt line empty.

Enabling TIOCSTI with sysctl -w dev.tty.legacy_tiocsti=1 make it works. Although the selected command still print on its own line as well as populating the prompt line.

Thank you for the great work btw.

Answer 33 · 2023-05-17T20:32:46.000Z

Hello,
I'm running
Linux Kernel 6.3.1-arch2-1
hstr 3.1-1
and it works only as expected with dev.tty.legacy_tiocsti = 1.

My understanding is that latest hstr release should work w/o TIOCSTI, therefore I don't understand why this issue is closed.

Answer 34 · 2023-05-21T08:55:39.000Z

The interactive history shows and I can search, but selecting a command using tab or enter returns to the prompt with the selected command on its own line and the prompt line empty.

Same issue on Fedora 38 (running on kernel 6.2.14-300.fc38.x86_64)

Answer 35 · 2023-06-02T12:34:15.000Z

Should there be a separate bug for this "selecting command does not execute directly" issue? I ask because this bug is closed.

Answer 36 · 2023-06-28T23:49:22.000Z

Hello, I'm running Linux Kernel 6.3.1-arch2-1 hstr 3.1-1 and it works only as expected with dev.tty.legacy_tiocsti = 1.

My understanding is that latest hstr release should work w/o TIOCSTI, therefore I don't understand why this issue is closed.

Same here, it was fixed for a while and then it broke again. kernel 6.3.9

Answer 37 · 2023-06-30T13:32:03.000Z

Void Linux, kernel 6.3.10, hstr does not work.

Answer 38 · 2023-07-02T07:12:53.000Z

Confirming on Debian Sid kernel 6.3.0-1-amd64 has the same issue. sysctl -w dev.tty.legacy_tiocsti=1 does fix the issue.

Answer 39 · 2023-07-21T18:03:57.000Z

This needs to be reopened.

Answer 40 · 2023-07-21T18:26:51.000Z

Several comments above saying hstr doesn't work. It's not clear what "doesn't work" means.

Does it mean hstr doesn't work at all without setting dev.tty.legacy_tiocsti=1? And if so with which shell? Or does it mean hstr works but Enter needs to be pressed twice to run a command from history? First Enter puts the command on the prompt, second Enter runs it. In either case I think that should be a new issue.

I'm on Arch Linux with kernel 6.4.4 and hstr works for me in Bash. Enter needs to be pressed twice to run a command from history which is different from with setting dev.tty.legacy_tiocsti=1 but it does work.

Answer 41 · 2023-07-23T02:57:35.000Z

Does it mean hstr doesn't work at all without setting dev.tty.legacy_tiocsti=1?

The same behavior as before the fix was applied

And if so with which shell?

bash

Or does it mean hstr works but Enter needs to be pressed twice to run a command from history?

No, that's not it

Answer 42 · 2023-07-23T05:04:56.000Z

@Gooberpatrol66 which distro are you on? Which terminal are you using? Which hstr version and how does your configuration in .bashrc differ from the recommended:

# HSTR configuration - add this to ~/.bashrc
alias hh=hstr                    # hh to be alias for hstr
export HSTR_CONFIG=hicolor       # get more colors
shopt -s histappend              # append new history items to .bash_history
export HISTCONTROL=ignorespace   # leading space hides commands from history
export HISTFILESIZE=10000        # increase history file size (default is 500)
export HISTSIZE=${HISTFILESIZE}  # increase history size (default is 500)
# ensure synchronization between bash memory and history file
export PROMPT_COMMAND="history -a; history -n; ${PROMPT_COMMAND}"
function hstrnotiocsti {
    { READLINE_LINE="$( { </dev/tty hstr ${READLINE_LINE}; } 2>&1 1>&3 3>&- )"; } 3>&1;
    READLINE_POINT=${#READLINE_LINE}
}
# if this is interactive shell, then bind hstr to Ctrl-r (for Vi mode check doc)
if [[ $- =~ .*i.* ]]; then bind -x '"\C-r": "hstrnotiocsti"'; fi
export HSTR_TIOCSTI=n

I'm using hstr 3.1, bash 5.1.016 and Linux 6.4.4 on Arch Linux. That works. I tried with Gnome Terminal, Console and Black Box. My .bashrc uses the recommended configuration.

I also tried hstr 3.0 on Fedora 38 and after manually fixing hstrnotiocsti in .bashrc, that also works.

Answer 43 · 2023-07-30T23:21:20.000Z

oh, i didn't see the bashrc changed

Answer 44 · 2023-09-27T10:26:14.000Z

I forgot I was still using the sysctl "fix", so I removed it and now hstr doesn't work for me.

I'm using hstr 3.1.0 on arch linux, kernel 6.5.5, and my bashrc has the same lines as in jakedane's comment above.

I can search history but pressing enter doesn't select the entry, it only echo'es it.
If I set dev.tty.legacy_tiocsti=1 it works.

Answer 45 · 2023-09-27T13:47:39.000Z

I can search history but pressing enter doesn't select the entry, it only echo'es it.

You have to press Enter twice. 1st Enter puts the selected history item on the bash prompt, 2nd Enter runs it.

If any expect hstr to work differently (that 1st Enter runs the command directly), I think that needs to be a separate issue.

Answer 46 · 2023-09-27T15:35:51.000Z

I can search history but pressing enter doesn't select the entry, it only echo'es it.

You have to press Enter twice. 1st Enter puts the selected history item on the bash prompt, 2nd Enter runs it.

If any expect hstr to work differently (that 1st Enter runs the command directly), I think that needs to be a separate issue.

@eleius another suggestion is to select your command, use TAB to bring it to your prompt, and then press enter; removing the need to hit Enter twice.

Answer 47 · 2023-09-28T05:29:05.000Z

@jakedane @jasonnab I've already tried Tab+Enter and Enter+Enter, but for some reason when I press either Tab or Enter, the selected history item is just displayed as when you type the echo command (hstr doesn't bring it to the bash prompt.)
I've tried deleting my current .bashrc and only placing the hstr lines in it, but still same issue. Don't know why it doesn't work.

Answer 48 · 2023-09-28T06:06:33.000Z

@eleius, don't be upset. I have hstr behaving exactly the same way on Void Linux 6.3.13.

Answer 49 · 2023-12-05T09:46:15.000Z

any update for this issue?
when it is planned a new release?

Answer 50 · 2023-12-05T10:13:03.000Z

@Mte90 hstr 3.1.0 fixed the issue. Currently with bash 5.2.21 in gnome-terminal 3.50.1 (vte 0.74.1) on Arch Linux, kernel 6.6.3, with the output of hstr --show-configuration in the .bashrc file, that works without problems. The kernel is not compiled with CONFIG_LEGACY_TIOCSTI set and dev.tty.legacy_tiocsti is also not set.

If it doesn't work for you, what specifically are you using?

Answer 51 · 2023-12-05T10:23:01.000Z

I didn't saw the new parameter for bash export HSTR_TIOCSTI=y I think that now it should work.

Answer 52 · 2024-05-16T11:10:22.000Z

I have the same problem on Ubuntu, since the upgrade to 24.04. That is kernel 6.8.0-31-generic and hstr 3.1.0 from the Ubuntu repos.

Answer 53 · 2024-05-16T12:01:30.000Z

@Dennysium it's your configuration. Compare hstr --show-configuration output with what you have in your .bashrc file.

Answer 54 · 2024-05-16T12:58:08.000Z

@Dennysium it's your configuration. Compare hstr --show-configuration output with what you have in your .bashrc file.

Thank you. I have appended the hstr --show-configuration output to my .bashrc, but still having the problem.

Answer 55 · 2024-05-21T10:38:47.000Z

I have updated a second pc to Ubuntu 24.04 (This is a Kubuntu machine). I have appended the output of hstr --show-configuration to my .bashrc file and run source ~/.bashrc. I have the described problem.

Answer 56 · 2024-05-21T13:37:29.000Z

The NO_TIOCSTI issues were fixed with hstr 3.1.0. There's no problem with hstr on Ubuntu 24.04 for me. If it doesn't work for you, your configuration is wrong. Did you scrub the old configuration? It only works with bash or zsh.

Answer 57 · 2024-05-22T10:40:08.000Z

@jakedane
Thank you for the clarification.
I run bash, this is my bashrc. The latter part is what I appended from hstrt --show-configuration:

 # ~/.bashrc: executed by bash(1) for non-login shells.
 # see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)
 # for examples
 
 # If not running interactively, don't do anything
 case $- in
     *i*) ;;
       *) return;;
 esac
 
 # don't put duplicate lines or lines starting with space in the history.
 # See bash(1) for more options
 #HISTCONTROL=ignoreboth
 
 # append to the history file, don't overwrite it
 shopt -s histappend
 
 # for setting history length see HISTSIZE and HISTFILESIZE in bash(1)
 #HISTSIZE=1000
 #HISTFILESIZE=2000
 
 # check the window size after each command and, if necessary,
 # update the values of LINES and COLUMNS.
 shopt -s checkwinsize
 
 # If set, the pattern "**" used in a pathname expansion context will
 # match all files and zero or more directories and subdirectories.
 #shopt -s globstar
 
 # make less more friendly for non-text input files, see lesspipe(1)
 [ -x /usr/bin/lesspipe ] && eval "$(SHELL=/bin/sh lesspipe)"
 
 # set variable identifying the chroot you work in (used in the prompt below)
 if [ -z "${debian_chroot:-}" ] && [ -r /etc/debian_chroot ]; then
     debian_chroot=$(cat /etc/debian_chroot)
 fi
 
 # set a fancy prompt (non-color, unless we know we "want" color)
 case "$TERM" in
     xterm-color|*-256color) color_prompt=yes;;
 esac
 
 # uncomment for a colored prompt, if the terminal has the capability; turned
 # off by default to not distract the user: the focus in a terminal window
 # should be on the output of commands, not on the prompt
 #force_color_prompt=yes
 
 if [ -n "$force_color_prompt" ]; then
     if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then
 	# We have color support; assume it's compliant with Ecma-48
 	# (ISO/IEC-6429). (Lack of such support is extremely rare, and such
 	# a case would tend to support setf rather than setaf.)
 	color_prompt=yes
     else
 	color_prompt=
     fi
 fi
 
 if [ "$color_prompt" = yes ]; then
     PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ '
 else
     PS1='${debian_chroot:+($debian_chroot)}\u@\h:\w\$ '
 fi
 unset color_prompt force_color_prompt
 
 # If this is an xterm set the title to user@host:dir
 case "$TERM" in
 xterm*|rxvt*)
     PS1="\[\e]0;${debian_chroot:+($debian_chroot)}\u@\h: \w\a\]$PS1"
     ;;
 *)
     ;;
 esac
 
 # enable color support of ls and also add handy aliases
 if [ -x /usr/bin/dircolors ]; then
     test -r ~/.dircolors && eval "$(dircolors -b ~/.dircolors)" || eval "$(dircolors -b)"
     alias ls='ls --color=auto'
     #alias dir='dir --color=auto'
     #alias vdir='vdir --color=auto'
 
     alias grep='grep --color=auto'
     alias fgrep='fgrep --color=auto'
     alias egrep='egrep --color=auto'
 fi
 
 # colored GCC warnings and errors
 #export GCC_COLORS='error=01;31:warning=01;35:note=01;36:caret=01;32:locus=01:quote=01'
 
 # some more ls aliases
 alias ll='ls -alF'
 alias la='ls -A'
 alias l='ls -CF'
 
 # Add an "alert" alias for long running commands.  Use like so:
 #   sleep 10; alert
 alias alert='notify-send --urgency=low -i "$([ $? = 0 ] && echo terminal || echo error)" "$(history|tail -n1|sed -e '\''s/^\s*[0-9]\+\s*//;s/[;&|]\s*alert$//'\'')"'
 
 # Alias definitions.
 # You may want to put all your additions into a separate file like
 # ~/.bash_aliases, instead of adding them here directly.
 # See /usr/share/doc/bash-doc/examples in the bash-doc package.
 
 if [ -f ~/.bash_aliases ]; then
     . ~/.bash_aliases
 fi
 
 # enable programmable completion features (you don't need to enable
 # this, if it's already enabled in /etc/bash.bashrc and /etc/profile
 # sources /etc/bash.bashrc).
 if ! shopt -oq posix; then
   if [ -f /usr/share/bash-completion/bash_completion ]; then
     . /usr/share/bash-completion/bash_completion
   elif [ -f /etc/bash_completion ]; then
     . /etc/bash_completion
   fi
 fi
 #My custom aliases
 alias libreoffice="flatpak run org.libreoffice.LibreOffice/x86_64/stable"
 
 
 # HSTR configuration - add this to ~/.bashrc
 alias hh=hstr                    # hh to be alias for hstr
 export HSTR_CONFIG=hicolor       # get more colors
 shopt -s histappend              # append new history items to .bash_history
 export HISTCONTROL=ignorespace   # leading space hides commands from history
 export HISTFILESIZE=10000        # increase history file size (default is 500)
 export HISTSIZE=${HISTFILESIZE}  # increase history size (default is 500)
 # ensure synchronization between bash memory and history file
 export PROMPT_COMMAND="history -a; history -n; ${PROMPT_COMMAND}"
 function hstrnotiocsti {
     { READLINE_LINE="$( { </dev/tty hstr ${READLINE_LINE}; } 2>&1 1>&3 3>&- )"; } 3>&1;
     READLINE_POINT=${#READLINE_LINE}
 }
 # if this is interactive shell, then bind hstr to Ctrl-r (for Vi mode check doc)
 if [[ $- =~ .*i.* ]]; then bind -x '"\C-r": "hstrnotiocsti"'; fi
 export HSTR_TIOCSTI=n

Answer 58 · 2024-05-22T12:04:50.000Z

Just one more important note:
Whe I use Ctrl + R ton invoke hstr, it works as expected. It does not work with hstr searchterm

Answer 59 · 2024-06-17T14:32:23.000Z

On Linux DEVICE_NAME 6.9.4-artix1-1 #1 SMP PREEMPT_DYNAMIC Wed, 12 Jun 2024 21:17:50 +0000 x86_64 GNU/Linux, hstr behaves as I would expect with the following in my .bashrc:

if [ "${NO_HH}" != "true" ] && [[ $- =~ .*i.* ]]; then
	# hh / hstr configuration (https://github.com/dvorka/hstr/)
	export HSTR_CONFIG=hicolor	# get more colors
	
	hstr_loc="";
	if which hh >/dev/null 2>&1; then
		hstr_loc="hh";
	elif which hstr >/dev/null 2>&1; then
		hstr_loc="hstr";
	fi
	
	hstr_mode="$($hstr_loc --is-tiocsti)";
	
	if [[ "${hstr_mode}" == "n" ]]; then
		# erk, no tiocsti available.
		function hstrnotiocsti {
			{ READLINE_LINE="$( { </dev/tty ${hstr_loc} ${READLINE_LINE}; } 2>&1 1>&3 3>&- )"; } 3>&1;
			READLINE_POINT=${#READLINE_LINE}
		}
		# if this is interactive shell, then bind hstr to Ctrl-r (for Vi mode check doc)
		if [[ $- =~ .*i.* ]]; then bind -x '"\C-r": "hstrnotiocsti"'; fi
		export HSTR_TIOCSTI=n

	else
		# tiocsti is enabled, bind as normal
		bind '"\C-r": "\C-a '"${hstr_loc}"' \C-j"';
	fi
	
	unset hstr_mode
	unset hstr_loc
fi

....in other words, hstr puts the command you select into the command prompt for you to review, and then hitting enter again will execute the command.

....if you are like me and have a version-controlled bin and .bashrc, then this may be useful if you simultaneously use machines with kernel versions both above and below 6.2.0.

Edit: it's mysteriously stopped working today. Investigating.

Answer 60 · 2024-06-30T13:42:11.000Z

For the record, it does not work with kernel 6.9.3-76060903-generic and zsh either. My .zshrc file has the same contents as in hstr --show-configuration.

Answer 61 · 2024-07-18T08:06:40.000Z

July 18, 2024

Kernel version: 6.8.0-38-generic
hstr version: 3.1.0 (2023-04-18T08:50:00)
I have placed hstr --show-configuration in my ~/.zshrc file.

It still doesn't work. The command is just printed but not executed (it worked on earlier versions of Linux).

Answer 62 · 2024-08-13T17:41:20.000Z

Same issue here: command is echoed, not executed.

Mint 22, using bash
Kernel version: 6.8.0-40-generic #40-Ubuntu SMP PREEMPT_DYNAMIC
hstr version: "3.1.0" (2023-04-18T08:50:00)

hstr --show-configuration contents are appended to ~/.bashrc

It works from a root prompt ( sudo -i ) but not as regular user.

Answer 63 · 2024-09-05T10:29:26.000Z

Same behavior for me (commands are echo'd but not executed):

uname -r
6.10.7-arch1-1

ZSH shell.

Is there any workaround for this problem?

Edit: ok this seems to work: #452 (comment)