Your message dated Sat, 03 Oct 2026 16:14:05 -0400
with message-id <E1xD67R-0000000CCsX-02LU@zion>
and subject line Re: Bug#697305: amuleweb crash (package amule-daemon)
has caused the Debian Bug report #697305,
regarding amuleweb crash (package amule-daemon)
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.)
--
697305: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697305
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: amule-daemon
Version: 2.3.1-9
amuleweb randomly crashes, mostly when we are visiting the web page. It
generally happens when we have visited the upload page and move back to
the download page.
amuled seems not to be affected by this.
System: Debian testing, AMD 64.
Below is the backtrace:
A fatal error has occurred and amuleweb has crashed.
Please assist us in fixing this problem by posting the backtrace below
in our
'aMule Crashes' forum and include as much information as possible
regarding the
circumstances of this crash. The forum is located here:
http://forum.amule.org/index.php?board=67.0
If possible, please try to generate a real backtrace of this crash:
http://wiki.amule.org/index.php/Backtraces
----------------------------=| BACKTRACE FOLLOWS:
|=----------------------------
Current version is: amuleweb 2.3.1 compiled with wxGTK2 v2.8.12
Running on: Linux 3.2.0-4-amd64 x86_64
[2] ?? in amuleweb[0x428a0a]
[3] wxFatalSignalHandler in
/usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0[0x7f265085e54c]
[4] ?? in /lib/x86_64-linux-gnu/libpthread.so.0[0x7f2650d0f030]
[5] ?? in amuleweb[0x4110e7]
[6] ?? in amuleweb[0x4116f7]
[7] ?? in amuleweb[0x4118c9]
[8] ?? in amuleweb[0x418dd8]
[9] ?? in amuleweb[0x427f6d]
[10] ?? in amuleweb[0x42887f]
[11] wxEvtHandler::ProcessEventIfMatches(wxEventTableEntryBase const&,
wxEvtHandler*, wxEvent&) in
/usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0[0x7f265085b3f6]
[12] wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*) in
/usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0[0x7f265085b564]
[13] wxEvtHandler::ProcessEvent(wxEvent&) in
/usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0[0x7f265085b887]
[14] wxEvtHandler::ProcessPendingEvents() in
/usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0[0x7f265085b360]
[15] wxAppConsole::ProcessPendingEvents() in
/usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0[0x7f26507de899]
[16] ?? in amuleweb[0x424bb0]
[17] ?? in amuleweb[0x42eb68]
[18] ?? in amuleweb[0x420846]
[19] wxEntry(int&, wchar_t**) in
/usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0[0x7f265080d4e5]
[20] ?? in amuleweb[0x40dab2]
[21] __libc_start_main in /lib/x86_64-linux-gnu/libc.so.6[0x7f264ef7eead]
[22] ?? in amuleweb[0x40e70d]
--------------------------------------------------------------------------------
--- End Message ---
--- Begin Message ---
Hi,
This report is against aMule 2.3.1 built with wxWidgets 2.8, and the
backtrace has no symbols, so there is nothing left to investigate: both
aMule and wxWidgets have changed a lot since 2013. I'm closing this bug;
please reopen it with a backtrace from the current version if amuleweb
still crashes.
Regards,
Sandro
--- End Message ---
