After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 69894 - Cannot reinstall after uninstall of 0.88
Cannot reinstall after uninstall of 0.88
Status: VERIFIED INCOMPLETE
Product: dia
Classification: Other
Component: win32
0.89
Other Windows
: Normal blocker
: ---
Assigned To: Steffen Macke
Steffen Macke
: 70102 70865 78984 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2002-01-28 15:01 UTC by David J. Orme
Modified: 2009-08-15 18:40 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description David J. Orme 2002-01-28 15:01:19 UTC
I ran the uninstall program via Start!Settings!"Control Panel" for version
0.88.  However, the install program for 0.99pre1 still says "dia is already
installed.  Please uninstall it first" and I can't install it.
Comment 1 Steffen Macke 2002-01-28 15:45:36 UTC
This is because the registry key HKEY_CLASSES_ROOT/diaFile was not
removed by the dia uninstaller. 

Manually removing this solves the problem.

The next version of the installer should take care of the problem.
Comment 2 Steffen Macke 2002-02-08 05:18:11 UTC
*** Bug 70865 has been marked as a duplicate of this bug. ***
Comment 3 Steffen Macke 2002-04-18 04:51:52 UTC
*** Bug 78984 has been marked as a duplicate of this bug. ***
Comment 4 Alan Horkan 2002-07-02 15:50:49 UTC
If install does not work properly you can always delete the files and
directory and then use "Regclean" from Microsoft to get rid of any
crap in your registry.  

if Steffen says this is fixed in the latest version then i geuss this
should be closed (crap i dont have enough privileges, nevermind)
reopen if the problem still happens in newer versions, thanks.    
Comment 5 Elijah Newren 2002-12-07 22:26:25 UTC
Closing, as per Stephen's comment.
Comment 6 Lars Clausen 2003-01-27 21:21:06 UTC
*** Bug 70102 has been marked as a duplicate of this bug. ***