[Kmymoney-devel] OSX/CI system: KF5-kmymoney build broken on branch frameworks

[Marko Käning]

Hi Cristian,
Hi Ian,

On 22 Jul 2014, at 21:59 , Marko Käning <mk-lists at email.de> wrote:
> That means, KMyMoney’s KF5 port now SUCCESSFULLY BUILT FOR THE 1ST TIME ON OSX!!! :-D

To be fully honest:

	Well, unfortunately I cannot run it successfully:

---
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib              0x00007fff85d44866 __pthread_kill + 10
1   libsystem_pthread.dylib             0x00007fff87cac35c pthread_kill + 92
2   libsystem_c.dylib                   0x00007fff8c638b1a abort + 125
3   libQt5Core_debug.5.dylib            0x0000000110c5aaa8 qt_message_fatal(QtMsgType, QMessageLogContext const&, QString const&) + 24
4   libQt5Core_debug.5.dylib            0x0000000110c5f038 qt_message_output(QtMsgType, QMessageLogContext const&, QString const&) + 72 (qlogging.cpp:1379)
5   libKF5KDELibs4Support.5.dylib       0x0000000112dfd9ce QDebug::~QDebug() + 222 (qdebug.h:92)
6   libKF5KDELibs4Support.5.dylib       0x0000000112df8b85 QDebug::~QDebug() + 21 (qdebug.h:94)
7   libKF5KDELibs4Support.5.dylib       0x0000000112edee28 KApplicationPrivate::init(bool) + 456 (kapplication.cpp:416)
8   libKF5KDELibs4Support.5.dylib       0x0000000112edec02 KApplication::KApplication(bool) + 258 (kapplication.cpp:311)
9   libKF5KDELibs4Support.5.dylib       0x0000000112edeaf5 KApplication::KApplication(bool) + 37 (kapplication.cpp:311)
10                                      0x000000010fa82613 main + 4579 (main.cpp:118)
11  libdyld.dylib                       0x00007fff859d75fd start + 1
---

but this doesn’t surprise me at all, as other KF5 applications have similar problems!
Check out my bug report for kate [1].
There I also mention khelpcenter and konversation which manage to exit *gracefully* _without_ crashing.

KMM still belongs to the crashing apps, since it is silently assuming that dbus is present!

This all is very likely caused by the way my CI system separates all frameworks and applications in their own jails.
It looks as if the access to the dbus socket isn’t properly done, or whatever else… I haven’t investigated that yet.

But it may well be that I only need to finally adapt QStandardsPaths, to avoid other hassle, including the dbus issue.

That will be my next endeavour! :)

But, perhaps you can try to fix KMM so that it doesn’t rely blindly on dbus without checking (as kate obviously does) and bring it thus to a state like khelpcenter or konversation.

Qt's apps (Assistant.app etc.) start without problems, but when I try to start qdbusviewer.app it also says "Error: Cannot connect to D-Bus:" without more details! [1] This might be a not so hard nut for Ian to crack...

Anyway, I am very happy that we got this far already.

Greets,
Marko



[1] https://bugs.kde.org/show_bug.cgi?id=337140#c5




-------------- next part --------------
A non-text attachment was scrubbed...
Name: kmymoney_2014-07-22-220222_MVM2.crash.gz
Type: application/x-gzip
Size: 14162 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kmymoney-devel/attachments/20140722/154e0a2a/attachment-0001.gz>