Executables in /usr/bin have changed to shared libraries & won't start

browser · 03-26-2017, 05:56 AM

I am using a debian based distro & somewhere & somehow a lot of my executables in /usr/bin & other places including my portable apps have had their "TYPE" changed from executable to "shared library" so that the apps will not startup by double clicking on them or even by linking, but will start if I use the terminal.
For example if I use a WindowManager like fluxbox & I want nm-applet to appear on the panel by double clicking /usr/bin/nm-applet that it will not start because its type has changed to a shared library.
AnyOne know how I could change them back to being an executable?
I have tried using different file managers to change them by opening up there Properties but none will let to change.

Thanks AnyOne

browser · 03-26-2017, 06:18 AM

When I click on a files Properties when using Krusader for example there is a option that allows you to change the files type,But when I click on this option it refuses to open.
So I do not know what else to do.

frankbell · 03-26-2017, 08:26 PM

Are you running krusader as root? You would likely need to in order the change a file's type.

I would be inclined to do this, as root, for testing purposes:

Open a terminal,
cd to /usr/bin
Run the file command on several of the affected files (assuming the file command still works).

Here's a sample output of the the file command:

Code:

# file nautilus
nautilus: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.32, BuildID[sha1]=8dc3c48c8f4bd2fb85914638cf6edb2d9a7ecc70, stripped

Post the output(s) of the command here, being sure to surround it with code tags, which become available when you click the "Go Advanced" button beneath the "Compose Post" windows.

More troubling is how this came to be. Frankly, this is a new one on me, but I'm concerned it could indicate corruption or compromise of the system. Maybe someone more knowledgeable than I will notice this thread.

ondoho · 03-27-2017, 01:33 AM

this is a problem with your file manager and not the executables themselves.

so you are starting them by
a) opening a file manager
b) go to e.g. /usr/bin
c) double-click on the executable?

i've never heard of anyone doing it like that.
my only suggestion is to change your usage habits, use an app menu for gui apps (*) and the command line for command line apps.

(*) have you tried dmenu, esp. dmenu_run?