Bug 364116

Summary:	Uninstaller doesn't remove C:\Program Files (x86)\digiKam
Product:	[Applications] digikam	Reporter:	matburnham+kdebugs
Component:	Bundle-Windows	Assignee:	Digikam Developers <digikam-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	caulier.gilles
Priority:	NOR
Version:	5.0.0
Target Milestone:	---
Platform:	Microsoft Windows
OS:	Microsoft Windows
Latest Commit:	http://commits.kde.org/scratch/mwiesweg/digikam-sc/2420f084608a6976dc1ee893e90440d69862f280	Version Fixed In:	5.0.0
Sentry Crash Report:

Description matburnham+kdebugs 2016-06-08 20:42:02 UTC

Twice now with a couple of beta7 installers, the uninstaller hasn't removed the C:\Program Files (x86)\digiKam directory. Removing it manually is a bit of a faff as stuff is still running so WIndows won't allow it. I think digikam.exe and dbus-daemon.exe are both still running.

I've done nothing special to run the (un)installer as admin. I *think* it brought up the UAC prompt, but I really can't remember.

Reproducible: Always

Steps to Reproduce:
1. Install beta-7.
2. Uninstall beta-7 using a newer installer.

Actual Results:  
3. Try to continue the install after the uninstall and get 'Error opening file for writing'

Comment 1 caulier.gilles 2016-06-08 20:49:43 UTC

yes confirmed. digiKam.exe still in memory after to close the session of application. I suspect that a DBUS problem under Windows.

In fact if you will DBUS (digiKam do not use it in fact currently for Windows), and after you close digiKam.exe, the application is closed properly.

DBUS is used by digiKam for Mysql DB interface. Currently, Mysql/MAriaBD are not yet available under MXE for cross-compiling with MinGW.

I'm looking if a new compilation option to disable DBUS support can be done safety.

Gilles Caulier

Comment 2 caulier.gilles 2016-06-09 21:21:49 UTC

matburnham,

Just for testing, please try this work around :

1/ run Windows process manager and kill dbus-lauch.exe and digikam.exe.

2/ Go to digiKam install dir and rename :
-> dbus-lauch.exe as dbus-lauch.bak
-> dbus-daemon.exe as dbus-daemon.bak

3/ restart digiKam, play with it, and close it. Does it stay in memory ?

Gilles Caulier

Comment 3 caulier.gilles 2016-06-09 21:36:18 UTC

Git commit 2420f084608a6976dc1ee893e90440d69862f280 by Gilles Caulier.
Committed on 09/06/2016 at 21:33.
Pushed by cgilles into branch 'master'.

disable DBUS into Windows installer as it make digiKam unstable as well.
Related: bug 363505
FIXED-IN: 5.0.0

M  +6    -11   project/mxe/04-build-installer.sh

http://commits.kde.org/scratch/mwiesweg/digikam-sc/2420f084608a6976dc1ee893e90440d69862f280

Comment 4 matburnham+kdebugs 2016-06-11 22:19:46 UTC

Sorry for the delay. Renaming dbus-launch.exe and dbus-daemon.exe and the following your instructions works as you expect - digikam.exe does not remain in memory.