Bug 924536

Summary: [abrt] wireshark-gnome-1.8.5-2.fc18: gtk_style_context_get_valist: Process /usr/sbin/wireshark was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Chris <esor.rehpotsirhc>
Component: wiresharkAssignee: Peter Hatina <phatina>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: huzaifas, jsafrane, lemenkov, phatina, rvokal, tsmetana
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:dc741ee58c8c66c7d3b64a3678c4f48af423c32a
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-04-03 07:49: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
File: build_ids
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Chris 2013-03-22 02:33:05 UTC
Description of problem:
Wireshark crashes when attempting to add/modify coloring rules.  

Go to View -> Coloring Rules

Select "New" or "Edit" an existing rule.

Choose "Foreground Color" or "Background Color".  On the next window choose the a color, then hit "select" to back to the previous window/dialogue.   Once "OK" is selected , Wireshark crashes.

I have tried this under kde and gnome using multiple themes, including the defaults.

Version-Release number of selected component:
wireshark-gnome-1.8.5-2.fc18

Additional info:
backtrace_rating: 4
cmdline:        wireshark
crash_function: gtk_style_context_get_valist
executable:     /usr/sbin/wireshark
kernel:         3.8.2-206.fc18.x86_64
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 gtk_style_context_get_valist at gtkstylecontext.c:1428
 #1 gtk_style_context_get at gtkstylecontext.c:1463
 #2 edit_color_filter_ok_cb at color_edit_dlg.c:400
 #3 _g_closure_invoke_va at gclosure.c:840
 #6 gtk_real_button_released at gtkbutton.c:1967
 #7 _g_closure_invoke_va at gclosure.c:840
 #10 gtk_button_button_release at gtkbutton.c:1802
 #12 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:85
 #17 gtk_widget_event_internal at gtkwidget.c:6303
 #18 gtk_widget_event at gtkwidget.c:5960

Comment 1 Chris 2013-03-22 02:33:51 UTC
Created attachment 714241 [details]
File: backtrace

Comment 2 Chris 2013-03-22 02:33:54 UTC
Created attachment 714242 [details]
File: build_ids

Comment 3 Chris 2013-03-22 02:33:55 UTC
Created attachment 714243 [details]
File: cgroup

Comment 4 Chris 2013-03-22 02:33:58 UTC
Created attachment 714244 [details]
File: core_backtrace

Comment 5 Chris 2013-03-22 02:34:00 UTC
Created attachment 714245 [details]
File: dso_list

Comment 6 Chris 2013-03-22 02:34:02 UTC
Created attachment 714246 [details]
File: environ

Comment 7 Chris 2013-03-22 02:34:04 UTC
Created attachment 714247 [details]
File: limits

Comment 8 Chris 2013-03-22 02:34:06 UTC
Created attachment 714248 [details]
File: maps

Comment 9 Chris 2013-03-22 02:34:08 UTC
Created attachment 714249 [details]
File: open_fds

Comment 10 Chris 2013-03-22 02:34:10 UTC
Created attachment 714250 [details]
File: proc_pid_status

Comment 11 Chris 2013-03-22 02:34:12 UTC
Created attachment 714251 [details]
File: var_log_messages

Comment 12 Peter Hatina 2013-04-03 07:49:36 UTC
Can not reproduce this, using:

wireshark-1.8.6-4.fc18.x86_64
wireshark-gnome-1.8.6-4.fc18.x86_64

Works as expected. The fix was done by reverting wireshark-gnome back to gtk2.

If you are using older wireshark, please update.

Closing.