Bugs in Archlinux32 packages, specific to 32-bit issues.

Bugs  FS#2  to  FS#92  have been recovered and may be incomplete, the
recovered Google/Bing cache data can be found here.

IDCategoryTask TypePrioritySeveritySummaryStatusProgress
133PackagesBug ReportMediumLowlibao and libpulse mixupNew
Task Description
resolving dependencies...
warning: cannot resolve "libpulse.so=0-32", a dependency of "libao"
warning: cannot resolve "libpulse-simple.so=0-32", a dependency of "libao"
:: The following package cannot be upgraded due to unresolvable dependencies:

:: Do you want to skip the above package for this upgrade? [y/N] n
error: failed to prepare transaction (could not satisfy dependencies)
:: unable to satisfy dependency 'libpulse.so=0-32' required by libao
:: unable to satisfy dependency 'libpulse-simple.so=0-32' required by libao
132PackagesBug ReportMediumLowOLPC-XO-1 kernel, usb8xx module crashingNew
Task Description
[   21.686772] usb8xxx: Firmware ready event received
[   21.717061] usb8xxx 1-1:1.0 (unnamed net_device) (uninitialized): 00:17:c4:10:e3:67, fw 5.110.22p23, cap 0x000003a3
[   21.897489] usb8xxx 1-1:1.0 wlan0: Marvell WLAN 802.11 adapter
[   22.004871] usb8xxx 1-1:1.0 wlan0: PREP_CMD: command 0x0074 failed: 2
[   22.109002] usb8xxx 1-1:1.0 wlan0: Firmware does not seem to support PS mode
[   22.217405] usb8xxx 1-1:1.0 wlan0: PREP_CMD: command 0x0043 failed: 1
[   22.318862] usb8xxx 1-1:1.0 wlan0: HOST_SLEEP_CFG failed 1
[   23.468484] usb8xxx 1-1:1.0 wlp0s15f5u1: renamed from msh0
[   43.523176] ------------[ cut here ]------------
[   43.556197] WARNING: CPU: 0 PID: 148 at net/wireless/core.c:1346 cfg80211_netdev_notifier_call+0x102/0x31e
[   43.625361] Modules linked in: input_leds led_class usb8xxx libertas serio_raw
[   43.664224] CPU: 0 PID: 148 Comm: wpa_supplicant Not tainted 5.10.5-arch1-1.0-olpc-xo1 #1
[   43.715531] Hardware name: OLPC XO/XO, BIOS OLPC Ver 1.00.01 06/11/2014
[   43.754829] EIP: cfg80211_netdev_notifier_call+0x102/0x31e
[   43.792862] Code: ff 89 f0 e8 4d fc ff ff 8b 46 7c 85 c0 74 2a 39 58 34 75 25 80 78 64 00 75 16 8b 96 80 00 00 00 85 d2 74 06 80 7a 64 00 75 06 <0f> 0b c6 40 62 01 31 d2 89 f0 e8 3d 7a 00 00 8b 86 88 00 00 00 8b
[   43.911511] EAX: c36e1d00 EBX: c2cb8800 ECX: ffffffff EDX: 00000000
[   43.958939] ESI: c341c000 EDI: c1f7d000 EBP: c1eebdd4 ESP: c1eebdbc
[   44.002464] DS: 007b ES: 007b FS: 0000 GS: 00e0 SS: 0068 EFLAGS: 00010246
[   44.045454] CR0: 80050033 CR2: b69e5428 CR3: 01ff0000 CR4: 00000090
[   44.088019] Call Trace:
[   44.126010]  ? fib_disable_ip+0x2a/0x2d
[   44.165297]  ? cfg80211_register_wdev+0x46/0x46
[   44.208941]  notifier_call_chain+0x2a/0x4e
[   44.252482]  raw_notifier_call_chain+0xc/0xe
[   44.296501]  call_netdevice_notifiers_info+0x5d/0x64
[   44.338599]  call_netdevice_notifiers+0x18/0x1a
[   44.379580]  __dev_notify_flags+0x4a/0x7c
[   44.419064]  dev_change_flags+0x3d/0x46
[   44.464304]  devinet_ioctl+0x260/0x4cd
[   44.502437]  inet_ioctl+0x139/0x163
[   44.539766]  ? dev_name_hash+0x20/0x36
[   44.577060]  ? dev_get_by_name_rcu+0x1c/0x2f
[   44.614874]  ? dev_ioctl+0x2e4/0x40e
[   44.651928]  ? inet_recvmsg+0x77/0x77
[   44.692778]  sock_ioctl+0x2ad/0x36f
[   44.730157]  ? preempt_count_add+0x4a/0x4f
[   44.771397]  ? ____sys_recvmsg+0xbc/0xbc
[   44.808485]  vfs_ioctl+0x1a/0x24
[   44.847256]  __ia32_sys_ioctl+0x5aa/0x5c4
[   44.891962]  ? debug_smp_processor_id+0x12/0x14
[   44.930996]  ? fpregs_assert_state_consistent+0x17/0x34
[   44.967562]  ? exit_to_user_mode_prepare+0x84/0x94
[   45.002448]  do_int80_syscall_32+0x2c/0x39
[   45.035656]  entry_INT80_32+0xf3/0xf3
[   45.067762] EIP: 0xb790ffc4
[   45.097915] Code: 83 c4 0c 89 d8 5b 5e 5f 5d c3 66 90 66 90 66 90 66 90 66 90 66 90 53 8b 54 24 10 8b 4c 24 0c 8b 5c 24 08 b8 36 00 00 00 cd 80 <5b> 3d 01 f0 ff ff 0f 83 a0 3f f3 ff c3 66 90 66 90 66 90 66 90 66
[   45.199342] EAX: ffffffda EBX: 00000007 ECX: 00008914 EDX: bffe736c
[   45.233187] ESI: bffe736c EDI: 0076c850 EBP: 00000000 ESP: bffe7348
[   45.266705] DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 007b EFLAGS: 00000296
[   45.300799] ---[ end trace 20811b76aa348f84 ]---
[   64.909322] IPv6: ADDRCONF(NETDEV_CHANGE): wlp0s15f5u1: link becomes ready

Warm reboot a second time seems to help.

131PackagesBug ReportMediumLowlibseccomp doesn't build in python bindingsNew
Task Description

no task description

130PackagesBug ReportMediumLowuser-manager and plasma-meta are in conflictNew
Task Description

:: removing user-manager breaks dependency ‘user-manager’ required by plasma-meta

129PackagesBug ReportMediumLowrust 1.47 is outdatedNew
Task Description

either building 1.49 via 1.48, via 1.47 or we have to bootstrap from a binary version again.

127PackagesBug ReportMediumLowiotop doesn't workNew
Task Description
root@arch32-stable-pentium4 ~]# iotop
No module named 'iotop'
To run an uninstalled copy of iotop,
launch iotop.py in the top directory

iotop is a Python script, presumably some Python modules are missing.

126PackagesBug ReportMediumLowlua hooks break in TeX on i686New
Task Description
PANIC: unprotected error in call to Lua API (CPU with SSE2 required)
PANIC: unprotected error in call to Lua API (CPU with SSE2 required)
fmtutil [ERROR]: running `luajittex -ini   -jobname=luajittex -progname=luajittex luatex.ini </dev/null' return status: 1
fmtutil [ERROR]: cannot copy log luajittex.log to: /var/lib/texmf/web2c/luajittex
fmtutil [ERROR]: returning error due to option --strict
fmtutil [ERROR]: running `luajithbtex -ini   -jobname=luajithbtex -progname=luajithbtex luatex.ini </dev/null' return status: 1
fmtutil [ERROR]: cannot copy log luajithbtex.log to: /var/lib/texmf/web2c/luajithbtex
fmtutil [ERROR]: returning error due to option --strict
error: command failed to execute correctly
125PackagesBug ReportMediumLowseamonkey broken on i686New
Task Description

