Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Not sending signal to selected process from signals dialog #641

Open
omnivagant opened this issue Oct 6, 2023 · 0 comments
Open
Assignees
Labels
bug Something isn't working

Comments

@omnivagant
Copy link

From the signals dialog, btop seems to send chosen signal to other process than the one mentioned by PID and name in top of the signals dialog.

To Reproduce

  1. Create some activity in a process so that it end up in the top of the process list
  2. Select the process and open the signals dialog
  3. Choose a signal and send it, 9 is easy to spot

Most often this has killed btop itself, my suspicion is that btop act on the current top process and not the one you thought you selected, whose PID and name is printed in the top of the signals dialog.

I have not been able to reproduce this when filtering processes.

Expected behavior

The signal should be sent to the process presented in the top of the signals dialog.

Info (please complete the following information):

  • btop version: 1.2.13
  • /usr/bin/btop: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib/ld-musl-x86_64.so.1, stripped
  • Linux 6.1.55-1-lts Fix documentation of --utf-force in README and --help. #2-Alpine SMP PREEMPT_DYNAMIC Thu, 28 Sep 2023 12:30:10 +0000 x86_64
@omnivagant omnivagant added the bug Something isn't working label Oct 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants