|
Bugzilla – Full Text Bug Listing |
| Summary: | yast2-users cmdline error | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Distribution | Reporter: | Michal Svec <msvec> |
| Component: | YaST2 | Assignee: | E-mail List <yast2-maintainers> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | dgonzalez, msvec, mvidner |
| Version: | Leap 15.4 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
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? 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 *** |
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.