Digikam ver. 2.6.0 crashing
Locked
 
|
I'm running ver. 2.6.0, updated today (build Jun 6 2012, target:
Debian), with KDE 4.8.3, on Kubuntu Linux 12.04. Before this update, I was running the previous version from Phillip's PPA, and uploading lots of images to Picasa without issue. Now, it crashes consistently after my account is verified and I ask for the update to begin. Getting this to work is critical, as any other way of uploading to Picasa fails to pick up image captions and descriptions. Anyone else having this problem? Any ideas how to fix it? Thanks in advance... Tom ~~~~~~~~~~~~~~~~~ Tom Cloyd, MS MA [hidden email] (435) 272-3332 Cedar City, Utah _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: Digikam ver. 2.6.0 crashing
|
|
It sound like a binary compatibility issue from packages, because
here, it do not crash (compiled by hand). To be sure, please run digiKam through GDB, try to reproduce crash, and get the backtrace as explained here : http://www.digikam.org/drupal/contrib Best Gilles Caulier 2012/6/7 Tom Cloyd <[hidden email]>: > I'm running ver. 2.6.0, updated today (build Jun 6 2012, target: Debian), > with KDE 4.8.3, on Kubuntu Linux 12.04. > > Before this update, I was running the previous version from Phillip's PPA, > and uploading lots of images to Picasa without issue. Now, it crashes > consistently after my account is verified and I ask for the update to begin. > Getting this to work is critical, as any other way of uploading to Picasa > fails to pick up image captions and descriptions. > > Anyone else having this problem? > > Any ideas how to fix it? > > Thanks in advance... > > Tom > ~~~~~~~~~~~~~~~~~ > Tom Cloyd, MS MA > [hidden email] > (435) 272-3332 > Cedar City, Utah > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: Digikam ver. 2.6.0 crashing
|
|
In reply to this post by Tom Cloyd
Are you using packages from my PPA now or some other packages? I could try to reproduce your problem if they are mine and see if there is something I can fix during build. /Philip On Jun 7, 2012 5:39 AM, "Tom Cloyd" <[hidden email]> wrote:
I'm running ver. 2.6.0, updated today (build Jun 6 2012, target: Debian), with KDE 4.8.3, on Kubuntu Linux 12.04. _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
On 06/07/2012 12:33 AM, Philip Johnsson wrote:
Philip & Giles, Thanks for your very prompt response. Philip - yes, I'm using your PPA, and being notified of updates via the Kubuntu 12.04 package manager Muon. I'm now running the jun 7 2012 build, and it's doing the same as yesterday's build. Giles - I barely understood the material at that link you gave me, but understood that I needed to install the debugging package I know Digikam has, and did so, and I now have a backtrace. I tried to follow through with the KDE reporting protocol to report the bug, but as with every other time I've tried to use it just gave up in frustration. It's too complicated and involved, and I just don't have time to wade through all those demands just to give them my backtrace. I'm not a programming professional, and this is just too much. I have a copy of the backtrace and have attached it to this email. I hope that will do for you. If I can help in any additional way, just let me know. Tom _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
digikam-20120607-020602.kcrash (11K)
Re: Digikam ver. 2.6.0 crashing
|
|
From the trace :
#8 0x02100fb0 in QObject::connect (sender=0x3a002f, signal=0xa630d8ab "2gotThumbnail(KUrl,QPixmap)", receiver=0xbfe0634c, method=0xa630d88e "1slotThumbnail(KUrl,QPixmap)", type=Qt::AutoConnection) at kernel/qobject.cpp:2551 #9 0xa63086f6 in KIPIPicasawebExportPlugin::PicasawebReplaceDialog::PicasawebReplaceDialog (this=0xbfe0634c, parent=0xae16a58, _caption=..., _iface=0x3a002f, _src=..., _dest=...) at /build/buildd/digikam-2.6.0/extra/kipi-plugins/picasawebexport/picasawebreplacedialog.cpp:183 #10 0xa6303c2d in KIPIPicasawebExportPlugin::PicasawebWindow::uploadNextPhoto (this=0xae16a58) at /build/buildd/digikam-2.6.0/extra/kipi-plugins/picasawebexport/picasawebwindow.cpp:654 It crash when the connection is done with Qt signal/slot : https://projects.kde.org/projects/extragear/graphics/kipi-plugins/repository/revisions/master/entry/picasawebexport/picasawebreplacedialog.cpp#L182 ... crash appear indeep into Qt... Why ? There is no reason. d->iface is not null, current instance is not null... So it look like a broken BC with Qt... ... or your backtrace is corrupted or uncomplete... Sound like you have get it from KDE crash handler, not GDB from a console. I recommend this last way to get a real suitable GDB backtrace... Gilles Caulier 2012/6/7 Tom Cloyd <[hidden email]>: > On 06/07/2012 12:33 AM, Philip Johnsson wrote: > > Are you using packages from my PPA now or some other packages? I could try > to reproduce your problem if they are mine and see if there is something I > can fix during build. > > /Philip > > On Jun 7, 2012 5:39 AM, "Tom Cloyd" <[hidden email]> wrote: >> >> I'm running ver. 2.6.0, updated today (build Jun 6 2012, target: Debian), >> with KDE 4.8.3, on Kubuntu Linux 12.04. >> >> Before this update, I was running the previous version from Phillip's PPA, >> and uploading lots of images to Picasa without issue. Now, it crashes >> consistently after my account is verified and I ask for the update to begin. >> Getting this to work is critical, as any other way of uploading to Picasa >> fails to pick up image captions and descriptions. >> >> Anyone else having this problem? >> >> Any ideas how to fix it? >> >> Thanks in advance... >> >> Tom >> ~~~~~~~~~~~~~~~~~ >> Tom Cloyd, MS MA >> [hidden email] >> (435) 272-3332 >> Cedar City, Utah >> _______________________________________________ >> Digikam-users mailing list >> [hidden email] >> https://mail.kde.org/mailman/listinfo/digikam-users > > Philip & Giles, > > Thanks for your very prompt response. > > Philip - yes, I'm using your PPA, and being notified of updates via the > Kubuntu 12.04 package manager Muon. I'm now running the jun 7 2012 build, > and it's doing the same as yesterday's build. > > Giles - I barely understood the material at that link you gave me, but > understood that I needed to install the debugging package I know Digikam > has, and did so, and I now have a backtrace. I tried to follow through with > the KDE reporting protocol to report the bug, but as with every other time > I've tried to use it just gave up in frustration. It's too complicated and > involved, and I just don't have time to wade through all those demands just > to give them my backtrace. I'm not a programming professional, and this is > just too much. > > I have a copy of the backtrace and have attached it to this email. I hope > that will do for you. If I can help in any additional way, just let me know. > > Tom Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
In reply to this post by Gilles Caulier-4
Giles,
Returning to my crash problem, here is the terminal input/output for my attempt to get a gdb backtrace. It doesn't appear to be working, and I have no idea what to do about it. I'll follow any instructions you can give me to get this to work. Thanks! tomc@LDT:~$ gdb digikam GNU gdb (Ubuntu/Linaro 7.4-2012.04-0ubuntu2) 7.4-2012.04 Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i686-linux-gnu". For bug reporting instructions, please see: <http://bugs.launchpad.net/gdb-linaro/>... Reading symbols from /usr/bin/digikam...Reading symbols from /usr/lib/debug/usr/bin/digikam...done. done. (gdb) bt No stack. (gdb) digikam Undefined command: "digikam". Try "help". (gdb) run digikam Starting program: /usr/bin/digikam digikam [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1". digikam: Unexpected argument 'digikam'. digikam: Use --help to get a list of available command line options. [Inferior 1 (process 13392) exited with code 0376] (gdb) bt No stack. (gdb) Tom ~~~~~~~~~~~~~~~~~ Tom Cloyd, MS MA [hidden email] (435) 272-3332 Cedar City / St. George, Utah, U.S.A On 06/06/2012 10:47 PM, Gilles Caulier wrote: > It sound like a binary compatibility issue from packages, because > here, it do not crash (compiled by hand). > > To be sure, please run digiKam through GDB, try to reproduce crash, > and get the backtrace as explained here : > > http://www.digikam.org/drupal/contrib > > Best > > Gilles Caulier > > 2012/6/7 Tom Cloyd<[hidden email]>: >> I'm running ver. 2.6.0, updated today (build Jun 6 2012, target: Debian), >> with KDE 4.8.3, on Kubuntu Linux 12.04. >> >> Before this update, I was running the previous version from Phillip's PPA, >> and uploading lots of images to Picasa without issue. Now, it crashes >> consistently after my account is verified and I ask for the update to begin. >> Getting this to work is critical, as any other way of uploading to Picasa >> fails to pick up image captions and descriptions. >> >> Anyone else having this problem? >> >> Any ideas how to fix it? >> >> Thanks in advance... >> >> Tom >> ~~~~~~~~~~~~~~~~~ >> Tom Cloyd, MS MA >> [hidden email] >> (435) 272-3332 >> Cedar City, Utah >> _______________________________________________ >> Digikam-users mailing list >> [hidden email] >> https://mail.kde.org/mailman/listinfo/digikam-users _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: Digikam ver. 2.6.0 crashing
|
|
In gdb you don't type "run digikam" ju just type "run" and digikam
will start and you use digikam as usual until it crash. After the crash you type the "bt" command in gdb. Otherwise you are doing it as you should so far. /Philip On Sun, Jun 10, 2012 at 2:09 AM, Tom Cloyd <[hidden email]> wrote: > Giles, > > Returning to my crash problem, here is the terminal input/output for my > attempt to get a gdb backtrace. It doesn't appear to be working, and I have > no idea what to do about it. I'll follow any instructions you can give me to > get this to work. Thanks! > > tomc@LDT:~$ gdb digikam > GNU gdb (Ubuntu/Linaro 7.4-2012.04-0ubuntu2) 7.4-2012.04 > Copyright (C) 2012 Free Software Foundation, Inc. > License GPLv3+: GNU GPL version 3 or later > <http://gnu.org/licenses/gpl.html> > This is free software: you are free to change and redistribute it. > There is NO WARRANTY, to the extent permitted by law. Type "show copying" > and "show warranty" for details. > This GDB was configured as "i686-linux-gnu". > For bug reporting instructions, please see: > <http://bugs.launchpad.net/gdb-linaro/>... > Reading symbols from /usr/bin/digikam...Reading symbols from > /usr/lib/debug/usr/bin/digikam...done. > done. > (gdb) bt > No stack. > (gdb) digikam > Undefined command: "digikam". Try "help". > (gdb) run digikam > Starting program: /usr/bin/digikam digikam > [Thread debugging using libthread_db enabled] > Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1". > digikam: Unexpected argument 'digikam'. > digikam: Use --help to get a list of available command line options. > [Inferior 1 (process 13392) exited with code 0376] > (gdb) bt > No stack. > (gdb) > > > Tom > ~~~~~~~~~~~~~~~~~ > Tom Cloyd, MS MA > [hidden email] > (435) 272-3332 > Cedar City / St. George, Utah, U.S.A > > > On 06/06/2012 10:47 PM, Gilles Caulier wrote: >> >> It sound like a binary compatibility issue from packages, because >> here, it do not crash (compiled by hand). >> >> To be sure, please run digiKam through GDB, try to reproduce crash, >> and get the backtrace as explained here : >> >> http://www.digikam.org/drupal/contrib >> >> Best >> >> Gilles Caulier >> >> 2012/6/7 Tom Cloyd<[hidden email]>: >>> >>> I'm running ver. 2.6.0, updated today (build Jun 6 2012, target: Debian), >>> with KDE 4.8.3, on Kubuntu Linux 12.04. >>> >>> Before this update, I was running the previous version from Phillip's >>> PPA, >>> and uploading lots of images to Picasa without issue. Now, it crashes >>> consistently after my account is verified and I ask for the update to >>> begin. >>> Getting this to work is critical, as any other way of uploading to Picasa >>> fails to pick up image captions and descriptions. >>> >>> Anyone else having this problem? >>> >>> Any ideas how to fix it? >>> >>> Thanks in advance... >>> >>> Tom >>> ~~~~~~~~~~~~~~~~~ >>> Tom Cloyd, MS MA >>> [hidden email] >>> (435) 272-3332 >>> Cedar City, Utah >>> _______________________________________________ >>> Digikam-users mailing list >>> [hidden email] >>> https://mail.kde.org/mailman/listinfo/digikam-users > > > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
In reply to this post by Gilles Caulier-4
Gilles, Philip,
Philip - thanks for the correction on how to use gdb. It worked perfectly (I think!). Gilles, I've pasted the backtrace to the bottom of this page. I also have kept the entire terminal output, if you need to look at what was going on before the trace. As stated before, what I'm doing immediately before the crash is this: 1. I have tagged two photos to upload to my Picasa account. 2. Selecting "tags" in the icon strip on the far left of the page, I locate the images. 3. From the main menu I select Export > Export to Picasa web. 4. I log into my account, then click the Start Upload button. The crash then occurs. If I can provide an additional information I'd be more than happy to. This is the ONLY difficulty I've had with Digikam, in several long day of working with it (I think it's an amazing program, by the way...) Thanks for your help! Tom ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Tom Cloyd / [hidden email] / (435) 272-3332 On 06/06/2012 10:47 PM, Gilles Caulier wrote: > It sound like a binary compatibility issue from packages, because > here, it do not crash (compiled by hand). > > To be sure, please run digiKam through GDB, try to reproduce crash, > and get the backtrace as explained here : > > http://www.digikam.org/drupal/contrib > > Best > > Gilles Caulier > > 2012/6/7 Tom Cloyd<[hidden email]>: >> I'm running ver. 2.6.0, updated today (build Jun 6 2012, target: Debian), >> with KDE 4.8.3, on Kubuntu Linux 12.04. >> >> Before this update, I was running the previous version from Phillip's PPA, >> and uploading lots of images to Picasa without issue. Now, it crashes >> consistently after my account is verified and I ask for the update to begin. >> Getting this to work is critical, as any other way of uploading to Picasa >> fails to pick up image captions and descriptions. >> >> Anyone else having this problem? >> >> Any ideas how to fix it? >> >> Thanks in advance... >> >> Tom >> ~~~~~~~~~~~~~~~~~ >> Tom Cloyd, MS MA >> [hidden email] >> (435) 272-3332 >> Cedar City, Utah >> _______________________________________________ >> Digikam-users mailing list >> [hidden email] >> https://mail.kde.org/mailman/listinfo/digikam-users 0x00000000 in ?? () (gdb) bt #0 0x00000000 in ?? () #1 0x02cd1fb0 in QObject::connect (sender=0x316a490, signal=0xa69028ab "2gotThumbnail(KUrl,QPixmap)", receiver=0xbfffdd8c, method=0xa690288e "1slotThumbnail(KUrl,QPixmap)", type=Qt::AutoConnection) at kernel/qobject.cpp:2551 #2 0xa68fd6f6 in KIPIPicasawebExportPlugin::PicasawebReplaceDialog::PicasawebReplaceDialog (this=0xbfffdd8c, parent=0xd246180, _caption=..., _iface=0x316a490, _src=..., _dest=...) at /build/buildd/digikam-2.6.0/extra/kipi-plugins/picasawebexport/picasawebreplacedialog.cpp:183 #3 0xa68f8c2d in KIPIPicasawebExportPlugin::PicasawebWindow::uploadNextPhoto (this=0xd246180) at /build/buildd/digikam-2.6.0/extra/kipi-plugins/picasawebexport/picasawebwindow.cpp:654 #4 0xa68fa985 in KIPIPicasawebExportPlugin::PicasawebWindow::slotListPhotosDoneForUpload (this=0xd246180, errCode=0, errMsg=..., photosList=...) at /build/buildd/digikam-2.6.0/extra/kipi-plugins/picasawebexport/picasawebwindow.cpp:473 #5 0x02cd06b1 in QMetaObject::activate (sender=0xda92db8, m=0xa69077f8, local_signal_index=5, argv=0xbfffe0a0) at kernel/qobject.cpp:3547 #6 0xa68e4455 in KIPIPicasawebExportPlugin::PicasawebTalker::signalListPhotosDone (this=0xda92db8, _t1=0, _t2=..., _t3=...) at /build/buildd/digikam-2.6.0/obj-i686-linux-gnu/extra/kipi-plugins/picasawebexport/picasawebtalker.moc:176 #7 0xa68ec2d8 in KIPIPicasawebExportPlugin::PicasawebTalker::parseResponseListPhotos (this=0xda92db8, data=...) at /build/buildd/digikam-2.6.0/extra/kipi-plugins/picasawebexport/picasawebtalker.cpp:879 #8 0xa68ed6ef in KIPIPicasawebExportPlugin::PicasawebTalker::slotResult (this=0xda92db8, job=0xd0c5b10) at /build/buildd/digikam-2.6.0/extra/kipi-plugins/picasawebexport/picasawebtalker.cpp:659 #9 0x02cd06b1 in QMetaObject::activate (sender=0xd0c5b10, m=0x2b354ac, local_signal_index=3, argv=0xbfffe448) at kernel/qobject.cpp:3547 #10 0x02985425 in KJob::result (this=0xd0c5b10, _t1=0xd0c5b10) at ./kjob.moc:208 #11 0x02985478 in KJob::emitResult (this=0xd0c5b10) at ../../kdecore/jobs/kjob.cpp:318 #12 0x01730328 in KIO::SimpleJob::slotFinished (this=0xd0c5b10) at ../../kio/kio/job.cpp:494 #13 0x0173942d in KIO::TransferJob::slotFinished (this=0xd0c5b10) at ../../kio/kio/job.cpp:1081 #14 0x017379e8 in qt_static_metacall (_a=0xbfffe6c0, _id=7, _o=0xd0c5b10, _c=<optimized out>) at ./jobclasses.moc:388 #15 KIO::TransferJob::qt_static_metacall (_o=0xd0c5b10, _c=QMetaObject::InvokeMetaMethod, _id=7, _a=0xbfffe6c0) at ./jobclasses.moc:375 #16 0x02cd06b1 in QMetaObject::activate (sender=0xc1e5038, m=0x1912480, local_signal_index=4, argv=0x0) at kernel/qobject.cpp:3547 #17 0x017eee85 in KIO::SlaveInterface::finished (this=0xc1e5038) at ./slaveinterface.moc:185 #18 0x017f1fa1 in KIO::SlaveInterface::dispatch (this=0xc1e5038, _cmd=104, rawdata=...) at ../../kio/kio/slaveinterface.cpp:172 #19 0x017ee4fa in KIO::SlaveInterface::dispatch (this=0xc1e5038) at ../../kio/kio/slaveinterface.cpp:88 #20 0x017dfb98 in KIO::Slave::gotInput (this=0xc1e5038) at ../../kio/kio/slave.cpp:344 #21 0x017e0200 in KIO::Slave::qt_static_metacall (_o=0xc1e5038, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbfffe980) at ./slave.moc:57 #22 0x02cd06b1 in QMetaObject::activate (sender=0x8776e50, m=0x190f110, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3547 #23 0x016faeb5 in KIO::Connection::readyRead (this=0x8776e50) at ./connection.moc:106 #24 0x016fb72a in dequeue (this=<optimized out>) at ../../kio/kio/connection.cpp:82 #25 KIO::ConnectionPrivate::dequeue (this=0xc8a0d30) at ../../kio/kio/connection.cpp:71 #26 0x02ccbc01 in QMetaCallEvent::placeMetaCall (this=0xdbcfa60, object=0x8776e50) at kernel/qobject.cpp:525 #27 0x02cd4c7b in QObject::event (this=0x8776e50, e=0xdbcfa60) at kernel/qobject.cpp:1195 #28 0x01ed7ed4 in notify_helper (e=0xdbcfa60, receiver=0x8776e50, this=0x85d7140) at kernel/qapplication.cpp:4559 #29 QApplicationPrivate::notify_helper (this=0x85d7140, receiver=0x8776e50, e=0xdbcfa60) at kernel/qapplication.cpp:4531 #30 0x01edd30d in QApplication::notify (this=0xdbcfa60, receiver=0x8776e50, e=0xdbcfa60) at kernel/qapplication.cpp:4288 #31 0x01b46b61 in KApplication::notify (this=0xbffff280, receiver=0x8776e50, event=0xdbcfa60) at ../../kdeui/kernel/kapplication.cpp:311 #32 0x02cb997e in QCoreApplication::notifyInternal (this=0xbffff280, receiver=0x8776e50, event=0xdbcfa60) at kernel/qcoreapplication.cpp:876 #33 0x02cbdad8 in sendEvent (event=<optimized out>, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #34 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x85889a0) at kernel/qcoreapplication.cpp:1500 #35 0x02cbde0c in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1393 #36 0x02cec494 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236 #37 postEventSourceDispatch (s=0x85cddc0) at kernel/qeventdispatcher_glib.cpp:279 #38 0x0463dd86 in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0 #39 0x0463e125 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #40 0x0463e201 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #41 0x02cec887 in QEventDispatcherGlib::processEvents (this=0x8589520, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #42 0x01f90aaa in QGuiEventDispatcherGlib::processEvents (this=0x8589520, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #43 0x02cb850d in QEventLoop::processEvents (this=0xbffff164, flags=...) at kernel/qeventloop.cpp:149 #44 0x02cb87a9 in QEventLoop::exec (this=0xbffff164, flags=...) at kernel/qeventloop.cpp:204 #45 0x02cbdeba in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148 #46 0x01ed5a74 in QApplication::exec () at kernel/qapplication.cpp:3820 #47 0x080b9460 in main (argc=197262792, argv=0xbc38280) at /build/buildd/digikam-2.6.0/core/digikam/main/main.cpp:232 _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: Digikam ver. 2.6.0 crashing
|
|
It crash always in PicasaWebTool.
Report this trace to KDE bugzilla please... Gilles Caulier 2012/6/14 Tom Cloyd <[hidden email]>: > Gilles, Philip, > > Philip - thanks for the correction on how to use gdb. It worked perfectly (I > think!). > > Gilles, > > I've pasted the backtrace to the bottom of this page. I also have kept the > entire terminal output, if you need to look at what was going on before the > trace. > > As stated before, what I'm doing immediately before the crash is this: > > 1. I have tagged two photos to upload to my Picasa account. > 2. Selecting "tags" in the icon strip on the far left of the page, I locate > the images. > 3. From the main menu I select Export > Export to Picasa web. > 4. I log into my account, then click the Start Upload button. > > The crash then occurs. > > If I can provide an additional information I'd be more than happy to. This > is the ONLY difficulty I've had with Digikam, in several long day of working > with it (I think it's an amazing program, by the way...) > > Thanks for your help! > > Tom > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Tom Cloyd / [hidden email] / (435) 272-3332 > > > On 06/06/2012 10:47 PM, Gilles Caulier wrote: >> >> It sound like a binary compatibility issue from packages, because >> here, it do not crash (compiled by hand). >> >> To be sure, please run digiKam through GDB, try to reproduce crash, >> and get the backtrace as explained here : >> >> http://www.digikam.org/drupal/contrib >> >> Best >> >> Gilles Caulier >> >> 2012/6/7 Tom Cloyd<[hidden email]>: >>> >>> I'm running ver. 2.6.0, updated today (build Jun 6 2012, target: Debian), >>> with KDE 4.8.3, on Kubuntu Linux 12.04. >>> >>> Before this update, I was running the previous version from Phillip's >>> PPA, >>> and uploading lots of images to Picasa without issue. Now, it crashes >>> consistently after my account is verified and I ask for the update to >>> begin. >>> Getting this to work is critical, as any other way of uploading to Picasa >>> fails to pick up image captions and descriptions. >>> >>> Anyone else having this problem? >>> >>> Any ideas how to fix it? >>> >>> Thanks in advance... >>> >>> Tom >>> ~~~~~~~~~~~~~~~~~ >>> Tom Cloyd, MS MA >>> [hidden email] >>> (435) 272-3332 >>> Cedar City, Utah >>> _______________________________________________ >>> Digikam-users mailing list >>> [hidden email] >>> https://mail.kde.org/mailman/listinfo/digikam-users > > Program received signal SIGSEGV, Segmentation fault. > 0x00000000 in ?? () > (gdb) bt > #0 0x00000000 in ?? () > #1 0x02cd1fb0 in QObject::connect (sender=0x316a490, signal=0xa69028ab > "2gotThumbnail(KUrl,QPixmap)", receiver=0xbfffdd8c, method=0xa690288e > "1slotThumbnail(KUrl,QPixmap)", > > type=Qt::AutoConnection) at kernel/qobject.cpp:2551 > #2 0xa68fd6f6 in > KIPIPicasawebExportPlugin::PicasawebReplaceDialog::PicasawebReplaceDialog > (this=0xbfffdd8c, parent=0xd246180, _caption=..., _iface=0x316a490, > _src=..., > _dest=...) at > /build/buildd/digikam-2.6.0/extra/kipi-plugins/picasawebexport/picasawebreplacedialog.cpp:183 > #3 0xa68f8c2d in > KIPIPicasawebExportPlugin::PicasawebWindow::uploadNextPhoto (this=0xd246180) > at > /build/buildd/digikam-2.6.0/extra/kipi-plugins/picasawebexport/picasawebwindow.cpp:654 > #4 0xa68fa985 in > KIPIPicasawebExportPlugin::PicasawebWindow::slotListPhotosDoneForUpload > (this=0xd246180, errCode=0, errMsg=..., photosList=...) > at > /build/buildd/digikam-2.6.0/extra/kipi-plugins/picasawebexport/picasawebwindow.cpp:473 > #5 0x02cd06b1 in QMetaObject::activate (sender=0xda92db8, m=0xa69077f8, > local_signal_index=5, argv=0xbfffe0a0) at kernel/qobject.cpp:3547 > #6 0xa68e4455 in > KIPIPicasawebExportPlugin::PicasawebTalker::signalListPhotosDone > (this=0xda92db8, _t1=0, _t2=..., _t3=...) > at > /build/buildd/digikam-2.6.0/obj-i686-linux-gnu/extra/kipi-plugins/picasawebexport/picasawebtalker.moc:176 > #7 0xa68ec2d8 in > KIPIPicasawebExportPlugin::PicasawebTalker::parseResponseListPhotos > (this=0xda92db8, data=...) > at > /build/buildd/digikam-2.6.0/extra/kipi-plugins/picasawebexport/picasawebtalker.cpp:879 > #8 0xa68ed6ef in KIPIPicasawebExportPlugin::PicasawebTalker::slotResult > (this=0xda92db8, job=0xd0c5b10) > at > /build/buildd/digikam-2.6.0/extra/kipi-plugins/picasawebexport/picasawebtalker.cpp:659 > #9 0x02cd06b1 in QMetaObject::activate (sender=0xd0c5b10, m=0x2b354ac, > local_signal_index=3, argv=0xbfffe448) at kernel/qobject.cpp:3547 > #10 0x02985425 in KJob::result (this=0xd0c5b10, _t1=0xd0c5b10) at > ./kjob.moc:208 > #11 0x02985478 in KJob::emitResult (this=0xd0c5b10) at > ../../kdecore/jobs/kjob.cpp:318 > #12 0x01730328 in KIO::SimpleJob::slotFinished (this=0xd0c5b10) at > ../../kio/kio/job.cpp:494 > #13 0x0173942d in KIO::TransferJob::slotFinished (this=0xd0c5b10) at > ../../kio/kio/job.cpp:1081 > #14 0x017379e8 in qt_static_metacall (_a=0xbfffe6c0, _id=7, _o=0xd0c5b10, > _c=<optimized out>) at ./jobclasses.moc:388 > #15 KIO::TransferJob::qt_static_metacall (_o=0xd0c5b10, > _c=QMetaObject::InvokeMetaMethod, _id=7, _a=0xbfffe6c0) at > ./jobclasses.moc:375 > #16 0x02cd06b1 in QMetaObject::activate (sender=0xc1e5038, m=0x1912480, > local_signal_index=4, argv=0x0) at kernel/qobject.cpp:3547 > #17 0x017eee85 in KIO::SlaveInterface::finished (this=0xc1e5038) at > ./slaveinterface.moc:185 > #18 0x017f1fa1 in KIO::SlaveInterface::dispatch (this=0xc1e5038, _cmd=104, > rawdata=...) at ../../kio/kio/slaveinterface.cpp:172 > #19 0x017ee4fa in KIO::SlaveInterface::dispatch (this=0xc1e5038) at > ../../kio/kio/slaveinterface.cpp:88 > #20 0x017dfb98 in KIO::Slave::gotInput (this=0xc1e5038) at > ../../kio/kio/slave.cpp:344 > #21 0x017e0200 in KIO::Slave::qt_static_metacall (_o=0xc1e5038, > _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbfffe980) at ./slave.moc:57 > #22 0x02cd06b1 in QMetaObject::activate (sender=0x8776e50, m=0x190f110, > local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3547 > #23 0x016faeb5 in KIO::Connection::readyRead (this=0x8776e50) at > ./connection.moc:106 > #24 0x016fb72a in dequeue (this=<optimized out>) at > ../../kio/kio/connection.cpp:82 > #25 KIO::ConnectionPrivate::dequeue (this=0xc8a0d30) at > ../../kio/kio/connection.cpp:71 > #26 0x02ccbc01 in QMetaCallEvent::placeMetaCall (this=0xdbcfa60, > object=0x8776e50) at kernel/qobject.cpp:525 > #27 0x02cd4c7b in QObject::event (this=0x8776e50, e=0xdbcfa60) at > kernel/qobject.cpp:1195 > #28 0x01ed7ed4 in notify_helper (e=0xdbcfa60, receiver=0x8776e50, > this=0x85d7140) at kernel/qapplication.cpp:4559 > #29 QApplicationPrivate::notify_helper (this=0x85d7140, receiver=0x8776e50, > e=0xdbcfa60) at kernel/qapplication.cpp:4531 > #30 0x01edd30d in QApplication::notify (this=0xdbcfa60, receiver=0x8776e50, > e=0xdbcfa60) at kernel/qapplication.cpp:4288 > #31 0x01b46b61 in KApplication::notify (this=0xbffff280, receiver=0x8776e50, > event=0xdbcfa60) at ../../kdeui/kernel/kapplication.cpp:311 > #32 0x02cb997e in QCoreApplication::notifyInternal (this=0xbffff280, > receiver=0x8776e50, event=0xdbcfa60) at kernel/qcoreapplication.cpp:876 > #33 0x02cbdad8 in sendEvent (event=<optimized out>, receiver=<optimized > out>) at > ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 > #34 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, > data=0x85889a0) at kernel/qcoreapplication.cpp:1500 > #35 0x02cbde0c in QCoreApplication::sendPostedEvents (receiver=0x0, > event_type=0) at kernel/qcoreapplication.cpp:1393 > #36 0x02cec494 in sendPostedEvents () at > ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236 > #37 postEventSourceDispatch (s=0x85cddc0) at > kernel/qeventdispatcher_glib.cpp:279 > #38 0x0463dd86 in g_main_context_dispatch () from > /lib/i386-linux-gnu/libglib-2.0.so.0 > #39 0x0463e125 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 > #40 0x0463e201 in g_main_context_iteration () from > /lib/i386-linux-gnu/libglib-2.0.so.0 > #41 0x02cec887 in QEventDispatcherGlib::processEvents (this=0x8589520, > flags=...) at kernel/qeventdispatcher_glib.cpp:424 > #42 0x01f90aaa in QGuiEventDispatcherGlib::processEvents (this=0x8589520, > flags=...) at kernel/qguieventdispatcher_glib.cpp:204 > #43 0x02cb850d in QEventLoop::processEvents (this=0xbffff164, flags=...) at > kernel/qeventloop.cpp:149 > #44 0x02cb87a9 in QEventLoop::exec (this=0xbffff164, flags=...) at > kernel/qeventloop.cpp:204 > #45 0x02cbdeba in QCoreApplication::exec () at > kernel/qcoreapplication.cpp:1148 > #46 0x01ed5a74 in QApplication::exec () at kernel/qapplication.cpp:3820 > #47 0x080b9460 in main (argc=197262792, argv=0xbc38280) at > /build/buildd/digikam-2.6.0/core/digikam/main/main.cpp:232 > Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
«
Return to digikam-users
|
1 view|%1 views
| Free forum by Nabble | Edit this page |