Red Hat Bugzilla – Bug 857598
[abrt] libreoffice-core-126.96.36.199-2.fc17: set_running_flag killed by signal 6 (SIGABRT)
Last modified: 2013-07-31 13:40:35 EDT
Description of problem:
Solo intente abrir writer justo cuando inicializaba el sistema, ya se habia abierto todo solo faltaba la conexion a internet.
Version-Release number of selected component:
libreport version: 2.0.13
cmdline: /usr/lib64/libreoffice/program/soffice.bin --writer '/home/juanman/Documents/MANUAL DE CALIGRAFIA.odt' --splash-pipe=6
Created attachment 613073 [details]
Created attachment 613074 [details]
Created attachment 613075 [details]
Created attachment 613076 [details]
Created attachment 613077 [details]
Created attachment 613078 [details]
Created attachment 613079 [details]
Created attachment 613080 [details]
googletranslate: "Just try to open writer just when initializing the system, had already opened all just missing the Internet connection."
From the backtrace you must have some java extension to LibreOffice installed. What's the output of...
unopkg list && unopkg list --shared && unopkg list --bundled
so we can see the list of extensions.
It appears to be a problem, possibly multithread related, with the java-gcj gui. So you may find that selecting openjdk from tools->options->java in LibreOffice will work better.
Does this fail with any document or just the one specified? If the latter, can you provide this in order to reproduce the problem?
The crash is due to this assertion failing:
g_assert((*java_vm)->GetEnv(java_vm, &tmp.void_env, JNI_VERSION_1_2) == JNI_OK);
Seems to be same as:
The assertion is failing because it's being called from a thread running Gtk+ that is part of LibreOffice, not the JVM. So it returns JNI_EDETACHED and a null environment, which causes a SIGSEGV even if we remove the assertion.
So we need to make the Gtk+ peer handle the fact that it may get a callback from other Gtk+ code if it's being used from a Gtk+ app.
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora
'version' of '17'.
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 prior to Fedora 17's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life.
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 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.
Thank you for reporting this bug and we are sorry it could not be fixed.