Is there a way to reboot the computer while its stuck on "Starting GNOME Desktop Manager"?
Ctrl-Alt-Backspace doesn,t work and if you haven't a reset button on the computer, pull the plug.
It may take a while to reboot.
Ssh to the machine as a normal user, sudo reboot. (This is assuming the network is running.)
Other than that, I know of no other way.
Dave Sent from my BlackBerry® smartphone powered by Mobilicity
-----Original Message----- From: Richard Vickery richard.vickeryrv@gmail.com Sender: users-bounces@lists.fedoraproject.org Date: Wed, 3 Jul 2013 11:30:43 To: Community support for Fedora usersusers@lists.fedoraproject.org Reply-To: Community support for Fedora users users@lists.fedoraproject.org Subject: Booting
On 07/03/2013 01:17 PM, davidschaak1@mobilicity.blackberry.com wrote:
Ctrl-Alt-Backspace doesn,t work and if you haven't a reset button on the computer, pull the plug.
And, if you're on a laptop, pull the battery. Back when I was doing tech support, I had that happen to a caller at least once.
Am 03.07.2013 22:19, schrieb Mateusz Marzantowicz:
On 03.07.2013 20:30, Richard Vickery wrote:
Is there a way to reboot the computer while its stuck on "Starting GNOME Desktop Manager"?
Yes, press the power button for a few seconds and then release it. This should work on most PCs and notebooks
this is a *hard power off* - gratulations....
if the kernel is still alive and acpid running press the power button *short* and wait a while - the system will do a *clean powerdown* in 99.9% of all cases
On 03.07.2013 22:32, Reindl Harald wrote:
Am 03.07.2013 22:19, schrieb Mateusz Marzantowicz:
On 03.07.2013 20:30, Richard Vickery wrote:
Is there a way to reboot the computer while its stuck on "Starting GNOME Desktop Manager"?
Yes, press the power button for a few seconds and then release it. This should work on most PCs and notebooks
this is a *hard power off* - gratulations....
So, what? Question was about rebooting without specifying type of reboot. I've never had any problems when hard rebooting Linux, especially just after power on.
if the kernel is still alive and acpid running press the power button *short* and wait a while - the system will do a *clean powerdown* in 99.9% of all cases
This might work or not in this particular situation but we know nothing about kernel condition.
Mateusz Marzantowicz
On Jul 3, 2013 1:12 PM, "Richard Vickery" richard.vickeryrv@gmail.com wrote:
Is there a way to reboot the computer while its stuck on "Starting GNOME
Desktop Manager"?
Usually by this point in the boot process you can press CTRL+ALT+F2 to get a console login. From there you can run ’reboot ’ to restart your system, or even better, just try restarting gdm with ’systemctl reboot gdm ’.
-T.C.
El 2013-07-04 02:04, T.C. Hollingsworth escribió:
On Jul 3, 2013 1:12 PM, "Richard Vickery" richard.vickeryrv@gmail.com wrote:
Is there a way to reboot the computer while its stuck on "Starting
GNOME Desktop Manager"?
Usually by this point in the boot process you can press CTRL+ALT+F2 to get a console login. From there you can run ’reboot ’ to restart your system, or even better, just try restarting gdm with ’systemctl reboot gdm ’.
-T.C.
Another good option if everything else fails (and you have configured previously kernel.sysrq=1 with sysctl) is:
Alt+SysRq+ {R, E, I, S, U, B}
See: https://en.wikipedia.org/wiki/Magic_SysRq_key#Uses
hello juan,
On 07/04/2013 04:49 AM, Juan Orti Alcaine wrote: <>
Another good option if everything else fails (and you have configured previously kernel.sysrq=1 with sysctl) is:
Alt+SysRq+ {R, E, I, S, U, B}
very good read. thanks for posting.
1 question. would not {r, e, i, s, u, b}, lower case, be used, as that is what is shown in chart?
Allegedly, on or about 04 July 2013, Juan Orti Alcaine sent:
Another good option if everything else fails (and you have configured previously kernel.sysrq=1 with sysctl) is:
Alt+SysRq+ {R, E, I, S, U, B}
Would you expect this to work with USB keyboards? There's more protocols in the way of USB than PS/2, or other schemes, requiring a working operating system.
El 2013-07-04 23:52, g escribió:
hello juan,
On 07/04/2013 04:49 AM, Juan Orti Alcaine wrote: <>
Another good option if everything else fails (and you have configured previously kernel.sysrq=1 with sysctl) is:
Alt+SysRq+ {R, E, I, S, U, B}
See: https://en.wikipedia.org/wiki/Magic_SysRq_key#Uses
very good read. thanks for posting.
1 question. would not {r, e, i, s, u, b}, lower case, be used, as that is what is shown in chart?
Yes, the letters should be lower case
El 2013-07-05 05:47, Tim escribió:
Allegedly, on or about 04 July 2013, Juan Orti Alcaine sent: Another good option if everything else fails (and you have configured previously kernel.sysrq=1 with sysctl) is:
Alt+SysRq+ {R, E, I, S, U, B}
See: https://en.wikipedia.org/wiki/Magic_SysRq_key#Uses
Would you expect this to work with USB keyboards? There's more protocols in the way of USB than PS/2, or other schemes, requiring a working operating system.
I've had no problems with USB keyboards, it should work as expected.
Am 03.07.2013 23:00, schrieb Mateusz Marzantowicz:
On 03.07.2013 22:32, Reindl Harald wrote:
Am 03.07.2013 22:19, schrieb Mateusz Marzantowicz:
On 03.07.2013 20:30, Richard Vickery wrote:
Is there a way to reboot the computer while its stuck on "Starting GNOME Desktop Manager"?
Yes, press the power button for a few seconds and then release it. This should work on most PCs and notebooks
this is a *hard power off* - gratulations....
So, what? Question was about rebooting without specifying type of reboot.
so what - for your tip pull the power supply would be quicker and the same
I've never had any problems when hard rebooting Linux, especially just after power on
maybe luck maybe you simply not know which not so important files got truncated
a hard power off is nothing anyone should recommend to another person if he is not the one solving problems which may appear after that *without a big fat warning*
if the kernel is still alive and acpid running press the power button *short* and wait a while - the system will do a *clean powerdown* in 99.9% of all cases
This might work or not in this particular situation but we know nothing about kernel condition.
since this is mostly a GNOME problem pretty sure acpid works
if such problems are happening repeatly configure sysrq http://en.wikipedia.org/wiki/Magic_SysRq_key
and last but not least CTRL+ALT+F3 may offer a text terminal with a working login however, a hard power off is the very last resort and not recommendable
Am 05.07.2013 05:47, schrieb Tim:
Allegedly, on or about 04 July 2013, Juan Orti Alcaine sent:
Another good option if everything else fails (and you have configured previously kernel.sysrq=1 with sysctl) is:
Alt+SysRq+ {R, E, I, S, U, B}
Would you expect this to work with USB keyboards? There's more protocols in the way of USB than PS/2, or other schemes, requiring a working operating system
i would not only expect, it works for sure
ALT+PrintScrn+S
[harry@srv-rhsoft:~]$ dmesg [44925.260133] SysRq : Emergency Sync [44927.114134] Emergency Sync complete ___________________________________
Under graphical environments (such as GNOME or KDE) 'Alt'+'PrintScrn/SysRq'+key combination generally only leads to a screenshot being dumped. To avoid this Print Screen feature the magic SysRq combination should include the Ctrl, becoming 'Ctrl'+'Alt'+'SysRq'+key. For the same purposes the AltGr key, if present, can be used in place of the Alt key. On some laptops SysRq is accessible only by pressing 'Fn'. In this case the combination is a bit trickier: hold 'Alt', hold 'Fn', hold 'SysRq', release 'Fn', press key. The magic SysRq can also be accessed from the serial console.[2]
On Jul 3, 2013 5:04 PM, "T.C. Hollingsworth" tchollingsworth@gmail.com wrote:
On Jul 3, 2013 1:12 PM, "Richard Vickery" richard.vickeryrv@gmail.com
wrote:
Is there a way to reboot the computer while its stuck on "Starting
GNOME Desktop Manager"?
Usually by this point in the boot process you can press CTRL+ALT+F2 to
get a console login. From there you can run ’reboot ’ to restart your system, or even better, just try restarting gdm with ’systemctl reboot gdm ’.
-T.C.
"systemctl reboot gdm" has too many arguments