Hide Forgot
Description of problem: Started app for the first time. Version-Release number of selected component: bijiben-3.20.0-2.fc24 Additional info: reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: bijiben crash_function: dequeue_pending_request executable: /usr/bin/bijiben global_pid: 4235 kernel: 4.5.0-302.fc24.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #4 dequeue_pending_request at xcb_io.c:177 #6 _XkbHandleGetMapReply at XKBGetMap.c:562 #7 XkbGetUpdatedMap at XKBGetMap.c:584 #8 XkbGetMap at XKBGetMap.c:603 #9 get_xkb at gdkkeys-x11.c:212 #10 update_direction at gdkkeys-x11.c:580 #11 _gdk_x11_keymap_state_changed at gdkkeys-x11.c:650 #12 gdk_x11_display_translate_event at gdkdisplay-x11.c:1064 #13 _gdk_x11_event_translator_translate at gdkeventtranslator.c:51 #14 _gdk_x11_display_queue_events at gdkeventsource.c:245 Potential duplicate: bug 1252950
Created attachment 1145745 [details] File: backtrace
Created attachment 1145746 [details] File: cgroup
Created attachment 1145747 [details] File: core_backtrace
Created attachment 1145748 [details] File: dso_list
Created attachment 1145749 [details] File: environ
Created attachment 1145750 [details] File: limits
Created attachment 1145751 [details] File: maps
Created attachment 1145752 [details] File: mountinfo
Created attachment 1145753 [details] File: namespaces
Created attachment 1145754 [details] File: open_fds
Created attachment 1145755 [details] File: proc_pid_status
Created attachment 1145756 [details] File: var_log_messages
Similar problem has been detected: I was starting Bijiben from GNOME Shell. reporter: libreport-2.7.1 backtrace_rating: 4 cmdline: bijiben crash_function: dequeue_pending_request executable: /usr/bin/bijiben global_pid: 13256 kernel: 4.5.7-300.fc24.x86_64 package: bijiben-3.20.2-1.fc24 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project reason: bijiben killed by SIGABRT reproducible: Not sure how to reproduce the problem runlevel: N 5 type: CCpp uid: 1000
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Similar problem has been detected: The application failed at start. reporter: libreport-2.7.2 backtrace_rating: 4 cmdline: bijiben crash_function: dequeue_pending_request executable: /usr/bin/bijiben global_pid: 18535 kernel: 4.9.6-100.fc24.x86_64 package: bijiben-3.20.2-1.fc24 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project reason: bijiben killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.