Hi, everyone!
Since August 2nd 2019 when aMule package for openSUSE Tumbleweed x86_64
was updated and enabled wxWidgets 3.0(*) I suffer the same problem I had
in February 2017
(http://lists.links2linux.de/pipermail/packman/2017-February/015091.html),
also with the PC and laptop.
The difference n
On 2017-02-27 18:05, Olaf Hering wrote:
Am Sat, 25 Feb 2017 23:35:38 +0100
schrieb Rolf Niepraschk :
Can anyone help? Thanks in advance.
aMule uses now wxWidgets-2.8 again. Its unclear if it helps with the
leak, apparently it used to work with that version.
It will take some time until the T
Reported the problem
(http://forum.amule.org/index.php?topic=21638.msg110966#msg110966) and
the backtrace (http://forum.amule.org/index.php?topic=21639.msg110967)
in the aMule forum (http://forum.amule.org/).
___
Packman mailing list
Packman@links2li
On 2017-02-27 14:02, Carlos E. R. wrote:
On 2017-02-27 13:56, evari...@riseup.net wrote:
2017-02-27 13:27:03: SharedFileList.cpp(333): Añadiendo archivo
/Varios/aMule/Temp/021.part.met a compartidos
Trick:
cer@minas-tirith:~> cat /usr/local/bin/ingles
#!/bin/sh
LANG=en_US.UTF-8 LC_ALL=en_US.
On 2017-02-26 13:40, evari...@riseup.net wrote:
Hi!
Since last two Packman's aMule package updates aMule starts using all
the available RAM until kernel kills it. It's a desktop PC with
openSUSE Tumbleweed x86_64 installed.
...
Thanks in advance.
__
Hi!
Since last two Packman's aMule package updates aMule starts using all
the available RAM until kernel kills it. It's a desktop PC with openSUSE
Tumbleweed x86_64 installed.
I first noticed the problem with aMule-2.3.2+git20161207.1524-3.1.x86_64
package. I supposed there was some kind of
