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
85Packages: StableBug ReportMediumLow[wireguard-arch] Package not being updated alongside ke...New
0%
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 …

78Packages: StableBug ReportMediumLowThe qt5 group contains packages of different versions.New
0%
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

63Packages: StableBug ReportMediumLownodejs crashes in libuv when cleaning up FSReqCallbackNew
0%
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 >, std::allocator, std::allocator > > > const&, std::vector, std::allocator >, std::allocator, std::allocator > > > const&) ()
#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)

Admin
Andreas Baumann commented on 07.02.2019 09:36

See also mailing list thread:

https://lists.archlinux.org/pipermail/arch-ports/2018-November/000835.html

Google Code

Showing tasks 1 - 3 of 3 Page 1 of 1

Available keyboard shortcuts

Tasklist

Task Details

Task Editing