Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 206564 - net-p2p/amule-2.1.3: crash after emerging x11-base/xorg-server-1.3.0.0-r3
Summary: net-p2p/amule-2.1.3: crash after emerging x11-base/xorg-server-1.3.0.0-r3
Status: RESOLVED DUPLICATE of bug 206490
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High normal
Assignee: Gentoo Linux bug wranglers
URL: http://ubuntuforums.org/showthread.ph...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-01-18 19:11 UTC by naranek
Modified: 2008-01-18 19:13 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description naranek 2008-01-18 19:11:44 UTC
Amule crashes after emerging x11-base/xorg-server-1.3.0.0-r3 and media-libs/fontconfig-2.5.0-r1

Reproducible: Always

Steps to Reproduce:
1.Emerge x11-base/xorg-server-1.3.0.0-r3 and media-libs/fontconfig-2.5.0-r1
2.Run amule

Actual Results:  
Initialising aMule
Checking if there is an instance already running...
No other instances are running.
The program 'amule' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 440 error_code 11 request_code 144 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.)
Comment 1 naranek 2008-01-18 19:13:04 UTC
I already tryed to delete ~/.aMule but nothing changes.
Comment 2 Jakub Moc (RETIRED) gentoo-dev 2008-01-18 19:13:50 UTC

*** This bug has been marked as a duplicate of bug 206490 ***

*** This bug has been marked as a duplicate of bug 206490 ***