Description of problem: On two fresh installations, although I configured none of the several local accounts for autologin, there is an account the automatically logs-in after booting the machines. I see the desktop during a fraction of a second an then an error message that says (in Spanish so my translation back to English might no the exact): "Something went wrong. An error happened and the system cannot be recovered. Close the session and try again." This happens with every boot on both machines. Version-Release number of selected component (if applicable): Installed from the Mageia 2 ISO image How reproducible: I installed 2 systems and it happened on both of them. Each system has several users. Steps to Reproduce: No really sure of this. On both cases I made a fresh installation and ended up with system showing this problem.
CC: (none) => listas.apl
Hey, we can't change Mageia 2's installer. So please test if those problems are present in Mageia 3 alphas too?
Keywords: (none) => NEEDINFOCC: (none) => sander.lepikVersion: 2 => Cauldron
That's not an installer issue. This is the desktop that is crashing. Are you using GNOME or KDE?
CC: (none) => thierry.vignaudComponent: Installer => RPM Packages
Summary: In a fresh installation => desktop crashed on autologin
(In reply to comment #2) > That's not an installer issue. > This is the desktop that is crashing. > Are you using GNOME or KDE? I use Gnome. Here I'm just guessing. IMHO, the desktop crashing is just a side-effect of something that was incorrectly configured by the installer. I didn't configure the auto-login and still it was happening. From this point we can easily imagine that Gnome was crashing because a something went wrong because of an incomplete/wrong configuration. We can also argue whether the desktop should crash on a wrong configuration, but this is another story.
(In reply to comment #1) > Hey, > > we can't change Mageia 2's installer. So please test if those problems are > present in Mageia 3 alphas too? At this precise moment I don't have a machine to try it. I'll give the information as soon as I can. However, if the problem was not explicitly solved for Mageia 3 (which was the aim of this bug), chances are that it will still happen.
No. GNOME has been upgraded between the to, and lot of stuff has changed in GNOME. Can you look at /var/log/gdm/* or you ~/.xsession-errors for any error messages?
CC: (none) => olavVersion: Cauldron => 2
(In reply to comment #5) > No. GNOME has been upgraded between the to, and lot of stuff has changed in > GNOME. > > Can you look at /var/log/gdm/* or you ~/.xsession-errors for any error > messages? These files are rotated constantly, so I have no trace of the time when this crash was happening (I fixed it manually several months ago).
Let me disagree with the change in this bug's title. What I signaled was that installer configured auto-login when I said I didn't want it and that this configuration was wrong driving the desktop to a crash.
Can anyone confirm if this is still a valid bug ? Roelof
CC: (none) => r.wobben
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 => RESOLVEDResolution: (none) => OLD