wireshark crashed with SIGSEGV

[Martin Olsson]

Binary package hint: wireshark

crash

steps to reproduce this bug (these steps usually work the first time I try it after boot but if I repeat them they don't work):
1. open wireshark using the Applications::Internet::Wireshark shortcut
2. inside wireshark, select Capture::Interfaces
3. dialog doesn't show any interfaces; close it using top-left X button
4. close wireshark using top-left X button
5. wireshark consumes 100% CPU for 20-30 secs on a quad core 2.8ghz
6. wireshark hits SEGV

also note that if I run "sudo wireshark" from a terminal, then I do see a lot of interfaces listed but then wireshark also shows a dialog on startup saying "running as root, this could be dangerous" so it's supposed to be able to list interfaces without having root access.

ProblemType: Crash
Architecture: amd64
Date: Sat Jan 30 17:33:19 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/wireshark
Package: wireshark 1.2.5-1
ProcCmdline: wireshark
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-12.16-generic
SegvAnalysis: Failure: Unknown offset literal: [r13+0x0]
Signal: 11
SourcePackage: wireshark
Stacktrace:
 #0 0x00007f55f92a504e in ?? () from /usr/lib/gtk-2.0/modules/libgail.so
 No symbol table info available.
 Cannot access memory at address 0x7fffeee724d8
StacktraceTop: ?? () from /usr/lib/gtk-2.0/modules/libgail.so
ThreadStacktrace:
 .
 Thread 1 (Thread 4345):
 #0 0x00007f55f92a504e in ?? () from /usr/lib/gtk-2.0/modules/libgail.so
 No symbol table info available.
 Cannot access memory at address 0x7fffeee724d8
Title: wireshark crashed with SIGSEGV
Uname: Linux 2.6.32-12-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop: gail_combo_real_initialize (obj=0x7f560a1f4520,

[Evan Huus (eapache)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running apport-collect <bug #> and any other logs that are relevant for this particular issue.

[Launchpad Janitor (janitor)]

[Expired for wireshark (Ubuntu) because there has been no activity for 60 days.]