Bug 248882 - digikam crashes when renaming using date/time info
Summary: digikam crashes when renaming using date/time info
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: AdvancedRename-engine (show other bugs)
Version: 1.3.0
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-24 11:19 UTC by Freek de Kruijf
Modified: 2018-09-02 15:18 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 1.7.0


Attachments
New crash information added by DrKonqi (18.14 KB, text/plain)
2010-08-24 11:44 UTC, Freek de Kruijf
Details
New crash information added by DrKonqi (18.33 KB, text/plain)
2010-08-26 22:41 UTC, Freek de Kruijf
Details
New crash information added by DrKonqi (18.85 KB, text/plain)
2010-10-06 16:03 UTC, Freek de Kruijf
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Freek de Kruijf 2010-08-24 11:19:33 UTC
Version:           1.3.0 (using KDE 4.5.0) 
OS:                Linux

Using the Rename function in the pull-down menu Image in the Tool bar after selecting more than one image works unreliable. Sometimes it works with 2 or 3 images. The string in the rename box I use for one image is [date:"FotoyyyyMMdd-hhmmss.jpg"]. The .jpg has to be removed for more than one image. So this appears to me as inconsistent.
digikam crashes on most occasions when using more that one image in the selection.
I installed the version of digikam with the debuginfo, but a traceback has not been produced.

Reproducible: Always

Steps to Reproduce:
Select a number of images in an album, press F2 enter the above string in the rename field and press the OK button. After that most of the time digikam crashes.
Comment 1 Freek de Kruijf 2010-08-24 11:44:37 UTC
Created attachment 50887 [details]
New crash information added by DrKonqi

digikam (1.3.0) on KDE Platform 4.5.00 (KDE 4.5.0) using Qt 4.6.3

- What I was doing when the application crashed: see the description which is already in this report.

-- Backtrace (Reduced):
#6  Digikam::Parser::parse (this=<value optimized out>, settings=...) at /usr/src/debug/digikam-1.3.0/utilities/advancedrename/common/parser.cpp:241
#7  0x00000000006f05d4 in Digikam::Parser::invalidModifiers (this=<value optimized out>, settings=...) at /usr/src/debug/digikam-1.3.0/utilities/advancedrename/common/parser.cpp:206
#8  0x00000000006ea036 in Digikam::Highlighter::highlightBlock (this=0x4f0bc40, text=...) at /usr/src/debug/digikam-1.3.0/utilities/advancedrename/common/highlighter.cpp:95
#9  0x00007fcb73a918e3 in QSyntaxHighlighterPrivate::reformatBlock (this=0x4f0bce0, block=...) at text/qsyntaxhighlighter.cpp:204
#10 0x00007fcb73a91aa0 in QSyntaxHighlighterPrivate::_q_reformatBlocks (this=0x4f0bce0, from=<value optimized out>, charsRemoved=<value optimized out>, charsAdded=<value optimized out>)
    at text/qsyntaxhighlighter.cpp:184
Comment 2 Marcel Wiesweg 2010-08-26 22:05:00 UTC
Andi will know if this bug is already fixed.
To test this, I recommend to try digikam 1.4
Comment 3 Andi Clemens 2010-08-26 22:24:16 UTC
I can not confirm this, works fine here. I'll also suggest to try it again with digiKam 1.4.0. If the problem still exists, please leave a comment :-)
Comment 4 Freek de Kruijf 2010-08-26 22:41:34 UTC
Created attachment 50989 [details]
New crash information added by DrKonqi

digikam (1.4.0) on KDE Platform 4.5.00 (KDE 4.5.0) using Qt 4.6.3

- What I was doing when the application crashed:
I selected 8 images and tried to rename them in the same way as described previously. However now I was using 1.4.0

-- Backtrace (Reduced):
#11 0x00000000006ef9ba in QList (this=0x54d3a30, settings=...) at /usr/include/QtCore/qlist.h:114
#12 QForeachContainer (this=0x54d3a30, settings=...) at /usr/include/QtCore/qglobal.h:2225
#13 Digikam::Parser::parse (this=0x54d3a30, settings=...) at /usr/src/debug/digikam-1.4.0/utilities/advancedrename/common/parser.cpp:219
#14 0x00000000006efc04 in Digikam::Parser::invalidModifiers (this=<value optimized out>, settings=...) at /usr/src/debug/digikam-1.4.0/utilities/advancedrename/common/parser.cpp:201
#15 0x00000000006ea460 in Digikam::Highlighter::highlightBlock (this=0x5649590, text=...) at /usr/src/debug/digikam-1.4.0/utilities/advancedrename/common/highlighter.cpp:95
Comment 5 Andi Clemens 2010-09-25 22:43:42 UTC
I still can not confirm this, and I can't see any hint in the code why it should crash.

Although your date option is a little bit weird (but not invalid), there shouldn't be a problem at all.

Maybe your Qt installation is broken in some way?
Can you figure out if some specific files crash? Maybe they have filenames that are unusual?
Comment 6 Freek de Kruijf 2010-09-28 23:21:19 UTC
The first time I did only a few (3-5) files which worked OK. After that I tried more (>10), which did not work (crash). Then I tried again 3-5, which did not work (crash). After that I tried 2 (crash), Finally only renaming one did work.
The file names of the original files are dscXXXXX.jpg, where XXXXX is 00001 till 99999. I have some new files, so I will try again tomorrow.
Comment 7 caulier.gilles 2010-10-06 14:53:46 UTC
Freek,

Can you try to reproduce the crash using digiKam 1.4.0 ?

Gilles Caulier
Comment 8 Freek de Kruijf 2010-10-06 16:03:47 UTC
Created attachment 52281 [details]
New crash information added by DrKonqi

digikam (1.4.0) on KDE Platform 4.5.2 (KDE 4.5.2) "release 5" using Qt 4.6.3

- What I was doing when the application crashed:

Same as in the current report. Same as in the current report.

-- Backtrace (Reduced):
#6  ref (this=0x53fcce0, settings=...) at /usr/include/QtCore/qatomic_x86_64.h:121
#7  QList (this=0x53fcce0, settings=...) at /usr/include/QtCore/qlist.h:114
#8  QForeachContainer (this=0x53fcce0, settings=...) at /usr/include/QtCore/qglobal.h:2225
#9  Digikam::Parser::parse (this=0x53fcce0, settings=...) at /usr/src/debug/digikam-1.4.0/utilities/advancedrename/common/parser.cpp:219
#10 0x00000000006efc04 in Digikam::Parser::invalidModifiers (this=<value optimized out>, settings=...) at /usr/src/debug/digikam-1.4.0/utilities/advancedrename/common/parser.cpp:201
Comment 9 Freek de Kruijf 2010-10-06 16:14:36 UTC
The previous backtrace was generated when trying to rename 18 pictures. After that I tried 4 and 2 and that resulted in a crash also. However renaming one picture works OK.
Comment 10 caulier.gilles 2010-11-24 09:12:02 UTC
digiKam 1.6.0 is out:

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

Please update and check if this entry still valid.

Thanks in advance

Gilles Caulier
Comment 11 Andi Clemens 2010-11-27 17:54:20 UTC
The backtrace seems to be the same as 237642...

*** This bug has been marked as a duplicate of bug 237642 ***
Comment 12 Freek de Kruijf 2010-11-30 11:24:57 UTC
The problem is no longer in 1.6.0. I tested it in openSUSE 11.4 Milestone 4.
It even works on .MOV files.