Launching on a system with an existing QtGui framework in /Library/Frameworks/
results in a crash, as DT does not explicitly specify to use its own. Moving
it out of /Library/Frameworks/ is a functioning workaround.
The system log says:
"[0x0-0x5a35a3].com.yourcompany.DwarfTherapist[0]: objc[29069]: Class
QCocoaColorPanelDelegate is implemented in both
/Applications/DwarfTherapist.app/Contents/MacOS/../Frameworks/QtGui.framework/Ve
rsions/4/QtGui and /Library/Frameworks/QtGui.framework/Versions/4/QtGui. One of
the two will be used. Which one is undefined."
repeated for each class in QtGui.framework. Then:
"[0x0-0x5a35a3].com.yourcompany.DwarfTherapist[0]: QObject::moveToThread:
Current thread (0x101409a20) is not the object's thread (0x1014b8d50).
Aug 13 17:54:08 Necronomacbook
[0x0-0x5a35a3].com.yourcompany.DwarfTherapist[0]: Cannot move to target thread
(0x101409a20)
Aug 13 17:54:08 Necronomacbook
[0x0-0x5a35a3].com.yourcompany.DwarfTherapist[0]: On Mac OS X, you might be
loading two sets of Qt binaries into the same process. Check that all plugins
are compiled against the right Qt binaries. Export DYLD_PRINT_LIBRARIES=1 and
check that only one set of binaries are being loaded."
This is DT 0.6.12 on OSX 10.6.8 with Developer Tools installed.
Please provide the "run.log" file in the "log" directory of DwarfTherapist
when this error occurred.
2012-Aug-13 18:11:47.421 INFO core Dwarf Therapist "0.6.12" starting normally.
[src/dwarftherapist.cpp:100] (setup_logging)
2012-Aug-13 18:11:47.715 INFO core Loaded 4 views from disk
[src/viewmanager.cpp:128] (reload_views)
2012-Aug-13 18:11:47.783 DEBUG core "redrew views in 67ms"
[src/viewmanager.cpp:160] (draw_views)
2012-Aug-13 18:11:47.795 DEBUG core setting up connections for MainWindow
[src/mainwindow.cpp:105] (MainWindow)
Original issue reported on code.google.com by im.not.u...@gmail.com on 14 Aug 2012 at 1:15
Original issue reported on code.google.com by
im.not.u...@gmail.comon 14 Aug 2012 at 1:15