Summary: | Export to facebook crashes | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Thomas Arend <thomas> |
Component: | Plugin-WebService-Facebook | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | caulier.gilles, shouryasgupta, thomas |
Priority: | NOR | Keywords: | drkonqi |
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 4.14.0 | |
Attachments: | New crash information added by DrKonqi |
Description
Thomas Arend
2015-09-12 15:51:49 UTC
The crash backtrace is not complete. Please install kipi-plugins debug package and run digiKam into GDB to get a suitable trace to hack. Gilles Caulier Created attachment 94522 [details]
New crash information added by DrKonqi
digikam (4.13.0) on KDE Platform 4.14.9 using Qt 4.8.6
Crash report now with kipi-plugins-debuginfo. I'm not familiar with GDB and have not the time to change this only for this bug.
-- Backtrace (Reduced):
#5 0x00007fee35514af6 in QVariant::toMap() const () at /usr/lib64/libQtCore.so.4
#6 0x00007fed6afdd781 in KIPIFacebookPlugin::FbTalker::parseExchangeSession(QByteArray const&) (this=this@entry=0x66975e0, data=...) at /usr/src/debug/digikam-4.13.0/extra/kipi-plugins/facebook/fbtalker.cpp:783
#7 0x00007fed6afe487c in KIPIFacebookPlugin::FbTalker::slotResult(KJob*) (this=0x66975e0, kjob=0x6666f40) at /usr/src/debug/digikam-4.13.0/extra/kipi-plugins/facebook/fbtalker.cpp:705
#8 0x00007fed6afe4a2c in KIPIFacebookPlugin::FbTalker::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=<optimized out>, _id=<optimized out>, _a=<optimized out>, _c=<optimized out>) at /usr/src/debug/digikam-4.13.0/build/extra/kipi-plugins/facebook/fbtalker.moc:92
[...]
#10 0x00007fee35985352 in KJob::result(KJob*) () at /usr/lib64/libkdecore.so.5
Hello Thomas Are you sure to have copied and pasted the right URL into the dialog box that pops up ? NOTE : https://www.facebook.com/connect/blank.html#_=_ is not the correct URL to post. The correct URL can be found in the link just previous to the "https://www.facebook.com/connect/blank.html#_=_" in browser history. If above is not the problem, can you please specify the exact steps (every dialog and button you open and click) to reproduce the crash, because facebook does not crash for me. Thanks Shourya (In reply to Shourya Singh Gupta from comment #3) > Hello Thomas > > Are you sure to have copied and pasted the right URL into the dialog box > that pops up ? > > NOTE : https://www.facebook.com/connect/blank.html#_=_ is not the correct > URL to post. The correct URL can be found in the link just previous to the > "https://www.facebook.com/connect/blank.html#_=_" in browser history. > > If above is not the problem, can you please specify the exact steps (every > dialog and button you open and click) to reproduce the crash, because > facebook does not crash for me. > > Thanks > Shourya There is no dialog in which I can type in a URL. Better I am not fast enougth to read the box before digikam crashes. There is no chance to type something in a box. I deleted kipihtmlexportrc and kipirc. Now digikam doesn't crash any more and I got an URL from facebook. It is an little tricky to get the URL because the page is immediately redirected to a security warning and the URL is rewritten. My experience is that a lot of kde programs have problems to migrate configuration files from one release to another release. I have saved the old config files. just in case someone wants to look for the reason of the crashes. |