Description of problem:
Clicking on the "Options" button in the Capture Interfaces dialog causes
wireshark to hang completely.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. open wireshark
2. click Capture->Interfaces
3. click "Options" on any interface in the list
can you please start wireshark from console/terminal and let me know what it
says? also if you can install the debuginfo package and send me a core.dump file.
I am starting it from the terminal, and there is no output. It doesn't crash,
so it doesn't create a core dump file. I have to kill it manually to recover,
or click the X close box and wait for the "this window isn't responding" to pop up.
I still can't reproduce your issue even with wireshark 1.0.3. Can you please retest with the latest version? Also remove ~/.wireshark directory and root/.wireshark
I experienced this "bug" also.
When wireshark starts, a small message window pops up in the upper left corner of the desktop warning the user about running programs as root, and waits for user input (click the "OK" button). The main application window quickly covers it, and the main window won't respond until the user clicks OK on the 1st message window.
Thought I'd post this to save someone else a problem.
Created attachment 325800 [details]
I'm seeing this on Fedora 10 (wireshark 1.0.3-1.fc10) with ~/.wireshark/ removed. I'm attaching the stacktrace from gdb.
I no longer see this issue. I'm currently using 1.0.3-1.fc10.
(In reply to comment #5)
> I'm seeing this on Fedora 10 (wireshark 1.0.3-1.fc10) with ~/.wireshark/
> removed. I'm attaching the stacktrace from gdb.
Are you sure you dismissed the pop-under dialog box that says "Running as user root and group root. This could be dangerous."? It gets me every time, but my original issue was different, only hanging after clicking "Options".
> Are you sure you dismissed the pop-under dialog box...
Yes. I'm not sure how you could see this bug if you don't. With the dialog up, I can't bring up the dialog with the "Options" button. The UI is unresponsive but not frozen.
I also see this issue with wireshark-1.0.5-1.fc10.i386, clicking on any button within the Capture Interfaces window causes wireshark to hang.
Killing the running dumpcap process allows wireshark to continue. Strangely this only happens for certain user accounts on my machine, however I have not been able to determine what is different between working and non-working accounts.
Removing the ~/.wireshark directory makes no difference to this behaviour.
I too faced the same problem.
If you want to start capturing packets using an interface,
then you can follow below procedure.
1. Edit -> preferences -> Capture
You can select the interface name and save it.
Packets can then be captured by pressing 'Start a new live capture' icon.
I just upgraded to FC 10 and running wireshark-1.0.5-1.fc10.i386 I have this problem, too. I started it from the terminal and get no output. If I click on "List the available interfaces" and then select "wlan0" wireshark hangs like everyone else is reporting.
However the workaround in Comment #9 worked for me.
This issue is fixed by the following SIGPIPE patch, as applied to upstream SVN.
Could this patch be applied to the current Fedora package until it's available in an upstream release?
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '9'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 9's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 9 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
This is definitely still an issue in Fedora 10. I haven't tried F11.
This isn't my bug so I can't change the version, it is IS still an issue.
I can confirm it's fixed upstream in the version that's shipped with F11.
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.