Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#46017 - [dovecot] doveadm segfaults when using FTS plugin since upgrade to glibc 2.22

Attached to Project: Arch Linux
Opened by Rob Hoelz (hoelzro) - Wednesday, 19 August 2015, 06:47 GMT
Last edited by Andreas Radke (AndyRTR) - Saturday, 31 October 2015, 20:49 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Andreas Radke (AndyRTR)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

When I try to run the following command on my box using dovecot:

doveadm expunge all mailbox spam

I get the following:

zsh: segmentation fault doveadm expunge all mailbox spam

This is using dovecot 2.2.18-1, and started happening since I upgraded to glibc 2.22-1. I tried downgrading to glibc 2.21-4, and the problem did not appear. The problem is fixed upstream in hg tip, so it should be resolved once dovecot 2.2.19 has been released.

Attached are the following files:

- bisect-test.sh - A test script I wrote to reliably reproduce the issue for hg bisect; it contains the setup and configuration needed to reproduce the bug. If it exits with status 0, everything is ok.
- dovecot-pkgbuild.patch - A patch for the PKGBUILD to fix the issue until an upstream release can be made. Once I built and installed a dovecot package using this patch, the problem no longer appears.
   dovecot-pkgbuild.patch (2.7 KiB)
   bisect-test.sh (0.7 KiB)
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Saturday, 31 October 2015, 20:49 GMT
Reason for closing:  Fixed
Comment by Rob Hoelz (hoelzro) - Friday, 30 October 2015, 16:33 GMT
Is there anything I can do to help move this along?
Comment by Andreas Radke (AndyRTR) - Saturday, 31 October 2015, 11:08 GMT
The fix is not included in 2.2.19 release? Do you see a different crash in 2.2.19? Anything from hg past 2.2.19 release that we need to apply?
Comment by Rob Hoelz (hoelzro) - Saturday, 31 October 2015, 15:40 GMT
It seems I didn't even notice that 2.2.19 came out! I don't see the crash with 2.2.19, so you can mark this as resolved!

Loading...