Bug 220194 - Moving or copying photos crashes Digikam
Summary: Moving or copying photos crashes Digikam
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Database-Scan (show other bugs)
Version: 1.0.0
Platform: MacPorts Other
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-26 23:33 UTC by Michał Kaczmarek
Modified: 2017-07-17 08:36 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 4.12.0


Attachments
attachment-25473-0.html (1.07 KB, text/html)
2015-07-08 07:50 UTC, Michał Kaczmarek
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Michał Kaczmarek 2009-12-26 23:33:18 UTC
Version:           1.0rc and 1.0 (using KDE 4.3.4)
Compiler:          Default compiler provided by MacPorts 
OS:                OS X
Installed from:    Mac OS X (Fink) Packages

1. Install current MacPorts on Mac OS X.
2. Install digikam-devel (i.e. 1.0rc)
3. Run digikam and try to copy or move any photo from one directory to another one (it does not matter whether it is a network or local directory).
4. 100% of times digikam crashes. Sometimes (less than 50%) KDE Crash Assistant shows up offering to report the crash but it does not finish during "Loading crash information".

After tweaking the Portfile to build 1.0 final instead of 1.0 rc I am still getting this problem 100% of times.

Contrary to several other errors during copying, in this case the file is not copied.

This is a part of the standard output which may be relevant:

digikam(10712,0x7fff705babe0) malloc: *** error for object 0x122715800: pointer being freed was not allocated
*** set a breakpoint in malloc_error_break to debug
KCrash: Application 'digikam' crashing...
sock_file=/Users/mikey/Library/Preferences/KDE/socket-crydee.local/kdeinit4__tmp_launch-a3YEEo__0
Warning: connect() failed: : No such file or directory
KCrash cannot reach kdeinit, launching directly.

[1]+  Stopped                 /Applications/MacPorts/KDE4/digikam.app/Contents/MacOS/digikam
crydee:~ mikey$ /Users/mikey/10712: No such file or directory

warning: Could not find object file "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_libgphoto2/work/libgphoto2-2.4.4/libgphoto2_port/libgphoto2_port/.libs/libgphoto2_port_la-gphoto2-port-info-list.o" - no debug information available for "gphoto2-port-info-list.c".


warning: Could not find object file "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_libgphoto2/work/libgphoto2-2.4.4/libgphoto2_port/libgphoto2_port/.libs/libgphoto2_port_la-gphoto2-port-log.o" - no debug information available for "gphoto2-port-log.c".
Comment 1 Michał Kaczmarek 2009-12-26 23:35:54 UTC
Note: I am using MacPorts packages, not Fink packages, but this choice was not available.
Comment 2 caulier.gilles 2010-01-25 21:52:23 UTC
digiKam 1.1. release will be done in few days. Please check if this entry still valid.

Thanks in advance

Gilles Caulier
Comment 3 caulier.gilles 2010-04-04 10:45:53 UTC
digiKam and Kipi-plugins 1.2.0 are out. Please check if crash is still valid there.

Thanks in advance

Gilles Caulier
Comment 4 caulier.gilles 2010-10-06 15:11:00 UTC
We waiting info using digiKam 1.4.0

Gilles Caulier
Comment 5 caulier.gilles 2015-07-04 06:00:37 UTC
New digiKam 4.11.0 is available.

https://www.digikam.org/node/740

Can you reproduce the problem with this release ?
Comment 6 Michał Kaczmarek 2015-07-08 07:50:21 UTC
Created attachment 93521 [details]
attachment-25473-0.html

Hi Gilles,

I am sorry, I no longer have a Mac, so I cannot verify it.

Michał

sob., 4.07.2015 o 08:00 użytkownik Gilles Caulier <caulier.gilles@gmail.com>
napisał:

> https://bugs.kde.org/show_bug.cgi?id=220194
>
> --- Comment #5 from Gilles Caulier <caulier.gilles@gmail.com> ---
> New digiKam 4.11.0 is available.
>
> https://www.digikam.org/node/740
>
> Can you reproduce the problem with this release ?
>
> --
> You are receiving this mail because:
> You reported the bug.
> You are on the CC list for the bug.
>