[arch-general] Weird program in $PATH
Hey everyone, today I tried to launch firefox from my awesome-wm launcher and instead of being offered firefox after typing fire, the prompt finished showing me alternatives and being a little lazy I just pushed enter. This gave me a window with some fire particle animations running on my screen. Searching for the program in my pacman.log did not show me anything so I'm wondering where this program comes from. Can anyone of you maybe help me to at least get this thing removed without having any files left that are only used by this program? Best regards, Heiko
On 19/08/14 16:32, Heiko Becker wrote:
Hey everyone,
today I tried to launch firefox from my awesome-wm launcher and instead of being offered firefox after typing fire, the prompt finished showing me alternatives and being a little lazy I just pushed enter. This gave me a window with some fire particle animations running on my screen.
Searching for the program in my pacman.log did not show me anything so I'm wondering where this program comes from. Can anyone of you maybe help me to at least get this thing removed without having any files left that are only used by this program?
Best regards,
Heiko
pacman -Ss aalib extra/aalib 1.4rc5-10 [installed] A portable ASCII art graphic library This gives you the aafire program, as well as aainfo, aasavefont and aatest, which demonstrate the capabilities of the aalib ASCII art library. Regards, Gurnaik
Searching for the program in my pacman.log did not show me anything so I'm wondering where this program comes from. Can anyone of you maybe help me to at least get this thing removed without having any files left that are only used by this program?
You can find the absolute path to the program by running something like $ which your_fire_program then you can determine which package owns it. $ pacman -Qo `which your_file_program` Then you can decide if you want to remove that package. If the file isn't owned by any package then it is probably something you installed yourself at some point in time. HTH
Hello everyone, thanks for the fast responses.
You can find the absolute path to the program by running something like
$ which your_fire_program This gave me /usr/bin/fire
then you can determine which package owns it.
$ pacman -Qo `which your_file_program`
And this finally gave me the mesa-demos package, which I maybe installed accidentally... So I could solve my problem. Thanks a lot. Best, Heiko
participants (3)
-
Delcypher
-
gurnaik
-
Heiko Becker