https://qa.mandrakesoft.com/show_bug.cgi?id=1069
Product: drakconf
Component: drakconf
Summary: BUG with LANGUAGE fr_FR:fr
Version: 9.1-0.9mdk
Platform: PC
OS/Version: All
Status: UNCONFIRMED
Severity: major
Priority: P2
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
The last version of DrakConf cannot launch embeded application. Error message/
[root@localhost bin]# perl drakconf
[root@localhost bin]# 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)
BUG with LANGUAGE fr_FR:fr
[root@localhost bin]# Use of uninitialized value in exec at
/usr/sbin/drakconf.real line 631 (#1)
Xlib: unexpected async reply (sequence 0xa5a)!
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 3105 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 'BadWindow (invalid Window parameter)'.
(Details: serial 3106 error_code 3 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.)
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
