Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at
Bug 2093218 - gplugin-0.37.0-2.fc37: FTBFS with Perl 5.36 on ppc64le
Summary: gplugin-0.37.0-2.fc37: FTBFS with Perl 5.36 on ppc64le
Alias: None
Product: Fedora
Classification: Fedora
Component: gplugin
Version: 37
Hardware: ppc64le
OS: Unspecified
Target Milestone: ---
Assignee: Elliott Sales de Andrade
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2022-06-03 10:23 UTC by Jitka Plesnikova
Modified: 2023-12-05 21:08 UTC (History)
2 users (show)

Fixed In Version: gplugin-0.37.0-3.fc37
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2023-12-05 21:08:02 UTC
Type: Bug

Attachments (Terms of Use)

Description Jitka Plesnikova 2022-06-03 10:23:26 UTC
I am working on adding Perl 5.36 to Fedora Rawhide/37.

The rebuild of gplugin failed with this version in side tag f37-perl:

23/23 Perl5 Loader                FAIL            0.75s   killed by signal 11 SIGSEGV
>>> MALLOC_PERTURB_=184 /builddir/build/BUILD/gplugin-0.37.0/redhat-linux-build/perl5/tests/test-perl5-loader
――――――――――――――――――――――――――――――――――――― ✀  ―――――――――――――――――――――――――――――――――――――
# random seed: R02S4b2ac4476c7f689f137c9f02d01588b0
# Start of loaders tests
# Start of perl5 tests
ok 1 /loaders/perl5/full
ok 2 /loaders/perl5/load-failed
ok 3 /loaders/perl5/load-exception
Summary of Failures:
23/23 Perl5 Loader                FAIL            0.75s   killed by signal 11 SIGSEGV
Ok:                 22  
Expected Fail:      0   
Fail:               1   
Unexpected Pass:    0   
Skipped:            0   
Timeout:            0   
Full log written to /builddir/build/BUILD/gplugin-0.37.0/redhat-linux-build/meson-logs/testlog.txt

Comment 1 Elliott Sales de Andrade 2022-07-29 23:21:03 UTC
Seems to be fine now.

Comment 2 Petr Pisar 2022-08-04 09:01:22 UTC
It still fails <>. Either it started failing again after F37 mass rebuild, or it fails randomly. The test crashes.

Comment 3 Petr Pisar 2022-08-04 10:28:07 UTC
Though I'm unable to reproduce it. Neither locally, nor in mock.

Comment 4 Ben Cotton 2022-08-09 13:38:58 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 37 development cycle.
Changing version to 37.

Comment 5 Aoife Moloney 2023-11-23 00:12:58 UTC
This message is a reminder that Fedora Linux 37 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '37'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 37 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 6 Aoife Moloney 2023-12-05 21:08:02 UTC
Fedora Linux 37 entered end-of-life (EOL) status on None.

Fedora Linux 37 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.