Charles A Edwards <[EMAIL PROTECTED]> writes:

> > Name        : drakconf                     Relocations: (not
> > relocateable) Version     : 9.1                               Vendor:
> > MandrakeSoft Release     : 0.9mdk                        Build Date:
> > Thu Jan 23 17:51:50 2003 Install date: (not installed)              
> > Build Host: ke.mandrakesoft.com Group       :
> > System/Configuration/Other    Source RPM: (none) Size        : 3624910
> >                          License: GPL
> > Packager    : Thierry Vignaud <[EMAIL PROTECTED]>
> > URL         : http://www.mandrakelinux.com/en/cvs.php3
> 
> Pkg now takes longer than kde to launch---strace attached

usually, when a perl gtk+-2 app eat all cpu power, it means gtk+ try
to crash but some bad interaction between perl, perl-gtk and gtk+
happens.

please try drakconf-9.1-0.11mdk release
 
> (#1) Xlib: unexpected async reply (sequence 0x113a)!

something very weird happened

> The program 'drakconf.real' received an X Window System error.
> This probably reflects a bug in the program.
> The error was 'BadIDChoice (invalid resource ID chosen for this
> connection)'.  (Details: serial 4479 error_code 14 request_code 1
> 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.) The program 'drakconf.real' received an X Window System
> error. This probably reflects a bug in the program.
> The error was 'BadIDChoice (invalid resource ID chosen for this
> connection)'.  (Details: serial 4477 error_code 14 request_code 1
> 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.)


Reply via email to