Bug 191414 - selecting "synchronize images with database" in album drop-down menu causes signal 6 (sigabrt)
Summary: selecting "synchronize images with database" in album drop-down menu causes s...
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Maintenance-Database (show other bugs)
Version: 0.10.0
Platform: Mandriva RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-03 04:40 UTC by kczflea.factory
Modified: 2017-12-16 11:10 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 5.8.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description kczflea.factory 2009-05-03 04:40:11 UTC
Version:           digiKam Version 0.10.0-beta3 Using KDE 4.1.3 (KDE 4.1.3) (using KDE 4.1.3)
OS:                Linux
Installed from:    Mandriva RPMs

Backtrace:

Application: digiKam (digikam), signal SIGABRT
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb4b3c6d0 (LWP 13110)]
[New Thread 0xaf4feb90 (LWP 13163)]
[New Thread 0xafcffb90 (LWP 13162)]
[New Thread 0xb0834b90 (LWP 13143)]
[New Thread 0xb109eb90 (LWP 13136)]
[New Thread 0xb2b1fb90 (LWP 13128)]
[New Thread 0xb3686b90 (LWP 13121)]
[New Thread 0xb3e87b90 (LWP 13120)]
[New Thread 0xb4942b90 (LWP 13111)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6  0xffffe424 in __kernel_vsyscall ()
#7  0xb59b3da0 in raise () from /lib/i686/libc.so.6
#8  0xb59b5808 in abort () from /lib/i686/libc.so.6
#9  0xb68aa445 in qt_message_output () from /usr/lib/libQtCore.so.4
#10 0xb68aa535 in qFatal () from /usr/lib/libQtCore.so.4
#11 0xb68aa59d in qt_assert_x () from /usr/lib/libQtCore.so.4
#12 0x081816fe in ?? ()
#13 0x08181871 in ?? ()
#14 0x08181871 in ?? ()
#15 0x08181871 in ?? ()
#16 0x08181871 in ?? ()
#17 0x08181871 in ?? ()
#18 0x08181871 in ?? ()
#19 0x08181871 in ?? ()
#20 0x08181871 in ?? ()
#21 0x08181871 in ?? ()
#22 0x08181871 in ?? ()
#23 0x08181871 in ?? ()
#24 0x08181871 in ?? ()
#25 0x08181871 in ?? ()
#26 0x08181871 in ?? ()
#27 0x08181871 in ?? ()
#28 0x08181871 in ?? ()
#29 0x08181871 in ?? ()
#30 0x08181871 in ?? ()
#31 0x08181871 in ?? ()
#32 0x08181871 in ?? ()
#33 0x08181871 in ?? ()
#34 0x08181871 in ?? ()
#35 0x08181871 in ?? ()
#36 0x08181871 in ?? ()
#37 0x08181871 in ?? ()
#38 0x08181871 in ?? ()
#39 0x08181871 in ?? ()
#40 0x08181871 in ?? ()
#41 0x08181871 in ?? ()
#42 0x08181871 in ?? ()
#43 0x08181a55 in ?? ()
#44 0x08181baf in ?? ()
#45 0xb69c0c8d in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#46 0xb69c1a95 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#47 0x0817d387 in ?? ()
#48 0x0817d74f in ?? ()
#49 0x0817d8da in ?? ()
#50 0xb69c0c8d in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#51 0xb69c1a95 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#52 0xb723470d in KIO::TransferJob::data () from /usr/lib/libkio.so.5
#53 0xb7235144 in KIO::TransferJob::slotData () from /usr/lib/libkio.so.5
#54 0xb723cdbf in KIO::TransferJob::qt_metacall () from /usr/lib/libkio.so.5
#55 0xb723cf33 in KIO::SpecialJob::qt_metacall () from /usr/lib/libkio.so.5
#56 0xb69c0c8d in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#57 0xb69c1a95 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#58 0xb72f0bc5 in KIO::SlaveInterface::data () from /usr/lib/libkio.so.5
#59 0xb72f38a8 in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.5
#60 0xb72f13aa in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.5
#61 0xb72e36a5 in KIO::Slave::gotInput () from /usr/lib/libkio.so.5
#62 0xb72e3a30 in KIO::Slave::qt_metacall () from /usr/lib/libkio.so.5
#63 0xb69c0c8d in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#64 0xb69c1a95 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#65 0xb7208ce5 in KIO::Connection::readyRead () from /usr/lib/libkio.so.5
#66 0xb720a81b in ?? () from /usr/lib/libkio.so.5
#67 0xb720ae7b in KIO::Connection::qt_metacall () from /usr/lib/libkio.so.5
#68 0xb69b9b8a in QMetaCallEvent::placeMetaCall ()
   from /usr/lib/libQtCore.so.4
#69 0xb69bb782 in QObject::event () from /usr/lib/libQtCore.so.4
#70 0xb605efac in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#71 0xb6067205 in QApplication::notify () from /usr/lib/libQtGui.so.4
#72 0xb6f2cb91 in KApplication::notify () from /usr/lib/libkdeui.so.5
#73 0xb69ab853 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#74 0xb69ac535 in QCoreApplicationPrivate::sendPostedEvents ()
   from /usr/lib/libQtCore.so.4
#75 0xb69ac71c in QCoreApplication::sendPostedEvents ()
   from /usr/lib/libQtCore.so.4
#76 0xb69d772d in ?? () from /usr/lib/libQtCore.so.4
#77 0xb53d67ea in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#78 0xb53d9f08 in ?? () from /usr/lib/libglib-2.0.so.0
#79 0xb53da0c8 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#80 0xb69d734a in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#81 0xb60fb95a in ?? () from /usr/lib/libQtGui.so.4
#82 0xb69a9ec3 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#83 0xb69aa081 in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#84 0xb69ac7f2 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#85 0xb605ee14 in QApplication::exec () from /usr/lib/libQtGui.so.4
#86 0x0829c05e in ?? ()
#87 0xb59a05c5 in __libc_start_main () from /lib/i686/libc.so.6
#88 0x0809e5c1 in _start ()

No Plug-ins loaded

Can always reproduce by selecting "Album" in menu list, then selecting "Synchronize images with database".
Comment 1 Andi Clemens 2009-05-09 13:06:03 UTC
I can not confirm this... Can you run digiKam in gdb and see if you get a proper backtrace? This one here is of no use.
If you compiled by yourself, you need to rebuild with debugging symbols. If it is a package, chances are that mandriva delivers packages with debugging information. Please install such an package and give us the new backtrace.

Andi
Comment 2 Andi Clemens 2009-05-24 10:33:11 UTC
Also you are using a very old version of digiKam (must be from October 2008 I guess). Can you try the latest version (0.10) or even SVN?

Andi
Comment 3 caulier.gilles 2009-06-03 15:52:17 UTC
Last chance to give us a feedback. next time we close this file...

Please give us a fresh report. Thanks in advance

Gilles Caulier
Comment 4 Andi Clemens 2009-06-10 09:43:03 UTC
forwarding from private mail:


Andi:
        
        Don't know whose bug report you are viewing.  This is cut and
        paste from
        the report I sent:
        
        Version:           digiKam Version 0.10.0-beta3 Using KDE 4.1.3
        (KDE
        4.1.3)
        (using KDE 4.1.3)
        OS:                Linux
        Installed from:    Mandriva RPMs
        
        This CLEARLY states I am using version 0.10.---
        
        I also had KDE 4.1.3 installed, but did not like the interface
        and not
        having the ability to configure each desktop.  I am currently
        using KDE
        3.5.
        
        All other installed programs operate properly with either 4.1 or
        3.5.
        
        Also, I am not proficient in ensuring I have all the necessary
        programs
        installed to collect the necessary and proper information you
        need.  If
        you need more information, please let me know which packages I
        need to
        install on my system.  I am trying to provide as much
        information as
        you need. but I need help in doing so.
        
        I recently had to reinstall most of my OS, due to improper
        detection of
        my first IDE Hard drive (now sr0).  This reinstall included the
        digikam
        package as notated above, with the same result.
        
        I am very happy to help you squash this bug, but I also require
        your help to provide to you the necessary information.
        
        Regards,
        
        Chris Zuhn
Comment 5 Andi Clemens 2009-06-10 09:47:58 UTC
Chris,

0.10-beta3 IS a very old version! :-)
0.10-final was released in April 2009 I guess and even this version is becoming old, since digikam-1.0.0-beta1 is already released.

