Version-Release number of selected component:
cmdline: /usr/bin/java -classpath /usr/share/jitsi/lib/felix.jar:/usr/share/jitsi/sc-bundles/sc-launcher.jar:/usr/share/jitsi/sc-bundles/util.jar:/usr/share/jitsi/lib -Djna.library.path=/usr/share/jitsi/lib/native -Dfelix.config.properties=file:/usr/share/jitsi/lib/felix.client.run.properties -Djava.util.logging.config.file=/usr/share/jitsi/lib/logging.properties -splash:splash.gif net.java.sip.communicator.launcher.SIPCommunicator
runlevel: N 5
var_log_messages: [System Logs]:\n-- Logs begin at Do 2015-02-12 15:40:28 CET, end at Mo 2015-03-09 16:19:24 CET. --
Thread no. 0 (4 frames)
#4 handle_error at xcb_io.c:213
#5 handle_response at xcb_io.c:325
#6 _XEventsQueued at xcb_io.c:364
#7 XEventsQueued at Pending.c:43
Created attachment 999620 [details]
Created attachment 999621 [details]
Created attachment 999622 [details]
Created attachment 999623 [details]
Created attachment 999624 [details]
Created attachment 999625 [details]
Created attachment 999626 [details]
Created attachment 999627 [details]
Created attachment 999628 [details]
Is this always reproducible?
no, it happens sometimes (seemingly random), when Jitsi tries to open a
Ah okay. Do you have the hs_err file for this? The backtrace is unfortunately not of much use.
Sorry, unfortunately I don't have it.
Fair enough. Next time this happens then, can you please save it and then attach the log here? The file should be in the dir that you start the program from.
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'
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
Thank you for reporting this bug and we are sorry it could not be fixed.