Bugzilla – Bug 157541
Error message during ssh remote installation
Last modified: 2006-04-24 12:27:17 UTC
The following error message is displayed when installing 10.1 beta7 remote on the console accessed via ssh: --8<-- SUSE Linux Installation /usr/X11R6/bin/xauth: creating new authority file /root/.Xauthority Welcome to the inst-sys... Linux 149.44.171.34 2.6.16-rc5-git9-2-default #1 Tue Mar 7 14:56:34 UTC 2006 i686 i686 i386 GNU/Linux /root run yast to start the installation inst-sys:~ # yast unicode_start skipped on /dev/pts/0 Probing connected terminal... Initializing virtual console... Found an xterm terminal on /dev/pts/0 (104 columns x 38 lines). *** Starting YaST2 *** Use of uninitialized value in split at /usr/share/YaST2/modules/Bootloader_API.pm line 211 (#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 numeric ne (!=) at /usr/share/YaST2/modules/Bootloader_API.pm line 215 (#1) Argument "<NULL>" isn't numeric in array element at /usr/lib/perl5/vendor_perl/5.8.8/Bootloader/Core/GRUB.pm line 1182 (#2) (W numeric) The indicated string was fed as an argument to an operator that expected a numeric value instead. If you're fortunate the message will identify which operator was so unfortunate. -->8-- This might just be cosmetic. I didn't see any impact on the installation so far.
There has been no activity for quite a while. I'm closing this bug as WONTFIX. If you feel this is inappropriate and the bug should remain open, or you have new information which may lead to an actual resolution, please reopen the bug and add the new status.