[gentoo-user] emerge segfault

[gentoo-user] emerge segfault

[Daniel Frey]

I came across a strange problem today. I am updating several machines 
and three machines developed this strange emerge issue:

Would you like to merge these packages? [Yes/No] yes
 >>> Verifying ebuild manifests
 >>> Running pre-merge checks for sys-libs/libxcrypt-4.4.38
Segmentation fault (core dumped)


I cannot do anything with emerge. It will still calculate dependencies 
but as soon as it goes to do pre-merge checks or actually build a 
package it segfaults.

I have a hard time believing this to be a hardware or memory fault as it 
appeared on three separate machines while upgrading.

Could this be a python upgrade failure?

-Dan

Re: [gentoo-user] emerge segfault

[Javier Martinez]

[-- Attachment #1.1.1: Type: text/plain, Size: 901 bytes --]

El 23/9/25 a las 0:02, Daniel Frey escribió:
> I came across a strange problem today. I am updating several machines 
> and three machines developed this strange emerge issue:
> 
> Would you like to merge these packages? [Yes/No] yes
>  >>> Verifying ebuild manifests
>  >>> Running pre-merge checks for sys-libs/libxcrypt-4.4.38
> Segmentation fault (core dumped)
> 
> 
> I cannot do anything with emerge. It will still calculate dependencies 
> but as soon as it goes to do pre-merge checks or actually build a 
> package it segfaults.
> 
> I have a hard time believing this to be a hardware or memory fault as it 
> appeared on three separate machines while upgrading.
> 
> Could this be a python upgrade failure?
> 
> -Dan
> 

Can you please post the last lines of the file /tmp/straceoutput 
resulting of the command:

strace -f -o /tmp/straceoutput emerge blablabla??

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3145 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

Re: [gentoo-user] emerge segfault

[Daniel Frey]

On 9/22/25 3:14 PM, Javier Martinez wrote:
> El 23/9/25 a las 0:02, Daniel Frey escribió:
>> I came across a strange problem today. I am updating several machines 
>> and three machines developed this strange emerge issue:
>>
>> Would you like to merge these packages? [Yes/No] yes
>>  >>> Verifying ebuild manifests
>>  >>> Running pre-merge checks for sys-libs/libxcrypt-4.4.38
>> Segmentation fault (core dumped)
>>
>>
>> I cannot do anything with emerge. It will still calculate dependencies 
>> but as soon as it goes to do pre-merge checks or actually build a 
>> package it segfaults.
>>
>> I have a hard time believing this to be a hardware or memory fault as 
>> it appeared on three separate machines while upgrading.
>>
>> Could this be a python upgrade failure?
>>
>> -Dan
>>
> 
> Can you please post the last lines of the file /tmp/straceoutput 
> resulting of the command:
> 
> strace -f -o /tmp/straceoutput emerge blablabla??

Unfortunately, that's not possible, I don't have strace and can't emerge 
anything:

# emerge strace
Calculating dependencies... done!
Dependency resolution took 0.65 s (backtrack: 0/20).


 >>> Verifying ebuild manifests

 >>> Emerging (1 of 1) dev-debug/strace-6.16::gentoo
Segmentation fault (core dumped)

Re: [gentoo-user] emerge segfault

[Javier Martinez]

[-- Attachment #1.1.1: Type: text/plain, Size: 1447 bytes --]

El 23/9/25 a las 0:19, Daniel Frey escribió:
> On 9/22/25 3:14 PM, Javier Martinez wrote:
>> El 23/9/25 a las 0:02, Daniel Frey escribió:
>>> I came across a strange problem today. I am updating several machines 
>>> and three machines developed this strange emerge issue:
>>>
>>> Would you like to merge these packages? [Yes/No] yes
>>>  >>> Verifying ebuild manifests
>>>  >>> Running pre-merge checks for sys-libs/libxcrypt-4.4.38
>>> Segmentation fault (core dumped)
>>>
>>>
>>> I cannot do anything with emerge. It will still calculate 
>>> dependencies but as soon as it goes to do pre-merge checks or 
>>> actually build a package it segfaults.
>>>
>>> I have a hard time believing this to be a hardware or memory fault as 
>>> it appeared on three separate machines while upgrading.
>>>
>>> Could this be a python upgrade failure?
>>>
>>> -Dan
>>>
>>
>> Can you please post the last lines of the file /tmp/straceoutput 
>> resulting of the command:
>>
>> strace -f -o /tmp/straceoutput emerge blablabla??
> 
> Unfortunately, that's not possible, I don't have strace and can't emerge 
> anything:
> 
> # emerge strace
> Calculating dependencies... done!
> Dependency resolution took 0.65 s (backtrack: 0/20).
> 
> 
>  >>> Verifying ebuild manifests
> 
>  >>> Emerging (1 of 1) dev-debug/strace-6.16::gentoo
> Segmentation fault (core dumped)
> 
> 
can you change python version with eselect?

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3145 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

Re: [gentoo-user] emerge segfault

[Daniel Frey]

On 9/22/25 4:12 PM, Javier Martinez wrote:
> El 23/9/25 a las 0:19, Daniel Frey escribió:
>> On 9/22/25 3:14 PM, Javier Martinez wrote:
>>> El 23/9/25 a las 0:02, Daniel Frey escribió:
>>>> I came across a strange problem today. I am updating several 
>>>> machines and three machines developed this strange emerge issue:
>>>>
>>>> Would you like to merge these packages? [Yes/No] yes
>>>>  >>> Verifying ebuild manifests
>>>>  >>> Running pre-merge checks for sys-libs/libxcrypt-4.4.38
>>>> Segmentation fault (core dumped)
>>>>
>>>>
>>>> I cannot do anything with emerge. It will still calculate 
>>>> dependencies but as soon as it goes to do pre-merge checks or 
>>>> actually build a package it segfaults.
>>>>
>>>> I have a hard time believing this to be a hardware or memory fault 
>>>> as it appeared on three separate machines while upgrading.
>>>>
>>>> Could this be a python upgrade failure?
>>>>
>>>> -Dan
>>>>
>>>
>>> Can you please post the last lines of the file /tmp/straceoutput 
>>> resulting of the command:
>>>
>>> strace -f -o /tmp/straceoutput emerge blablabla??
>>
>> Unfortunately, that's not possible, I don't have strace and can't 
>> emerge anything:
>>
>> # emerge strace
>> Calculating dependencies... done!
>> Dependency resolution took 0.65 s (backtrack: 0/20).
>>
>>
>>  >>> Verifying ebuild manifests
>>
>>  >>> Emerging (1 of 1) dev-debug/strace-6.16::gentoo
>> Segmentation fault (core dumped)
>>
>>
> can you change python version with eselect?

No - I did check that before posting. I don't have a python option in 
eselect. That is what made me think python is completely broken.

# eselect
Usage: eselect <global options> <module name> <module options>

Global options:
   --brief                   Make output shorter
   --colour=<yes|no|auto>    Enable or disable colour output (default 
'auto')
   --eprefix=<path>          Override the EPREFIX variable for a 
cross-prefix build
   --root=<path>             The target root path for eselect's operations

Built-in modules:
   help                      Display a help message
   usage                     Display a usage message
   version                   Display version information

Extra modules:
   arptables                 Manage the iptables/arptables/ebtables symlinks
   bashcomp                  Manage contributed bash-completion scripts
   binutils                  Manage installed versions of sys-devel/binutils
   compiler-shadow           Manage compiler shadow link directories 
(distcc, ccache)
   ebtables                  Manage the iptables/arptables/ebtables symlinks
   ecj                       Manage ECJ targets
   editor                    Manage the EDITOR environment variable
   env                       Manage environment variables set in /etc/env.d/
   fontconfig                Manage fontconfig /etc/fonts/conf.d symlinks
   gcc                       Manage installed versions of sys-devel/gcc
   iptables                  Manage the iptables/arptables/ebtables symlinks
   java-vm                   Manage the Java system and user VM
   kernel                    Manage the /usr/src/linux symlink
   locale                    Manage the LANG environment variable
   maven                     Manage Maven targets
   modules                   Query eselect modules
   news                      Read Gentoo ("GLEP 42") news items
   pager                     Manage the PAGER environment variable
   pinentry                  Manage /usr/bin/pinentry implementation
   profile                   Manage the make.profile symlink
   rc                        Manage /etc/init.d scripts in runlevels
   rust                      Manage the Rust compiler versions
   vi                        Manage /usr/bin/vi implementations
   visual                    Manage the VISUAL environment variable



-Dan

Re: [gentoo-user] emerge segfault

[Javier Martinez]

[-- Attachment #1.1.1: Type: text/plain, Size: 4964 bytes --]

Can you please get into /usr/lib/python-exec, find which emerge binaries 
have you there and try to exec the emerge script with another python 
interpreter as with "python3.11 ./emerge" or whatelse python versions 
you had¿?

El 23/9/25 a las 1:39, Daniel Frey escribió:
> On 9/22/25 4:12 PM, Javier Martinez wrote:
>> El 23/9/25 a las 0:19, Daniel Frey escribió:
>>> On 9/22/25 3:14 PM, Javier Martinez wrote:
>>>> El 23/9/25 a las 0:02, Daniel Frey escribió:
>>>>> I came across a strange problem today. I am updating several 
>>>>> machines and three machines developed this strange emerge issue:
>>>>>
>>>>> Would you like to merge these packages? [Yes/No] yes
>>>>>  >>> Verifying ebuild manifests
>>>>>  >>> Running pre-merge checks for sys-libs/libxcrypt-4.4.38
>>>>> Segmentation fault (core dumped)
>>>>>
>>>>>
>>>>> I cannot do anything with emerge. It will still calculate 
>>>>> dependencies but as soon as it goes to do pre-merge checks or 
>>>>> actually build a package it segfaults.
>>>>>
>>>>> I have a hard time believing this to be a hardware or memory fault 
>>>>> as it appeared on three separate machines while upgrading.
>>>>>
>>>>> Could this be a python upgrade failure?
>>>>>
>>>>> -Dan
>>>>>
>>>>
>>>> Can you please post the last lines of the file /tmp/straceoutput 
>>>> resulting of the command:
>>>>
>>>> strace -f -o /tmp/straceoutput emerge blablabla??
>>>
>>> Unfortunately, that's not possible, I don't have strace and can't 
>>> emerge anything:
>>>
>>> # emerge strace
>>> Calculating dependencies... done!
>>> Dependency resolution took 0.65 s (backtrack: 0/20).
>>>
>>>
>>>  >>> Verifying ebuild manifests
>>>
>>>  >>> Emerging (1 of 1) dev-debug/strace-6.16::gentoo
>>> Segmentation fault (core dumped)
>>>
>>>
>> can you change python version with eselect?
> 
> No - I did check that before posting. I don't have a python option in 
> eselect. That is what made me think python is completely broken.
> 
> # eselect
> Usage: eselect <global options> <module name> <module options>
> 
> Global options:
>    --brief                   Make output shorter
>    --colour=<yes|no|auto>    Enable or disable colour output (default 
> 'auto')
>    --eprefix=<path>          Override the EPREFIX variable for a cross- 
> prefix build
>    --root=<path>             The target root path for eselect's operations
> 
> Built-in modules:
>    help                      Display a help message
>    usage                     Display a usage message
>    version                   Display version information
> 
> Extra modules:
>    arptables                 Manage the iptables/arptables/ebtables 
> symlinks
>    bashcomp                  Manage contributed bash-completion scripts
>    binutils                  Manage installed versions of sys-devel/ 
> binutils
>    compiler-shadow           Manage compiler shadow link directories 
> (distcc, ccache)
>    ebtables                  Manage the iptables/arptables/ebtables 
> symlinks
>    ecj                       Manage ECJ targets
>    editor                    Manage the EDITOR environment variable
>    env                       Manage environment variables set in /etc/ 
> env.d/
>    fontconfig                Manage fontconfig /etc/fonts/conf.d symlinks
>    gcc                       Manage installed versions of sys-devel/gcc
>    iptables                  Manage the iptables/arptables/ebtables 
> symlinks
>    java-vm                   Manage the Java system and user VM
>    kernel                    Manage the /usr/src/linux symlink
>    locale                    Manage the LANG environment variable
>    maven                     Manage Maven targets
>    modules                   Query eselect modules
>    news                      Read Gentoo ("GLEP 42") news items
>    pager                     Manage the PAGER environment variable
>    pinentry                  Manage /usr/bin/pinentry implementation
>    profile                   Manage the make.profile symlink
>    rc                        Manage /etc/init.d scripts in runlevels
>    rust                      Manage the Rust compiler versions
>    vi                        Manage /usr/bin/vi implementations
>    visual                    Manage the VISUAL environment variable
> 
> 
> 
> -Dan
> 


[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3145 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

Re: [gentoo-user] emerge segfault

[Daniel Frey]

On 9/22/25 4:50 PM, Javier Martinez wrote:
> Can you please get into /usr/lib/python-exec, find which emerge binaries 
> have you there and try to exec the emerge script with another python 
> interpreter as with "python3.11 ./emerge" or whatelse python versions 
> you had¿?
> 

OK - I have python3.12 and python3.13.

Emerge doesn't work with python 3.13:

/usr/lib/python-exec/python3.13/emerge: this Python implementation 
(python3.13) is not supported by the script.

It segfaults with 3.12.

-Dan

Re: [gentoo-user] emerge segfault

[Javier Martinez]

[-- Attachment #1.1.1: Type: text/plain, Size: 692 bytes --]

El 23/9/25 a las 2:07, Daniel Frey escribió:
> On 9/22/25 4:50 PM, Javier Martinez wrote:
>> Can you please get into /usr/lib/python-exec, find which emerge 
>> binaries have you there and try to exec the emerge script with another 
>> python interpreter as with "python3.11 ./emerge" or whatelse python 
>> versions you had¿?
>>
> 
> OK - I have python3.12 and python3.13.
> 
> Emerge doesn't work with python 3.13:
> 
> /usr/lib/python-exec/python3.13/emerge: this Python implementation 
> (python3.13) is not supported by the script.
> 
> It segfaults with 3.12.
> 
> -Dan
> 

If you do #python3_13 /usr/lib/python-exec/python3.12/emerge is that 
what appears you?

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3145 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

Re: [gentoo-user] emerge segfault

[Daniel Frey]

On 9/22/25 6:08 PM, Javier Martinez wrote:
> El 23/9/25 a las 2:07, Daniel Frey escribió:
>> On 9/22/25 4:50 PM, Javier Martinez wrote:
>>> Can you please get into /usr/lib/python-exec, find which emerge 
>>> binaries have you there and try to exec the emerge script with 
>>> another python interpreter as with "python3.11 ./emerge" or whatelse 
>>> python versions you had¿?
>>>
>>
>> OK - I have python3.12 and python3.13.
>>
>> Emerge doesn't work with python 3.13:
>>
>> /usr/lib/python-exec/python3.13/emerge: this Python implementation 
>> (python3.13) is not supported by the script.
>>
>> It segfaults with 3.12.
>>
>> -Dan
>>
> 
> If you do #python3_13 /usr/lib/python-exec/python3.12/emerge is that 
> what appears you?

I tried invoking python 3.13 directly with emerge and it gave me the 
message.

After a lot of poking around, I think distcc did something strange and 
messed up some packages. I've restored from a stage4 backup and disabled 
distcc globally, emerge will likely be running overnight.

-Dan

Re: [gentoo-user] emerge segfault

[Javier Martinez]

[-- Attachment #1.1.1: Type: text/plain, Size: 1173 bytes --]

El 23/9/25 a las 7:36, Daniel Frey escribió:
> On 9/22/25 6:08 PM, Javier Martinez wrote:
>> El 23/9/25 a las 2:07, Daniel Frey escribió:
>>> On 9/22/25 4:50 PM, Javier Martinez wrote:
>>>> Can you please get into /usr/lib/python-exec, find which emerge 
>>>> binaries have you there and try to exec the emerge script with 
>>>> another python interpreter as with "python3.11 ./emerge" or whatelse 
>>>> python versions you had¿?
>>>>
>>>
>>> OK - I have python3.12 and python3.13.
>>>
>>> Emerge doesn't work with python 3.13:
>>>
>>> /usr/lib/python-exec/python3.13/emerge: this Python implementation 
>>> (python3.13) is not supported by the script.
>>>
>>> It segfaults with 3.12.
>>>
>>> -Dan
>>>
>>
>> If you do #python3_13 /usr/lib/python-exec/python3.12/emerge is that 
>> what appears you?
> 
> I tried invoking python 3.13 directly with emerge and it gave me the 
> message.
> 
> After a lot of poking around, I think distcc did something strange and 
> messed up some packages. I've restored from a stage4 backup and disabled 
> distcc globally, emerge will likely be running overnight.
> 
> -Dan
> 
It's really strange....

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3145 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]