Your message dated Sat, 16 Feb 2019 20:15:58 -0500
with message-id
<cab4xwxw25fc_yzpsifvxyucwq0p4q4nlvo3-qp+ybbg+cew...@mail.gmail.com>
and subject line Re: [Pkg-amule-devel] Bug#774637: amule: aMule crash when
importing part files
has caused the Debian Bug report #774637,
regarding amule: aMule crash when importing part files
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
774637: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774637
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: amule
Version: 2.3.1+git1a369e47-3
Severity: normal
Dear Maintainer,
I recently tried to import a part file through the aMule import option. After
choosing the proper folder (which holds the *.part, *.part.met, *.part.met.bak
files only) I am queried for whether aMule should delete the original files
after import. Regardless of whether I answer 'Yes' or 'No', aMule crashes
immediately after that. The original files are never removed and the 'imported'
file gets added the the download list, but the parts already downloaded are not
recognised (the download starts from 0%). I include a backtrace generated by
the crash.
I also remembered that I used the import function a couple of months ago
without any problems on aMule 2.3.1-11. I installed that version from Debian
snapshot repository and tried it but the behaviour was the same, so the problem
probably lies in one of the libraries mentioned in the backtrace and not in
aMule itself. I also tried to downgrade those libraries, but I failed probably
due to other dependencies.
Regards,
Krzysztof Bieniasz
-- System Information:
Debian Release: 8.0
APT prefers testing-proposed-updates
APT policy: (990, 'testing-proposed-updates'), (990, 'testing'), (500,
'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=pl_PL.utf8, LC_CTYPE=pl_PL.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages amule depends on:
ii amule-common 2.3.1+git1a369e47-3
ii libc6 2.19-13
ii libcrypto++9 5.6.1-6
ii libgcc1 1:4.9.1-19
ii libgeoip1 1.6.2-2
ii libstdc++6 4.9.1-19
ii libupnp6 1:1.6.19+git20141001-1
ii libwxbase2.8-0 2.8.12.1+dfsg2-2
ii libwxgtk2.8-0 2.8.12.1+dfsg2-2
ii zlib1g 1:1.2.8.dfsg-2+b1
Versions of packages amule recommends:
ii amule-utils 2.3.1+git1a369e47-3
ii unzip 6.0-14
Versions of packages amule suggests:
ii amule-utils-gui 2.3.1+git1a369e47-3
-- no debconf information
Terminated after throwing an instance of 'CInvalidStateEx'
what(): CRunTimeException::CInvalidStateException: CFile: Cannot close
closed file.
backtrace:
[2] ?? in /usr/lib/x86_64-linux-gnu/libstdc++.so.6[0x7f1488903bb6]
[3] ?? in /usr/lib/x86_64-linux-gnu/libstdc++.so.6[0x7f1488903c01]
[4] ?? in /usr/lib/x86_64-linux-gnu/libstdc++.so.6[0x7f1488903e19]
[5] ?? in amule[0x5bed07]
[6] ?? in amule[0x5ed2c4]
[7] ?? in amule[0x452e77]
[8] ?? in amule[0x454eb9]
[9] wxThreadInternal::PthreadStart(wxThread*) in
/usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0[0x7f1488ed14e5]
[10] ?? in /lib/x86_64-linux-gnu/libpthread.so.0[0x7f148ac210a4]
[11] clone in /lib/x86_64-linux-gnu/libc.so.6[0x7f14880caccd]
--- End Message ---
--- Begin Message ---
version: 1:2.3.2-1
On Tue, Jan 6, 2015 at 7:47 PM Sandro Tosi <[email protected]> wrote:
>
> > Here you are, output from gdb as requested. I edited it slightly to
> > obfuscate filepaths for privacy reasons. Hope this helps.
>
> Thanks! this has been reported upstream.
Upstream reported this as fixed with version 2.3.2
--
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi
--- End Message ---
