Starting htop from konsole vs launcher acts different - Slackware 15.0 KDE
0
votes
0
answers
19
views
I want to ask mostly out of curiosity to understand, what detail can have impact on behavior of htop program (or any other in the future) in following case. By default I had htop v3.1 installed, but because it doesn't allow to monitor I/O statistics, I've decided to download newer version "dedicated" for Slackware Current, which is v3.4. I could install it without any issue, however I've noticed one thing. When I launch it from the Application Launcher, everything works fine, however when I open Konsole first, then execute htop no matter if I'm logged in as an user or root, I can't press F1 or F2 - for example to enter setting (normally F2) I need to press F4.
When investigating shortcut in the Launcher I see it points to
/usr/local/share/applications/htop.desktop
config file, however I can't see inside any parameters that could have impact on that.
Another difference I can only see is that when I launch htop in the same time from both the Launcher and explicitly in Konsole, first instance have in "Command" column kind of 2x processes /usr/bin/konsole -qwindowtitle Htop -qwindowicon htop -e /usr/local/bin/htop
and /usr/local/bin/htop
. For the other method there is only htop
.
When I open Konsole first and try starting by typing `/usr/local/bin/htop', then F keys are also mixed / not working correctly.
Any ideas what is the source of this?
Asked by Jacob
(1 rep)
Mar 24, 2025, 07:54 PM