Bug 541377 - [abrt] crash detected in wireshark-gnome-1.2.2-1.fc12
Summary: [abrt] crash detected in wireshark-gnome-1.2.2-1.fc12
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: wireshark
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Radek Vokál
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:c5d71e2726077f704ca737c5cf1...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-11-25 18:08 UTC by Erik Johnson
Modified: 2010-06-14 11:22 UTC (History)
1 user (show)

Fixed In Version: wireshark-1.2.9-1
Clone Of:
Environment:
Last Closed: 2010-06-14 11:22:36 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (12.40 KB, text/plain)
2009-11-25 18:08 UTC, Erik Johnson 		no flags Details
Backtrace from wireshark-gnome-1.2.4-1.fc12.x86_64 (installed from updates-testing repo) (14.47 KB, text/plain)
2009-12-04 22:53 UTC, Erik Johnson 		no flags Details
View All

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
Note You need to log in before you can comment on or make changes to this bug.