Bug 354954 - Lastest X update crashes aMule
Summary: Lastest X update crashes aMule
Status: RESOLVED DUPLICATE of bug 345131
Alias: None
Product: openSUSE 10.2
Classification: openSUSE
Component: X.Org (show other bugs)
Version: Final
Hardware: PC openSUSE 10.2
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Stefan Dirsch
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-01-19 14:49 UTC by Hans-Peter Jansen
Modified: 2008-01-19 14:57 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Hans-Peter Jansen 2008-01-19 14:49:04 UTC
Latest X update crashes aMule-20070927-0.pm.1 similar to:

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 650 error_code 11 request_code 147 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.) 

Looks like it happens for 10.3 also:
http://www.linux-club.de/ftopic90337.html
Comment 1 Claudio Gregorio 2008-01-19 14:57:43 UTC
Same as #345131. Need immediate attention

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