Description of problem: Started a capture on an ath9k wireless interface in monitor mode Version-Release number of selected component: wireshark-gnome-1.12.7-2.fc22 Additional info: reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: /usr/sbin/wireshark crash_function: update_options_table executable: /usr/sbin/wireshark global_pid: 2566 kernel: 4.1.8-200.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1001 Truncated backtrace: Thread no. 1 (10 frames) #0 update_options_table at capture_dlg.c:2406 #1 save_options_cb at capture_dlg.c:2545 #2 _g_closure_invoke_va at gclosure.c:831 #5 gtk_button_do_release at gtkbutton.c:1899 #6 gtk_real_button_released at gtkbutton.c:2017 #11 multipress_released_cb at gtkbutton.c:613 #12 ffi_call_unix64 at ../src/x86/unix64.S:76 #13 ffi_call at ../src/x86/ffi64.c:525 #14 g_cclosure_marshal_generic_va at gclosure.c:1561 #15 _g_closure_invoke_va at gclosure.c:831
Created attachment 1080473 [details] File: backtrace
Created attachment 1080474 [details] File: cgroup
Created attachment 1080475 [details] File: core_backtrace
Created attachment 1080476 [details] File: dso_list
Created attachment 1080477 [details] File: environ
Created attachment 1080478 [details] File: limits
Created attachment 1080479 [details] File: maps
Created attachment 1080480 [details] File: mountinfo
Created attachment 1080481 [details] File: namespaces
Created attachment 1080482 [details] File: open_fds
Created attachment 1080483 [details] File: proc_pid_status
Created attachment 1080484 [details] File: var_log_messages
Worked fine in wireshark-1.12.6-4.fc22.x86_64.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.