aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Author Topic: The Update for the X-Server did kill aMule (SOLVED)  (Read 4514 times)

Arghmage

  • Newbie
  • Karma: 0
  • Offline Offline
  • Posts: 4
The Update for the X-Server did kill aMule (SOLVED)
« 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.)
« Last Edit: January 18, 2008, 10:26:37 PM by Festor »
Logged

Festor

  • Hero Member
  • *****
  • Karma: 79
  • Offline Offline
  • Posts: 935
  • Offline -> Studying...
Re: The Update for the X-Server did kill aMule
« Reply #1 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
« Last Edit: January 18, 2008, 08:08:17 PM by Festor »
Logged

izan

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 10
Re: The Update for the X-Server did kill aMule
« Reply #2 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?
Logged

izan

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 10
Re: The Update for the X-Server did kill aMule
« Reply #3 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?
Logged

Festor

  • Hero Member
  • *****
  • Karma: 79
  • Offline Offline
  • Posts: 935
  • Offline -> Studying...
Re: The Update for the X-Server did kill aMule
« Reply #4 on: January 18, 2008, 09:38:56 PM »
« Last Edit: January 18, 2008, 10:27:35 PM by Festor »
Logged