aMule crashes on startup with Gdk-ERROR: 'BadMatch (invalid parameter attributes)'
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
AMule |
Fix Released
|
Unknown
|
|||
amule (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: amule
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu.
Description: Ubuntu maverick (development branch)
Release: 10.10
2) The version of the package you are using, via 'apt-cache policy packagename' or by checking in Synaptic.
amule:
Installed: 2.2.6+debian0-7
Candidate: 2.2.6+debian0-7
3) What you expected to happen
The program starts and runs normally.
4) What happened instead
jimmy@jimmy:~$ amule
Initialising aMule 2.2.6 using wxGTK2 v2.8.10
Checking if there is an instance already running...
No other instances are running.
ListenSocket: Ok.
HTTP download thread started
Gdk-ERROR **: The program 'amule' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
(Details: serial 2825 error_code 8 request_code 2 minor_code 0)
(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.)
aborting...
Trace/breakpoint trap
jimmy@jimmy:~$
summary: |
- X Window System error 'BadMatch (invalid parameter attributes)' + aMule crashes on startup with Gdk-ERROR: 'BadMatch (invalid parameter + attributes)' |
Changed in amule: | |
status: | Unknown → Fix Released |
export XLIB_SKIP_ ARGB_VISUALS= 1 works.