aMule Bug Tracker - aMule
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0000723aMuleMessagespublic2005-12-13 04:392008-02-24 01:28
Reporters0undt3ch 
Assigned ToXaignar 
PrioritynormalSeverityminorReproducibilityalways
StatusresolvedResolutionfixed 
PlatformOSOS Version
Product VersionSVN 
Target VersionFixed in VersionSVN 
Fixed in Revision
Operating System
Summary0000723: Status bar wrongly reports 'kad: ok'
DescriptionOn the status bar I see kad: ok, on the kad info I see firewalled, guess the status bar wasn't updated
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Filespng screenshot-20051213@035915.png (33,178) 2005-12-13 04:41
http://bugs.amule.org/file_download.php?file_id=104&type=bug
png

png screenshot-20051214@060814.png (57,176) 2005-12-14 06:57
http://bugs.amule.org/file_download.php?file_id=105&type=bug
png

png screenshot-20051214@151443.png (51,274) 2005-12-14 15:57
http://bugs.amule.org/file_download.php?file_id=106&type=bug
png
Issue History
Date ModifiedUsernameFieldChange
2005-12-13 04:39s0undt3chNew Issue
2005-12-13 04:41s0undt3chFile Added: screenshot-20051213@035915.png
2005-12-13 13:43s0undt3chNote Added: 0001654
2005-12-13 13:55XaignarStatusnew => resolved
2005-12-13 13:55XaignarResolutionopen => fixed
2005-12-13 13:55XaignarAssigned To => Xaignar
2005-12-14 06:56s0undt3chStatusresolved => feedback
2005-12-14 06:56s0undt3chResolutionfixed => reopened
2005-12-14 06:56s0undt3chNote Added: 0001662
2005-12-14 06:57s0undt3chFile Added: screenshot-20051214@060814.png
2005-12-14 15:57s0undt3chFile Added: screenshot-20051214@151443.png
2005-12-14 15:59s0undt3chNote Added: 0001670
2008-02-24 01:28XaignarStatusfeedback => resolved
2008-02-24 01:28XaignarFixed in Version => SVN
2008-02-24 01:28XaignarResolutionreopened => fixed
2008-02-24 01:28XaignarNote Added: 0002670

Notes
(0001654)
s0undt3ch   
2005-12-13 13:43   
As a follow up, this got solved.
Problem was: Natural Stupidity.
Source of Problem: I hadn't passed --enable/disable-kad-compile

Solution: For me this bug can be closed.
(0001662)
s0undt3ch   
2005-12-14 06:56   
On the seccond screenshot you'll see that this still happens, and the snap I'm using is dated 13th December. It was running for 5 hours.
(0001670)
s0undt3ch   
2005-12-14 15:59   
On the 3rd screenshot, you see that both infos match, and aMule is now running for 14 hours. Took this long to correct the info?
(0002670)
Xaignar   
2008-02-24 01:28   
This has been fixed in current SVN. Thanks for reporting the problem.