Version-Release number of selected component: bijiben-3.14.1-1.fc21 Additional info: reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: bijiben crash_function: bjb_main_view_get_selection_mode executable: /usr/bin/bijiben kernel: 3.17.2-300.fc21.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:1022 #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:3405 #12 biji_item_delete at biji-item.c:292 #17 gtk_widget_dispose at gtkwidget.c:11924 #18 webkit_web_view_dispose at Source/WebKit/gtk/webkit/webkitwebview.cpp:1384 Potential duplicate: bug 1026207
Created attachment 955020 [details] File: backtrace
Created attachment 955021 [details] File: cgroup
Created attachment 955022 [details] File: core_backtrace
Created attachment 955023 [details] File: dso_list
Created attachment 955024 [details] File: environ
Created attachment 955025 [details] File: exploitable
Created attachment 955026 [details] File: limits
Created attachment 955027 [details] File: maps
Created attachment 955028 [details] File: open_fds
Created attachment 955029 [details] File: proc_pid_status
Created attachment 955030 [details] File: var_log_messages
Another user experienced a similar problem: I opened the notes app and then closed it. I did not create a note or type in any text. reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: bijiben crash_function: bjb_main_view_get_selection_mode executable: /usr/bin/bijiben kernel: 3.17.7-300.fc21.x86_64 package: bijiben-3.14.2-1.fc21 reason: bijiben killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1810
*** Bug 1026207 has been marked as a duplicate of this bug. ***
*** Bug 1087043 has been marked as a duplicate of this bug. ***
Another user experienced a similar problem: create a new notes, do nothing then close the process reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: bijiben crash_function: bjb_main_view_get_selection_mode executable: /usr/bin/bijiben kernel: 3.18.3-201.fc21.x86_64 package: bijiben-3.14.2-1.fc21 reason: bijiben killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: I opened GNotes and clicked on "New" to test it out. Then I clicked on X to close it and it closed, but I ended up receiving a problem alert. It did not ask me to save the new notes. reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: bijiben crash_function: bjb_main_view_get_selection_mode executable: /usr/bin/bijiben kernel: 3.19.3-200.fc21.x86_64 package: bijiben-3.14.2-1.fc21 reason: bijiben killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.