aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Author Topic: Amule Crash on Ubuntu 16.04  (Read 3101 times)

srad75

  • Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 3
Amule Crash on Ubuntu 16.04
« on: August 19, 2016, 11:31:30 PM »

Hello friend, i always used Amule on Ubuntu 14.04, but when i upgrade the system with Ubuntu 16.04 Amule after 10-15 minutes close with this following message...
what could be your problem?!


An assertion failed!

../../src/BaseClient.cpp(2143): assert "Assert failure" failed in ProcessPublicKeyPacket().

ASSERT INFO:
../../src/BaseClient.cpp(2143): assert "Assert failure" failed in ProcessPublicKeyPacket().

BACKTRACE:
[1] wxOnAssert(char const*, int, char const*, char const*, char const*)
[2] void std::__cxx11::basic_string<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> >::_M_construct<wchar_t const*>(wchar_t const*, wchar_t const*, std::forward_iterator_tag)
[3] non-virtual thunk to CryptoPP::PK_FinalTemplate<CryptoPP::TF_SignerImpl<CryptoPP::TF_SignatureSchemeOptions<CryptoPP::TF_SS<CryptoPP::PKCS1v15, CryptoPP::SHA1, CryptoPP::RSA, int>, CryptoPP::RSA, CryptoPP::PKCS1v15_SignatureMessageEncodingMethod, CryptoPP::SHA1> > >::~PK_FinalTemplate()
[4] non-virtual thunk to CryptoPP::PK_FinalTemplate<CryptoPP::TF_SignerImpl<CryptoPP::TF_SignatureSchemeOptions<CryptoPP::TF_SS<CryptoPP::PKCS1v15, CryptoPP::SHA1, CryptoPP::RSA, int>, CryptoPP::RSA, CryptoPP::PKCS1v15_SignatureMessageEncodingMethod, CryptoPP::SHA1> > >::~PK_FinalTemplate()
[5] non-virtual thunk to CryptoPP::PK_FinalTemplate<CryptoPP::TF_SignerImpl<CryptoPP::TF_SignatureSchemeOptions<CryptoPP::TF_SS<CryptoPP::PKCS1v15, CryptoPP::SHA1, CryptoPP::RSA, int>, CryptoPP::RSA, CryptoPP::PKCS1v15_SignatureMessageEncodingMethod, CryptoPP::SHA1> > >::~PK_FinalTemplate()
[6] wxAppConsoleBase::CallEventHandler(wxEvtHandler*, wxEventFunctor&, wxEvent&) const
[7] wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&)
[8] wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*)
[9] wxEvtHandler::TryHereOnly(wxEvent&)
[10] wxEvtHandler::ProcessEventLocally(wxEvent&)
[11] wxEvtHandler::ProcessEvent(wxEvent&)
[12] wxEvtHandler::ProcessPendingEvents()
[13] wxAppConsoleBase::ProcessPendingEvents()
[14] wxApp::DoIdle()
[15] g_main_context_dispatch
[16] g_main_loop_run
[17] gtk_main
[18] wxGUIEventLoop::DoRun()
[19] wxEventLoopBase::Run()
[20] wxAppConsoleBase::MainLoop()
[21] wxEntry(int&, wchar_t**)
[22] __libc_start_main


Logged

tw90998088

  • Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 1
Re: Amule Crash on Ubuntu 16.04
« Reply #1 on: August 29, 2016, 11:23:45 AM »

I aslo have this error msg, and ubuntu 16.04 will freeze sometimes if using amule, I dont want use SVN version, can I install old version?
Logged

trekfan1

  • Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 33
Re: Amule Crash on Ubuntu 16.04
« Reply #2 on: September 02, 2016, 10:47:06 AM »

same on my pc, only solution i have found is to use Amule on Win on virtualbox, it's NOT possible to use another version of amule on Ubuntu.
Logged
Sorry for my English, I'm Italian

GonoszTopi

  • The current man in charge of most things.
  • Administrator
  • Hero Member
  • *****
  • Karma: 164
  • Offline Offline
  • Posts: 2713
Re: Amule Crash on Ubuntu 16.04
« Reply #3 on: September 06, 2016, 08:12:09 PM »

It is a known bug and it has been fixed long ago. Unfortunately the fix isn't yet in the Ubuntu binaries...
Logged
concordia cum veritate

hopelessone

  • Full Member
  • ***
  • Karma: 1
  • Offline Offline
  • Posts: 105
  • Ubuntu 8.04
Re: Amule Crash on Ubuntu 16.04
« Reply #4 on: November 18, 2016, 02:51:30 AM »

so where on earth are the working binaries then? cant find squat for amule, amuled, amulegui...........
Logged

macdogdaddy

  • Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 1
Re: Amule Crash on Ubuntu 16.04
« Reply #5 on: April 25, 2017, 03:40:56 AM »

I was yet another user with this problem, but who came up with a really simple solution.  I wanted to post my simple solution here for everyone.  What I did:

1) Uninstall aMule v.2.4.0-svn:

Code: [Select]
sudo apt-get remove amule amule-common amule-utils
2) Downgrade to the latest amule-stable release "aMule v2.3.2"

Install the ".deb" packages of a stable amule release by going to this site https://pkgs.org/download/amule and downloading the ".deb" packages for "Debian Sid" (the packages for Ubuntu 16.10 are the same, and the packages for Ubuntu 17.04 were finally updated but won't install).  Then use GDebi to install each of the main packages, amule, amule-common, amule-utils.  GDebi will complain of unmet dependencies, but no worries.  On the download page there is a "requires" tab.  Click on that tab and dl each of the unmet dependencies GDebi complains about until you've managed to install the entire bundle.   If you want "amule-utils" or "amule-utils-gui" then you'll have to enter "amule-utils" into the search bar on that webpage and do the same thing.  I'm running Ubuntu 16.04 MATE, so for me it looked like this:

  1) libcrypto++6_5.6.4-6_amd64.deb
  2) libboost-system1.62.0_1.62.0+dfsg-4_amd64.deb
  3) amule-common_2.3.2-1_all.deb
  4) amule_2.3.2-1+b2_amd64.deb
  5) libreadline7_7.0-2_amd64.deb
  6) amule-utils_2.3.2-1+b2_amd64.deb

This will likely be the same for you, but may vary slightly by Ubuntu flavor.   So you may have to dl a few different dependencies before GDebi will install aMule for you.  In total, once I figured out what to do, this took me no more than 10-20 mins to complete.  I've been running v2.3.2 for over a week now with my ports open and a hi-ID, and not a single crash so far.

It's a shame that nobody from the (still very much supported) Ubuntu's LTS team has decided to fix this well know problem by updating the repo's from "aMule v.2.4.0-svn" to a newer version of amule where this problem was long ago fixed.  But for now, downgrading to a stable release is a simple solution.  Hope this helps.

P.S. - if you have any legitimate reasons why downgrading may not be a good option (security?), then please join the discussion.  But keep in mind that most people aren't ready to compile their own packages from tarball.
« Last Edit: April 25, 2017, 04:57:20 AM by macdogdaddy »
Logged