Bug 387504 - Crash but No Error message is shown when running the compiled binary for Kexi3.1Alpha
Summary: Crash but No Error message is shown when running the compiled binary for Kexi...
Status: CLOSED INTENTIONAL
Alias: None
Product: KEXI
Classification: Applications
Component: Documentation (show other bugs)
Version: 3.1.0 Alpha
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Kexi Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-12-01 16:09 UTC by Hrishikesh Barman
Modified: 2018-12-15 23:06 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
screenshot of error (41.08 KB, image/png)
2017-12-01 17:01 UTC, Hrishikesh Barman
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Hrishikesh Barman 2017-12-01 16:09:21 UTC
I tried building Kexi Alpha3.1, the build was successful but I was not able to run the binary. Here's the screenshot[https://i.imgur.com/SJM797k.png] of the error I get when I try to run the binary. I suppose there should be a proper error message shown why the crash happened. This is the bug I am reporting this for.

On the otherhand, It shows an error about knotification not configured properly, but that should not stop kexi from starting and I suppose knotification was called in the first place because the error message dialogue was raised.

So either I did some wrong steps in building kexi most probably, nevertheless there should be a proper error message in that dialog box.

Here are the build steps I followed.

I followed the recommended setup and git cloned the sources of kdb, kproperty, kreport and kexi.

After that, I built kdb,kproperty and kreport using the following flag:

$ cmake -H. -B~/kde/build/PACKAGE_NAME_HERE -DCMAKE_INSTALL_PREFIX=~/kde/inst5

After that I did make and make install on all these packages and they were installed in ~/kde/inst5
I installed the other dependencies like GraphViz and doxygen from the package manager and built kexi3.1Alpha using the following command:

$ cmake -H. -B~/kde/build/kexi -DCMAKE_INSTALL_PREFIX=~/kde/inst5 -DCMAKE_PREFIX_PATH=~/kde/inst5

The build was successful, with a warning that the recommended package marble was not included, that's fine because I don't need marble for now.

Now when I run ~/kde/inst5/bin/kexi3.1
I get an error about the breeze icons not found, Kexi is searching for the breeze icons in ~/.local/share/kexi instead of ~/kde/inst5/share/kexi , So I copied the kexi directory from inst5 to the .local one and the error about the icons was gone.

Now there were few more errors about some speech engine, I installed them with my package manager and those errors were gone.

Now I am left with what's in the screenshot I provided in the start.

If there was a proper error message I couldn've done something but I am completely clueless now what to do and how to do.
Comment 1 Jarosław Staniek 2017-12-01 16:57:09 UTC
Thanks for the effort. Because I am not sure this discussion belongs here because this bug tracking system blocks editing of message once one is sent and *actually* what we need here is discussion and work on build instructions. If there is some code feature for Kexi to make in the meantime, we can do that within this bug report.

All I can say if that I've seen this error and it's local environment misconfiguration. Not your fault, it's just complex because modern apps are advanced, share many resources, have many dependencies and assumes specific runtime environment features. Once it's set up on your system you will forget it and just use conveniently.

I propose to continue at https://forum.kde.org/viewtopic.php?f=220&t=143090
Comment 2 Hrishikesh Barman 2017-12-01 17:01:41 UTC
Created attachment 109156 [details]
screenshot of error
Comment 3 Jarosław Staniek 2017-12-11 12:28:36 UTC
Changed category to Docs, it's largely about build instructions. Setting status to NEEDSINFO as we can find some ideas to improve code.
Comment 4 Jarosław Staniek 2018-02-27 12:39:59 UTC
Empty dialog is visible when plugins were not found. The dialog itself was fixed in #389844. But we do not support the images anymore (until there is funding for it). Please use newer versions (3.1 final or 3.2 Alpha).