|
Bugzilla – Full Text Bug Listing |
| Summary: | "yast2 lan list" warns about closing STDIN | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Christian Boltz <suse-beta> |
| Component: | YaST2 | Assignee: | E-mail List <yast2-maintainers> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | kanderssen, schubi, suse-beta |
| Version: | Current | Flags: | schubi:
needinfo?
(suse-beta) |
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | openSUSE 42.2 | ||
| Whiteboard: | |||
| Found By: | Beta-Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
(In reply to Christian Boltz from comment #0) > I see this with yast2-network-3.3.6-1.1.noarch (sorry, I didn't have time > for tumbleweed updates in the last weeks) I have tested the current 4.0.14 version and it has worked. Maybe you should give an update a try ? :-) > > This bug is probably not depending on the hardware or config, therefore not > attaching y2logs. If you need them nevertheless, please tell me. If you still an error please attach the logs. Thanks ! Seems to be a duplicate of https://bugzilla.suse.com/show_bug.cgi?id=966042, so closing it by now. Feel free to reopen it if I'm wrong. *** This bug has been marked as a duplicate of bug 966042 *** |
The output says it all: # yast2 lan list id name, bootproto 0 Wireless 7260, Not configured 1 RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller, Not configured Warning: unable to close filehandle properly: Bad file descriptor, <STDIN> line 5 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. I see this with yast2-network-3.3.6-1.1.noarch (sorry, I didn't have time for tumbleweed updates in the last weeks) This bug is probably not depending on the hardware or config, therefore not attaching y2logs. If you need them nevertheless, please tell me.