aMule Forum

English => en_Bugs => Topic started by: Arghmage on January 18, 2008, 06:31:32 PM

Title: The Update for the X-Server did kill aMule (SOLVED)
Post by: Arghmage on January 18, 2008, 06:31:32 PM

After updating the X-Server in Ubuntu (there was a security hole), amule is impossible to run.

Quote

$ amulegui
Connecting...
Going to event loop...
Remote GUI EC event handler
LOG: amule-remote-gui.cpp(294): Succeeded! Connection established to aMule SVN
The program 'amulegui' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 1932 error_code 11 request_code 148 minor_code 5)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

Title: Re: The Update for the X-Server did kill aMule
Post by: Festor on January 18, 2008, 07:35:23 PM

Confirmed in all CVS...  ???

I dont understand anything..  >:( why only affect to amule?

EDIT: Please read this, I found a solution:

http://forum.amule.org/index.php?topic=14259.0

Title: Re: The Update for the X-Server did kill aMule
Post by: izan on January 18, 2008, 09:29:47 PM

Yes. I have the same problem  after upgrade xserver-xorg in ubuntu gutsy >:(
I start to be very very bored of the ubuntu way of doing things.

# amulegui
The program 'amulegui' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 4716 error_code 11 request_code 148 minor_code 5)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

Any solution?

Title: Re: The Update for the X-Server did kill aMule
Post by: izan on January 18, 2008, 09:32:35 PM

Ok Festor, it worked for me, downgrading xserver-xorg-core
But why this bug?
It is another solution without downgrading?

Title: Re: The Update for the X-Server did kill aMule
Post by: Festor on January 18, 2008, 09:38:56 PM

Waiting for a fix of xserver-xorg-core package  :-\ . I do not think they take more than 2-3 days

EDIT: Fix released... :D

Download this, or use Updater Manager of Ubuntu

32 bits:
http://security.ubuntu.com/ubuntu/pool/main/x/xorg-server/xserver-xorg-core_1.2.0-3ubuntu8.2_i386.deb

64 bits:
http://security.ubuntu.com/ubuntu/pool/main/x/xorg-server/xserver-xorg-core_1.2.0-3ubuntu8.2_amd64.deb

PowerPC
http://security.ubuntu.com/ubuntu/pool/main/x/xorg-server/xserver-xorg-core_1.2.0-3ubuntu8.2_powerpc.deb

Sparc
http://security.ubuntu.com/ubuntu/pool/main/x/xorg-server/xserver-xorg-core_1.2.0-3ubuntu8.2_sparc.deb