warvair / peerblock

Automatically exported from code.google.com/p/peerblock
Other
0 stars 1 forks source link

Uninstall doesn't remove base install-directory #23

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Uninstall PeerBlock

What is the expected output? What do you see instead?
- The directory in which PeerBlock was installed should be deleted;
instead, that directory is left on the harddrive even though it's empty.

What version of the product are you using? On what operating system?
- Reported in PeerBlock r65.

Original issue reported on code.google.com by peerbloc...@gmail.com on 26 Jul 2009 at 5:17

GoogleCodeExporter commented 9 years ago

Original comment by peerbloc...@gmail.com on 26 Jul 2009 at 5:18

GoogleCodeExporter commented 9 years ago
It seems to work fine here! I will look into it though...

Original comment by mynameherebro on 26 Jul 2009 at 5:22

GoogleCodeExporter commented 9 years ago

Original comment by peerbloc...@gmail.com on 26 Jul 2009 at 5:25

GoogleCodeExporter commented 9 years ago
After running some more repro-tests I've been able to reproduce this, but only
because I accidentally had left a program running that had held a reference to 
a file
in that directory.  Even leaving a Windows Explorer open and viewing that 
directory
wasn't enough to repro the problem, on Win7 x64 at least.  When the problem was
reproducing, I also couldn't delete the directory using Windows Explorer . . . 
so it
really does not appear to be a PeerBlock-specific problem.

I'll leave this bug open since it would be nice if we could pop up a message 
telling
the user that we cannot delete the directory because some program is holding 
open a
reference to it, and ideally identify that program.  Not targetting this
functionality for 0.9.1 though, as I think it really is a low-priority issue at 
this
point.

If anyone has a better repro case that could result in this bug happening for 
reasons
beyond the user's control, please let us know.

Original comment by peerbloc...@gmail.com on 27 Jul 2009 at 4:37

GoogleCodeExporter commented 9 years ago
I do believe that this might be something that XhmikosR should be able to take 
care of. 

Original comment by mynameherebro on 5 Mar 2010 at 7:02

GoogleCodeExporter commented 9 years ago
Actually no, because this is not a bug in the installer and it's not even a 
defect
IMO. Plus I cannot reproduce on Windows 7 so this bug is nonexistent for me.

Original comment by XhmikosR on 9 Mar 2010 at 11:36

GoogleCodeExporter commented 9 years ago
Hmm. So I suspect that this is then closed. 

Original comment by mynameherebro on 10 Mar 2010 at 6:34

GoogleCodeExporter commented 9 years ago

Original comment by XhmikosR on 4 Jun 2010 at 2:34

GoogleCodeExporter commented 9 years ago

Original comment by mynameherebro on 5 Jun 2010 at 7:02