Hi all,
We can't release our application because of this problem so I tested
more. Here's some facts about the problem:
* Mitk Workbench doesn't have the problem. It happens only on Linux on
each new releases (commit + make package), even if they are all
based on MITK 2018.04.2. I do not use the "build tree", I use "make
package".
* --Blueberry.clean and deleting ~/.local/share/Imeka produce almost
the same error.
* The paths are right. imagenavigator.so is where the app thinks it is.
* It's clearly related to plugins.db located in ~/.local/share/Imeka.
The first (and only) crash is creating this file. The next run is
doubling its size, to a working condition. A working build simply
creates the file and continue running the application.
* There's no problem on the computer where the package was created.
Even when I delete plugins.db. And even when I delete all
dependencies: Qt, MITK build and our app build. It seems to be
incompatible between 16.04 and 18.04 builds but I'm not sure about
that yet. Overall, this makes the bug really hard to test.
Knowing that the Mitk Workbench is fine and that you added "a few Qt
dependencies" to fix it, can I have more details about what you did? How
did you know which dependencies to add? I can't really add the
imagenavigator plugin "more" than it's already added? How am I supposed
to add them? Moreover, is there a way to have a stacktrace? It's only
complaining about imagenavigator.so but I know that it exists at the
right place! I must be doing something in my app that MITK Workbench
isn't doing and I need to know who the culprint is.
Nil Goyette
Le 2019-06-21 à 04:47, Dinkelacker, Stefan a écrit :
Hi,
we had several of these issues and shortly before the last release.
One had to open the Workbench three times before it continuously
worked afterwards. Most of the issues were Qt related and we could fix
it by adding a few Qt dependencies to our scripts that are actually
meant to be dynamically loaded during runtime. We also noticed that
these issues only occurred when starting MITK out of the build tree
but the installers just worked fine as all binaries are at a single
place.
AFAIK we still didn’t find the actual cause for the Poco-issue but it
never happened in installers. Do you build installers for your clients
or are they using build-tree versions of MITK?
I also see that you use the releases/2018-04 branch instead of the
latest stable tag v2018.04.2. Just a small warning that it may fail
from time to time, even though it should be much more stable than the
master branch, though.
Stefan
*From:*Nil Goyette [mailto:nil.goye...@imeka.ca]
*Sent:* Thursday, June 20, 2019 3:41 PM
*To:* mitk-users@lists.sourceforge.net
*Subject:* [mitk-users] Startup error: ctkPluginException on first run
Hi all,
I upgraded to MITK 2018.04, built linux installers and my users see
this error on the first time they open the application.
0.393! WARNING: Startup error: ctkPluginException: The plugin
"/home/fmorency/softwares/MITK-v2018.04.2-54-gca0a3e57c1-linux-x86_64/bin/plugins/liborg_mitk_gui_qt_imagenavigator.so"
could not be loaded: Cannot load library
/home/fmorency/softwares/MITK-v2018.04.2-54-gca0a3e57c1-linux-x86_64/bin/plugins/liborg_mitk_gui_qt_imagenavigator.so:
(/home/fmorency/softwares/MITK-v2018.04.2-54-gca0a3e57c1-linux-x86_64/bin/plugins/liborg_blueberry_core_expressions.so:
undefined symbol:
_ZN5berry14ElementHandler6CreateEPNS_19ExpressionConverterEPN4Poco3XML7ElementE)
It opens without any problem when they try again. It's happen *only
the first time*. It seems you can't mix MITK 2016.11 and MITK 2018.04.
We tried deleting the temp folder ~/.local/share/Imeka, or using
--Blueberry.clean, but it gives almost the same error as before.
0.437! WARNING: Failed to install plugin
QUrl("file:///home/fmorency/softwares/MITK-v2018.04.2-54-gca0a3e57c1-linux-x86_64/bin/plugins/liborg_mitk_gui_qt_imagenavigator.so"
<file:///\\home\fmorency\softwares\MITK-v2018.04.2-54-gca0a3e57c1-linux-x86_64\bin\plugins\liborg_mitk_gui_qt_imagenavigator.so>)
: ctkPluginException: Failed to install plugin
Caused by: ctkPluginException: The plugin ... *REST IS IDENTICAL*
I guess that renaming the project, from "Imeka" to anything else,
would solve this problem, but we don't really want to change our
company name! Is there a way to avoid this? Asking our users to open
the application twice seems unprofessional.
Nil Goyette
_______________________________________________
mitk-users mailing list
mitk-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mitk-users
