aMule Forum
English => aMule crashes => Topic started by: angelinux-slack on October 16, 2009, 09:02:17 PM
-
When i run aMule in Slackware 13.0 / KDE, XFCE, Blackbox, Fluxbox, WindowsMaker, Enlightenment, all is right.
But if a run in FVWM, aMule start correctly, and when i minimize to tray, and i tried to maximize by doubleclick, aMule crash, and terminal show me:
Current version is: aMule 2.2.6 using wxGTK2 v2.8.10
Running on: Linux 2.6.29.6-smp i686
[2] ?? in amule [0x806ae19]
[3] wxFatalSignalHandler in /usr/lib/libwx_baseu-2.8.so.0[0xb7a39a26]
[4] ?? in [0xffffe400]
If i tried ti maximize by rightclick and show amule, this crash and showme:
The program 'amule' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadDrawable (invalid Pixmap or Window parameter)'.
(Details: serial 179120 error_code 9 request_code 62 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.)
If i launch amuule with --sync, and repeat... amule loop and flashes, and 3 or 4 seconds after, crash with same result
-
Just to make things sure, you are not calling amule with --sync directly, do you? (like: amule --sync)
Because "sync" is an option for starting a gdb run.
-
oops, yes i did, amule --sync directly in terminal