Your message dated Fri, 23 Jun 2006 12:50:35 +0200
with message-id <[EMAIL PROTECTED]>
and subject line closing
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: mldonkey-server
Version: 2.5.3-5
Severity: important
After startup:
Nov 19 17:11:14 santiamen mlnet: Core started
Nov 19 17:11:14 santiamen mlnet: Disabling output to console, to enable: stdout
true
mldonkey-server takes 4 minutes to crash:
Nov 19 17:15:12 santiamen mlnet_error: Fatal error: out-of-bound access in
array or string
Nov 19 17:15:12 santiamen mldonkey_server: Process PID ( 11884 ) exit with
return code 2
Nov 19 17:15:12 santiamen mldonkey_server: Process respawning too fast : only
live 247.
Before that it crash when I was trying to login with debian defaults options on
downloads.ini
but until I added a 192.168.1.255 (local network) it crashed everytime I try to
login by
the browser interface.
Let me know what do you want me to test modify on the config to resolve this.
-- System Information
Debian Release: 3.0
Architecture: sparc
Kernel: Linux santiamen 2.4.21 #1 SMP Thu Aug 7 19:29:27 EDT 2003 sparc
Locale: LANG=C, LC_CTYPE=C
Versions of packages mldonkey-server depends on:
ii adduser 3.51 Add and remove users and groups
ii debconf 1.3.15 Debian configuration management sy
ii libc6 2.3.2-7 GNU C Library: Shared libraries an
ii mime-support 3.18-1.3 MIME files 'mime.types' & 'mailcap
ii zlib1g 1:1.1.4-1 compression library - runtime
--- End Message ---
--- Begin Message ---
Package: mldonkey-server
This bug cannot be reproduced anymore and is therefore likely to have
been fixed by a new upstream release. I'm closing it.
Cheers,
Samuel.
--- End Message ---
