Bug 97783 - Digikam crashes after deleting pictures
Summary: Digikam crashes after deleting pictures
Status: RESOLVED WORKSFORME
Alias: None
Product: digikam
Classification: Applications
Component: Database-Trash (show other bugs)
Version: 0.7.1
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-01-24 10:28 UTC by lrathle
Modified: 2022-01-23 09:17 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 7.6.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description lrathle 2005-01-24 10:29:00 UTC
Version:           0.7.1 (using KDE KDE 3.3.2)
Installed from:    Compiled From Sources
Compiler:          gcc-3.4.1-3mdk 
OS:                Linux

My camera : Nikon D70

I've deleted 178 pictures from my camera. It took me twice to succeed. The first time Digikam crashed before deleting the pictures. The second time it crashed just after I quit the camera gui and when I switched off my camera.

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 1101093024 (LWP 9155)]
[KCrash handler]
#7  0xca70c040 in ?? ()
#8  0x40be0af8 in QPixmap::deref () from /usr/lib/qt3/lib/libqt-mt.so.3
#9  0x08571b30 in ?? ()
#10 0x41314b20 in __after_morecore_hook () from /lib/tls/libc.so.6
#11 0x085630a0 in ?? ()
#12 0x41314b20 in __after_morecore_hook () from /lib/tls/libc.so.6
#13 0x410fbaa8 in ?? () from /usr/lib/qt3/lib/libqt-mt.so.3
#14 0x08563100 in ?? ()
#15 0x080facc0 in ?? ()
#16 0x40ca70ed in QPixmap::~QPixmap () from /usr/lib/qt3/lib/libqt-mt.so.3
#17 0x08563100 in ?? ()
#18 0x410fbaa8 in ?? () from /usr/lib/qt3/lib/libqt-mt.so.3
#19 0x084a4d98 in ?? ()
#20 0x401811ae in QCache<QPixmap>::deleteItem () from /usr/lib/libdigikam.so.0
#21 0x40f681f3 in QGCache::makeRoomFor () from /usr/lib/qt3/lib/libqt-mt.so.3
#22 0x08563100 in ?? ()
#23 0x084a4d98 in ?? ()
#24 0x410fbaa8 in ?? () from /usr/lib/qt3/lib/libqt-mt.so.3
#25 0xbffff024 in ?? ()
#26 0x0855e888 in ?? ()
#27 0x0000d458 in ?? ()
#28 0x410fbaa8 in ?? () from /usr/lib/qt3/lib/libqt-mt.so.3
#29 0x00013a82 in ?? ()
#30 0x080facc0 in ?? ()
#31 0x00100000 in ?? ()
#32 0x40f68337 in QGCache::setMaxCost () from /usr/lib/qt3/lib/libqt-mt.so.3
#33 0x080facc0 in ?? ()
#34 0x000068d6 in ?? ()
#35 0xffffffff in ?? ()
#36 0x08159550 in ?? ()
#37 0x410fbaa8 in ?? () from /usr/lib/qt3/lib/libqt-mt.so.3
#38 0x080facc0 in ?? ()
#39 0x080fac98 in ?? ()
#40 0x40ca9f2b in QPMCache::timerEvent () from /usr/lib/qt3/lib/libqt-mt.so.3
#41 0x080facc0 in ?? ()
#42 0x00013a82 in ?? ()
#43 0x01332b48 in ?? ()
#44 0x410fbaa8 in ?? () from /usr/lib/qt3/lib/libqt-mt.so.3
#45 0x080fac98 in ?? ()
#46 0xbffff390 in ?? ()
#47 0x080fac98 in ?? ()
#48 0x40c92b05 in QObject::event () from /usr/lib/qt3/lib/libqt-mt.so.3
#49 0x080fac98 in ?? ()
#50 0xbffff390 in ?? ()
#51 0xbffff090 in ?? ()
#52 0x410fbaa8 in ?? () from /usr/lib/qt3/lib/libqt-mt.so.3
#53 0x410fbaa8 in ?? () from /usr/lib/qt3/lib/libqt-mt.so.3
#54 0x0812c938 in ?? ()
#55 0xbffff390 in ?? ()
#56 0x40c30015 in QApplication::internalNotify ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#57 0x080fac98 in ?? ()
#58 0xbffff390 in ?? ()
#59 0xbffff390 in ?? ()
#60 0x411ae871 in operator delete () from /usr/lib/libstdc++.so.6
Comment 1 Renchi Raju 2005-01-28 23:28:17 UTC
can you compile with debug enabled and send a full backtrace. i can't reproduce it here
Comment 2 lrathle 2005-02-01 21:39:33 UTC
sorry for the delay, but I still don't have enough pictures to do this manipulation. I'll do it for the end of this week and send the report.
Comment 3 lrathle 2005-02-09 20:30:06 UTC
Hello,

I now have the pictures. Since digiKam 0.7.2-beta1 is out, what do you prefer me to do ? Try with this version or try again with 0.7.1 ?
Comment 4 Renchi Raju 2005-02-09 22:44:03 UTC
doesn't matter. make sure whatever you are using is compiled with debug support enabled
Comment 5 Renchi Raju 2005-03-06 17:14:09 UTC
lack of feedback. closing bug. reopen if you have new information