| Summary: | Drakxconf launches the autologin configuration tool instead of the bootloader configuration tool | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Malo Deniélou <pmdenielou> |
| Component: | RPM Packages | Assignee: | Thierry Vignaud <thierry.vignaud> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Low | Keywords: | NEEDINFO |
| Version: | 2 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
|
Description
Malo Deniélou
2012-08-24 12:13:20 CEST
Malo Deniélou
2012-08-24 12:13:37 CEST
Depends on:
(none) =>
7160 confirmed here mga1 i586
Thierry Vignaud
2012-08-24 16:07:00 CEST
Depends on:
7160 =>
(none) Works for me on both mga2 & cauldron (x86_64): - clicking the "set up autologin" icon results in displaying the autologin settings - clicking the "set up boot system" icon results in displaying the boot loader settings Keywords:
(none) =>
NEEDINFO No, Thierry, you need to type drakxconf in root console. The bug is not present with drakconf. Why do you run it directly? That's a internal simple wrapper that I wrote which is run by mcc when in text mode... Priority:
Normal =>
Low Workarounded in SVN by preventing using it in graphical mode. Thanks, but the workaround is not correct. Since the point is that selecting 'Boot loader' should give the good option, whether in graphical or console mode. Basically, the use case is: when X fails for a reason or another, using drakxconf in console mode is a normal thing to do. It's how I discovered the bug. And it's definitely linked with bug 7160 where, without X, typing drakboot in console mode makes sense, but without the expected behaviour of configuring the boot loader. This message is a reminder that Mageia 2 is nearing its end of life. Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- The Mageia Bugsquad Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad Status:
NEW =>
RESOLVED |