No on my side. I have seen no really critical bug for 2.1.3, nor any crash report with info that can be reproducible on my side to fix it. Everything I've seen seems distro-related.
Fair enough. But aMule still crashes
here. Therefore, if "critical bugs for 2.13 are not seen", it has to be some other system componet failure. I would like some finger pointing here, as something is causing aMule to crash and I would like to know what it is.
I am running amule 2.1.3 full time, and it crashes regularly about every 8 days, like a clock.
I launch aMule like thus
$ date > ~/Temp/date_arranque_amule.txt ; amule ; echo "******************" ; echo -n "Amule fue arrancado: " ; cat ~/Temp/date_arranque_amule.txt ; echo "******************" ; echo -n "Hora actual: " ; date ; echo "******************"And I get:
----------------------------=| BACKTRACE FOLLOWS: |=----------------------------
Current version is: aMule 2.1.3 using wxGTK2 v2.6.3 (Unicoded)
Running on: Linux 2.6.8-2-386 i686
Violación de segmento
******************
Amule fue arrancado: jue abr 5 14:52:05 CEST 2007
******************
Hora actual: vie abr 13 22:30:51 CEST 2007
******************And also:
----------------------------=| BACKTRACE FOLLOWS: |=----------------------------
Current version is: aMule 2.1.3 using wxGTK2 v2.6.3 (Unicoded)
Running on: Linux 2.6.8-2-386 i686
Violación de segmento
******************
Amule fue arrancado: vie abr 13 22:31:47 CEST 2007
******************
Hora actual: dom abr 22 01:41:26 CEST 2007
******************And so on...
Other info: this is Debian 3.1 Sarge, with:
$ dpkg -l libgtk2* | grep ^ii
ii libgtk2.0-0 2.6.4-3.1 The GTK+ graphical user interface library
ii libgtk2.0-bin 2.6.4-3.1 The programs for the GTK+ graphical user int
ii libgtk2.0-comm 2.6.4-3.1 Common files for the GTK+ graphical user int
ii libgtk2.0-dev 2.6.4-3.1 Development files for the GTK+ library
$ grep amule /etc/apt/sources.list
deb http://amule-debian.dyndns.org/ debian/ # Para aMule 2.1.3 GTK2
$ dpkg -l amule*
Desired=Unknown/Install/Remove/Purge/Hold
| Estado=No/Instalado/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: mayúsc.=malo)
||/ Nombre Versión Descripción
+++-=============================-=============================-==========================================================================
ii amule 2.1.3-1 aNOTHER eMule P2P Client (monolithic client)
ii amule-common 2.1.3-1 aNOTHER eMule P2P Client (common shared files)
ii amule-console-utils 2.1.3-1 aNOTHER eMule P2P Client (console utils)
ii amule-daemon 2.1.3-1 aNOTHER eMule P2P Client (daemon client)
ii amule-gui-utils 2.1.3-1 aNOTHER eMule P2P Client (GUI utils)
ii amule-remote-gui 2.1.3-1 aNOTHER eMule P2P Client (remote GUI)
ii amule-utils 2.1.3-1 aNOTHER eMule P2P Client (utils dummy Package)So is it wxWidgets, GTK2, kernel version, etc.?
You probably cannot reproduce the problem
in your system, but I'm fairly sure you could really easily reproduce my system (debian 3.1 with the above pointed apt source) and see for yourself. Unless you are so sure it is not an aMule problem, in which case I would like to know which component is failing here.
Regards.
PS: and by the way, my other Debian 3.1 system (headless) running amule "daemon" of the same version
never crashes,
but gets the Kad disconnection problem and never reconnects to Kad unless restarted. I guess this is also unrreproducible.
