When I try to run `w`, I get this error:
/usr/local/bin/.libs/w: error while loading shared libraries: libproc2.so.1: cannot open shared object file: No such file or directory
It's not a big deal, but it used to work just fine. In the meanwhile, I'll use `who` instead.
I confirm the error.
Running "locate libproc2.so.1" returns nothing, so the file is not present on the system. Funnily, it's not present on my Mint install, either.
I ran these commands on tilde.club:
rdlmda@tilde:~$ which w /usr/local/bin/w rdlmda@tilde:~$ ldd /usr/local/bin/w not a dynamic executable
If it's not a dynamic executable, I'm not sure why it's complaining about the lack of a .so system file.
The results on my system are different:
~$ which w /usr/bin/w ~$ ldd /usr/bin/w linux-vdso.so.1 (0x000077c65cc4d000) libproc2.so.0 => /lib/x86_64-linux-gnu/libproc2.so.0 (0x000077c65cbf6000) libsystemd.so.0 => /lib/x86_64-linux-gnu/libsystemd.so.0 (0x000077c65cb16000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x000077c65c800000) /lib64/ld-linux-x86-64.so.2 (0x000077c65cc4f000) libcap.so.2 => /lib/x86_64-linux-gnu/libcap.so.2 (0x000077c65cb09000) libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20 (0x000077c65c6b8000) liblz4.so.1 => /lib/x86_64-linux-gnu/liblz4.so.1 (0x000077c65cae5000) liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x000077c65cab3000) libzstd.so.1 => /lib/x86_64-linux-gnu/libzstd.so.1 (0x000077c65c5fe000) libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 (0x000077c65ca8e000)
On Mon, 8 Jun 2026, gg--- via tildeclub wrote:
When I try to run `w`, I get this error:
/usr/local/bin/.libs/w: error while loading shared libraries: libproc2.so.1: cannot open shared object file: No such file or directory
It's not a big deal, but it used to work just fine. In the meanwhile, I'll use `who` instead.
I would check paths your user might have in .bashrc file or related. w works as normal from my user.
If you want me to login to your user and do some checking let me know and I will take a look.
Thanks ~deepend
On Jun 12, 2026, at 1:54 PM, rdlmda via tildeclub tildeclub@lists.tildeverse.org wrote:
I confirm the error.
Running "locate libproc2.so.1" returns nothing, so the file is not present on the system. Funnily, it's not present on my Mint install, either.
I ran these commands on tilde.club:
rdlmda@tilde:~$ which w /usr/local/bin/w rdlmda@tilde:~$ ldd /usr/local/bin/w not a dynamic executable
If it's not a dynamic executable, I'm not sure why it's complaining about the lack of a .so system file.
The results on my system are different:
~$ which w /usr/bin/w ~$ ldd /usr/bin/w linux-vdso.so.1 (0x000077c65cc4d000) libproc2.so.0 => /lib/x86_64-linux-gnu/libproc2.so.0 (0x000077c65cbf6000) libsystemd.so.0 => /lib/x86_64-linux-gnu/libsystemd.so.0 (0x000077c65cb16000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x000077c65c800000) /lib64/ld-linux-x86-64.so.2 (0x000077c65cc4f000) libcap.so.2 => /lib/x86_64-linux-gnu/libcap.so.2 (0x000077c65cb09000) libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20 (0x000077c65c6b8000) liblz4.so.1 => /lib/x86_64-linux-gnu/liblz4.so.1 (0x000077c65cae5000) liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x000077c65cab3000) libzstd.so.1 => /lib/x86_64-linux-gnu/libzstd.so.1 (0x000077c65c5fe000) libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 (0x000077c65ca8e000)
On Mon, 8 Jun 2026, gg--- via tildeclub wrote:
When I try to run `w`, I get this error:
/usr/local/bin/.libs/w: error while loading shared libraries: libproc2.so.1: cannot open shared object file: No such file or directory
It's not a big deal, but it used to work just fine. In the meanwhile, I'll use `who` instead.
On 2026-06-13 04:00 ICT, deepend via tildeclub wrote:
I would check paths your user might have in .bashrc file or related. w works as normal from my user.
I had a vague and quite possibly mistaken idea that /usr/local/bin typically precedes /usr/bin in $PATH, so that locally installed programs take precedence over their distribution-supplied counterparts?
I am unable to run w as well, it says I'm missing the same library.
On Sat, Jun 13, 2026 at 04:56:48PM +0700, barnold--- via tildeclub wrote:
On 2026-06-13 04:00 ICT, deepend via tildeclub wrote:
I would check paths your user might have in .bashrc file or related. w works as normal from my user.
I had a vague and quite possibly mistaken idea that /usr/local/bin typically precedes /usr/bin in $PATH, so that locally installed programs take precedence over their distribution-supplied counterparts? -- barnold HCMC 16:46 ICT ► 30.9°C ◆ Clouds ◆ 12Km/h SSE ◆ 65% RH
I am unable to run w as well, it says I'm missing the same library.
I see the same, with the default PATH env for tilde.club
bcc@tilde:~$ env -i bash -c 'echo $PATH' /usr/local/bin:/usr/bin
bcc@tilde:~$ grep -r PATH . ./.bash_profile:PATH=$PATH:$HOME/bin ./.bash_profile:export PATH
bcc@tilde:~$ echo $PATH /usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/home/bcc/.composer/vendor/bin:/home/bcc/.dotnet/tools:/home/bcc/bin
The extra ones are coming from /etc/profile.d
/usr/local/bin/w (the first for me with the standard path) is broken:
bcc@tilde:~$ which w /usr/local/bin/w bcc@tilde:~$ w /usr/local/bin/.libs/w: error while loading shared libraries: libproc2.so.1: cannot open shared object file: No such file or directory
But the system one in /usr/bin is fine:
bcc@tilde:~$ /usr/bin/w 13:13:59 up 18:55, 55 users, load average: 1.36, 3.15, 3.50 USER TTY LOGIN@ IDLE JCPU PCPU WHAT bcc pts/38 13:09 7.00s 0.21s 0.03s /usr/bin/w ...
Ben
On Mon, 8 Jun 2026, gg--- via tildeclub wrote:
When I try to run `w`, I get this error:
/usr/local/bin/.libs/w: error while loading shared libraries: libproc2.so.1: cannot open shared object file: No such file or directory
It's not a big deal, but it used to work just fine. In the meanwhile, I'll use `who` instead.
You may also run `/usr/bin/w` directly as a workaround, which works. Also, you may set this one as a default for your user, by symlinking it into your `~/bin/` directory, using Bourne shell command like this:
mkdir -p ~/bin && ln -s /usr/bin/w ~/bin/w
Logout, then re-login; and `w` on your shell should now work.
Regards, ~xwindows
tildeclub@lists.tildeverse.org
-
barnold＠tilde.club -
Ben Charlton -
deepend -
ecjonas＠tilde.club -
gg＠tilde.club -
rdlmda -
xwindows