We can not hunt down a bug from such an old, unstable version, since nobody of us is using this anymore of course (and it wouldn't make sense either if chances are that the bug is already fixed in later versions).

I don't think Mandriva only has this old beta3 package of digiKam in its repository?

Gilles,
you use Mandriva? What is the latest version?

Andi
Comment 6 Andi Clemens 2009-06-10 13:53:47 UTC
Please don't sent private mails, if it belongs in bugreports.
I don't know Mandriva, Gilles might know the system a lot better.

Forwarding from private mail:

Andi:  I am using the repositories for 2009.0, i586, as set up by
"EasyUrpmi.zarb.org".  I have tried updating to 2009.1, but it was that
installation that trashed my system.  I then went back to 2009.0, first
from CD, and then the on-line update, to get the latest (or so I
thought!).

I would be more than happy to use digikam 1.0.0----, but I am not at all
proficient at compiling anything :-(  Also, I hesitate to use a "beta"
verison of anything; don't like to be a guinea pig, and besides, my wife
complains I spend too much time at the computer :-).  

Let me know where i can download the latest version, and I will give
that a whirl.  RPM package, preferrably, but, if necessary, I can try to
install from source or other file.

Regards,

Chris Zuhn
Comment 7 caulier.gilles 2009-12-25 20:06:59 UTC
digiKam 1.0.0 is out since few days...

http://www.digikam.org/drupal/node/491

Please try with this version coming with more than 400 bug-fixes.

Thanks in advance

Gilles Caulier
Comment 8 Johannes Wienke 2010-01-08 21:28:30 UTC
I'm closing this bug as the version is very old and there is no new information since half a year. Feel free to reopen this report if necessary.
Comment 9 caulier.gilles 2017-12-16 11:10:17 UTC
This crash is not reproducible use current 5.8.0 pre-release bundle available
here :

https://files.kde.org/digikam/

I close this file now. Re-open it if necessary.

Gilles Caulier