https://bugzilla.novell.com/show_bug.cgi?id=224251 ------- Comment #1 from seife@novell.com 2006-11-28 11:45 MST ------- console log from my client machine: seife@strolchi:~> ssh -X root@e111 root@e111's password: openSUSE Installation /usr/bin/xauth: creating new authority file /root/.Xauthority Welcome to the inst-sys on 10.10.101.111 2.6.18.2-31-default x86_64 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 (128 columns x 26 lines). *** Starting YaST2 *** Useless use of string eq in void context at /usr/lib/perl5/vendor_perl/5.8.8/Bootloader/Core/GRUB.pm line 1382 (#1) (W void) You did something without a side effect in a context that does nothing with the return value, such as a statement that doesn't return a value from a block, or the left side of a scalar comma operator. Very often this points not to stupidity on your part, but a failure of Perl to parse your program the way you thought it would. For example, you'd get this if you mixed up your C precedence with Python precedence and said $one, $two = 1, 2; when you meant to say ($one, $two) = (1, 2); Another common error is to use ordinary parentheses to construct a list reference when you should be using square or curly brackets, for example, if you say $array = (1,2); when you should have said $array = [1,2]; The square brackets explicitly turn a list value into a scalar value, while parentheses do not. So when a parenthesized list is evaluated in a scalar context, the comma is treated like C's comma operator, which throws away the left argument, which is not what you want. See perlref for more on this. This warning will not be issued for numerical constants equal to 0 or 1 since they are often used in statements like 1 while sub_with_side_effects(); String constants that would normally evaluate to 0 or 1 are warned about. X11 connection rejected because of wrong authentication. *** Preparing SSH installation for reboot *** *** NOTE: after reboot, you have to reconnect and call *** *** /usr/lib/YaST2/startup/YaST2.ssh *** Connection to e111 closed by remote host. Connection to e111 closed. seife@strolchi:~> ssh -X root@e111 Warning: Permanently added 'e111,10.10.101.111' (RSA) to the list of known hosts. Password: Have a lot of fun... /usr/bin/xauth: creating new authority file /root/.Xauthority e111:~ # /usr/lib/YaST2/startup/YaST2.ssh *** Starting YaST2 *** *** Preparing SSH installation for reboot *** *** NOTE: after reboot, you have to reconnect and call *** *** /usr/lib/YaST2/startup/YaST2.ssh *** Broadcast message from root (pts/0) (Tue Nov 28 19:27:55 2006): The system is going down for reboot NOW! removed `/var/lib/YaST2/runme_at_boot' continue with booting ... You can login with the (new?) root password or the new created user account in a few seconds ... e111:~ # Connection to e111 closed. seife@strolchi:~> ssh -X root@e111 ssh: connect to host e111 port 22: No route to host seife@strolchi:~> ssh -X root@e134 Warning: Permanently added 'e134,10.10.101.134' (RSA) to the list of known hosts. Password: Last login: Tue Nov 28 19:30:43 2006 Have a lot of fun... e134:~ # /usr/lib/YaST2/startup/YaST2.ssh e134:~ # -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.