Bug 989279

Summary: OCICLI warns (perl) unable to close filehandle properly: Bad file descriptor
Product: [openSUSE] openSUSE Tumbleweed Reporter: Jeroen Pluimers <jeroen.forums.opensuse.org>
Component: YaST2Assignee: E-mail List <yast2-maintainers>
Status: RESOLVED DUPLICATE QA Contact: Jiri Srain <jsrain>
Severity: Normal    
Priority: P5 - None CC: ancor, jeroen.forums.opensuse.org, mvidner
Version: Current   
Target Milestone: ---   
Hardware: x86-64   
OS: SUSE Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Jeroen Pluimers 2016-07-17 10:24:04 UTC
On "openSUSE Tumbleweed (20160714) (x86_64)" with text based install (no GUI at all), I get this a warning when executing OCICLI.

More details at https://gist.github.com/jpluimers/e26ffaf9d406e5e1da5e255b39eb5520

# OCICLI http://software.opensuse.org/ymp/server:monitoring/openSUSE_Tumbleweed/lnav.ymp
If you continue, the following repositories will be subscribed:
	* http://download.opensuse.org/repositories/openSUSE:/Tumbleweed/standard/
	* http://download.opensuse.org/repositories/server:/monitoring/openSUSE_Tumbleweed/
If you continue, the following software packages will be installed:
	* lnav
Warning: unable to close filehandle properly: Bad file descriptor, <STDIN> line
	7 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.
    
Continue? y/N
Comment 1 Steffen Winterfeldt 2016-08-12 13:13:17 UTC
Please attach yast logs (run 'save_y2logs' and attach the archive it creates).
Comment 2 Martin Vidner 2016-09-01 08:12:53 UTC
I dont think the logs would help here.

Possibly a duplicate of https://bugzilla.suse.com/show_bug.cgi?id=966042
Comment 3 Ancor Gonzalez Sosa 2016-10-06 16:00:23 UTC
(In reply to Martin Vidner from comment #2)
> I dont think the logs would help here.
> 
> Possibly a duplicate of https://bugzilla.suse.com/show_bug.cgi?id=966042

O also think so

*** This bug has been marked as a duplicate of bug 966042 ***