[DRE-maint] Bug#995115: /usr/bin/ruby: symbol lookup error: /lib/x86_64-linux-gnu/libruby-2.7.so.2.7: undefined symbol: rb_st_numhash

[Francesco Poli]

Control: reassign -1 libruby2.7


On Sun, 26 Sep 2021 20:46:50 +0200 David Kalnischkies wrote:

[...]
> > 274 upgraded, 6 newly installed, 0 to remove and 0 not upgraded.
> > Need to get 0 B/745 MB of archives.
> > After this operation, 313 MB of additional disk space will be used.
> > Do you want to continue? [Y/n]
> > /usr/bin/ruby: symbol lookup error: /lib/x86_64-linux-gnu/libruby-2.7.so.2.7: undefined symbol: rb_st_numhash
> > E: Sub-process /usr/bin/apt-listbugs apt returned an error code (127)
> > E: Failure running script /usr/bin/apt-listbugs apt
> 
> The script exits unsuccessfully and as such the action is stopped.
> apt hence works as intended, it is "just" not intended that the scripts
> called do crash in such ways, but that is the bug of those scripts or
> their interpreters not of apt itself.

Hello xiscu,
I am the maintainer of apt-listbugs (thanks to David for reassigning
the bug report!).

As David explained, apt exits with errors, because apt-listbugs fails
to run.
But, from what I see, it seems that apt-listbugs fails to run, because
ruby (the interpreter for the programming language apt-listbugs is
written in) crashes with an undefined symbol error in its library
(libruby-2.7.so.27).

Hence, what you should do is understand why ruby crashes on your system.

Personally, I am unable to reproduce the crash: on my Debian testing
boxes, ruby (and apt-listbugs) works without any issues. I have also
tried on an up-to-date Debian unstable system, but it works there, as
well.

> 
> 
> > trying to deinstall apt-listbugs results on the same problem.

Trying to remove apt-listbugs using apt (or aptitude) will result in
another attempt to automatically run apt-listbugs (before it is
actually removed!), and hence, no luck!

But you can temporarily disable apt-listbugs, by editing file
'/etc/apt/apt.conf.d/10apt-listbugs' . Inside this file, you may
modify the following line:

  DPkg::Pre-Install-Pkgs {"/usr/bin/apt-listbugs apt";};

by prepending it with a comment symbol, so that it becomes:

  // DPkg::Pre-Install-Pkgs {"/usr/bin/apt-listbugs apt";};


That way, apt-listbugs will not run and you will (hopefully) be able to
use apt to fix your system.
Once your system is fixed, you should be able to run ruby programs
without any crash.
You may try to run apt-listbugs as your regular user:

  $ apt-listbugs -v
  0.1.35

When it works, without any crash, you may re-enable its automatic
invocation by apt (by reverting the above change to
'/etc/apt/apt.conf.d/10apt-listbugs').

I hope this is clear enough.

[...]
> Seems like a ruby upgrade broke it
[...]

It definitely seems that the problem is in ruby.
I am hence reassigning to libruby2.7 .

Bye!


-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
..................................................... Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-ruby-extras-maintainers/attachments/20210927/abe40189/attachment-0001.sig>