Summary: | digikam crashes when trying to edit (and save) photos | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | TioDuke <tioduke> |
Component: | Albums-Engine | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | andresbajotierra, caulier.gilles |
Priority: | NOR | ||
Version: | 1.1.0 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 5.7.0 | |
Sentry Crash Report: | |||
Attachments: |
GDB Backtrace
GDB backtrace (digikam w/debugging symbols) gdb backtrace (digikam/kipi-plugins w/debugging symbols) |
Description
TioDuke
2010-02-18 13:06:43 UTC
We need a pure GDB backtrace to hack. Gilles Caulier Created attachment 40915 [details]
GDB Backtrace
Attaching the GDB backtrace.
Tio, your backtrace is uncomplete. do you have installed digikam debug package ? Gilles Caulier Gilles, you are right. I have only the kdegraphics-common debug package installed. Unfortunately Arch does not provide one. I will try to compile it myself without stripping the debugging symbols and post a new backtrace. Sorry for the inconvenience. Check also if previous *digikam* and *kipi* installed packages are properly removed from your computer It sound like an already reported issue Gilles Caulier Created attachment 40925 [details]
GDB backtrace (digikam w/debugging symbols)
Gilles,
I am uploading the trace using an unstripped digikam package. Tell me if it is OK.
Gilles, I haven't read your previous post so I did not know you needed me to recompile *kipi*, sorry. I will do now, but it'll take some time (this is a slow machine). I hope I finish before leaving for work. Regarding this bug being reported before, I did search before posting but he only report that looked by me is about memory leaks after editing more than one file: the circumstances looked the same with the on;y difference that I am experiencing crashes. No more : Thread 1 (Thread 0xb2f92960 (LWP 12826)): #0 0xb5775c7d in QString::operator==(QString const&) const () from /usr/lib/libQtCore.so.4 #1 0xb6b1b071 in ?? () from /usr/lib/libkio.so.5 #2 0x09307d28 in ?? () #3 0xbfffe898 in ?? () #4 0x00000010 in ?? () #5 0xbfffe870 in ?? () #6 0x0000001d in ?? () #7 0x0000001d in ?? () #8 0x000000fe in ?? () #9 0x00000027 in ?? () #10 0x0000011c in ?? () #11 0x00000027 in ?? () #12 0x000000c0 in ?? () #13 0x00000028 in ?? () #14 0x000000de in ?? () #15 0x00000028 in ?? () #16 0x000000df in ?? () #17 0x00000028 in ?? () #18 0xbfffe88c in ?? () #19 0x086bfba0 in ?? () #20 0xb6c6375c in ?? () from /usr/lib/libkio.so.5 #21 0xb6c7063d in ?? () from /usr/lib/libkio.so.5 #22 0xbfffc77e in ?? () #23 0xbfffc780 in ?? () #24 0xbfffe8c0 in ?? () #25 0x00000050 in ?? () #26 0x00000400 in ?? () #27 0xbfffc7b0 in ?? () #28 0xbfffe8c4 in ?? () #29 0x086bfb78 in ?? () #30 0x09921da4 in ?? () #31 0x09921da0 in ?? () #32 0xbfffe810 in ?? () #33 0x002f0029 in ?? () #34 0x000001a5 in ?? () #35 0x00000040 in ?? () #36 0x00004313 in ?? () #37 0x00000020 in ?? () #38 0x38323179 in ?? () #39 0x642e3632 in ?? () #40 0x6b696769 in ?? () #41 0x65746d61 in ?? () #42 0x6966706d in ?? () #43 0x742e656c in ?? () #44 0x0000706d in ?? () #45 0x00000000 in ?? () (gdb) Look like the last trace part is important here, but there is nothing to see... We can see thta it's just located to KDELibs... But where exactly ? Gilles Caulier As crash is in QString, check this entry : https://bugs.kde.org/show_bug.cgi?id=214718 Gilles Caulier Created attachment 40926 [details]
gdb backtrace (digikam/kipi-plugins w/debugging symbols)
Gilles,
Both packages aren't stripped in this new backtrace. I hope I did not forget anything this time.
It's always the same : Thread 1 (Thread 0xb2f92960 (LWP 28337)): #0 0xb5775c7d in QString::operator==(QString const&) const () from /usr/lib/libQtCore.so.4 #1 0xb6b1b071 in ?? () from /usr/lib/libkio.so.5 #2 0x0b1473b8 in ?? () #3 0xbfffe898 in ?? () #4 0x00000020 in ?? () #5 0x40260000 in ?? () #6 0x08536fb0 in ?? () #7 0x084b5248 in ?? () #8 0x00000000 in ?? () (gdb) Sound like KDELibs problem. Do you read my comment #9 Gilles Caulier Gilles, I have not read your post when I submitted the backtrace (I did not refresh my browser, sorry). There are a couple of things I want to point out: - I am on 32 bits system (while bug 214718 seems to be related to 64 bits). - The proposed fix seems to have been released for digikam 1.1.0 (the version I am using). I can check the sources I used to compile in order to see if the fix is there, though. I do understand now that the problem is somewhere in the kdelibs. However, how come the only application that seems to be crashing is digikam? Shouldn't this problem be affecting other kde components? Do you want me to make a backtrace using kdelibs with debugging symbols? Do you think it may help the kdelibs maintainers? Thank you in advance and sorry for the inconveniences. >Do you want me to make a backtrace using kdelibs with debugging symbols?
yes, this is the only to progress here...
Gilles Caulier
Gilles, I've just found out about bug 222974 and to me it looks very much like this one. What do you think? It's possible. You need to update KDELibs to be sure... Gilles Caulier As this is QString::operator== + KIO, I will assume this is indeed bug 222974. (fixed for KDE SC 4.4.1) Merging. Thanks (Reopen if you experience a similar crash with KDE SC 4.4.1) *** This bug has been marked as a duplicate of bug 222974 *** I can confirm this bug being a duplicate of bug 222974: I have applied the corrections intriduced by the following svn commit http://websvn.kde.org/?view=rev&revision=1091941 in the kde sc 4.4.0 version of kio and the crashes are now gone. I have tested throughout the week-end and everything seems fine (digikam as well as kde apps). Thank you. Since digiKam 5.0.0, KDirWatch was been replaced by QFileSytemWatcher. It will not reproducible. Gilles Caulier |