Bug 1445

Summary:	System instability with amule runing
Product:	Mageia	Reporter:	wato dol <wato.dol>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	dmorganec, marja11
Version:	Cauldron	Keywords:	NEEDINFO
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:	amule	CVE:
Status comment:

Description wato dol 2011-05-27 10:01:46 CEST

With amule 2.3.1-1.mga1 package runing in Mageia / Gnome system, I noticed several instabilities appearing to be randomised but frequent :
- Screen freezed after long time runing, at my level, nothing to do but switch-off
- Internet access significant slow for other softwares (Firefox, thunderbird...), this slow can't be (for me) explained by connection limits
- When computer is locked, impossible to re-enter in the system (like screenfreeze ?)

Sensibility of this bug : depends on other softwares runing in parallels
I tempted to degrade in the monitoring system the priority of this amule process, this is efficient to let other softwares access internet in better conditions, but I still noticed screen freezing problems

My Computer is a Dell D630

Manuel Hiebel 2011-05-27 10:06:43 CEST

Source RPM: (none) => amule

Comment 1 Marja Van Waes 2011-10-14 20:47:24 CEST

@ wato do

Sorry for responding so very late.

Is the problem still there in current cauldron or updated mageia 1?


Current version in cauldron is 2.3.1-0.rc1.4.mga2
current version in mageia 1 is 2.3.1-0.rc1.2.mga1

Keywords: (none) => NEEDINFO
CC: (none) => marja11

Comment 2 D Morgan 2011-10-31 15:23:05 CET

Please test the Rc2 that i just uploaded

CC: (none) => dmorganec

Comment 3 Marja Van Waes 2011-11-12 22:26:16 CET

Reporter, could you please reply to the previous questions? If you don't reply this bug can be closed as OLD two weeks from now. Thank you.

Comment 4 Marja Van Waes 2011-12-06 12:24:24 CET

(In reply to comment #3)
> Reporter, could you please reply to the previous questions? If you don't reply
> this bug can be closed as OLD two weeks from now. Thank you.



Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

Status: NEW => RESOLVED
Resolution: (none) => OLD