[Kde-imaging] [kipiplugins] [Bug 334284] digikam crashes when attempting to stitch panorama

[aa.ivanov at gmail.com]

https://bugs.kde.org/show_bug.cgi?id=334284

--- Comment #6 from aa.ivanov at gmail.com ---
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 at 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 at 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.

-- 
You are receiving this mail because:
You are the assignee for the bug.