Description of problem: Reproducible : Always Steps to Reproduce: 1 - Launch bijiben 2 - Create a new empty note 3 - Quit bijiben 4 - Crash occurs Version-Release number of selected component: bijiben-3.16.0-1.fc22 Additional info: reporter: libreport-2.5.0 backtrace_rating: 4 cmdline: bijiben crash_function: bjb_main_view_get_selection_mode executable: /usr/bin/bijiben global_pid: 12078 kernel: 4.0.0-0.rc4.git0.1.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 bjb_main_view_get_selection_mode at bjb-main-view.c:799 #1 populate_main_toolbar at bjb-main-toolbar.c:988 #2 _g_closure_invoke_va at gclosure.c:831 #5 bjb_window_base_switch_to at bjb-window-base.c:609 #6 just_switch_to_main_view at bjb-note-view.c:158 #7 on_note_trashed at bjb-note-view.c:165 #11 g_signal_emit_by_name at gsignal.c:3401 #12 biji_item_delete at biji-item.c:292 #17 gtk_widget_dispose at gtkwidget.c:11962 #18 webkit_web_view_dispose at Source/WebKit/gtk/webkit/webkitwebview.cpp:1384 Potential duplicate: bug 1026207
Created attachment 1007691 [details] File: backtrace
Created attachment 1007692 [details] File: cgroup
Created attachment 1007693 [details] File: core_backtrace
Created attachment 1007694 [details] File: dso_list
Created attachment 1007695 [details] File: environ
Created attachment 1007696 [details] File: limits
Created attachment 1007697 [details] File: maps
Created attachment 1007698 [details] File: mountinfo
Created attachment 1007699 [details] File: namespaces
Created attachment 1007700 [details] File: open_fds
Created attachment 1007701 [details] File: proc_pid_status
Created attachment 1007702 [details] File: var_log_messages
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.