|
Bugzilla – Full Text Bug Listing |
| Summary: | Yast ncurses does not open Network Settings perl error | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | ray herman <rh> |
| Component: | YaST2 | Assignee: | E-mail List <yast2-maintainers> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Current | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
Looks like bug 1122473. Reproduced, it is. *** This bug has been marked as a duplicate of bug 1122473 *** |
VERSION_ID="20190110" Ncurses YaST cannot open Network Settings from ncurses mrnu. YaST > System > Network Settings # yast lan opens the module OK. Error message points to perl # yast [System > Network Settings] [Quit] Warning: unable to close filehandle __ANONIO__ properly: Bad file descriptor, <STDIN> line 2 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.