Community Packages

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#44169 - [wireshark-gtk] segmentation fault

Attached to Project: Community Packages
Opened by nerdix (nerdix) - Friday, 13 March 2015, 08:44 GMT
Last edited by Timothy Redaelli (tredaelli) - Tuesday, 17 March 2015, 10:59 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Timothy Redaelli (tredaelli)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description: wireshark-gtk 1.12.4-1 crashes after upgrade to newes version


Additional info:
* package wireshark-gtk 1.12.4-1 (x86_64)
* see attached strace output


Steps to reproduce:

Upgrade to wireshark-gtk to version 1.12.4-1.
Start wireshark -> it will seqfault

downgrading to 1.12.3-1 fixes the issue
   out (163.8 KiB)
This task depends upon

Closed by  Timothy Redaelli (tredaelli)
Tuesday, 17 March 2015, 10:59 GMT
Reason for closing:  Fixed
Additional comments about closing:  In 1.12.4-2, thanks to Will for the analysis
Comment by nerdix (nerdix) - Friday, 13 March 2015, 14:03 GMT
I just grabbed the PKGBUILD from AUR and recompiled with --with-gtk3=no and --with-gtk2=yes and the resulting packages works!
So the issue is GTK3 related.
Comment by Will Dietz (dtzWill) - Saturday, 14 March 2015, 16:13 GMT
I'm also encountering this issue, but am not having success with a gtk2 version.

Using wireshark-gtk2 from AUR[1] (which includes the configure flags mentioned) still results
in a binary that segfaults.

I don't have a good explanation for that behavior as compared to what was previously reported.

Regardless, some digging shows this is a rather common issue on many other platforms and distributions
such as Redhat[2], OSX[3], and FreeBSD[4].

They all observe the same behavior on 1.12.3 and 1.12.4, and interestingly the FreeBSD bug
has folks mentioning running a later broken version prevents previously-working earlier versions
from working. Not quite sure what would cause this but might explain the differences in results
with a rebuild against gtk2. Dunno.

Anyway, the good news is they all have been resolved with the same patch to 'configure',
which I've adapted to modify 'configure.ac' instead (since we regenerate 'configure').

This fixes the issue locally and given the prevelance of the issue and shared solution
I suspect will fix it for us as well but encourage further testing as appropriate.

Patch and updated PKGBUILD applying it are attached.

~Will


[1] https://aur.archlinux.org/packages/wireshark-gtk2/
[2] https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=1187978
[3] https://trac.macports.org/ticket/46850
[4] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195980
   PKGBUILD (3.2 KiB)
   configure-pixmap-fix.diff (0.7 KiB)
Comment by Timothy Redaelli (tredaelli) - Monday, 16 March 2015, 11:52 GMT
Since I'm not able to reproduce this problem (1.12.4-1 works without any problem in my x86_64 PCs), can you test the 1.12.4-2 version?
Comment by Will Dietz (dtzWill) - Monday, 16 March 2015, 15:03 GMT
Works great for me, thanks!
Comment by nerdix (nerdix) - Monday, 16 March 2015, 15:29 GMT
I confirm the new 1.12.4-2 package from the communtity repo works now! Thanks for fixing!

Loading...