hmmm...first bug report:
Ingredients:
- Mandriva 2005 LE
- aMule MDV 2005 rpm's installed (amule-2.0.3-1.rtr205.i586.rpm + commandline + webserver packages).
- Latest wxGTK packages from the same aMule packager.
Tha bug (I don't know if it's of aMule, or the package..but that I'll let it discover to you
)
Closing aMule directly from the taskbar icon having it minimized (without having opened aMule itself (the full GUI)), closes the program, and aMule taskbar icon dissapear, but it left instead a white space in the taskbar. And if you try to run aMule again, GUI doesn't appears, but (as "top" says), aMule opens two "amule" process, using 50% of CPU each one (if you kill one of the process, the other one ups the CPU use to 99%, so I assume than both process are trying to take the full CPU time).
This bug can be avoided by closing aMule from taskbar PREVIOUSLY HAVING (or having previously?
) MAXIMIZED THE GUI, or closing aMule with the classic "X" icon.
Now in spanish (sorry if my english isn't very good, but it's a bit difficult explanation...
)
Si cierras el aMule directamente mientras que está minimizado en la barra de tareas (sin tener el GUI maximizado, vamos), el amule se cierra y el icono del amule se quita de la barra de tareas, pero se queda en cambio un espacio en blanco. Y si intentas ejecutar de nuevo el amule, el GUI no llega a aparecer, pero en cambio (viendolo en "top"), se ejecuta dos veces el proceso "amule", consumiendo cada uno el 50% de la CPU (si matas uno de los dos, el otro pasa a consumir el 100%, o sea que es de asumir que ambos intentan consumir el 100%).
Este problema es evitable cerrando el aMule desde el icono de la barra de tareas PERO teniendo el GUI del amule maximizado (o "presente", como prefirais llamarlo), o cerrando el aMule con el clásico icono de la "X".
-- Little update: I've run amule from the console, and tried to close it "the bad way" to see if it gives any error/debug report (or something). What I've noticed instead of this is that console "freezes" in the latest normal message, until you close the console (then amule closes properly).
[default@localhost ~]$ amule
Initialising aMule
Checking if there is an instance already running...
Loading temp files from /home/default/.aMule/Temp.
All PartFiles Loaded.
ListenSocket: Ok.
External connections disabled in config file
*** Server UDP socket (TCP+3) at 0.0.0.0:6774
*** TCP socket (TCP) listening on 0.0.0.0:6771
*** Client UDP socket (extended eMule) at 0.0.0.0:6772
^[vfddc (oh, nice, isn't it? ;D )And if you close aMule properly (with maximized GUI or "X" icon.... :
[default@localhost ~]$ amule
Initialising aMule
Checking if there is an instance already running...
Loading temp files from /home/default/.aMule/Temp.
All PartFiles Loaded.
ListenSocket: Ok.
External connections disabled in config file
*** Server UDP socket (TCP+3) at 0.0.0.0:6774
*** TCP socket (TCP) listening on 0.0.0.0:6771
*** Client UDP socket (extended eMule) at 0.0.0.0:6772
Shutting down aMule...
aMule dialog destroyed
Now, exiting main app...
aMule shutdown: Terminating core.
aMule shutdown completed.
[default@localhost ~]$
