Bug 1275475

Summary: [abrt] bijiben: poll_for_event(): bijiben killed by SIGABRT
Product: [Fedora] Fedora Reporter: Diogo Campos <diogocamposwd>
Component: bijibenAssignee: Pete Walter <walter.pete>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 23CC: alex.ploumistos, ask.me8, azhchay, chmelarz, ezwen-redhatbugzilla, krzysztofbti, lray+redhatbugzilla, marcvanwageningen, pabloganuza, py, srrosten, vivek.hyperspace, xzj8b3
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/177943a3cd2ae271dae4f20b08955a2415c899ac
Whiteboard: abrt_hash:cff854173b8499f6ea13e143678a5d0595adf4d1;VARIANT_ID=workstation;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-20 15:10:45 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status none

Description Diogo Campos 2015-10-27 02:50:08 UTC 
Version-Release number of selected component:
bijiben-3.18.1-1.fc23

Additional info:
reporter:       libreport-2.6.3
backtrace_rating: 4
cmdline:        bijiben
crash_function: poll_for_event
executable:     /usr/bin/bijiben
global_pid:     2968
kernel:         4.2.3-300.fc23.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (9 frames)
 #4 poll_for_event at xcb_io.c:271
 #5 poll_for_response at xcb_io.c:289
 #6 _XEventsQueued at xcb_io.c:363
 #7 XPending at Pending.c:55
 #8 gdk_check_xpending at gdkeventsource.c:266
 #9 gdk_event_source_check at gdkeventsource.c:303
 #10 g_main_context_check at gmain.c:3681
 #12 g_main_context_iteration at gmain.c:3901
 #13 g_application_run at gapplication.c:2311
Comment 1 Diogo Campos 2015-10-27 02:50:13 UTC 
Created attachment 1086693 [details]
File: backtrace
Comment 2 Diogo Campos 2015-10-27 02:50:15 UTC 
Created attachment 1086694 [details]
File: cgroup
Comment 3 Diogo Campos 2015-10-27 02:50:17 UTC 
Created attachment 1086695 [details]
File: core_backtrace
Comment 4 Diogo Campos 2015-10-27 02:50:19 UTC 
Created attachment 1086696 [details]
File: dso_list
Comment 5 Diogo Campos 2015-10-27 02:50:21 UTC 
Created attachment 1086697 [details]
File: environ
Comment 6 Diogo Campos 2015-10-27 02:50:22 UTC 
Created attachment 1086698 [details]
File: limits
Comment 7 Diogo Campos 2015-10-27 02:50:26 UTC 
Created attachment 1086699 [details]
File: maps
Comment 8 Diogo Campos 2015-10-27 02:50:28 UTC 
Created attachment 1086700 [details]
File: mountinfo
Comment 9 Diogo Campos 2015-10-27 02:50:29 UTC 
Created attachment 1086701 [details]
File: open_fds
Comment 10 Diogo Campos 2015-10-27 02:50:31 UTC 
Created attachment 1086702 [details]
File: proc_pid_status
Comment 11 Pablo Ganuza 2015-11-24 10:24:55 UTC 
Another user experienced a similar problem:

I just wanted to start it.

reporter:       libreport-2.6.3
backtrace_rating: 4
cmdline:        bijiben
crash_function: poll_for_event
executable:     /usr/bin/bijiben
global_pid:     9630
kernel:         4.2.5-300.fc23.x86_64
package:        bijiben-3.18.1-1.fc23
reason:         bijiben killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 12 lray+redhatbugzilla 2016-02-16 08:06:52 UTC 
Similar problem has been detected:

Starting the application in flight mode

reporter:       libreport-2.6.4
backtrace_rating: 4
cmdline:        bijiben
crash_function: poll_for_event
executable:     /usr/bin/bijiben
global_pid:     5128
kernel:         4.3.5-300.fc23.x86_64
package:        bijiben-3.18.2-1.fc23
reason:         bijiben killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 13 Zdenek Chmelar 2016-03-05 16:29:26 UTC 
*** Bug 1315011 has been marked as a duplicate of this bug. ***
Comment 14 Alexander Ploumistos 2016-05-18 17:35:36 UTC 
Similar problem has been detected:

Bijiben just refuses to start.
If I try to start it from the terminal, I don't get any useful information, even with G_MESSAGES_DEBUG=all.

reporter:       libreport-2.6.4
backtrace_rating: 4
cmdline:        bijiben
crash_function: poll_for_event
executable:     /usr/bin/bijiben
global_pid:     12026
kernel:         4.4.9-300.fc23.x86_64
package:        bijiben-3.18.2-1.fc23
reason:         bijiben killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 15 vivek.hyperspace 2016-05-25 12:19:01 UTC 
Similar problem has been detected:

this application often crashes in my system.this application doesnt show up even when i'm try to open for several times

reporter:       libreport-2.6.4
backtrace_rating: 4
cmdline:        bijiben
crash_function: poll_for_event
executable:     /usr/bin/bijiben
global_pid:     15817
kernel:         4.4.9-300.fc23.x86_64
package:        bijiben-3.18.2-1.fc23
reason:         bijiben killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 16 xzj8b3 2016-05-26 21:42:28 UTC 
*** Bug 1340265 has been marked as a duplicate of this bug. ***
Comment 17 Zdenek Chmelar 2016-10-12 22:15:09 UTC 
I do not see any crashes for long time. Bijiben starts well under both X11 and Wayland. I propose to close this issue

bijiben-3.20.2-1.fc24.x86_64
Comment 18 Fedora Admin XMLRPC Client 2016-11-17 21:47:18 UTC 
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 19 Fedora Admin XMLRPC Client 2016-11-17 22:42:34 UTC 
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 20 Fedora End Of Life 2016-11-24 12:56:00 UTC 
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.
Comment 21 Fedora End Of Life 2016-12-20 15:10:45 UTC 
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.