Bug 541377

Summary: [abrt] crash detected in wireshark-gnome-1.2.2-1.fc12
Product: [Fedora] Fedora Reporter: Erik Johnson <blu3fed0ra>
Component: wiresharkAssignee: Radek Vokál <rvokal>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:c5d71e2726077f704ca737c5cf1f564058db87e3
Fixed In Version: wireshark-1.2.9-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-06-14 11:22:36 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
Backtrace from wireshark-gnome-1.2.4-1.fc12.x86_64 (installed from updates-testing repo) none

Description Erik Johnson 2009-11-25 18:08:21 UTC 
abrt detected a crash.

Comment: This crash happened multiple times when backspacing to edit display filters.
Attached file: backtrace
cmdline: wireshark
component: wireshark
executable: /usr/sbin/wireshark
kernel: 2.6.31.5-127.fc12.x86_64
package: wireshark-gnome-1.2.2-1.fc12
rating: 4
reason: Process was terminated by signal 11
Comment 1 Erik Johnson 2009-11-25 18:08:23 UTC 
Created attachment 373800 [details]
File: backtrace
Comment 2 Radek Vokál 2009-12-01 07:41:24 UTC 
Thanks for the report. Can you try to reproduce this issue with wireshark-1.2.4 from the updates-testing repo?
Comment 3 Erik Johnson 2009-12-04 22:52:30 UTC 
It took awhile to reproduce it, but I was finally able to. I'll attach a backtrace.
Comment 4 Erik Johnson 2009-12-04 22:53:41 UTC 
Created attachment 376233 [details]
Backtrace from wireshark-gnome-1.2.4-1.fc12.x86_64 (installed from updates-testing repo)
Comment 5 Radek Vokál 2009-12-08 15:25:14 UTC 
Thanks, looks like both are same. I'll open an upstream bug and also try to find the cause of the problem.
Comment 6 Radek Vokál 2010-06-14 11:22:36 UTC 
This has been fixed upstream in wireshark-1.2.9