On Mon, 2003-01-27 at 12:14, Bernard Varaine wrote: > drakxservices run fine when called direct from console but when called > from drakconf doesn't. > > > [root@doit bernard]# drakconf > [root@doit bernard]# Use of uninitialized value in split at > /usr/lib/libDrakX/detect_devices.pm line > 111 (#1) > (W uninitialized) An undefined value was used as if it were already > defined. It was interpreted as a "" or a 0, but maybe it was a > mistake. > To suppress this warning assign a defined value to your variables. > > To help you figure out what was undefined, perl tells you what > operation > you used the undefined value in. Note, however, that perl > optimizes your > program and the operation displayed in the warning may not necessarily > appear literally in your program. For example, "that $foo" is > usually optimized into "that " . $foo, and the warning will refer to > the concatenation (.) operator, even though there is no . in your > program. > > Use of uninitialized value in concatenation (.) or string at > /usr/lib/libDrakX/detect_devices.pm line 533 (#1) > Use of uninitialized value in pattern match (m//) at > /usr/lib/libDrakX/detect_devices.pm line 182 (#1) > Use of uninitialized value in pattern match (m//) at > /usr/lib/libDrakX/detect_devices.pm line 190 (#1) > Use of uninitialized value in exec at /usr/sbin/drakconf.real line 631 (#1) > Use of uninitialized value in pattern match (m//) at /usr/sbin/drakconf.real > line 689 (#1) > Xlib: sequence lost (0x1007a > 0x7fe) in reply type 0x0! > Xlib: sequence lost (0x10000 > 0x7fe) in reply type 0x0! > Xlib: sequence lost (0x10000 > 0x802) in reply type 0x0! > 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 2042 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.) > EMBED > parent XID 48234974 > mcc pid 31365 > The program 'drakconf.real' received an X Window System error. > This probably reflects a bug in the program. > The error was '243'. > (Details: serial 49151 error_code 243 request_code 18 minor_code 16) > (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.) > TODO: XSetInputFocus if force_focus > TODO: ensure focus stuff
I can confirm this one. Besides drakxservices, I get the same type of error when trying to launch urpmi or rpmdrake from drakconf as well. -- Jason Komar <[EMAIL PROTECTED]> Lubetec