breaks in more SIMD optimizations.

124PackagesBug ReportMediumLowmutter and gnome-shell are in confllictNew
Task Description

:: installing mutter (3.38.1-1.1) breaks dependency ‘libmutter-6.so=0-32’ required by gnome-shell

123PackagesBug ReportMediumLowlibhandy0, libhandy conflictsNew
Task Description

libhandy0: /usr/share/vala/vapi/libhandy-0.0.deps exists in filesystem (owned by libhandy)
libhandy0: /usr/share/vala/vapi/libhandy-0.0.vapi exists in filesystem (owned by libhandy)

121PackagesBug ReportVery LowHighMultiple packages need rebuild after libicu upgradeAssigned
Task Description

Over in  FS#119 , @abaumann mentioned that the libicu upgrade from 67 to 68 was part of what broke gdb. I missed the libicu upgrade when looking at gdb, but now that that one is resolved, I noticed a number of other packages that still link against the old and now nonexistant /usr/lib/libicu*.so.67 files. On my particular system, the following packages are installed, link to icu 67, and need rebuilt as well:

* harfbuzz-icu (2.7.0-1.0)
* mongo-c-driver (1.17.3-1.0)
* postfix (3.5.6-2.0)
* postgresql (12.4-1.0)
* postgresql-old-upgrade (12.5-1.0)
* samba (4.12.3-1.2)
* smbclient (4.12.3-1.2)
* syslog-ng (3.28.1-3.0)
* texlive-bin (2020.54586-4.0)
* xfsprogs (5.8.0-1.0)

… but I’m sure you have a way of determining all the affected packages?

As a workaround, in case others have the same problem, I manually extracted the old versioned .so files from the previous package to get things working again:

tar -C / -xf /var/cache/pacman/pkg/icu-67.1-1.0-i686.pkg.tar.zst –wildcards ‘usr/lib/lib*.so.*’ ```

- I’ll just have to remember to clean them up again later.

117PackagesBug ReportVery LowLowvboxdrive module missingUnconfirmed
Task Description

vboxdrv module is missing making virtualbox unusable.

I’m currently running kernel 5.9.0-1.0-pae but it doesn’t seem to be there in any version

116PackagesBug ReportMediumLowRace causes iptables not to be ready after startupNew
Task Description

Nov 06 08:04:01 eurohp1 systemd[1]: Starting IPv4 Packet Filtering Framework… Nov 06 08:04:01 eurohp1 iptables-restore[287]: Another app is currently holding the xtables lock. Perhap>
Nov 06 08:04:01 eurohp1 systemd[1]: iptables.service: Main process exited, code=exited, status=4/NOPERMI>
Nov 06 08:04:01 eurohp1 systemd[1]: iptables.service: Failed with result ‘exit-code’.
Nov 06 08:04:01 eurohp1 systemd[1]: Failed to start IPv4 Packet Filtering Framework.

Works when starting iptables later manually.

This is security relevant as not having a firewall after startup puts the system at risk.

115PackagesBug ReportMediumLowgnome doesn't startNew
Task Description

gnome-shell segfaults in libmutter.

                                                               Stack trace of thread 1009:
                                                               #0  0x00000000b64d5436 n/a (libmutter-cogl-6.so.0 + 0xe436)
                                                               #1  0x00000000b64d809c n/a (libmutter-cogl-6.so.0 + 0x1109c)
                                                               #2  0x00000000b653edb9 n/a (libmutter-cogl-6.so.0 + 0x77db9)
                                                               #3  0x00000000b64f8fc5 cogl_flush (libmutter-cogl-6.so.0 + 0x31fc5)
                                                               #4  0x00000000b6549154 cogl_onscreen_swap_buffers_with_damage (libmutter-cogl-6.so.0 + 0x82154)
                                                               #5  0x00000000b6c59f73 n/a (libmutter-clutter-6.so.0 + 0x10ff73)
                                                               #6  0x00000000b6c53cf2 n/a (libmutter-clutter-6.so.0 + 0x109cf2)
                                                               #7  0x00000000b6c54747 n/a (libmutter-clutter-6.so.0 + 0x10a747)
                                                               #8  0x00000000b6bf52ad n/a (libmutter-clutter-6.so.0 + 0xab2ad)
                                                               #9  0x00000000b7703bde g_main_context_dispatch (libglib-2.0.so.0 + 0x4dbde)
                                                               #10 0x00000000b7752962 n/a (libglib-2.0.so.0 + 0x9c962)
                                                               #11 0x00000000b7702299 g_main_loop_run (libglib-2.0.so.0 + 0x4c299)
                                                               #12 0x00000000b697f216 meta_run (libmutter-6.so.0 + 0xb9216)
                                                               #13 0x000000000043144e n/a (gnome-shell + 0x244e)
                                                               #14 0x00000000b7cd900e __libc_start_main (libc.so.6 + 0x1f00e)
                                                               #15 0x0000000000431635 n/a (gnome-shell + 0x2635)
113PackagesBug ReportVery LowLow[leafpad]: segfaultsNew
Task Description

start leafpad
everything looks fine
type or paste anything and it segfaults with this error in dmesg

leafpad[550]: segfault at 1 ip b77adf13 sp bfd0eaec error 4 in libgobject-2.0.so.0.6400.3[b7787000+2f000]
112PackagesBug ReportVery LowLow[lxpanel]: segfaults on startupNew
Task Description

# pacman -Sy lxde
reboot and start lxsession
lxpanel will crash immediately, with this error in dmesg

pcmanfm[501]: segfault at 2d ip b74823cf sp bf9dd0d0 error 4 in libpango-1.0.so.0.4600.0[b7466000+29000]

lxpanel does not have this problem with GTK3
# pacman -Sy lxde-gtk3
works as expectd

109PackagesBug ReportMediumLowgcc10 -fno-common breaks jdkNew
Task Description

/usr/bin/ld: /build/java-openjdk/src/jdk14u-jdk-14.0.1+7/build/linux-x86-server-release/support/native/java.base/libjava/childproc.o:/build/java-openjdk/src/jdk14u-jdk-14.0.1+7/src/java.base/unix/native/libjava/childproc.h:129: multiple definition of `parentPathv’; /build/java-openjdk/src/jdk14u-jdk-14.0.1+7/build/linux-x86-server-release/support/native/java.base/libjava/ProcessImpl_md.o:/build/java-openjdk/src/jdk14u-jdk-14.0.1+7/src/java.base/unix/native/libjava/childproc.h:129: first defined here

collect2: error: ld returned 1 exit status

This is fixed known and fixed upstream (without just setting
-fcommon again):


