Description of problem: Just starting the application for the first time ever Version-Release number of selected component: bijiben-3.17.4-1.fc23 Additional info: reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: bijiben crash_function: biji_manager_note_new_full executable: /usr/bin/bijiben global_pid: 27924 kernel: 4.2.0-0.rc2.git0.1.fc23.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (8 frames) #0 biji_manager_note_new_full at biji-manager.c:876 #1 instanciate_note at provider/biji-import-provider.c:117 #2 go_through_notes_cb at provider/biji-import-provider.c:168 #3 next_async_callback_wrapper at gfileenumerator.c:305 #4 g_task_return_now at gtask.c:1106 #5 complete_in_idle_cb at gtask.c:1120 #9 g_main_context_iteration at gmain.c:3869 #10 g_application_run at gapplication.c:2311
Created attachment 1055684 [details] File: backtrace
Created attachment 1055685 [details] File: cgroup
Created attachment 1055686 [details] File: core_backtrace
Created attachment 1055687 [details] File: dso_list
Created attachment 1055688 [details] File: environ
Created attachment 1055689 [details] File: limits
Created attachment 1055690 [details] File: maps
Created attachment 1055691 [details] File: mountinfo
Created attachment 1055692 [details] File: namespaces
Created attachment 1055693 [details] File: open_fds
Created attachment 1055694 [details] File: proc_pid_status
Created attachment 1055695 [details] File: var_log_messages
Another user experienced a similar problem: SEGV when openning bijiben reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/bijiben crash_function: biji_manager_note_new_full executable: /usr/bin/bijiben global_pid: 21337 kernel: 4.2.6-301.fc23.x86_64 package: bijiben-3.18.2-1.fc23 reason: bijiben killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
And another user is experiencing it also. Is anyone going to look into this problem?
This is easily reproducible: 1. execute bijiben --new-note 2. close the new note window 3. It segfaults. Always. When this will be fixed please?
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 '23'. 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 23 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 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.
cannot reproduce in f27