Page 1 of 2 12 LastLast
Results 1 to 10 of 12

Thread: Ctrl alt F2. What next?

  1. #1
    Join Date
    Aug 2006
    Location
    London, UK
    Beans
    Hidden!

    Ctrl alt F2. What next?

    Sometimes a program freezes and effects the ability of other actions. After I press ctrl alt F2 and it drops me into the manual login, what should I do next to restart the system and minimise the loss of data.

  2. #2
    Join Date
    Jan 2008
    Beans
    4,757

    Re: Ctrl alt F2. What next?

    Instead of Ctrl Alt F2, you can use Ctrl+Alt+Backspace to restart X and return to the login screen.

    Although, if you wish to carry on with your current method, just login to the VT session and type in
    Code:
    sudo killall appname
    Then return to your X session (Ctrl+Alt+F7), then continue with your duties.

    Regards
    Iain

  3. #3
    Join Date
    Jan 2007
    Location
    /dev/random
    Beans
    Hidden!
    Distro
    Ubuntu 11.10 Oneiric Ocelot

    Re: Ctrl alt F2. What next?

    Another alternative is to restart X (the graphical interface). When X freezes, simply push ctrl-alt-backspace. This will restart X without restarting the computer, then you can login again. Be aware though that you lose any unsaved data in any open applications.

    If ctrl-alt-backspace won't do anything you can use a terminal (getting to it as you described) and then after login issuing

    Code:
    sudo /etc/init.d/gdm restart
    If that doesn't do the trick either (which is rare) you can raise a skinny elephant. It's a silly name for a simple meme.

    Hold down alt + SysRQ (often also labeled Print Screen) and press the following keys in order:

    R - raising (switches keyboard from raw mode)
    S - skinny (sync all mounted filesystems)
    E - elephants (shuts down all processes except init)
    I - is (terminates all processes except init)
    U - utterly (remounts all filesystems in read-only mode)
    B - boring (immediately reboots the system)

    This is for when nothing else works.
    Sturgeon's Law: Ninety percent of everything is crap.

  4. #4
    Join Date
    Aug 2006
    Location
    London, UK
    Beans
    Hidden!

    Re: Ctrl alt F2. What next?

    Thank you both for your responses.

    Is there any restart combinaton of keys that does not bring a loss of data?

    Robin

  5. #5
    Join Date
    Oct 2005
    Beans
    475

    Re: Ctrl alt F2. What next?

    What's the difference between these commands?

    sudo reboot
    sudo shutdown -r now
    sudo /etc/init.d/gdm restart

  6. #6
    Join Date
    Nov 2006
    Location
    Spain
    Beans
    175
    Distro
    Ubuntu 9.04 Jaunty Jackalope

    Re: Ctrl alt F2. What next?

    The 1 and 2 reboots and the last one restarts only the GDM, not the whole system.

  7. #7
    Join Date
    Jan 2008
    Location
    Bentonville AR
    Beans
    Hidden!
    Distro
    Ubuntu 13.10 Saucy Salamander

    Re: Ctrl alt F2. What next?

    Code:
    sudo init 0
    Sayak Banerjee
    KDE Sysadmin | KDE e.V.
    Need help? Contact us.

  8. #8
    Join Date
    Aug 2006
    Location
    London, UK
    Beans
    Hidden!

    Re: Ctrl alt F2. What next?

    It seems that after Ctrl alt F2 I should in preference run

    sudo init 0

    so as to avoid a loss of data.

    sudo init 0 seems to halt the system. I should then follow it with

    sudo /etc/init.d/gdm restart

    If that fails try the other ideas mentioned in the replies.

    Have I understood properly?



    I have found that killall is difficult to use unless I know the exact process name. How do I find it if I have dropped into the command line?

    Robin

  9. #9
    Join Date
    Aug 2006
    Location
    London, UK
    Beans
    Hidden!

    Re: Ctrl alt F2. What next?

    Would someone like to confirm my assumptions in my last posting above?

    Robin

  10. #10
    Join Date
    Jan 2006
    Location
    Sunny Southend-on-Sea
    Beans
    5,424
    Distro
    Ubuntu 14.04 Trusty Tahr

    Re: Ctrl alt F2. What next?

    Quote Originally Posted by Robbyx View Post
    I have found that killall is difficult to use unless I know the exact process name. How do I find it if I have dropped into the command line?
    Well, you can tab-complete the process name. So, for example, killall fire followed by TAB will complete the command to killall firefox. Otherwise, ps ax will show you all the processes that are running, with their process IDs. If you want to really kill a process, you can kill -9 <PID>. See man ps and man kill for more information.
    None but ourselves can free our minds

Page 1 of 2 12 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •