0000524: Manually changed server priorities are not remembered - aMule Bug Tracker

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

ID

Project

Category

View Status

Date Submitted

Last Update

0000524

aMule

Servers

public

2005-08-06 01:22

2005-08-14 01:14

Reporter

gjc

Assigned To

Kry

Priority

normal

Severity

major

Reproducibility

always

Status

closed

Resolution

open

Platform

OS

OS Version

Product Version

2.0.3

Target Version

Fixed in Version

Summary

0000524: Manually changed server priorities are not remembered

Description

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

Tags

No tags attached.

Fixed in Revision

Operating System

Relationships

Notes
(0001190) spiorf (reporter) 2005-08-06 02:04	also in current cvs

(0001194) Kry (manager) 2005-08-06 22:29	Used to debian bug reports? (just curious)

(0001198) Xaignar (manager) 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 (manager) 2005-08-10 13:26	Nevermind the autp-update, that doesn't affect the existing priorities.

(0001221) Kry (manager) 2005-08-14 01:14	Works perfectly here. Closing

Issue History
Date Modified	Username	Field	Change
2005-08-06 01:22	gjc	New Issue
2005-08-06 02:04	spiorf	Note Added: 0001190
2005-08-06 22:29	Kry	Note Added: 0001194
2005-08-10 13:25	Xaignar	Note Added: 0001198
2005-08-10 13:26	Xaignar	Note Added: 0001199
2005-08-14 01:14	Kry	Status	new => assigned
2005-08-14 01:14	Kry	Assigned To	=> Kry
2005-08-14 01:14	Kry	Status	assigned => closed
2005-08-14 01:14	Kry	Note Added: 0001221

Copyright © 2000 - 2025 MantisBT Team