digikam does not terminate properly

[Søren Holm]

Binary package hint: digikam

After having started up digikam and closing it again, the digikam process is still running. Apparently some threads are waiting for something. The memory consumption and all looks like before closing the digikam window.
gdb tells me this :

(gdb) thread apply all bt

Thread 12 (Thread 0x7fffd1ed4710 (LWP 2362)):
#0 0x00007fffef7c0603 in *__GI___poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=-1)
    at ../sysdeps/unix/sysv/linux/poll.c:87
#1 0x00007fffec64c1e9 in ?? () from /lib/libglib-2.0.so.0
#2 0x00007fffec64c63c in g_main_context_iteration () from /lib/libglib-2.0.so.0
#3 0x00007ffff10c3bc3 in QEventDispatcherGlib::processEvents (this=0x1439430, flags=<value optimized out>)
    at kernel/qeventdispatcher_glib.cpp:412
#4 0x00007ffff1096792 in QEventLoop::processEvents (this=<value optimized out>, flags=DWARF-2 expression error: DW_OP_reg operations must be used either alone or in conjuction with DW_OP_piece.
) at kernel/qeventloop.cpp:149
#5 0x00007ffff1096b7c in QEventLoop::exec (this=0x7fffd1ed3d30, flags=DWARF-2 expression error: DW_OP_reg operations must be used either alone or in conjuction with DW_OP_piece.
) at kernel/qeventloop.cpp:201
#6 0x00007ffff0fa222d in QThread::exec (this=<value optimized out>) at thread/qthread.cpp:490
#7 0x00007fffd92292b0 in ?? () from /usr/lib/qt4/plugins/phonon_backend/phonon_xine.so
#8 0x00007ffff0fa51ae in QThreadPrivate::start (arg=0x143d3e0) at thread/qthread_unix.cpp:266
#9 0x00007ffff0d14981 in start_thread (arg=<value optimized out>) at pthread_create.c:304
#10 0x00007fffef7ccd6d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x0000000000000000 in ?? ()

Thread 10 (Thread 0x7fffd3b11710 (LWP 2360)):
#0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:212
#1 0x00007fffd8fcd051 in ?? () from /usr/lib/libxine.so.1
#2 0x00007ffff0d14981 in start_thread (arg=<value optimized out>) at pthread_create.c:304
#3 0x00007fffef7ccd6d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#4 0x0000000000000000 in ?? ()

Thread 9 (Thread 0x7fffdc0e4710 (LWP 2358)):
#0 0x00007fffef7c0603 in *__GI___poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=-1)
    at ../sysdeps/unix/sysv/linux/poll.c:87
#1 0x00007fffec64c1e9 in ?? () from /lib/libglib-2.0.so.0
#2 0x00007fffec64c63c in g_main_context_iteration () from /lib/libglib-2.0.so.0
#3 0x00007ffff10c3bc3 in QEventDispatcherGlib::processEvents (this=0xfa27c0, flags=<value optimized out>)
    at kernel/qeventdispatcher_glib.cpp:412
#4 0x00007ffff1096792 in QEventLoop::processEvents (this=<value optimized out>, flags=DWARF-2 expression error: DW_OP_reg operations must be used either alone or in conjuction with DW_OP_piece.
) at kernel/qeventloop.cpp:149
#5 0x00007ffff1096b7c in QEventLoop::exec (this=0x7fffdc0e3d90, flags=DWARF-2 expression error: DW_OP_reg operations must be used either alone or in conjuction with DW_OP_piece.
) at kernel/qeventloop.cpp:201
#6 0x00007ffff0fa222d in QThread::exec (this=<value optimized out>) at thread/qthread.cpp:490
#7 0x00007ffff0fa51ae in QThreadPrivate::start (arg=0xf91710) at thread/qthread_unix.cpp:266
#8 0x00007ffff0d14981 in start_thread (arg=<value optimized out>) at pthread_create.c:304
#9 0x00007fffef7ccd6d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#10 0x0000000000000000 in ?? ()

Thread 8 (Thread 0x7fffdc8e5710 (LWP 2357)):
#0 0x00007fffef7c0603 in *__GI___poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=-1)
    at ../sysdeps/unix/sysv/linux/poll.c:87
#1 0x00007fffec64c1e9 in ?? () from /lib/libglib-2.0.so.0
#2 0x00007fffec64c63c in g_main_context_iteration () from /lib/libglib-2.0.so.0
#3 0x00007ffff10c3bc3 in QEventDispatcherGlib::processEvents (this=0x10df9c0, flags=<value optimized out>)
    at kernel/qeventdispatcher_glib.cpp:412
