Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-dev: Re: [Wireshark-dev] Possible Bug: Wireshark hangs on File/Save, File/SaveAs, Fil

From: Guy Harris <guy@xxxxxxxxxxxx>
Date: Wed, 01 Aug 2007 12:03:33 -0700
David Gersic wrote:

I can run Wireshark ok, and it seems to work great. I'm a normal
user, so on startup it I'm prompted for root's password. That goes
fine, and it starts and I can capture packets no problem.

Are you running it from the command line or an icon/menu on the desktop? In order to get a core dump, you might have to run it as yourself rather than as root (you *don't* need to run it as root if you're just reading an existing file rather than capturing - and, on some platforms, you can even arrange not to have to run it as root to capture, but I digress...).

The problem happens when I try to use File/Save or File/SaveAs to
save the packets to a file. Wireshark hangs, and has to be killed. I
see the same thing happen with File/Open to open a previously saved file.

Can you run this under strace, and see if it's hanging in a system call?

If you run the "ldd" command on Wireshark, it should report which version of GTK+ it's using. Do you have any other GTK+-based applications that use the same version of GTK+ (e.g., the Gimp or various GNOME applications), and do they have the same problems?

On http://www.wireshark.org/faq.html it says to try to get a core
dump. I tried kill-6 to get a coredump, but while it did get Wireshark
to die, it didn't produce a coredump.

That might be because you're running it as root.  See above.