bl-exit not working:

devnull · 2020-02-28 13:00:26

Hello all, I'm posting a bunch I know, just trying to keep every thread separated.

Just dist-upgraded from Helium to Lithium, and `bl-exit` opens up but does nothing whatever I press.

I have the following output in a terminal:

1) Logout	  3) Hibernate	    5) Reboot	      7) Quit-Dialogue
2) Suspend	  4) Hybrid-Sleep   6) Power-Off
Please choose an option 5

reboot
systemctl: error while loading shared libraries: libsystemd-shared-232.so: cannot open shared object file: No such file or directory
loginctl: error while loading shared libraries: libsystemd-shared-232.so: cannot open shared object file: No such file or directory

Thanks!

rbh · 2020-02-28 13:23:12

devnull wrote:

Just dist-upgraded from Helium to Lithium, and `bl-exit` opens up but does nothing whatever I press.
[...]
systemctl: error while loading shared libraries: libsystemd-shared-232.so: cannot open shared object file: No such file or directory
loginctl: error while loading shared libraries: libsystemd-shared-232.so: cannot open shared object file: No such file or directory

Have you searched for the files? When I do

locate libsystemd-shared

I get the result: "/lib/systemd/libsystemd-shared-241.so"

You have done both "apt update" and "apt dist-upgrade"?

Have you tried to reinstall bl-exit?

devnull · 2020-02-28 13:29:06

Hi, thanks.

Yes, the file is there:

$ locate libsystemd-shared
/lib/systemd/libsystemd-shared-232.so

I've done both update and dist-upgrade and upgrade and everything.

I haven't thought about reinstalling bl-exit actually. I tried with apt remove bl-exit and I have a

E: Unable to locate package bl-exit

Not sure how to go from here

rbh · 2020-02-28 14:42:31

devnull wrote:

Yes, the file is there:

$ locate libsystemd-shared
/lib/systemd/libsystemd-shared-232.so

I have anoter version of libsystemd-shared. I have installed packaged systemd version 241-7~deb10u3.
If you installed from debian stable (buster), you sholud have the same version.

What's the result of "$ dpkg -l | grep systemd"

ohnonot · 2020-02-29 09:23:31

I think your newly dist-upgraded system would like to get rebooted.
Tricky when systemd itself balks, but surely not impossible?

damo · 2020-02-29 09:55:22

devnull wrote:

...
I haven't thought about reinstalling bl-exit actually. I tried with apt remove bl-exit and I have a
E: Unable to locate package bl-exit
Not sure how to go from here

The executable is bl-exit, which is provided by bunsen-exit.

Is your systemd in the right place - it should be in /usr/bin?

which systemctl

Siera_Cortney · Yesterday 08:12:57

That bit about the package name being bunsen-exit instead of bl-exit is super helpful. I think a lot of people make that mistake when trying to troubleshoot or reinstall. It’s definitely worth checking if bunsen-exit is actually marked as installed after the dist-upgrade.

johnraff · Today 07:46:19

Most of our packages are named "bunsen-something", while most commands are 'bl-something'.

It's quite common for packages to provide a number of different commands, so obviously they can't all share the package name. In Debian, though, there are many packages where the package name and command name are the same, which confuses things.

#1 2020-02-28 13:00:26

bl-exit not working:

#2 2020-02-28 13:23:12

Re: bl-exit not working:

#3 2020-02-28 13:29:06

Re: bl-exit not working:

#4 2020-02-28 14:42:31

Re: bl-exit not working:

#5 2020-02-29 09:23:31

Re: bl-exit not working:

#6 2020-02-29 09:55:22

Re: bl-exit not working:

#7 Yesterday 08:12:57

Re: bl-exit not working:

#8 Today 07:46:19

Re: bl-exit not working:

Board footer