search

warvair / peerblock

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

Peerblock does not show activity in its log, and is not blocking after the program is closed and started. #181

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?

1.Start PeerBlock.
2.Exit program from the notification area icon.
3.Start Peerblock.

What is the expected output? What do you see instead?

I expect PeerBlock to show activity in its log and blocking sites. The log
is blank and its not blocking anything. It works normally after a reboot,
but still has the problem when its closed and started again.

What version of PeerBlock are you using? On what operating system? 32- or
64-bit?

I am using PeerBlock-Setup_v1.0.0.r202. I am using Windows XP Pro SP3,
32-bit operating system.

Please provide any additional information below.  Make sure to attach
peerblock.log and/or any screenshots that would help explain your problem.

My error log is very old and does not refer to this issue. I was having
problems with Issue 80, before I tried r202.

Thanks,

Scott

Original issue reported on code.google.com by scottmsa...@gmail.com on 31 Oct 2009 at 6:17

Attachments:

GoogleCodeExporter commented 9 years ago 
We just last night posted a special "test release" containing a fix that I 
believe
will resolve this issue.  If you could try out PeerBlock 1.0+ (r205)
(http://update.peerblock.com/bugs/i177_sj3kd/PeerBlock-Setup_v1.0.0.r205.exe) 
and let
us know if it fixes the problem for you, that would be great!

Original comment by peerbloc...@gmail.com on 1 Nov 2009 at 10:24

GoogleCodeExporter commented 9 years ago 
This release seemed to fix my particular problem. I had to reboot my computer 
after I
installed it and tried it. It updated the lists....and came up with an empty 
log, and
wasn't blocking anything. Upon a reboot it opened fine, and I am able to close 
it
using the notification icon and start it...and it appears to be working 
properly.

Scott

Original comment by scottmsa...@gmail.com on 2 Nov 2009 at 3:25

GoogleCodeExporter commented 9 years ago 
Yep, the root cause of the bug was actually happening while you tried to exit
PeerBlock, as we were attempting to stop the Microsoft IpFilterDriver . . . 
which
would then get hung in a "STOP_PENDING" state, such that it would be impossible 
to
restart it when you next tried to start PeerBlock.  I should have mentioned that
you'll want to reboot your system after installing this new release - sorry 
about that.

This r205 test-release was built as an "Interim"/Beta Release, which means that 
it
will automatically detect a new version of that release-type when we next post 
one. 
(Probably in another two or three weeks.)  We probably won't be releasing a new
Stable Release (i.e. "PeerBlock 1.1") for another couple of months, so the Beta
Release train will likely be the only one to contain this fix for awhile.  We 
may
release a PeerBlock 1.0.1 "bugfix" Stable Release containing just this fix plus 
a few
other annoying XP-hitting ones (once we resolve them), but no promises...

I'll close this bug as a duplicate of Issue #177, as it looks like it was the 
same
problem (and the same fix resolved them both).

Original comment by peerbloc...@gmail.com on 2 Nov 2009 at 3:47