#4 0x00007ffff1096792 in QEventLoop::processEvents (this=<value optimized out>, flags=DWARF-2 expression error: DW_OP_reg operations must be used either alone or in conjuction with DW_OP_piece.
) at kernel/qeventloop.cpp:149
#5 0x00007ffff1096b7c in QEventLoop::exec (this=0x7fffdc8e4d90, flags=DWARF-2 expression error: DW_OP_reg operations must be used either alone or in conjuction with DW_OP_piece.
) at kernel/qeventloop.cpp:201
#6 0x00007ffff0fa222d in QThread::exec (this=<value optimized out>) at thread/qthread.cpp:490
#7 0x00007ffff0fa51ae in QThreadPrivate::start (arg=0xfa16c0) at thread/qthread_unix.cpp:266
#8 0x00007ffff0d14981 in start_thread (arg=<value optimized out>) at pthread_create.c:304
#9 0x00007fffef7ccd6d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#10 0x0000000000000000 in ?? ()

Thread 7 (Thread 0x7fffdd0e6710 (LWP 2356)):
#0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1 0x00007ffff0fa5d6b in QWaitConditionPrivate::wait (this=<value optimized out>, mutex=0x10ccc58, time=18446744073709551615)
    at thread/qwaitcondition_unix.cpp:88
---Type <return> to continue, or q <return> to quit---
#2 QWaitCondition::wait (this=<value optimized out>, mutex=0x10ccc58, time=18446744073709551615)
    at thread/qwaitcondition_unix.cpp:160
#3 0x00007ffff4fcb2bc in Digikam::ParkingThread::run (this=0x10ccc40)
    at /build/buildd/digikam-1.3.0/libs/threads/threadmanager.cpp:101
#4 0x00007ffff0fa51ae in QThreadPrivate::start (arg=0x10ccc40) at thread/qthread_unix.cpp:266
#5 0x00007ffff0d14981 in start_thread (arg=<value optimized out>) at pthread_create.c:304
#6 0x00007fffef7ccd6d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7ffff7fae7c0 (LWP 2329)):
#0 0x00007fffef7c0603 in *__GI___poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=999)
    at ../sysdeps/unix/sysv/linux/poll.c:87
#1 0x00007fffec64c1e9 in ?? () from /lib/libglib-2.0.so.0
#2 0x00007fffec64c63c in g_main_context_iteration () from /lib/libglib-2.0.so.0
#3 0x00007ffff10c3bc3 in QEventDispatcherGlib::processEvents (this=0xaae510, flags=<value optimized out>)
    at kernel/qeventdispatcher_glib.cpp:412
#4 0x00007ffff1d6a7de in QGuiEventDispatcherGlib::processEvents (this=0x4a6b860, flags=<value optimized out>)
    at kernel/qguieventdispatcher_glib.cpp:204
#5 0x00007ffff1096792 in QEventLoop::processEvents (this=<value optimized out>, flags=DWARF-2 expression error: DW_OP_reg operations must be used either alone or in conjuction with DW_OP_piece.
) at kernel/qeventloop.cpp:149
#6 0x00007ffff1096b7c in QEventLoop::exec (this=0x7fffffffd1d0, flags=DWARF-2 expression error: DW_OP_reg operations must be used either alone or in conjuction with DW_OP_piece.
) at kernel/qeventloop.cpp:201
#7 0x00007ffff109ac2b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#8 0x000000000077ba5d in main (argc=<value optimized out>, argv=<value optimized out>)
    at /build/buildd/digikam-1.3.0/digikam/main.cpp:195
(gdb)

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: digikam 2:1.3.0-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-9.14-generic 2.6.35-rc5
Uname: Linux 2.6.35-9-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Thu Jul 22 01:19:24 2010
InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100616)
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=da_DK.UTF-8
 LANGUAGE=
SourcePackage: digikam

[Major Carter (sam-carter)]

- Kubuntu 10.10 Beta (32-bit)
- digiKam 1.4.0

I'm also seeing the digiKam process remaining in memory every time I exit digiKam.
Example: If I start and exit digiKam 10 times, I have 10 digiKam processes in memory.

[b3nmore (b3nmore)]

- Xubuntu 10.04 (32-bit)
- digiKam 1.4.0 (lucid kubuntu backports ppa)

Same for me on Xfce.

[managementboy (managementboy)]

on my system too! Kubuntu 10.10 with kubutu backports updated today.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[MarcoA (marcoalici)]

The same here!

Ubuntu 10.10 64bit
digiKam: 1.4.0

Digikam is still running after closing.
After rebooting all sessions still running at shutdown try to start.