Bug 1201046 - yast2-users cmdline error
Summary: yast2-users cmdline error
Status: RESOLVED DUPLICATE of bug 1203080
Alias: None
Product: openSUSE Distribution
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Leap 15.4
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: Jiri Srain
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-06-30 08:28 UTC by Michal Svec
Modified: 2022-09-09 15:16 UTC (History)
3 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michal Svec 2022-06-30 08:28:51 UTC
Adding a user using yast2-users cmdline interface throws an error:

bash# yast2 users add username=someuser uid=12345

Password for New User:
Confirm the password:
Warning: unable to close filehandle properly: Bad file descriptor, <STDIN> line
        9 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.
Comment 2 David Diaz 2022-07-12 07:49:25 UTC
Hi Michal!

I can't see anything relevant in the attached logs. In fact, the `useradd` command was successfully executed.

Are you able to reproduce it?
Comment 3 Martin Vidner 2022-07-12 15:47:54 UTC
I invoke the powers of my mail archive!
The problem is in perl-Term-ReadLine, fixed in TW.

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