https://bugs.kde.org/show_bug.cgi?id=421718

--- Comment #6 from Veps <v...@gmx.de> ---
(In reply to emohr from comment #1)
> In Windows we have still the problem that the "dbus-deamon.exe" gets not
> killed after closing Kdenlive. 
> 
> 2 possibilities: 
> - restart the PC and the de-installer should work or 
> - goto task manager (CTRL+Shift+esc) and kill "dbus-deamon.exe" and the
> de-installer should work.

First of all, I can still confirm this bug for:
* KDEnlive: v20.12.2
* OS: Windows 7 Pro x64

FURTHERMORE
* The problem is not solved by restarting! (Was my first thought too but well
-- no.)
* Run "./kdenlive/uninstall.exe" as Administrator does not solve the problem
too -- what is what you would expect considering the error message. (Just FYI.)
* "dbus-deamon.exe" is, as far as I can tell, not running ("Task manager ->
Show process from all users"). Maybe there is another process blocking? Though
I'm not sure about the internals of MS Windows but I would expect the binary to
get loaded into memory hence I would expect the binary to be deletable from the
hard disk though it is currently running/executed.

Memory or not, I can easily (with Admin rights) rename the
"kdenlive/bin/dbus-deamon.exe" to somehting else, nevertheless still no
un-installation is performed.

MORE FUNNY
However I wonder why "README.md" and "LICENSE.txt" are mared as "read-only"
files!?

It gets even more funny when you remove the attribute from the two files, run
`dir /ar /s` in console/cmd.exe in the local folder and get no results BUT the
Windows Explorer still shows under properties for the folder "./kdenlive" a
check for "Read-only (Only applies to files in the folder)". Also at this point
un-install.exe still does not work.

HERE IT GETS CREEPY
Un-checking "Read-only" in the Windows Explorer properties dialog, say okay to
"Apply changes to this folder, subfolders and files", Windows runs through all
the files assumingly and then you get out of the property window and back in
and read-only is again/still checked.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to