| Summary: | No root password | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | matteo pozzoli <mattepozzoli> |
| Component: | Installer | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | marja11 |
| Version: | 5 | Keywords: | NEEDINFO |
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
|
Description
matteo pozzoli
2016-03-13 15:30:41 CET
(In reply to matteo pozzoli from comment #0) > Description of problem: During the installer of Mageia-5_x86_64 Did you use a traditional (so non-Live) iso, or a Live iso? Did you check its sha1sum before using it? > I could > not enter the root password. Why not? (please be as precise as possible) > So now when I try to install a new application > (*.rpm) I did know the authentication password. what should I do to solve > the problem? We have too little information at the moment. You could try hitting "enter" without typing a password, though. Keywords:
(none) =>
NEEDINFO It should have asked you for a root password at this step: - classical installer: http://doc.mageia.org/installer/5/en/content/addUser.html - live installer: http://doc.mageia.org/installer/5/en/content/addUser.html @ Matteo Please reply. We don't have the slightest idea what happened For instance: * We do not know whether you got the screen to add the password, but your keyboard didn't respond * or whether you didn't get that screen * we do not know which iso you used to install from * we do not know whether you could reproduce the problem when installing again (preferably from an iso you retrieved in a different way) When you reply, we'll probably need additional information, because none of us hit this issue. That is _not_ to spoil your day, but because, without enough information, it is impossible to fix bugs. Please read: https://wiki.mageia.org/en/How_to_report_a_bug_properly Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution. Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Closing as OLD. Feel free to reopen and supply the requested information, if needed Status:
NEW =>
RESOLVED Changing resolution from OLD to INVALID as the bug report in itself is not old, but as we did not get any tangible information, it looks like a user mistake and not a bug in the first place. Resolution:
OLD =>
INVALID |