Bug 262499 - Cannot rename .AVI files
Summary: Cannot rename .AVI files
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: AdvancedRename-file (show other bugs)
Version: 3.2.0
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks: 261773
  Show dependency treegraph
 
Reported: 2011-01-08 08:25 UTC by Simon
Modified: 2022-01-31 21:57 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In: 6.0.0
Sentry Crash Report:


Attachments
Crash when renaming, maybe related? (26.73 KB, application/octet-stream)
2011-02-12 10:59 UTC, Simon
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Simon 2011-01-08 08:25:38 UTC
Version:           1.8.0 (using KDE 4.5.4) 
OS:                Linux

For every single .AVI file in the selection the rename dialog says «cannot rename» or «file does not exist» (even though it did rename the file). The progress dialog then does not continue until it is aborted and restarted.

Reproducible: Always




OS: Linux (x86_64) release 2.6.36-2.slh.3-aptosid-amd64
Compiler: cc
Comment 1 Simon 2011-02-12 10:59:52 UTC
Created attachment 57182 [details]
Crash when renaming, maybe related?

This is becoming a little annoying. Renaming JPEG files works fine, but AVI files nearly always fail.
Comment 2 caulier.gilles 2011-02-12 11:11:59 UTC
No, it's completly different. Probably the thumbnails thread issue:

Thread 2 (Thread 0x7f6478b27710 (LWP 9061)):
[KCrash Handler]
#5  0x00007f64cbd39854 in Digikam::ThumbnailLoadingTask::execute (this=0x7f64706b8190) at /data/cworkspace/digikam-trunk/digikam/libs/threadimageio/thumbnailtask.cpp:100
#6  0x00007f64cbd18c0d in Digikam::LoadSaveThread::run (this=0x2b41800) at /data/cworkspace/digikam-trunk/digikam/libs/threadimageio/loadsavethread.cpp:124
#7  0x00007f64cbd6095c in Digikam::DynamicThread::DynamicThreadPriv::run (this=0x2b59e50) at /data/cworkspace/digikam-trunk/digikam/libs/threads/dynamicthread.cpp:306
#8  0x00007f64c7ddbd5f in ?? () from /usr/lib/libQtCore.so.4
#9  0x00007f64c7de5e15 in ?? () from /usr/lib/libQtCore.so.4
#10 0x00007f64c525a8ba in start_thread (arg=<value optimized out>) at pthread_create.c:300
#11 0x00007f64c70a502d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#12 0x0000000000000000 in ?? ()

Gilles Caulier
Comment 3 Simon 2011-02-13 12:07:30 UTC
Could I, in theory, debug this with qtcreator?
I could try, as soon as I know where libkexiv2 and Co. have gone and how to compile/install everything with the new git repo.
Comment 4 Andi Clemens 2011-03-06 11:43:17 UTC
The best thing would be to ignore media types that are not images in the progress bar dialog. The problem with crashing could arise in other places, too.

Gilles,

what do you think? Should we just skip displaying a thumbnail for video, audio and other types when showing the graphical progress bar dialog?

Andi
Comment 5 jay Pa 2011-10-06 03:34:30 UTC
Must confirm this behaiviour with AVI files - additionally renaming multiple files when including any AVI results in flickering thumbnails for the respective album; this occurs after renaming the automatically marked rest of the files which remained unrenamed after the error.
Reproducible: Always
Digikam Version: 2.2 on ubuntu 11.04 64bit
Comment 6 jay Pa 2011-10-06 03:42:14 UTC
Additional information to my previous comment: 
Obviously related to thumbnail creation, here the output from cmd line:

digikam(22884)/digikam (core) Digikam::ThumbnailCreator::createThumbnail: Cannot create thumbnail for  "/path/to/file/FILENAME.AVI" 
digikam(22884)/digikam (core) Digikam::ThumbnailCreator::load: Thumbnail is null for  "/path/to/file/FILENAME.AVI"

seems to be related to bug 261773
Comment 7 Simon 2012-07-12 08:30:29 UTC
This is still valid in 2.6.0.
Comment 8 caulier.gilles 2012-07-12 08:34:23 UTC
And with 2.7.0 ?
Comment 9 Michael Bona 2013-03-01 11:13:24 UTC
Still happening in Version 3.0.0-rc (on KDE 4.10, OpenSuse)
Comment 10 caulier.gilles 2013-03-01 11:14:51 UTC
What's happen with 3.0.0 final release ? (not RC)

Gilles Caulier
Comment 11 Michael Bona 2013-03-01 11:28:45 UTC
Will check as soon as package is provided. This will happen with OpenSuse 12.3., due in about 2 weeks.

But is there hope? Has anything been done to address this bug between RC and final?
Comment 12 Michael Bona 2013-03-24 11:12:44 UTC
Yes, it still happens with 3.0.0 final. 

digiKam
Version 3.0.0
Using KDE Development Platform 4.10.00 "release 1"
Comment 13 Michael Bona 2013-06-17 21:13:00 UTC
Still happens with 3.2.

digiKam
Version 3.2.0
Using KDE Development Platform 4.10.3 "release 1"
Comment 14 caulier.gilles 2013-12-04 17:53:11 UTC
To Andi, comment #4,

See my comment here about progressmanager :

https://bugs.kde.org/show_bug.cgi?id=261773#c10

Gilles Caulier
Comment 15 caulier.gilles 2014-08-31 13:21:54 UTC
Michael,

This file still valid using last digiKam 4.2.0 and last Exiv2 shared lib 0.24 (this last one is able to manage video metadata) ?

Gilles Caulier
Comment 16 caulier.gilles 2015-05-17 07:54:25 UTC
Michael,

Did you seen my previous comment ? Can you check with last digiKam 4.10.0 ?

Gilles Caulier
Comment 17 Michael Bona 2015-05-18 15:31:20 UTC
Gilles,

sorry for missing this, I don't always realize if KDE mails are for me or cc'ed to me.

Don't have 4.1 yet, but I can properly rename .avi files with digikam 3.5 on KDE 4.14.6. 

I did not realize the manual renaming works now because renaming on import now works properly as well, minimizing the need for manual renaming.

In any case: Thank you for your efforts in solving this!
Michael
Comment 18 Simon 2015-05-18 18:19:36 UTC
Indeed, it works fine with 3.5, thanks a lot for fixing this bug!
Comment 19 Simon 2015-11-07 10:13:46 UTC
I am using 4.4.0 now, and it seems like there is a regression. It shows exactly the same behaviour again.
Comment 20 caulier.gilles 2015-11-07 10:21:38 UTC
4.4.0 is not the last one, but 4.14.0, which is a big difference.

Gilles Caulier
Comment 21 caulier.gilles 2018-03-14 05:04:03 UTC
Fixed with next 6.0.0 release which integrate a new video metadata parser based
on FFMPEg instead Exiv2. Video date extraction work as expected and video file
rename is completed properly.