DigiKam crashes while handling 3gp video file

[tdn]

When I clicked on an 3gp (was avi) video in DigiKam it crashed.

Attached is the output from digiKam.

[tdn (spam-thomasdamgaard)]

I have more information on this issue:
1: It was not an avi video file. It was a 3GP file (recorded from a SonyEricsson K810i mobile phone)
2: The bug is easily reproducable.
3: Even though I have installed digikam-dbgsym package with debug symbols, I get this message, when trying to view the backtrace in KCrashHandler:

This backtrace appears to be of no use.
This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash.

(no debugging symbols found)

[Parthan SR (parth-technofreak)]

Thank you for taking your time to report this bug and help making Ubuntu better. Please specify the release version of Ubuntu installed in your computer as well as the version of the software package you are reporting the bug against. You can find the version of a software installed in your computer by issuing the following command in a terminal: apt-cache policy <package-name>.

[Parthan SR (parth-technofreak)]

Updated the bug summary and description for the correction made by the reporter.

[tdn (spam-thomasdamgaard)]

I use Ubuntu 8.04 Hardy Heron.
DigiKam version:
~ $ apt-cache policy digikam
digikam:
  Installed: 2:0.9.3-2ubuntu1
  Candidate: 2:0.9.3-2ubuntu1
  Version table:
 *** 2:0.9.3-2ubuntu1 0
        500 http://dk.archive.ubuntu.com hardy/main Packages
        100 /var/lib/dpkg/status

[Luka Renko (lure)]

You can try collecting the stack trace by running digikam with "gdb".

Just start digikam under gdb by executing "gdb digikam" in command line.
When gdb starts, type "r" and Enter. Then try to reproduce.

When program crashes, you can type "backtrace" which will provide you the stack trace.

[tdn (spam-thomasdamgaard)]

I tried what you suggested.
It seems that it is not digikam itself that crashes but 'nspluginviewer'?

Maybe this means that this is a bug in another applikation/package?

Output from gdb here:
Error: Directory Olympus with 18761 entries considered invalid; not read.
Error: Directory Olympus with 18761 entries considered invalid; not read.
Error: Directory Olympus with 18761 entries considered invalid; not read.
Error: Directory Olympus with 18761 entries considered invalid; not read.
Error: Directory Olympus with 18761 entries considered invalid; not read.
Found dcraw version: 8.83
Error: Directory Makernote with 18761 entries considered invalid; not read.
Warning: Failed to read Makernote, rc = 6
Cannot load metadata using Exiv2 (/home/tdn/Pictures/incoming-photos/mvi_2407.a
vi: The file contains data of an unknown image type)
Cannot load metadata using Exiv2 (/home/tdn/Pictures/incoming-photos/mvi_2407.a
vi: The file contains data of an unknown image type)
Cannot load metadata using Exiv2 (/home/tdn/Pictures/incoming-photos/mvi_2409.a
vi: The file contains data of an unknown image type)
Cannot load metadata using Exiv2 (/home/tdn/Pictures/incoming-photos/mvi_2409.a
vi: The file contains data of an unknown image type)
Cannot load metadata using Exiv2 (/home/tdn/Pictures/incoming-photos/mvi_2408.a
vi: The file contains data of an unknown image type)
Cannot load metadata using Exiv2 (/home/tdn/Pictures/incoming-photos/mvi_2408.a
vi: The file contains data of an unknown image type)
Cannot load metadata using Exiv2 (/home/tdn/Pictures/incoming-photos/mov00242.3
gp: The file contains data of an unknown image type)
Cannot load metadata using Exiv2 (/home/tdn/Pictures/incoming-photos/mov00242.3
gp: The file contains data of an unknown image type)
Cannot load metadata using Exiv2 (/home/tdn/Pictures/incoming-photos/mov00242.3
gp: The file contains data of an unknown image type)
argn=MIME, argv=audio/3gpp
[00000001] main private debug: checking builtin modules
[00000001] main private debug: checking plugin modules
[00000001] main private debug: loading plugins cache file /home/tdn/.vlc/cache/p
lugins-04081e.dat
[00000001] main private debug: recursively browsing `/usr/lib/vlc'
[00000001] main private debug: module bank initialized, found 225 modules
[00000001] main private debug: opening config file /home/tdn/.vlc/vlcrc
[00000001] main private debug: CPU has capabilities 486 586 MMX MMXEXT SSE SSE2
FPU
[00000001] main private debug: looking for memcpy module: 3 candidates
[00000001] main private debug: using memcpy module "memcpymmxext"
[00000289] main playlist debug: waiting for thread completion
[00000289] main playlist debug: thread 1086572880 (playlist) created at priority
 0 (playlist/playlist.c:184)
[00000290] main private debug: waiting for thread completion
[00000290] main private debug: thread 1094965584 (preparser) created at priority
 0 (playlist/playlist.c:210)
[00000291] main interface debug: looking for interface module: 1 candidate
[00000291] main interface debug: using interface module "hotkeys"
[00000291] main interface debug: thread 1103358288 (interface) created at priori
ty 0 (interface/interface.c:231)
[00000293] main...

[xteejx (xteejx)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

[xteejx (xteejx)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!