Find the answer to your Linux question:
Results 1 to 7 of 7
Often I get the following message when starting FireFox: Firefox is already running, but is not responding. To open a new window, you must first close the existing Firefox process, ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Linux Newbie blnl's Avatar
    Join Date
    Jan 2009
    Location
    The Netherlands
    Posts
    168

    Question [SOLVED] How to kill uninterruptible process?


    Often I get the following message when starting FireFox:
    Firefox is already running, but is not responding. To open a new window, you must first close the existing Firefox process, or restart your system.
    At the same time CPU usage goes to 100%, load is extremely high and my PC is becoming unresponsive.

    I tried killing the process:
    Code:
    killall -9 firefox
    but without success.

    In the System Monitor I see that firefox is marked as "uninterruptible" process.

    Two questions:
    Why is this happening?
    How to kill such an uninteruptible process?
    Fedora_20@Dell_Latitude_E6410
    Ubuntu_14.04_LTS@HP_Compaq_DC7100

  2. #2
    RDU
    RDU is offline
    Just Joined!
    Join Date
    Aug 2010
    Posts
    89
    above kill -9, I think there is only reboot...
    But are you running 64 bit and have openned PDF file in the browser ? There is some old version of Adobe reader plugin wich hang on 64 bits, so make the browser hang. In this case, check to kill those acroread process (kill -9) and it will free the browser itself.

  3. #3
    Linux Newbie blnl's Avatar
    Join Date
    Jan 2009
    Location
    The Netherlands
    Posts
    168
    No, I'm running 32 bit. No PDF is opened in the browser.

    I tried removing
    .mozilla/firefox/profile.default/lock and
    .mozilla/firefox/profile.default/.parentlock, but it didn't help.

    By the way, the issue started a week ago, after consuming a bunch of fedora12 updates.
    Last edited by blnl; 08-06-2010 at 08:25 AM.
    Fedora_20@Dell_Latitude_E6410
    Ubuntu_14.04_LTS@HP_Compaq_DC7100

  4. $spacer_open
    $spacer_close
  5. #4
    Linux Newbie blnl's Avatar
    Join Date
    Jan 2009
    Location
    The Netherlands
    Posts
    168
    I believe I solved it! (by reinstalling firefox and thunderbird)

    Code:
    yum reinstall firefox
    yum reinstall thunderbird
    Everything seems to be normal again (no annoying error messages, no uninteruptible processes, CPU load is normal).
    Fedora_20@Dell_Latitude_E6410
    Ubuntu_14.04_LTS@HP_Compaq_DC7100

  6. #5
    Linux Engineer Segfault's Avatar
    Join Date
    Jun 2008
    Location
    Acadiana
    Posts
    877
    Another utility is xkill, it works differently, forces X server to close connection to the client. Works even when process is not listening - and thus not reponding to kill command.

  7. #6
    Linux Newbie blnl's Avatar
    Join Date
    Jan 2009
    Location
    The Netherlands
    Posts
    168

    Thumbs up

    Quote Originally Posted by Segfault View Post
    Another utility is xkill, it works differently, forces X server to close connection to the client. Works even when process is not listening - and thus not reponding to kill command.
    Thanks a lot!
    This can be very useful.
    Fedora_20@Dell_Latitude_E6410
    Ubuntu_14.04_LTS@HP_Compaq_DC7100

  8. #7
    Linux Engineer Segfault's Avatar
    Join Date
    Jun 2008
    Location
    Acadiana
    Posts
    877
    You are welcome!

    The problem with kill (pkill, killall) command is it is a signal sent to the process. If the process in question is stuck it may not be listening to signals sent to it. The only solution is to kill the parent process. If parent is init ... then it looks like reboot. BTW, pstree command will display it rather nicely.
    Luckily enough in X server you can choose which child to terminate using xkill.

Posting Permissions

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