aMule Bug Tracker - aMule
View Issue Details
0000524aMuleServerspublic2005-08-06 01:222005-08-14 01:14
gjc 
Kry 
normalmajoralways
closedopen 
2.0.3 
 
0000524: Manually changed server priorities are not remembered
How to reproduce:
1. Go to server list
2. Change priority of a server to High
3. Close amule
4. Start amule again
5. Go to server list

Expected:
 - The server I configured to High priority would remain High priority;

Actual result:
 - The priority of the server is not remembered; it stays with Normal
No tags attached.
Issue History
2005-08-06 01:22gjcNew Issue
2005-08-06 02:04spiorfNote Added: 0001190
2005-08-06 22:29KryNote Added: 0001194
2005-08-10 13:25XaignarNote Added: 0001198
2005-08-10 13:26XaignarNote Added: 0001199
2005-08-14 01:14KryStatusnew => assigned
2005-08-14 01:14KryAssigned To => Kry
2005-08-14 01:14KryStatusassigned => closed
2005-08-14 01:14KryNote Added: 0001221

Notes
(0001190)
spiorf   
2005-08-06 02:04   
also in current cvs
(0001194)
Kry   
2005-08-06 22:29   
Used to debian bug reports? (just curious)
(0001198)
Xaignar   
2005-08-10 13:25   
I am unable to reproduce this bug in current CVS. By any chance, are you using the auto-update feature for servers?
(0001199)
Xaignar   
2005-08-10 13:26   
Nevermind the autp-update, that doesn't affect the existing priorities.
(0001221)
Kry   
2005-08-14 01:14   
Works perfectly here. Closing