[Solved] Segmentation fault during slapt-get -u

[Papasot]

After yesterday's (20 April 2021) system update I get this every time I try to update again:

Code: Select all

Retrieving package data [http://www.slackel.gr/repo/i486/slackware-current/]...Cached
Retrieving patch list [http://www.slackel.gr/repo/i486/slackware-current/]...Cached
Retrieving checksum list [http://www.slackel.gr/repo/i486/slackware-current/]...Cached
Retrieving checksum signature [http://www.slackel.gr/repo/i486/slackware-current/]...Cached
Verifying checksum signature [http://www.slackel.gr/repo/i486/slackware-current/]...Segmentation fault

Yesterday's update itsef went well as usual, but after that I just can't update again. The problem is present in both 32- and 64-bit installations. At first I thought it was a sourcefourge issue, but that "segmentation fault" is unusual. slapt-get --add-keys won't work either.

[djemos]

Yes, i know.
Type

Code: Select all

sudo slapt-get -i icu4c-69.1-x86_64-1

for 32 bit

Code: Select all

sudo slapt-get -i icu4c-69.1-i586-1

Then

Code: Select all

sudo slapt-get -u
sudo slapt-get --upgrade

[Papasot]

Solved. I looked up at Slackware-Current change logs before posting here, but it wasn't clear icu4c was the problem.
Thank you Dimitri!

[djemos]

Another error only on 32bit
if gnupg2 is installed slapt-get -u segfaults
So for now i had to uninstall gnupg2 to be able to upgrade the system.
It is really strange if gnupg2 is installed
running

Code: Select all

sudo gdb slapt-get

then type

Code: Select all

run --update

i get

Code: Select all

Program received signal SIGPIPE, Broken pipe.
0xb795d637 in write () from /lib/libc.so.6
(gdb) 

[Papasot]

Another error only on 32bit
if gnupg2 is installed slapt-get -u segfaults
So for now i had to uninstall gnupg2 to be able to upgrade the system.
It is really strange if gnupg2 is installed
running

Code: Select all

sudo gdb slapt-get

then type

Code: Select all

run --update

i get

Code: Select all

Program received signal SIGPIPE, Broken pipe.
0xb795d637 in write () from /lib/libc.so.6
(gdb) 

This is weird... I don't have this problem in my long-standing 32-bit installation. gnupg2 is installed (specifically, 2.2.27-i586-3), and I don't have this problem. I update/upgrade the system without issues. Debugging with gdb doesn't reveal any problem during run --update or run --upgrade either.

[djemos]

So, it has to do with my slackel-32 bit in virtual box installed.
This is good since it happens only to me and not affect slackel 32 bit in general.