Your message dated Sun, 13 Aug 2017 21:35:28 -0500
with message-id <1988258.VBqjUG6vMY@riemann>
and subject line Re: digikam: Process never goes away after quitting Digikam
has caused the Debian Bug report #774053,
regarding digikam: Process never goes away after quitting Digikam
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
774053: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774053
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: digikam
Version: 4:4.4.0-1.1
Severity: important
After using Ctrl-Q to quit Digikam, its window goes away but its
process doesn't. For instance:
jgoerzen 4780 0.8 6.9 3489600 556824 ? Sl 14:24 4:01 digikam
jgoerzen 10368 0.0 5.2 3420716 421808 ? Sl Dec25 0:29 digikam
I can kill them with kill(1) with no ill effect, but look at how much
RAM it soaks up.
John
-- System Information:
Debian Release: 8.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages digikam depends on:
ii digikam-data 4:4.4.0-1.1
ii digikam-private-libs 4:4.4.0-1.1
ii kde-runtime 4:4.14.2-1
ii libc6 2.19-13
ii libgcc1 1:4.9.1-19
ii libgphoto2-6 2.5.4-1.1+b2
ii libgphoto2-port10 2.5.4-1.1+b2
ii libkdcraw23 4:4.14.0-1
ii libkdecore5 4:4.14.2-4
ii libkdeui5 4:4.14.2-4
ii libkexiv2-11 4:4.14.2-1
ii libkhtml5 4:4.14.2-4
ii libkio5 4:4.14.2-4
ii libkipi11 4:4.13.3-1
ii libknotifyconfig4 4:4.14.2-4
ii libkparts4 4:4.14.2-4
ii libopencv-core2.4 2.4.9.1+dfsg-1+b1
ii libopencv-imgproc2.4 2.4.9.1+dfsg-1+b1
ii libphonon4 4:4.8.0-4
ii libqt4-dbus 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii libqt4-sql 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii libqt4-sql-sqlite 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii libqt4-xml 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii libqtcore4 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii libsolid4 4:4.14.2-4
ii libstdc++6 4.9.1-19
ii libthreadweaver4 4:4.14.2-4
ii perl 5.20.1-3
ii phonon 4:4.8.0-4
Versions of packages digikam recommends:
ii chromium [www-browser] 39.0.2171.71-2
ii elinks [www-browser] 0.12~pre6-5+b2
ii google-chrome-stable [www-browser] 39.0.2171.95-1
ii iceweasel [www-browser] 31.3.0esr-1
ii kipi-plugins 4:4.4.0-1.1
ii konqueror [www-browser] 4:4.14.2-1
ii lynx-cur [www-browser] 2.8.9dev1-2+b1
ii mplayerthumbs 4:4.14.0-1
ii w3m [www-browser] 0.5.3-19
Versions of packages digikam suggests:
ii digikam-doc 4:4.4.0-1.1
pn systemsettings <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
On Sunday, January 3, 2016 5:25:49 PM CDT you wrote:
> With digikam 4.14.0, I can't reproduce this: the processes all go away as
> expected.
Closing, since no longer reproducible.
-Steve
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
