Hide Forgot
abrt version: 1.1.18 architecture: x86_64 Attached file: backtrace, 31279 bytes cmdline: wireshark /home/vadim/recordings/Facebook/18_05_fb_vadim_3d_party.cap component: wireshark Attached file: coredump, 70885376 bytes crash_function: IA__gtk_label_new executable: /usr/sbin/wireshark kernel: 2.6.35.13-91.fc14.x86_64 package: wireshark-gnome-1.4.6-1.fc14 rating: 4 reason: Process /usr/sbin/wireshark was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1307035765 uid: 820 How to reproduce ----- 1. Execute wireshark. 2. Open some recording with http traffic. 3. Follow tcp stream. 4. Crash.
Created attachment 502587 [details] File: backtrace
Wireshark got recently updated to wireshark-1.4.7-1.fc14. Please reopen if you still experience this problem.
I don't have permission to reopen this directly, but I experienced the same thing today with 1.4.7-1.fc15 (duplicate backtrace according to ABRT).
Can you provide a .pcap file which makes wireshark to crash?
Package: wireshark-gnome-1.4.7-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. open trace file with wireshark 2. attempt to filter on http.response.code 401 3. whamo!!!!
Rick, No pcap attached?
Package: wireshark-gnome-1.4.10-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.opened a .pcap trace file for analysis 2.follow tcp stream 3.clear filter 4.crashed Comment ----- Don't know if the pcap file is needed for this bugreport,unfortunately I cannot share it. Trace file was on remote server mounted with gvfs (ssh), don't know if relevant.
just a standard http traffic pcap file
I was looking at packets. I had filtered a stream. It actually crashed after I had switched to another virtual desktop. backtrace_rating: 4 Package: wireshark-gnome-1.6.6-1.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne)
Created attachment 584535 [details] File: backtrace
I have had wireshark crash many times. It doesn't seem to matter what the capture is, but it does seem to be related to filtering.
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached 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, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping