http://bugzilla.suse.com/show_bug.cgi?id=1051295 Bug ID: 1051295 Summary: non interactive use of yast seems currently broken Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers@suse.de Reporter: roger.whittaker@suse.com QA Contact: jsrain@suse.com Found By: --- Blocker: --- seen in 20170725 with yast2-3.3.4-1.1.x86_64 For example: # yast lan help YaST Configuration Module lan ------------------------------ Network Card Configuration Basic Syntax: yast2 lan interactive yast2 lan <command> [verbose] [options] yast2 lan help yast2 lan longhelp yast2 lan xmlhelp yast2 lan <command> help Commands: add Add a network card delete Delete a network card edit Change existing configuration list Display configuration summary show Display configuration summary Run 'yast2 lan <command> help' for a list of available options. Warning: unable to close filehandle properly: Bad file descriptor, <STDIN> line 21 during global destruction (#1) (S io) There were errors during the implicit close() done on a filehandle when its reference count reached zero while it was still open, e.g.: { open my $fh, '>', $file or die "open: '$file': $!\n"; print $fh $data or die "print: $!"; } # implicit close here Because various errors may only be detected by close() (e.g. buffering could allow the print in this example to return true even when the disk is full), it is dangerous to ignore its result. So when it happens implicitly, perl will signal errors by warning. Prior to version 5.22.0, perl ignored such errors, so the common idiom shown above was liable to cause silent data loss. -- You are receiving this mail because: You are on the CC list for the bug.