Re: NEW: graphics/digikam [4/4 digikam 5]
*ping* after independent test On Sun Jun 17, 2018 at 09:31:51PM -0300, Elias M. Mariani wrote: > The application starts OK with the new revision of qtwebkit. > I did not test the functionality, might be some bugs in there... > No big errors in the console. > > I think its OK to replace the old version of digikam. > > Cheers. > Elias. > > 2018-06-16 4:02 GMT-03:00 Rafael Sadowski : > > Please update qtwebkit and everything should be back to normal. > > > > On Sun Jun 10, 2018 at 09:23:52PM -0300, Elias M. Mariani wrote: > >> No good. > >> Couldn't get digikam to work. > >> This one will be hard to crack. > >> > >> Cheers. > >> Elias. > >> > >> 2018-06-09 21:37 GMT-03:00 Elias M. Mariani : > >> > Well, after applying the patch to graphics/opencv, > >> > Compiling that beast of code. > >> > Then compiling the mega-beast of code that is digikam... > >> > I return with a "No OK". > >> > At least in this machine where I run the tests. > >> > Even worst, I do not have much to help debug... > >> > > >> > After the "loading cameras..." splash screen the application goes > >> > down, attached you will find the output of the console, after the last > >> > line the application just closes. > >> > > >> > It might be a problem with how I applied the patch for OpenCV, so I > >> > will compile one more time the beasts... I hate Digikam so much... So > >> > wait for a further report but probably the problem is elsewhere. > >> > > >> > Cheers. > >> > Elias. > >> >
Re: NEW: graphics/digikam [4/4 digikam 5]
The application starts OK with the new revision of qtwebkit. I did not test the functionality, might be some bugs in there... No big errors in the console. I think its OK to replace the old version of digikam. Cheers. Elias. 2018-06-16 4:02 GMT-03:00 Rafael Sadowski : > Please update qtwebkit and everything should be back to normal. > > On Sun Jun 10, 2018 at 09:23:52PM -0300, Elias M. Mariani wrote: >> No good. >> Couldn't get digikam to work. >> This one will be hard to crack. >> >> Cheers. >> Elias. >> >> 2018-06-09 21:37 GMT-03:00 Elias M. Mariani : >> > Well, after applying the patch to graphics/opencv, >> > Compiling that beast of code. >> > Then compiling the mega-beast of code that is digikam... >> > I return with a "No OK". >> > At least in this machine where I run the tests. >> > Even worst, I do not have much to help debug... >> > >> > After the "loading cameras..." splash screen the application goes >> > down, attached you will find the output of the console, after the last >> > line the application just closes. >> > >> > It might be a problem with how I applied the patch for OpenCV, so I >> > will compile one more time the beasts... I hate Digikam so much... So >> > wait for a further report but probably the problem is elsewhere. >> > >> > Cheers. >> > Elias. >>
Re: NEW: graphics/digikam [4/4 digikam 5]
Please update qtwebkit and everything should be back to normal. On Sun Jun 10, 2018 at 09:23:52PM -0300, Elias M. Mariani wrote: > No good. > Couldn't get digikam to work. > This one will be hard to crack. > > Cheers. > Elias. > > 2018-06-09 21:37 GMT-03:00 Elias M. Mariani : > > Well, after applying the patch to graphics/opencv, > > Compiling that beast of code. > > Then compiling the mega-beast of code that is digikam... > > I return with a "No OK". > > At least in this machine where I run the tests. > > Even worst, I do not have much to help debug... > > > > After the "loading cameras..." splash screen the application goes > > down, attached you will find the output of the console, after the last > > line the application just closes. > > > > It might be a problem with how I applied the patch for OpenCV, so I > > will compile one more time the beasts... I hate Digikam so much... So > > wait for a further report but probably the problem is elsewhere. > > > > Cheers. > > Elias. >
Re: NEW: graphics/digikam [4/4 digikam 5]
On Tue Jun 12, 2018 at 11:04:35AM +0200, Marc Espie wrote: > On Tue, Jun 12, 2018 at 07:16:39AM +0200, Rafael Sadowski wrote: > > On Sun Jun 10, 2018 at 09:23:52PM -0300, Elias M. Mariani wrote: > > > No good. > > > Couldn't get digikam to work. > > > This one will be hard to crack. > > > > > > > Thanks for the feedback. > > > > I run in the same trap. This is new, I'm trying to fix it, I need to > > fix it. I need digikam back. > > If this is new, this is likely to be some kind of buffer overflow that > retguard exposes. > It's defiantly new, webkit. Thread 1 received signal SIGTRAP, Trace/breakpoint trap. 0x079d971c05fb in cti_vm_throw () from /usr/local/lib/libQt5WebKit.so.2.1 (gdb) bt #0 0x079d971c05fb in cti_vm_throw () from /usr/local/lib/libQt5WebKit.so.2.1 #1 0x079d971525e7 in JSC::Interpreter::execute(JSC::ProgramExecutable*, JSC::ExecState*, JSC::JSObject*) () from /usr/local/lib/libQt5WebKit.so.2.1 #2 0x079d9726b52e in JSC::evaluate(JSC::ExecState*, JSC::SourceCode const&, JSC::JSValue, JSC::JSValue*) () from /usr/local/lib/libQt5WebKit.so.2.1 #3 0x079d95f83b7d in WebCore::ScriptController::evaluateInWorld(WebCore::ScriptSourceCode const&, WebCore::DOMWrapperWorld*) () from /usr/local/lib/libQt5WebKit.so.2.1 #4 0x079d95f83e06 in WebCore::ScriptController::evaluate(WebCore::ScriptSourceCode const&) () from /usr/local/lib/libQt5WebKit.so.2.1 #5 0x079d96f95511 in WebCore::ScriptElement::executeScript(WebCore::ScriptSourceCode const&) () from /usr/local/lib/libQt5WebKit.so.2.1 #6 0x079d9605e92f in WebCore::HTMLScriptRunner::executePendingScriptAndDispatchEvent(WebCore::PendingScript&) () from /usr/local/lib/libQt5WebKit.so.2.1 #7 0x079d9605e7e4 in WebCore::HTMLScriptRunner::executeParsingBlockingScript() () from /usr/local/lib/libQt5WebKit.so.2.1 #8 0x079d9605f10b in WebCore::HTMLScriptRunner::executeScriptsWaitingForLoad(WebCore::CachedResource*) () from /usr/local/lib/libQt5WebKit.so.2.1 #9 0x079d9605370f in WebCore::HTMLDocumentParser::notifyFinished(WebCore::CachedResource*) () from /usr/local/lib/libQt5WebKit.so.2.1 #10 0x079d960a2453 in WebCore::CachedResource::checkNotify() () from /usr/local/lib/libQt5WebKit.so.2.1 #11 0x079d960f10f9 in WebCore::SubresourceLoader::didFinishLoading(double) () from /usr/local/lib/libQt5WebKit.so.2.1 #12 0x079d9630d2fa in WebCore::QNetworkReplyHandler::finish() () from /usr/local/lib/libQt5WebKit.so.2.1 #13 0x079d9630bb0a in WebCore::QNetworkReplyHandlerCallQueue::flush() () from /usr/local/lib/libQt5WebKit.so.2.1 #14 0x079d9630f40a in WebCore::QNetworkReplyWrapper::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/local/lib/libQt5WebKit.so.2.1 #15 0x079dbc057572 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/local/lib/libQt5Core.so.2.2 #16 0x079d3fbe7dea in QNetworkReply::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/local/lib/libQt5Network.so.2.2 #17 0x079dbc04f952 in QObject::event(QEvent*) () from /usr/local/lib/libQt5Core.so.2.2 #18 0x079ddfef80dc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/local/lib/libQt5Widgets.so.2.2 #19 0x079ddfef96d9 in QApplication::notify(QObject*, QEvent*) () from /usr/local/lib/libQt5Widgets.so.2.2 #20 0x079dbc0200ba in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/local/lib/libQt5Core.so.2.2 #21 0x079dbc0211c7 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/local/lib/libQt5Core.so.2.2 #22 0x079dbc07e987 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /usr/local/lib/libQt5Core.so.2.2 #23 0x079daff7e889 in g_main_dispatch (context=) at gmain.c:3177 #24 g_main_context_dispatch (context=) at gmain.c:3830 #25 0x079daff7ec93 in g_main_context_iterate (context=, block=, dispatch=, self=) at gmain.c:3903 #26 0x079daff7ed73 in g_main_context_iteration (context=0x79d7b329e00, may_block=0) at gmain.c:3964 #27 0x079dbc07e1cb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/local/lib/libQt5Core.so.2.2 #28 0x079dbc020766 in QCoreApplication::processEvents(QFlags) () from /usr/local/lib/libQt5Core.so.2.2 #29 0x079d993448b7 in Digikam::DSplashScreen::setMessage(QString const&) () from /usr/local/lib/libdigikamcore.so.1.0 #30 0x079dd4cd1c04 in Digikam::DigikamApp::setupActions() () from /usr/local/lib/libdigikamgui.so.1.0 #31 0x079dd4cd57b7 in Digikam::DigikamApp::DigikamApp() () from /usr/local/lib/libdigikamgui.so.1.0 #32 0x079b29902fc0 in main ()
Re: NEW: graphics/digikam [4/4 digikam 5]
On Tue, Jun 12, 2018 at 07:16:39AM +0200, Rafael Sadowski wrote: > On Sun Jun 10, 2018 at 09:23:52PM -0300, Elias M. Mariani wrote: > > No good. > > Couldn't get digikam to work. > > This one will be hard to crack. > > > > Thanks for the feedback. > > I run in the same trap. This is new, I'm trying to fix it, I need to > fix it. I need digikam back. If this is new, this is likely to be some kind of buffer overflow that retguard exposes.
Re: NEW: graphics/digikam [4/4 digikam 5]
On Sun Jun 10, 2018 at 09:23:52PM -0300, Elias M. Mariani wrote: > No good. > Couldn't get digikam to work. > This one will be hard to crack. > Thanks for the feedback. I run in the same trap. This is new, I'm trying to fix it, I need to fix it. I need digikam back. > Cheers. > Elias. > > 2018-06-09 21:37 GMT-03:00 Elias M. Mariani : > > Well, after applying the patch to graphics/opencv, > > Compiling that beast of code. > > Then compiling the mega-beast of code that is digikam... > > I return with a "No OK". > > At least in this machine where I run the tests. > > Even worst, I do not have much to help debug... > > > > After the "loading cameras..." splash screen the application goes > > down, attached you will find the output of the console, after the last > > line the application just closes. > > > > It might be a problem with how I applied the patch for OpenCV, so I > > will compile one more time the beasts... I hate Digikam so much... So > > wait for a further report but probably the problem is elsewhere. > > > > Cheers. > > Elias. >
Re: NEW: graphics/digikam [4/4 digikam 5]
No good. Couldn't get digikam to work. This one will be hard to crack. Cheers. Elias. 2018-06-09 21:37 GMT-03:00 Elias M. Mariani : > Well, after applying the patch to graphics/opencv, > Compiling that beast of code. > Then compiling the mega-beast of code that is digikam... > I return with a "No OK". > At least in this machine where I run the tests. > Even worst, I do not have much to help debug... > > After the "loading cameras..." splash screen the application goes > down, attached you will find the output of the console, after the last > line the application just closes. > > It might be a problem with how I applied the patch for OpenCV, so I > will compile one more time the beasts... I hate Digikam so much... So > wait for a further report but probably the problem is elsewhere. > > Cheers. > Elias.
Re: NEW: graphics/digikam [4/4 digikam 5]
Well, after applying the patch to graphics/opencv, Compiling that beast of code. Then compiling the mega-beast of code that is digikam... I return with a "No OK". At least in this machine where I run the tests. Even worst, I do not have much to help debug... After the "loading cameras..." splash screen the application goes down, attached you will find the output of the console, after the last line the application just closes. It might be a problem with how I applied the patch for OpenCV, so I will compile one more time the beasts... I hate Digikam so much... So wait for a further report but probably the problem is elsewhere. Cheers. Elias. digikam.output Description: Binary data
