Summary: | digikam crashes when attempting to stitch panorama | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | aa.ivanov |
Component: | Plugin-Generic-Panorama | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | benjamin.girault, caulier.gilles, Info, mathieu |
Priority: | NOR | Keywords: | drkonqi |
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 4.1.0 | |
Attachments: |
kipi-panorama-tmp-*/* files
gdb session |
Description
aa.ivanov
2014-05-03 15:24:10 UTC
Can you send me your temporary files? On my system, they are located in /tmp/kde-<username>/kipi-panorama-tmp-<something>/. Use your JPEG files for generating the temporary files. (You can send them to me in a private email if you want, or attach them to this report. Created attachment 86580 [details]
kipi-panorama-tmp-*/* files
Attaching tarbal of my temp files.
digiKam 4.0.0 is out : http://www.digikam.org/node/713 Please check if this entry still valid with this new version. Thanks in advance Gilles Caulier It seems that you are using one of the 2014.0 RC version of Hugin. The problem is most probably that the hugin project file parser of the panorama plugin is not handling the "Tpy" and "Tpp" parameters of input files ("i" lines of a pto). Those were introduced in Hugin 2014.0beta1 as translation variables of the picture. Can you downgrade Hugin to at least 2013.0 to confirm the bug? Also, and prior to downgrading, if you can include in the bug report the console (debug) output of the plugin, that help me confirm the bug also. I apologize for the late reply. Here are my updates: @ Gilles Caulier: I'm sorry but I haven't really tried this with digikam 4.0.0. From what I see, I'm convinced this is related to a kipi plugin and its interaction with hugin as Benjamin has suggested. @Benjamin Girault: I did downgrade hugin to 2013.0.0 using the package from fedora's official update repository. It did work out just fine - I was able to complete the wizard and create a panorama file with several different settings and input files. Actually I was completely unable to crash the thing. As you've requested in your last comment, I've run digikam from console and collected the output. I also went ahead and ran the panoramagui command which seems to be what digikam calls. It did not produce any more or any different output. So I'm pasting the digikam output: [andrew@karupin ~]$ digikam Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath) Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath) QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in use, all queries will cease to work. digikam(6496)/KIPI (general) KIPIPanoramaPlugin::PreviewPage::slotAction: Unknown starting action 1 digikam(6496)/KIPI (general) KIPIPanoramaPlugin::PreviewPage::slotAction: Unknown starting action 1 digikam(6496)/KIPI (general) KIPIPanoramaPlugin::PreviewPage::slotAction: Unknown starting action 1 digikam(6496)/KIPI (general) KIPIPanoramaPlugin::PreviewPage::slotAction: Unknown starting action 1 digikam(6496)/KIPI (general) KIPIPanoramaPlugin::PreviewPage::slotAction: Unknown action 1 digikam(6496)/KIPI (general) KIPIPanoramaPlugin::PreviewPage::slotAction: Unknown action 1 digikam(6496)/KIPI (general) KIPIPanoramaPlugin::PreviewPage::slotAction: Unknown action 1 digikam(6496)/KIPI (general) KIPIPanoramaPlugin::PreviewPage::slotAction: Unknown action 1 digikam(6496)/KIPI (general) KIPIPanoramaPlugin::PreviewPage::slotAction: Unknown starting action 2 digikam(6496)/KIPI (general) KIPIPanoramaPlugin::PreviewPage::slotAction: Unknown action 2 digikam(6496)/KIPI (general) KIPIPanoramaPlugin::PreviewPage::slotAction: Unknown starting action 3 digikam(6496)/KIPI (general) KIPIPanoramaPlugin::PreviewPage::slotAction: Unknown action 3 digikam(6496)/KIPI (general) KIPIPanoramaPlugin::PreviewPage::slotAction: Unknown starting action 4 KCrash: Application 'digikam' crashing... KCrash: Attempting to start /usr/libexec/kde4/drkonqi from kdeinit QSocketNotifier: Invalid socket 15 and type 'Read', disabling... QSocketNotifier: Invalid socket 18 and type 'Read', disabling... QSocketNotifier: Invalid socket 22 and type 'Read', disabling... QSocketNotifier: Invalid socket 26 and type 'Read', disabling... QSocketNotifier: Invalid socket 71 and type 'Read', disabling... QSocketNotifier: Invalid socket 77 and type 'Read', disabling... QSocketNotifier: Invalid socket 73 and type 'Read', disabling... QSocketNotifier: Invalid socket 70 and type 'Read', disabling... digikam: Fatal IO error: client killed [andrew@karupin ~]$ Please note both programs rejected '--debug' parameter and their help messages did not mention a way of raising the debug level for these messages. If such a way exists, I'm not familiar with it and I'd need further advise. To debug, follow instructions here : http://www.digikam.org/contrib Gilles Caulier *** Bug 336268 has been marked as a duplicate of this bug. *** Created attachment 87209 [details]
gdb session
Installed debug info packages and ran the gdb commands suggested on the web pages pointed.
Please take a look if any of this is of some use to you.
Hope I didn't miss some step somewhere.
Thank you for the gdb trace. That confirms the reason of the bug, which should be fixed in the git repository. |