Description of problem: After the last updates amule don't start. I open a terminal and only get violación de segmento (segment fault) Steps to Reproduce: Directly 1. try to launch amule from menu 2. nothing happens From a terminal inside the desktop 1. open a terminal 2. run amule 3. get segment fault First i think was a corrupted statistics.dat like in previous fails but i even renamed the amule's configuration directory and i still get the segment fault
Hi, Confirmed here on my mga5 for x86_64 :( Since this update https://bugs.mageia.org/show_bug.cgi?id=18184 amule can no more start.
CC: (none) => geiger.david68210Assignee: bugsquad => geiger.david68210
Hi katnatek, I just rebuild amule against libcryptopp 5.6.3 on 5/Core/Updates_testing repo, could you test with this update if amule now start and run properly? Thanks in advance! - amule-2.3.1-12.1.mga5
(In reply to David GEIGER from comment #2) > Hi katnatek, > > I just rebuild amule against libcryptopp 5.6.3 on 5/Core/Updates_testing > repo, could you test with this update if amule now start and run properly? > > Thanks in advance! > > - amule-2.3.1-12.1.mga5 Start again!, i will report if i note some strange. Thank you
CC: (none) => 231036448
(In reply to David GEIGER from comment #2) Works well until now, i think you can promote the package to official updates and close as solved this bug
Assigning to QA, Advisory: ============================= Many users have reported that amule doesn't start anymore and gets a segfault after launch since a recent security update of libcryptopp. This update is simply a rebuild against this new libcryptopp and fixes this issue. Packages in 5/core/updates_testing: ======================== amule-2.3.1-12.1.mga5 amule-commandline-2.3.1-12.1.mga5 amule-webserver-2.3.1-12.1.mga5 Source RPM: ======================== amule-2.3.1-12.1.mga5.src.rpm
Assignee: geiger.david68210 => qa-bugs
Installed amule 2.3.1-12 packages on x86_64. Starting it goes nowhere; no segfault though. $ amule 2016-04-30 08:06:28: Initialising aMule 2.3.1 compiled with wxGTK2 v2.8.12 2016-04-30 08:06:28: Checking if there is an instance already running... 2016-04-30 08:06:28: No other instances are running. Updated to 2.3.1-12.1 $ amule 2016-04-30 08:16:51: Initialising aMule 2.3.1 compiled with wxGTK2 v2.8.12 2016-04-30 08:16:51: Checking if there is an instance already running... 2016-04-30 08:16:51: No other instances are running. 2016-04-30 08:17:02: ListenSocket: Ok. 2016-04-30 08:17:02: Loading temp files from /home/lcl/.aMule/Temp. 2016-04-30 08:17:02: All PartFiles Loaded. 2016-04-30 08:17:36: Now, exiting main app... 2016-04-30 08:17:36: aMule OnExit: Terminating core. 2016-04-30 08:17:36: aMule shutdown completed. This brought up the first time notice and offered to download a list of webservers - said yes but left it there and closed down.
CC: (none) => tarazed25
Whiteboard: (none) => MGA5-64-OK
i586 in virtualbox Installed amule, amule-commandline, amule-webserver and libcryptopp6-5.6.3-1.1. $ amule crashed with segmentation fault. The 64bit test started out without the commandline and webserver packages which would explain the lack of a segfault in the earlier test. Updated the packages: $ amule 2016-04-30 09:12:22: Initialising aMule 2.3.1 compiled with wxGTK2 v2.8.12 2016-04-30 09:12:22: Checking if there is an instance already running... 2016-04-30 09:12:22: No other instances are running. 2016-04-30 09:12:26: ListenSocket: Ok. 2016-04-30 09:12:26: Loading temp files from /home/lcl/.aMule/Temp. 2016-04-30 09:12:26: All PartFiles Loaded. 2016-04-30 09:13:10: Now, exiting main app... 2016-04-30 09:13:10: aMule OnExit: Terminating core. 2016-04-30 09:13:10: aMule shutdown completed. Validating this.
Keywords: (none) => validated_updateWhiteboard: MGA5-64-OK => MGA5-64-OK MGA5-32-OKCC: (none) => sysadmin-bugs
A repeat test of the pre-update on another x86_64 machine with all the packages installed gave the same result; amule starts but hangs without a segfault.
(In reply to Len Lawrence from comment #8) > A repeat test of the pre-update on another x86_64 machine with all the > packages installed gave the same result; amule starts but hangs without a > segfault. Do you use KDE?, one follower in identi.ca report some similar https://identi.ca/panko/comment/NhxrwVgVQ-ap-11hXe5LRg Translation: ¿do you use plasma/KDE? Since the changes in the support of the systray and further use of xembedsniproxy amule hangs at start... without the package plasma-systray-legacy works well, but without icon's tray. amule-daemon also works without issues.
Hardware: i586 => All
I compile amule-2.4.0-0.git20160416.1.mga6.src.rpm from cauldron in my magiea 5 i586 , i install it and also works well so another option is backport that version to mageia 5
Not KDE or Plasma; these tests were run under Mate.
On my Mageia 5 x86_64 Gnome system, after last update amule doesn't start. $ amule 2016-05-01 22:12:16: Initialising aMule 2.3.1 compiled with wxGTK2 v2.8.12 2016-05-01 22:12:16: Checking if there is an instance already running... 2016-05-01 22:12:16: No other instances are running. ... no response....
CC: (none) => carlo.gozzi
Advisory uploaded.
Whiteboard: MGA5-64-OK MGA5-32-OK => advisory MGA5-64-OK MGA5-32-OK
An update for this issue has been pushed to the Mageia Updates repository. http://advisories.mageia.org/MGAA-2016-0070.html
Status: NEW => RESOLVEDResolution: (none) => FIXED