| Summary: | Reboot from GDM hangs on a BIOS system. | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Doug Laidlaw <laidlaws> |
| Component: | Installer | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | marja11, olav, qa-bugs |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
|
Description
Doug Laidlaw
2014-11-13 07:42:37 CET
Sorry, my Official is 32-bit, my Cauldron is 64-bit. Hardware:
i586 =>
x86_64 How exactly do you reboot? If you didn't do that by just giving the "reboot" command in a terminal, please try whether that works better. CC:
(none) =>
marja11 On typing "sudo reboot" in a terminal, the screen went black within a second or two, disk activity stopped and I couldn't access a TTY. I don't normally do it that way. I find that unless I log out, my session is not saved. So I log out from the menu, and select Restart in GDM. That is how I did it before the bug report. I finish up in the same place, but not nearly so quickly. Was that a terminal in Gnome, or was that on a text tty? That might sound like a silly question, but I've seen something unexpectedly different in a Gnome-terminal than in any text tty See https://bugs.mageia.org/show_bug.cgi?id=14489#c0 Btw, how was your cauldron started? As a Mga5beta1 install (if so from which iso)? @ ovitters Is GDM capable of setting what to boot into next, in other words: when restarting from GDM, can the bootloader be skipped/ignored/whatever? If so, where can you check its restart settings? CC:
(none) =>
olav As I understand it, the way to avoid the GUI is to use rebootin. KDM gives me the option of selecting an OS, but it relies on rebootin. I have Grub2 as my bootloader, and it doesn't support rebootin. In reply to Comment 4: It was XFCE's normal terminal. I can try a tty. My original Cauldron was in a mess, with commands not set SUID. The drakconf and mgaapplet screens would flicker and disappear on being started. I did a clean reinstall from the alpha 2 liveDVD, installed all updates, then upgraded it with the 64-bit Beta 1 DVD. That seemed to change nothing, i.e. I was already at that point. The problem started to show up before the reinstall, and I attributed it to the faulty installation. It could have come from a recent normal update. In a console, logged in as root (not using su) the commands
shutdown -r now
and
reboot
both ran perfectly.
This seems to be fixed since I installed task-kde-minimal. (In reply to Doug Laidlaw from comment #8) > This seems to be fixed since I installed task-kde-minimal. cc'ing QA-team in case someone who installed the LiveGnome DVD can reproduce a hang when restarting from GDM (no need to install XFCE afterwards, IMHO, because very few users will do that). I think this bug can be closed if no one can reproduce it in a plain install (with updates) from the 5beta1 Live. CC:
(none) =>
qa-bugs s/afterwards/before testing/ (In reply to Marja van Waes from comment #9) > (In reply to Doug Laidlaw from comment #8) > > This seems to be fixed since I installed task-kde-minimal. > > > cc'ing QA-team in case someone who installed the LiveGnome DVD can reproduce > a hang when restarting from GDM (no need to install XFCE afterwards, IMHO, > because very few users will do that). > > I think this bug can be closed if no one can reproduce it in a plain install > (with updates) from the 5beta1 Live. It could be hardware-related as well. I didn't have the boot problem that made 4.1 necessary, but Mondo left me with no keyboard. Everybody probably has a small selection of them. XFCE can be installed from the installer, but I think that it may be the minimal package. I agree that the bug can probably be closed. |