This update has been unpushed.
This update has been unpushed.
@ciupicri You reported those errors against nodejs20-20.11.1-3.fc40, but provided negative karma against 20.12.0. Can you please re-test with 20.12.0? I can't reproduce the issue you're seeing on either version (on either x86_64 or aarch64 architectures).
The updated tracker-miners package appears to have resolved the crash-loop for me. Thanks!
The tracker-miners package is in a permanent SIGSYS crash-loop:
coredumpctl info
PID: 27879 (tracker-extract)
UID: 1000 (sgallagh)
GID: 1000 (sgallagh)
Signal: 31 (SYS)
Timestamp: Mon 2024-03-25 08:53:42 EDT (2min 24s ago)
Command Line: /usr/libexec/tracker-extract-3 --socket-fd 3
Executable: /usr/libexec/tracker-extract-3
Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/tracker-miner-fs-3.service
Unit: user@1000.service
User Unit: tracker-miner-fs-3.service
Slice: user-1000.slice
Owner UID: 1000 (sgallagh)
Boot ID: 88912d5941f74c9eb5c6415cb5266fd0
Machine ID: d1bc453d65eb41d687b54efb2b2c05fe
Hostname: emerginghell.pineridge.gallagherhome.com
Storage: /var/lib/systemd/coredump/core.tracker-extract.1000.88912d5941f74c9eb5c6415cb5266fd0.27879.1711371222000000.zst (present)
Size on Disk: 298.3K
Package: tracker-miners/3.7.0-1.fc40
build-id: 3f975e793c3b012160aedc3135559e29c78a2319
Message: Process 27879 (tracker-extract) of user 1000 dumped core.
Module libgvfscommon.so from rpm gvfs-1.54.0-2.fc40.aarch64
Module libgvfsdbus.so from rpm gvfs-1.54.0-2.fc40.aarch64
Module libicudata.so.74 from rpm icu-74.2-1.fc40.aarch64
Module liblzma.so.5 from rpm xz-5.6.0-3.fc40.aarch64
Module libexpat.so.1 from rpm expat-2.6.2-1.fc40.aarch64
Module libicuuc.so.74 from rpm icu-74.2-1.fc40.aarch64
Module libbz2.so.1 from rpm bzip2-1.0.8-18.fc40.aarch64
Module libxml2.so.2 from rpm libxml2-2.12.5-1.fc40.aarch64
Module libjson-glib-1.0.so.0 from rpm json-glib-1.8.0-3.fc40.aarch64
Module libffi.so.8 from rpm libffi-3.4.4-7.fc40.aarch64
Module libselinux.so.1 from rpm libselinux-3.6-4.fc40.aarch64
Module libmount.so.1 from rpm util-linux-2.40-0.9.rc1.fc40.aarch64
Module libz.so.1 from rpm zlib-ng-2.1.6-2.fc40.aarch64
Module libpcre2-8.so.0 from rpm pcre2-10.42-2.fc40.2.aarch64
Module libiptcdata.so.0 from rpm libiptcdata-1.0.5-17.fc40.aarch64
Module libexif.so.12 from rpm libexif-0.6.24-7.fc40.aarch64
Module libexempi.so.8 from rpm exempi-2.6.4-5.fc40.aarch64
Module libicui18n.so.74 from rpm icu-74.2-1.fc40.aarch64
Module libseccomp.so.2 from rpm libseccomp-2.5.3-8.fc40.aarch64
Module libblkid.so.1 from rpm util-linux-2.40-0.9.rc1.fc40.aarch64
Module libgsf-1.so.114 from rpm libgsf-1.14.51-4.fc40.aarch64
Module libgmodule-2.0.so.0 from rpm glib2-2.80.0-1.fc40.aarch64
Module libtracker-sparql-3.0.so.0 from rpm tracker-3.7.0-1.fc40.aarch64
Module libgobject-2.0.so.0 from rpm glib2-2.80.0-1.fc40.aarch64
Module libgio-2.0.so.0 from rpm glib2-2.80.0-1.fc40.aarch64
Module libglib-2.0.so.0 from rpm glib2-2.80.0-1.fc40.aarch64
Module libtracker-extract.so from rpm tracker-miners-3.7.0-1.fc40.aarch64
Module tracker-extract-3 from rpm tracker-miners-3.7.0-1.fc40.aarch64
Stack trace of thread 27882:
#0 0x0000ffffbba214d0 epoll_pwait (libc.so.6 + 0x1014d0)
#1 0x000bffffbb13d0d4 n/a (n/a + 0x0)
#2 0x000bffffbb13d0d4 n/a (n/a + 0x0)
#3 0x0064ffffbb13dab8 n/a (n/a + 0x0)
#4 0x0066ffffbbee46f8 n/a (n/a + 0x0)
#5 0x0003ffffbbe51d08 n/a (n/a + 0x0)
#6 0x006effffbc157594 n/a (n/a + 0x0)
#7 0x0078ffffbc150994 n/a (n/a + 0x0)
#8 0x003dffffbc1b5898 n/a (n/a + 0x0)
#9 0x006bffffbc152064 n/a (n/a + 0x0)
#10 0x007dffffbc1520cc n/a (n/a + 0x0)
#11 0x003bffffbc18243c n/a (n/a + 0x0)
#12 0x0070ffffbb9b5e38 n/a (n/a + 0x0)
#13 0x007dffffbba2118c n/a (n/a + 0x0)
ELF object binary architecture: AARCH64
This works fine with platform-python.
This update has been unpushed.
This update has been unpushed.
Content Resolver was broken until a short time ago. It'll still need a few hours to catch up.
Once it does, tecla will automatically be added to the set of packages that will be auto-built for ELN. However, for expediency I've gone ahead and kicked off a build manually.
The segfault on Node.js 20 should be fixed now. Please re-test.
This update has been unpushed.
This update has been unpushed.
This update has been unpushed.
They can't coexist because they put different files in the same place (/usr/include/node
). They have to explicitly conflict in that case.