108Packages: StagingBug ReportVery LowHighlldb fails to run any binary (error: failed to launch o...Unconfirmed
Task Description

Very easy to reproduce. lldb version 10.0.0, just try to run any binary.

[aeden@arch32 bin]$ lldb $(which date)
(lldb) target create “/usr/bin/date” Current executable set to ‘/usr/bin/date’ (i386).
(lldb) run
error: failed to launch or debug process

103Packages: StableBug ReportMediumLowyarn segfaultsNew
Task Description

experienced when building buildbot-www

/bin/sh: line 1: 4744 Segmentation fault (core dumped) yarn install –pure-lockfile

102Packages: StableBug ReportMediumLowfirefox-i18-n gets pushed to stable though firefox is n...New
Task Description

warning: cannot resolve “firefox>=71.0”, a dependency of “firefox-i18n-de”

100Packages: StableBug ReportVery LowLowmldonkey crashesUnconfirmed
Task Description

All versions of mldonkey crash in arch32 updated. (segmentation fault and core dumped)

85Packages: StableBug ReportMediumLow[wireguard-arch] Package not being updated alongside ke...New
Task Description

The last update to this package was August 25, despite several new kernel builds since this. As a result, the package does not work and users must use …

82Packages: StableBug ReportMediumLow[glibc] ld warning: /usr/lib32/ld-linux.so.2: corrupt G...New
Task Description

Attached to Project: Archlinux32
Opened by Jeff Hodd - 11.07.2019
Last edited by Andreas Baumann - 09.08.2019
FS#82 - [glibc] ld warning: /usr/lib32/ld-linux.so.2: corrupt GNU_PROPERTY_TYPE (5) size: 0

All software builds are producing this warning. Some builds are failing because of the error return on linking. I’m also seeing failures on LD_PRELOADs.

/bin/ld: warning: /usr/lib/ld-linux.so.2: corrupt GNU_PROPERTY_TYPE (5) size: 0

Easy to reproduce. Just build this program:

# test.c
# Compiled with ‘gcc test.c’ int main() {

  return 0;


This was reported at bugs.archlinux.org (reference https://bugs.archlinux.org/task/63015) where it was closed and considered fixed if built using the –enable-cet flag. I built glibc with the –enable-cet flag, but am still seeing the failures, so not fixed.
Closed by Andreas Baumann
09.08.2019 11:44
Reason for closing: Fixed

  Comments (6)
  Related Tasks (0/0)

Jeff Hodd commented on 16.07.2019 03:29

I’ve narrowed down the glibc upgrade to glibc-2.29-1.26 -&gt; glibc-2.29-1.27. The error doesn’t occur with glibc-2.29-1.26. There were 3 changes made to the arch32 PKGBUILD for the glibc-2.29-1.27 release. One of them caused this issue.
Andreas Baumann commented on 16.07.2019 05:33

There is another thing which can change: the toolchain.
This GNU_PROPERTY error is something the compiler emits (we think it’s CET stuff, but it’s badly
documented). Binutils ld seems not to like this ELF section.

The error is the same as in:


What’s puzzling me: –enable-cet is there in glibc, gcc, binutils (just not for i486, as CET doesn’t\
work for older CPUs).

Commit: 09d03cbd4c57b8eabfadd22b67929d958b2409d7 and d57a456faa674c24e8869a26a14c497c95accf1f in
glibc are mine, they try to change stack alignment and handling of SSE for pentium4 for Java, also without effect.
Andreas Baumann commented on 16.07.2019 05:35

About linker warnings being turned to errors (as for compiler warnings turned to errors): this
is something the DEVELOPER should do, NOT the PACKAGER. Released software should:
- NOT include asserts
- NOT include debug code
- NOT include code only used for running tests
- NOT use -Werror
- NOT use -Wl,–fatal-warnings

See for instance extra-cmake-modules-5.59.0-ld-no-fatal-warning.patch.
Jeff Hodd commented on 16.07.2019 21:50

I knew about the cet issue. Did quite abit of looking around to get some insight into it (even looked at the code - elf-properties.c - and it looks like the Elf_Internal_Note description size is coming back with a value of 0. the other possibility is that (size % 4) is something other than 0 which is less likely). From what i could gather, cet is supposed to be enabled in the latest builds of glibc for i686 even though, as you pointed out, it’s not well documented. I did do a 2.29-4 i686 build with cet enabled and it made no difference vis-a-vis the warning. I also checked the upstream diff between 2.29-1.26 and 2.29-1.27 and noticed the addition of –enable-static-pie and thought maybe position independent executables may explain it. Did another glibc build with static pie disabled and that made no difference. Am about to go back and check the diff again and see what else may have changed.

I did check the CMakeLists.txt file for my failing build and it uses -Werror and -Wl,–fatal-warnings so I will remove those. But that doesn;t actually fix the underlying issue of the warning which we shouldn;t be seeing.

It is up to the developer, but too often one has to show that a change fixes an issue before you’ll get any attention. I may not be THE developer for this particular package, but I am A developer (in general), so I don;t feel uncomfortable making code changes.

I’ll keep looking around for differences between the 1.26 and 1.27 builds.
Jeff Hodd commented on 16.07.2019 22:15

if (note-&gt;descsz &lt; 8 || (note-&gt;descsz % align_size) != 0)



(_("warning: %pB: corrupt GNU_PROPERTY_TYPE (%ld) size: %#lx"),
 abfd, note-&gt;type, note-&gt;descsz);
    return FALSE;

The warning is printing out the description size - and that’s 0.

Apparently it’s supposed to be &gt;= 8 and divisible by 4:

unsigned int align_size = bed-&gt;s-&gt;elfclass == ELFCLASS64 ? 8 : 4;

I am assuming that arch32 doesn’t support ELFCLASS64.
Jeff Hodd commented on 22.07.2019 17:13


Google Cache

78Packages: StableBug ReportMediumLowThe qt5 group contains packages of different versions.New
Task Description

Attached to Project: Archlinux32
Opened by Erling Hellenäs - 05.07.2019
FS#78 - The qt5 group contains packages of different versions.

The qt5 group contains a qt5-base which is of a later revision, 5.12.4 instead of 5.12.3. pyside2 is also of a this later revision, but I don’t use it. I guess the group should be fixed.

Workaround: I downgraded qt5-base and it is working again.

I get this error: sddm-greeter[441]: Cannot mix incompatible Qt library (version 0x50c03) with this library (version 0x50c04)
Then systemd dumps core.

Excerpt from my journal: External Link

The group definition as seen when installing the group with pacman: External Link

My architecture is i686.

I consider it critical since QT is not working.

Google Cache

76Packages: StableBug ReportMediumLowlibreoffice-fresh needs to be rebuild against icuNew
Task Description

Attached to Project: Archlinux32
Opened by Raphael Scholer - 25.05.2019
FS#76 - libreoffice-fresh needs to be rebuild against icu

  Comments (1)
  Related Tasks (0/0)

Levi commented on 25.05.2019 18:22

This bug is already captured 90% by https://bugs.archlinux32.org/index.php?do=details&amp;task_id=72 (see my comment underneath it), although to be fair I noted it against libreoffice-stable since that’s what I use.

Google Cache

74Packages: StableBug ReportMediumLowwebkit2gtk requires SSE2New
Task Description

Attached to Project: Archlinux32
Opened by Andreas Baumann - 16.05.2019
FS#74 - webkit2gtk requires SSE2

– Performing Test HAVE_SSE2_EXTENSIONS
– Performing Test HAVE_SSE2_EXTENSIONS - Failed
CMake Error at CMakeLists.txt:115 (message):

SSE2 support is required to compile WebKit

not quite clear yet, what happens, if it gets disabled forcefully..

  Comments (5)
  Related Tasks (0/0)

Andreas Baumann commented on 16.05.2019 18:43

Let’s see, what happens if we just comment out the SSE2 test in CMakeLists.txt.. :-) Admin
Andreas Baumann commented on 17.05.2019 11:54

Rebuilding runs in issues like:

make[2]: *** No rule to make target ‘JavaScriptCore-4.0.gir’, needed by ‘WebKit2-4.0.gir’. Stop.

Using in ‘build’ make JavaScriptCore-4-gir VERBOSE=1 reveils the true nature of the bug:

/usr/lib/gcc/i686-pc-linux-gnu/8.3.0/include/stddef.h:435: syntax error, unexpected identifier in ' float128 max_align_f128 attribute1)));’ at ‘__float128’

So again, the 128-bit alignment hack in glibc spreading everywhere.
Andreas Baumann commented on 17.05.2019 11:56

Also the make error sounds suspicious, like cmake/make generated files are not really tested.
Andreas Baumann commented on 17.05.2019 11:59

The 128-alignment issue is hopefully just a warning..
Andreas Baumann commented on 17.05.2019 12:55

patched build in the queue..

Google Cache

1) aligned(alignof(float128
70Packages: Build-listBug ReportMediumLowchromium not available for i686 (fails in compiler intr...New
Task Description

Attached to Project: Archlinux32
Opened by Andreas Baumann - 10.05.2019
FS#70 - chromium needs SSE2

chromium starts, but every page it loads ends in “Aw snap” and on the console:

Check failed: cpu.has_sse2().

Google Cache

68Packages: Build-listBug ReportMediumLowdmd rebuild results in gen_man segfaultNew
Task Description

FS#68 : dmd rebuild results in gen_man segfault
Opened by Andreas Baumann - 01.05.2019. FS#68 - dmd rebuild results in gen_man segfault. make: Entering directory ‘/build/dmd/src/dmd/docs’ …

67Packages: StableBug ReportMediumLowldc segfault - Arch LinuxNew
Task Description

01.05.2019 - Program terminated with signal SIGSEGV, Segmentation fault. #0 0xb30d3329 in getenv () from /usr/lib/libc.so.6 (gdb) bt #0 0xb30d3329 in …

64Packages: StableBug ReportMediumLow[wireguard] wireguard-arch-0.0.20190227-3.0-i686 does n...New
Task Description

Attached to Project: Archlinux32
Opened by Daniel Moch - 16.03.2019
FS#64 - [wireguard] wireguard-arch-0.0.20190227-3.0-i686 does not work with 4.20.10.arch1-1.0 kernel

running `modprobe wireguard` yields `modprobe: ERROR: could not insert ‘wireguard’: Exec format error`

  Comments (1)
  Related Tasks (0/0)

Daniel Moch commented on 16.03.2019 11:52

I should add that downgrading to wireguard-arch 0.0.20190123-7.0 resolved the issue.

Google Cache

63Packages: StableBug ReportMediumLownodejs crashes in libuv when cleaning up FSReqCallbackNew
Task Description

Attached to Project: Archlinux32
Opened by Andreas Baumann - 07.02.2019
FS#63 - nodejs crashes in libuv when cleaning up FSReqCallback

Program terminated with signal SIGSEGV, Segmentation fault.
#0 0×00945919 in node::fs::FSReqCallback::~FSReqCallback() ()
[Current thread is 1 (Thread 0xb5614880 (LWP 2013))]
(gdb) bt
#0 0×00945919 in node::fs::FSReqCallback::~FSReqCallback() ()
#1 0×00937274 in node::fs::FSReqAfterScope::~FSReqAfterScope() ()
#2 0x0093767d in node::fs::AfterInteger(uv_fs_s*) ()
#3 0xb7e910e0 in uv.work_done () from /usr/lib/libuv.so.1
#4 0xb7e9526e in ?? () from /usr/lib/libuv.so.1
#5 0xb7ea51f8 in uv.io_poll () from /usr/lib/libuv.so.1
#6 0xb7e95c51 in uv_run () from /usr/lib/libuv.so.1
#7 0x00905d37 in node::Start(v8::Isolate*, node::IsolateData*, std::vector, std::allocator &gt;, std::allocator, std::allocator &gt; &gt; &gt; const&amp;, std::vector, std::allocator &gt;, std::allocator, std::allocator &gt; &gt; &gt; const&amp;) ()
#8 0×00903655 in node::Start(int, char**) ()
#9 0x008acef1 in main ()

This affects gyp, vault and probably some other packages, depending whether those callbacks are used or not.

  Comments (1)
  Related Tasks (0/0)

Andreas Baumann commented on 07.02.2019 09:36

See also mailing list thread:


Google Code

62Packages: TestingBug ReportMediumLowsddm-greeter abortsNew
Task Description

Attached to Project: Archlinux32
Opened by Andreas Baumann - 01.02.2019
Last edited by Andreas Baumann - 12.05.2019
FS#62 - sddm-greeter aborts

(gdb) bt
#0 0xb7fbea41 in kernel_vsyscall ()
#1 0xb6418746 in raise () from /usr/lib/libc.so.6
#2 0xb64021e3 in abort () from /usr/lib/libc.so.6
#3 0xb6793775 in QMessageLogger::fatal(char const*, …) const () from /usr/lib/libQt5Core.so.5
#4 0xb74da6fc in QV4::Compiler::Codegen::visit(QQmlJS::AST::UiProgram*) () from /usr/lib/libQt5Qml.so.5
#5 0xb756f446 in QJSEngine::QJSEngine(QJSEnginePrivate&amp;, QObject*) () from /usr/lib/libQt5Qml.so.5
#6 0xb76afe1d in QQmlEngine::QQmlEngine(QObject*) () from /usr/lib/libQt5Qml.so.5
#7 0xb7cf93bb in QQuickViewPrivate::init(QQmlEngine*) () from /usr/lib/libQt5Quick.so.5
#8 0x0050c571 in SDDM::GreeterApp::addViewForScreen(QScreen*) ()
#9 0x0050d1a4 in SDDM::GreeterApp::startup() ()
#10 0xb69a6a4e in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5
#11 0xb697a565 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5
#12 0xb697d8c6 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) ()
from /usr/lib/libQt5Core.so.5
#13 0xb697dcd9 in QCoreApplication::sendPostedEvents(QObject*, int) () from /usr/lib/libQt5Core.so.5
#14 0xb69d4f74 in ?? () from /usr/lib/libQt5Core.so.5
#15 0xb55bca1e in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#16 0xb55beafa in ?? () from /usr/lib/libglib-2.0.so.0
#17 0xb55beb46 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#18 0xb69d44bb in QEventDispatcherGlib::processEvents(QFlags) ()
–Type for more, q to quit, c to continue without paging– from /usr/lib/libQt5Core.so.5
#19 0xb6978ff6 in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5
#20 0xb698188b in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5
#21 0x004ed3d0 in main () There seems to be a problem around Javascript and Qt5 Comments (1)
Related Tasks (0/0) Admin
Andreas Baumann commented on 12.05.2019 18:25 New bug on pentium4:
Stack trace of thread 387:
#0 0x00000000b7fa8841
kernel_vsyscall (linux-gate.so.1)

         #1  0x00000000b63311b6 raise (libc.so.6)
         #2  0x00000000b631b1e3 abort (libc.so.6)
         #3  0x00000000b66b2773 _ZNK14QMessageLogger5fatalEPKcz (libQt5Core.so.5)
         #4  0x00000000b7b98592 _ZN13QSGRenderLoop28handleContextCreationFailureEP12QQuickWindowb (libQt5Quick.so.5)
         #5  0x00000000b7b99a1d n/a (libQt5Quick.so.5)
         #6  0x00000000b7b9a35b n/a (libQt5Quick.so.5)
         #7  0x00000000b6c95427 _ZN7QWindow5eventEP6QEvent (libQt5Gui.so.5)
         #8  0x00000000b7c22c60 _ZN12QQuickWindow5eventEP6QEvent (libQt5Quick.so.5)
         #9  0x00000000b68a8845 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5)
         #10 0x00000000b6c898ab _ZN22QGuiApplicationPrivate18processExposeEventEPN29QWindowSystemInterfacePrivate11ExposeEventE (libQt5Gui.so.5)
         #11 0x00000000b6c89bda _ZN22QGuiApplicationPrivate24processWindowSystemEventEPN29QWindowSystemInterfacePrivate17WindowSystemEventE (libQt5Gui.so.5)
         #12 0x00000000b6c5e085 _ZN22QWindowSystemInterface22sendWindowSystemEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Gui.so.5)
         #13 0x00000000b0b7631d n/a (libQt5XcbQpa.so.5)
         #14 0x00000000b54ddb1e g_main_context_dispatch (libglib-2.0.so.0)
         #15 0x00000000b54dfbfa n/a (libglib-2.0.so.0)
         #16 0x00000000b54dfc46 g_main_context_iteration (libglib-2.0.so.0)
         #17 0x00000000b690172b _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5)
         #18 0x00000000b68a72d6 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5)
         #19 0x00000000b68af8db _ZN16QCoreApplication4execEv (libQt5Core.so.5)
         #20 0x00000000004a4330 main (sddm-greeter)
         #21 0x00000000b631c669 __libc_start_main (libc.so.6)
         #22 0x00000000004a4635 _start (sddm-greeter)
         Stack trace of thread 388:
         #0  0x00000000b7fa8841 __kernel_vsyscall (linux-gate.so.1)
         #1  0x00000000b63e0ed3 __poll (libc.so.6)
         #2  0x00000000b7a236ce n/a (libxcb.so.1)
         #3  0x00000000b7a25864 xcb_wait_for_event (libxcb.so.1)
         #4  0x00000000b0b751ea n/a (libQt5XcbQpa.so.5)
         #5  0x00000000b66f39e0 n/a (libQt5Core.so.5)
         #6  0x00000000b620dab2 start_thread (libpthread.so.0)
         #7  0x00000000b63ea96a __clone (libc.so.6)
         Stack trace of thread 389:
         #0  0x00000000b7fa8841 __kernel_vsyscall (linux-gate.so.1)
         #1  0x00000000b63e0ed3 __poll (libc.so.6)
         #2  0x00000000b54dfb55 n/a (libglib-2.0.so.0)
         #3  0x00000000b54dfc46 g_main_context_iteration (libglib-2.0.so.0)
         #4  0x00000000b690172b _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5)
         #5  0x00000000b68a72d6 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5)
         #6  0x00000000b66f2412 _ZN7QThread4execEv (libQt5Core.so.5)
         #7  0x00000000b0a20cdd n/a (libQt5DBus.so.5)
         #8  0x00000000b66f39e0 n/a (libQt5Core.so.5)
         #9  0x00000000b620dab2 start_thread (libpthread.so.0)
         #10 0x00000000b63ea96a __clone (libc.so.6)
         Stack trace of thread 391:
         #0  0x00000000b7fa8841 __kernel_vsyscall (linux-gate.so.1)
         #1  0x00000000b63e0ed3 __poll (libc.so.6)
         #2  0x00000000b54dfb55 n/a (libglib-2.0.so.0)
         #3  0x00000000b54dfc46 g_main_context_iteration (libglib-2.0.so.0)
         #4  0x00000000b690172b _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5)
         #5  0x00000000b68a72d6 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5)
         #6  0x00000000b66f2412 _ZN7QThread4execEv (libQt5Core.so.5)
         #7  0x00000000b77189c3 n/a (libQt5Qml.so.5)
         #8  0x00000000b66f39e0 n/a (libQt5Core.so.5)
         #9  0x00000000b620dab2 start_thread (libpthread.so.0)
         #10 0x00000000b63ea96a __clone (libc.so.6)

Google Cache

61Packages: StableBug ReportMediumLowdmd fails to build with evalu8.d:function evalu8(elem ....New
Task Description

01.05.2019 - From the discusison in: https://forum.dlang.org/thread/dsrjmpnavxqsjqmlvotf@forum.dlang.org. Well the problem is that the mangling produced …

58Packages: StableBug ReportMediumLowtexlive-bin doesn't buildNew
Task Description

22.12.2018 - g++ -DHAVE_CONFIG_H -I. -I../../../texk/web2c -I./w2c -I/build/texlive-bin/src/texlive-source/Work/texk -I/build/texlive-bin/src/texlive-source/texk …

54Packages: StableBug ReportMediumLow[pam] links against libaudit, but doesn't declare a dep...New
Task Description

Attached to Project: Archlinux32
Opened by Luke Shumaker - 09.10.2018
FS#54 - [pam] links against libaudit, but doesn’t declare a dependency on [audit]

Both core/pam 1.3.1-1.2 and staging/pam 1.3.1-1.3 have their libpam.so link against libaudit:

$ readelf –dynamic /usr/lib/libpam.so.0.84.2

Dynamic section at offset 0xfdbc contains 27 entries:

Tag        Type                         Name/Value

0×00000001 (NEEDED) Shared library: [libaudit.so.1]

However, the package does not declare depends=(audit) (’audit’ is the package that contains libaudit.so).

This is normally a fairly invisible mistake because recent versions of systemd depend on audit, so systemd-users (i.e. most users) will have audit installed anyway.

This affects `su` (of util-linux) and `sudo` (of sudo), which both link against libpam.

  Comments (4)
  Related Tasks (0/0)

Erich Eckner commented on 09.10.2018 20:42

pam also links against libaudit.so.1 iff rebuilt for x86_64 - but not the currently built one for x86_64:

— /dev/fd/63 2018-10-09 22:41:57.015507993 +0200
+++ /dev/fd/62 2018-10-09 22:41:57.015507993 +0200
@@ -3,9 +3,9 @@
pkgbase = pam
pkgver = 1.3.1-1
pkgarch = x86_64
-pkgbuild_sha256sum = 3a72016938e6f3e8660a0f8774b576bf58aa4c7b218948e1fadcf39a3e7ebf9d
-packager = Erich Eckner
-builddate = 1539104335
+pkgbuild_sha256sum = e178fcb37ae20afe3f75b66ec5c29bb9eaf5d5e25d032d62e01e2fc54cf2ed32
+packager = Tobias Powalowski
+builddate = 1529655718
builddir = /build
buildenv = !distcc
buildenv = color
@@ -23,129 +23,129 @@
options = !upx
options = !debug
installed = acl-2.2.53-1-x86_64
-installed = archlinux-keyring-20181003-1-any
+installed = archlinux-keyring-20180404-1-any
installed = argon2-20171227-3-x86_64
installed = attr-2.4.48-1-x86_64
-installed = audit-2.8.4-2-x86_64
installed = autoconf-2.69-4-any
-installed = automake-1.16.1-1-any
+installed = automake-1.15.1-1-any
installed = bash-4.4.023-1-x86_64
-installed = binutils-2.31.1-3-x86_64
+installed = binutils-2.30-5-x86_64
installed = bison-3.0.5-1-x86_64
-installed = bzip2-1.0.6-8-x86_64
-installed = ca-certificates-20180821-1-any
-installed = ca-certificates-mozilla-3.39-1-x86_64
-installed = ca-certificates-utils-20180821-1-any
-installed = coreutils-8.30-1-x86_64
+installed = bzip2-1.0.6-7-x86_64
+installed = ca-certificates-20170307-1-any
+installed = ca-certificates-cacert-20140824-4-any
+installed = ca-certificates-mozilla-3.37.3-1-x86_64
+installed = ca-certificates-utils-20170307-1-any
+installed = coreutils-8.29-1-x86_64
installed = cracklib-2.9.6-1-x86_64
-installed = cryptsetup-2.0.4-1-x86_64
-installed = curl-7.61.1-3-x86_64
+installed = cryptsetup-2.0.3-2-x86_64
+installed = curl-7.60.0-1-x86_64
installed = db-5.3.28-4-x86_64
-installed = dbus-1.12.10-2-x86_64
-installed = device-mapper-2.02.181-1-x86_64
+installed = dbus-1.12.8-1-x86_64
+installed = device-mapper-2.02.177-5-x86_64
installed = diffutils-3.6-1-x86_64
-installed = docbook-xml-4.5-8-any
+installed = docbook-xml-4.5-7-any
installed = docbook-xsl-1.79.2-4-any
-installed = e2fsprogs-1.44.4-1-x86_64
-installed = expat-2.2.6-1-x86_64
-installed = fakeroot-1.23-1-x86_64
-installed = file-5.34-1-x86_64
-installed = filesystem-2018.8-1-x86_64
+installed = e2fsprogs-1.44.2-1-x86_64
+installed = expat-2.2.5-1-x86_64
+installed = fakeroot-1.22-1-x86_64
+installed = file-5.33-3-x86_64
+installed = filesystem-2018.1-2-x86_64
installed = findutils-4.6.0-2-x86_64
installed = flex-2.6.4-1-x86_64
installed = gawk-4.2.1-1-x86_64
-installed = gc-7.6.8-1-x86_64
-installed = gcc-8.2.1+20180831-1-x86_64
-installed = gcc-libs-8.2.1+20180831-1-x86_64
-installed = gdbm-1.18-1-x86_64
+installed = gc-7.6.6-1-x86_64
+installed = gcc-8.1.1+20180531-1-x86_64
+installed = gcc-libs-8.1.1+20180531-1-x86_64
+installed = gdbm-1.14.1-1-x86_64
installed = gettext-
-installed = glib2-2.58.1-1-x86_64
-installed = glibc-2.28-4-x86_64
+installed = glib2-2.56.1-1-x86_64
+installed = glibc-2.27-3-x86_64
installed = gmp-6.1.2-1-x86_64
-installed = gnupg-2.2.10-1-x86_64
-installed = gnutls-3.5.19-2-x86_64
-installed = gpgme-1.11.1-2-x86_64
-installed = gpm-1.20.7.r27.g1fd1941-1-x86_64
+installed = gnupg-2.2.8-1-x86_64
+installed = gnutls-3.5.18-1-x86_64
+installed = gpgme-1.11.1-1-x86_64
+installed = gpm-1.20.7-8-x86_64
installed = grep-3.1-1-x86_64
installed = groff-1.22.3-7-x86_64
-installed = guile-2.2.4-1-x86_64
+installed = guile-2.2.3-1-x86_64
installed = gzip-1.9-1-x86_64
-installed = hwids-20180518-1-any
-installed = iana-etc-20180913-1-any
-installed = icu-62.1-1-x86_64
-installed = iptables-1:1.6.2-3-x86_64
-installed = json-c-0.13.1-2-x86_64
+installed = hwids-20171003-1-any
+installed = iana-etc-20180221-1-any
+installed = icu-61.1-1-x86_64
+installed = iptables-1.6.2-2-x86_64
+installed = json-c-0.13.1-1-x86_64
installed = kbd-2.0.4-1-x86_64
-installed = keyutils-1.5.11-1-x86_64
+installed = keyutils-1.5.10-2-x86_64
installed = kmod-25-1-x86_64
installed = krb5-1.16.1-1-x86_64
installed = less-530-1-x86_64
-installed = libarchive-3.3.3-1-x86_64
+installed = libarchive-3.3.2-2-x86_64
installed = libassuan-2.5.1-1-x86_64
-installed = libatomic_ops-7.6.6-1-x86_64
+installed = libatomic_ops-7.6.4-1-x86_64
installed = libcap-2.25-1-x86_64
installed = libcap-ng-0.7.9-1-x86_64
-installed = libelf-0.174-1-x86_64
+installed = libelf-0.171-1-x86_64
installed = libffi-3.2.1-2-x86_64
installed = libgcrypt-1.8.3-1-x86_64
-installed = libgpg-error-1.32-1-x86_64
+installed = libgpg-error-1.31-1-x86_64
+installed = libidn-1.34-2-x86_64
installed = libidn2-2.0.5-1-x86_64
installed = libksba-1.3.5-1-x86_64
-installed = libldap-2.4.46-2-x86_64
+installed = libldap-2.4.46-1-x86_64
installed = libmnl-1.0.4-1-x86_64
installed = libmpc-1.1.0-1-x86_64
-installed = libnftnl-1.1.1-1-x86_64
-installed = libnghttp2-1.33.0-1-x86_64
+installed = libnftnl-1.1.0-1-x86_64
+installed = libnghttp2-1.31.1-1-x86_64
installed = libnl-3.4.0-1-x86_64
-installed = libpcap-1.9.0-1-x86_64
+installed = libpcap-1.8.1-2-x86_64
installed = libpsl-0.20.2-1-x86_64
-installed = libsasl-2.1.26-13-x86_64
-installed = libseccomp-2.3.3-1-x86_64
+installed = libsasl-2.1.26-12-x86_64
+installed = libseccomp-2.3.2-2-x86_64
installed = libsecret-0.18.6-1-x86_64
installed = libssh2-1.8.0-2-x86_64
-installed = libsystemd-239.2-1-x86_64
+installed = libsystemd-238.133-4-x86_64
installed = libtasn1-4.13-1-x86_64
-installed = libtirpc-1.1.4-1-x86_64
-installed = libtool-2.4.6+42+gb88cebd5-2-x86_64
+installed = libtirpc-1.0.3-2-x86_64
+installed = libtool-2.4.6+40+g6ca5e224-7-x86_64
installed = libunistring-0.9.10-1-x86_64
installed = libusb-1.0.22-1-x86_64
-installed = libutil-linux-2.32.1-2-x86_64
-installed = libxml2-2.9.8-5-x86_64
+installed = libutil-linux-2.32-3-x86_64
+installed = libxml2-2.9.8-2-x86_64
installed = libxslt-1.1.32+3+g32c88216-1-x86_64
-installed = linux-api-headers-4.17.11-1-any
-installed = lz4-1:1.8.3-1-x86_64
+installed = linux-api-headers-4.16.1-1-any
+installed = lz4-1:1.8.2-2-x86_64
installed = m4-1.4.18-1-x86_64
installed = make-4.2.1-2-x86_64
installed = mpfr-4.0.1-1-x86_64
installed = ncurses-6.1-3-x86_64
installed = nettle-3.4-1-x86_64
-installed = npth-1.6-1-x86_64
-installed = openssl-1.1.1-1-x86_64
-installed = p11-kit-0.23.14-1-x86_64
-installed = pacman-5.1.1-1-x86_64
-installed = pacman-mirrorlist-20180912-1-any
-installed = pam-1.3.1-1-x86_64
+installed = npth-1.5-1-x86_64
+installed = openssl-1.1.0.h-1-x86_64
+installed = p11-kit-0.23.12-1-x86_64
+installed = pacman-5.1.0-2-x86_64
+installed = pacman-mirrorlist-20180524-1-any
+installed = pam-1.3.0-2-x86_64
installed = pambase-20171006-1-any
-installed = patch-2.7.6-3-x86_64
+installed = patch-2.7.6-1-x86_64
installed = pcre-8.42-1-x86_64
-installed = pcre2-10.32-1-x86_64
-installed = perl-5.28.0-1-x86_64
-installed = pinentry-1.1.0-4-x86_64
-installed = pkgconf-1.5.3-1-x86_64
+installed = pcre2-10.31-1-x86_64
+installed = perl-5.26.2-1-x86_64
+installed = pinentry-1.1.0-3-x86_64
+installed = pkgconf-1.4.2-2-x86_64
installed = popt-1.16-9-x86_64
installed = procps-ng-3.3.15-1-x86_64
installed = readline-7.0.005-1-x86_64
installed = sed-4.5-1-x86_64
-installed = shadow-4.6-1-x86_64
-installed = sqlite-3.25.2-1-x86_64
-installed = sudo-1.8.25.p1-1-x86_64
-installed = systemd-239.2-1-x86_64
+installed = shadow-4.5-4-x86_64
+installed = sqlite-3.24.0-1-x86_64
+installed = sudo-1.8.23-2-x86_64
+installed = systemd-238.133-4-x86_64
installed = tar-1.30-1-x86_64
installed = texinfo-6.5-1-x86_64
-installed = tzdata-2018e-2-x86_64
-installed = util-linux-2.32.1-2-x86_64
+installed = tzdata-2018e-1-any
+installed = util-linux-2.32-3-x86_64
installed = w3m-0.5.3.git20180125-1-x86_64
installed = which-2.21-2-x86_64
installed = xz-5.2.4-1-x86_64
-installed = zlib-1:1.2.11-3-x86_64
-installed = zstd-1.3.5-1-x86_64
+installed = zlib-1:1.2.11-2-x86_64
Erich Eckner commented on 09.10.2018 20:47

As can be seen, the new version of systemd pulls in audit, against which then the linking happens.
I would not do anything about this issue (if that’s ok with you, Luke), because:
1st it only affects systems w/o systemd - e.g. non-standard systems
2nd it will solve itself with the next (upstream) release/rebuild of pam (or at least, if upstream does not add audit to the depends, it will become an upstream bug which we should report to them)

Luke Shumaker commented on 09.10.2018 21:28

Parabola supports OpenRC, so this risks breaking sudo for Parabola OpenRC users, making it more severe for us downstream than it is for you.

That isn’t to say that you have to take actionand fix it for us; it is a low-priority bug for Arch Linux 32 users, so if you want to wait for it to be resolved in upsteam Arch, that’s your prerogative. But it means that in the mean-time, Parabola will have to repackage it to avoid breaking our OpenRC users’ boxes.
bill auger commented on 10.10.2018 01:16

related to: https://bugs.archlinux.org/task/60365

Google Cache

40Packages: StableBug ReportMediumLow[extra/gimp] is uninstallable because [extra/gegl02 ...New
Task Description

20.06.2018 - [extra/gegl02] (which provided gegl=0.2; [extra/gegl] is 0.3) was removed, despite that it was still needed by [extra/gimp]. [extra/gimp] is an old …

39Packages: StableBug ReportMediumLowxorg modesetting module fails with illegal instructionNew
Task Description

Attached to Project: Archlinux32
Opened by Andreas Baumann - 13.06.2018
Last edited by Andreas Baumann - 13.09.2018
FS#39 - xorg modesetting module fails with illegal instruction

[ 22.717] (EE) Illegal instruction at address 0xb632cd37
[ 22.718] (EE)
Fatal server error:
[ 22.718] (EE) Caught signal 4 (Illegal instruction). Server aborting
[ 22.719] (EE)

               PID: 242 (Xorg)
         UID: 0 (root)
         GID: 0 (root)
      Signal: 6 (ABRT)
   Timestamp: Wed 2018-06-13 20:53:43 CEST (41s ago)
Command Line: /usr/lib/Xorg :0
  Executable: /usr/lib/Xorg

Control Group: /user.slice/user-0.slice/session-c1.scope

        Unit: session-c1.scope
       Slice: user-0.slice
     Session: c1
   Owner UID: 0 (root)
     Boot ID: ea12301d13874fac8112dad7bf566bdb
  Machine ID: 2f98089cbe8d40cb8776a580d6803b58
    Hostname: arch32-staging
     Storage: /var/lib/systemd/coredump/core.Xorg.0.ea12301d13874fac8112dad7bf566bdb.242.1528916023000&gt;
     Message: Process 242 (Xorg) of user 0 dumped core.
              Stack trace of thread 242:
              #0  0x00000000b7f58d21 __kernel_vsyscall (linux-gate.so.1)
              #1  0x00000000b7d749c2 raise (libc.so.6)
              #2  0x00000000b7d5e71e abort (libc.so.6)
              #3  0x000000000056b555 OsAbort (Xorg)
              #4  0x000000000056b5d2 FatalError (Xorg)
              #5  0x000000000060a93a n/a (Xorg)
              #6  0x00000000b7f58d38 __kernel_rt_sigreturn (linux-gate.so.1)
              #7  0x00000000b632cd37 n/a (kms_swrast_dri.so)
              #8  0x00000000b5f0181f n/a (kms_swrast_dri.so)
              #9  0x00000000b7f698b3 call_init.part.0 (ld-linux.so.2)
              #10 0x00000000b7f699b2 _dl_init (ld-linux.so.2)
              #11 0x00000000b7f6d7e0 dl_open_worker (ld-linux.so.2)
              #12 0x00000000b7e7bc91 _dl_catch_exception (libc.so.6)
              #13 0x00000000b7f6d077 _dl_open (ld-linux.so.2)
              #14 0x00000000b7b8cb73 n/a (libdl.so.2)
              #15 0x00000000b7e7bc91 _dl_catch_exception (libc.so.6)
              #16 0x00000000b7e7bd40 _dl_catch_error (libc.so.6)
              #17 0x00000000b7b8d333 n/a (libdl.so.2)
              #18 0x00000000b7b8cc16 dlopen (libdl.so.2)
              #19 0x00000000b7f2eb6e n/a (libgbm.so.1)
              #20 0x00000000b7f2ecb3 n/a (libgbm.so.1)
              #21 0x00000000b7f2ee24 n/a (libgbm.so.1)
              #22 0x00000000b7f2f0d7 n/a (libgbm.so.1)
              #23 0x00000000b7f2c9ba gbm_create_device (libgbm.so.1)
              #24 0x00000000b6ef4ee4 glamor_egl_init (libglamoregl.so)
              #25 0x00000000b7f49b4a n/a (modesetting_drv.so)
              #26 0x000000000051c169 InitOutput (Xorg)
              #27 0x000000000049d8e1 n/a (Xorg)
              #28 0x00000000b7d60041 __libc_start_main (libc.so.6)
              #29 0x000000000049e7e2 _start (Xorg)
  Comments (7)
  Related Tasks (0/0)

Andreas Baumann commented on 14.06.2018 15:53

#0 0xb7f3ad21 in kernel_vsyscall () [-
#1 0xb7d579c2 in raise () from /usr/lib/libc.so.6
#2 0xb7d4171e in abort () from /usr/lib/libc.so.6
#3 0x005855f5 in OsAbort () at ../xorg-server-1.20.0/os/utils.c:1350
#4 0×00585672 in AbortServer () at ../xorg-server-1.20.0/os/log.c:877
#4 0×00585672 in AbortServer () at ../xorg-server-1.20.0/os/log.c:877
#5 FatalError (f=0x65e1bc “Caught signal %d (%s). Server aborting\n”)
at ../xorg-server-1.20.0/os/log.c:1015
#6 0x00624b5a in OsSigHandler (signo=, sip=, unused=,
signo=, sip=, unused=) at ../xorg-server-1.20.0/os/osinit.c:156
#8 0xb62d5d37 in SwrJit::X86Intrinsic::X86Intrinsic (this=0xbf955e24)
at ../mesa-18.1.1/src/gallium/drivers/swr/rasterizer/jitter/functionpasses/lower_x86.cpp:66
#9 std::pair, std::allocator &gt; const, SwrJit::X86Intrinsic&gt;::pair (this=0xbf955e0c,
x=…, y=…)
at /usr/include/c++/8.1.1/bits/stl_pair.h:301
#10 0xb5eaa81f in
static_initialization_and_destruction_0(int, int) [clone .constprop.236] ()

  at /usr/include/c++/8.1.1/new:169

#11 0xb7f4b8b3 in call_init.part () from /lib/ld-linux.so.2
#12 0xb7f4b9b2 in _dl_init () from /lib/ld-linux.so.2
#13 0xb7f4f7e0 in dl_open_worker () from /lib/ld-linux.so.2
#14 0xb7e5ec91 in _dl_catch_exception () from /usr/lib/libc.so.6
#15 0xb7f4f077 in _dl_open () from /lib/ld-linux.so.2
#16 0xb7b6fb73 in ?? () from /usr/lib/libdl.so.2
#17 0xb7e5ec91 in _dl_catch_exception () from /usr/lib/libc.so.6
#18 0xb7e5ed40 in _dl_catch_error () from /usr/lib/libc.so.6
—Type to continue, or q to quit— #19 0xb7b70333 in ?? () from /usr/lib/libdl.so.2
#20 0xb7b6fc16 in dlopen () from /usr/lib/libdl.so.2
#21 0xb7f10b6e in dri_open_driver (dri=, dri=)

  at ../mesa-18.1.1/src/gbm/backends/dri/gbm_dri.c:354

#22 0xb7f10cb3 in dri_load_driver (dri=0x17e9660) at ../mesa-18.1.1/src/gbm/backends/dri/gbm_dri.c:439
#23 dri_screen_create_dri2 (dri=dri@entry=0x17e9660, driver_name=)

  at ../mesa-18.1.1/src/gbm/backends/dri/gbm_dri.c:439

#24 0xb7f10e24 in dri_screen_create_sw (dri=0x17e9660)

  at ../mesa-18.1.1/src/gbm/backends/dri/gbm_dri.c:539

#25 0xb7f110d7 in dri_device_create (fd=13) at ../mesa-18.1.1/src/gbm/backends/dri/gbm_dri.c:1429
#26 0xb7f0e9ba in gbm_create_device (fd=13) at ../mesa-18.1.1/src/gbm/main/gbm.c:137
#27 0xb6ebaee4 in glamor_egl_init (scrn=0x17e83a0, fd=13)

  at ../xorg-server-1.20.0/glamor/glamor_egl.c:894

#28 0xb7f2bb4a in try_enable_glamor (pScrn=0x17e83a0)

  at ../xorg-server-1.20.0/hw/xfree86/drivers/modesetting/driver.c:753

#29 PreInit (pScrn=, flags=)

  at ../xorg-server-1.20.0/hw/xfree86/drivers/modesetting/driver.c:972

#30 0×00536209 in InitOutput (pScreenInfo=0x6fd520 , argc=6, argv=0xbf957944)

  at ../xorg-server-1.20.0/hw/xfree86/common/xf86Init.c:536

#31 0x004b7991 in dix_main (envp=, argv=, argc=)

  at ../xorg-server-1.20.0/dix/main.c:193

#32 main (argc=, argv=, envp=)

  at ../xorg-server-1.20.0/dix/stubmain.c:34

=&gt; 0xb62d5d37 &lt;+71&gt;: vmovq -0×20(%ebp),%xmm0

 0xb62d5d3c &lt;+76&gt;:    vmovq  %xmm0,0x18(%esi)

Looks like AVX optimized code in libswr though I’m deleting -D swr-arches=avx,avx2 in
the diff-PKGBUILD (maybe wrongly)?
Andreas Baumann commented on 14.06.2018 17:55

So, I read OpenSWR requires at least AVX, so we can safely drop the library for 32-bit
machines, right?

So removing swr from the gallium-drivers, then I get croaks about gallium-nine requiring
a pipe.

I’ll continue to drop options in arch-meson in PKGBUILD till I get a working build..

Any help welcome. :-) Admin
Andreas Baumann commented on 14.06.2018 18:13

Some docu:


Trying the following patch at the moment:

eval “$(

declare -f build | \
  sed '
    /-D gallium-drivers=/s/,swr//g
    s/-D swr-arches=avx,avx2//g
    s/-D gallium-nine=true/-D gallium-nine=false/g
    s/-D osmesa=gallium/-D osmesa=classic/g


Erich Eckner commented on 14.06.2018 20:54

only glitch I see with your fix is, that the options are in one line in `declare -f build`, so the line-matching makes no sense
Andreas Baumann commented on 15.06.2018 06:07

one line? It should actually be one line each and it worked for me? *puzzle*
Andreas Baumann commented on 15.06.2018 08:55

This seems to work. But I’m disabling and changing an awful lot of stuff:

# disable AVX/AVX2 in openswf, makes no sense with old CPUs
eval “$(

declare -f build | \
  sed '
    /-D gallium-drivers=/s/,swr//g
    s/-D swr-arches=avx,avx2//g
    s/-D gallium-nine=true/-D gallium-nine=false/g
    s/-D osmesa=gallium/-D osmesa=classic/g
declare -f package_mesa | \
  sed '
    s@_install fakeinstall/usr/lib/d3d@#\0@g
    s@_install fakeinstall/usr/lib/libswrAVX.*@#\0@g


Andreas Baumann commented on 13.09.2018 08:34

Fails again with (mesa 18.1.8 on testing):

Program received signal SIGILL, Illegal instruction.
0xb627e167 in ?? () from /usr/lib/dri/kms_swrast_dri.so
=&gt; 0xb627e167: c5 fa 7e 45 e0 vmovq -0×20(%ebp),%xmm0

Google Cache

Bing Cache

36Packages: TestingBug ReportMediumLowtexlive-core: SSE2 requiredNew
Task Description

Attached to Project: Archlinux32
Opened by Andreas Baumann - 14.04.2018
Last edited by Andreas Baumann - 16.04.2018
FS#36 - texlive-core: SSE2 required

(4/5) Updating TeXLive format files… PANIC: unprotected error in call to Lua API (CPU with SSE2 required)
fmtutil [ERROR]: running `luajittex -ini -jobname=luajittex -progname=luajittex luatex.ini /null’ return status 1
fmtutil [ERROR]: return error due to options –strict
error: command failed to execute correctly
(5/5) Updating TeXLive font maps…

So, the problem seems to be in lua itself?

Bing Cache

28Packages: Build-listBug ReportMediumLowpostgrest: checks start a Postgresql server and then te...New
Task Description

Starting check()… WARNING [pifpaf.drivers] `psutil.Popen(pid=2683, status=’terminated’)` is already gone, sending SIGKILL to its process group
WARNING [pifpaf.drivers] `psutil.Popen(pid=2671, status=’terminated’)` is already gone, sending SIGKILL to its process group
WARNING [pifpaf.drivers] `psutil.Popen(pid=2669, status=’terminated’)` is already gone, sending SIGKILL to its process group
ERROR [pifpaf] Error while running command: [b’/usr/bin/pg_ctl’, ‘-w’, ‘-o’, ‘-k /tmp/tmp5_5e9_hy -p 5432 -h “”‘, ‘start’]
createdb: could not connect to database template1: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket “/run/postgresql/.s.PGSQL.5432”? ERROR: A failure occurred in check().
ERROR: Build failed, check /data/archbuild/staging-i686/arch32/build

Disabling tests for now.

  Comments (1)
  Related Tasks (0/0)

Andreas Baumann commented on 15.02.2018 16:56

Didn’t pifpaf itself had problems building? Maybe it’s a pifpaf issue..

Bing cache

20Packages: Build-listBug ReportMediumLow[sagemath-doc] building documentation using Sphinx segf...New
Task Description

[tutorial ] Saved pickle file: citations.pickle
[tutorial ] Exception occurred:
[tutorial ] File “/usr/lib/python2.7/site-packages/sphinx/environment/init.py”, line 152, in dump
[tutorial ] pickle.dump(env, f, pickle.HIGHEST_PROTOCOL)
[tutorial ] MemoryError
[tutorial ] The full traceback has been saved in /tmp/sphinx-err-kSNZ9A.log, if you want to report the issue to the developers.
[tutorial ] Please also report this if it was a user error, so that a better error message can be provided next time.
[tutorial ] A bug report can be filed in the tracker at . Thanks!
Build finished. The built documents can be found in /build/sagemath-doc/src/sage-8.1/src/doc/html/ja/tutorial
/startdir/PKGBUILD: line 79: 2540 Segmentation fault (core dumped) python2 sage_setup/docbuild –no-pdf-links -k all html
==&gt; ERROR: A failure occurred in build().


==&gt; ERROR: Build failed, check /data/archbuild/staging-i686/copy/build

Bing Cache

Showing tasks 1 - 40 of 40 Page 1 of 1

Available keyboard shortcuts


Task Details

Task Editing