public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: staticsafe <me@staticsafe.ca>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user]  Firefox not killing processes on close
Date: Sun, 10 Nov 2013 16:53:22 -0500	[thread overview]
Message-ID: <52800052.1060404@staticsafe.ca> (raw)
In-Reply-To: <527FFCC8.8060508@gmail.com>

On 11/10/2013 16:38, Dale wrote:
> Howdy,
> 
> I have noticed something that really bugs me.  I sometimes have a few
> Firefox sessions running.  I do this because I have to be logged into a
> website with more than one user/password.  Here is my issue.  If I click
> the X box to close a session of Firefox, it doesn't seem to kill the
> process.  I end up having to go to a Konsole and killing the process
> with either the kill command or pkill.  Naturally, all the processes are
> named Firefox so I can't tell one from the other.  That leads to me
> killing the wrong one at times. 
> 
> My question is this, why does Firefox not kill its processes as it
> should?  When I click the X and it closes, it should kill the process
> right?  When it does not kill correctly and I try to restart that
> session, I get the error that the session is already running.
> 
> This has been going on for a while.  What can I look for or do to
> correct this? 
> 
> Also, after large updates, I go to the boot runlevel, kill any processes
> that shouldn't be running, then go back to default runlevel.  Sometimes,
> I have to kill quite a few processes to get a clean list.  While this is
> not just a Firefox issue, it is just the one that gets in the way the
> most.  It seems there is a underlying issue somewhere and Firefox is
> just one symptom. 
> 
> Anyone have thoughts on this? 
> 
> Thanks.
> 
> Dale
> 
> :-)  :-)  
> 

What version of Firefox? What addons (if any) do you use with Firefox?

I have this problem except it is with Thunderbird (on Windows).

-- 
staticsafe
O< ascii ribbon campaign - stop html mail - www.asciiribbon.org
Please don't top post. It is not logical.
Please don't CC me! I'm subscribed to whatever list I just posted on.


  reply	other threads:[~2013-11-10 21:53 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-10 21:38 [gentoo-user] Firefox not killing processes on close Dale
2013-11-10 21:53 ` staticsafe [this message]
2013-11-10 22:07   ` Dale
2013-11-11 22:40     ` Frank Steinmetzger
2013-11-11 22:49       ` Peter Weilbacher
2013-11-12  2:28       ` Dale
2013-11-11  1:07 ` Walter Dnes
2013-11-11  3:53   ` Dale
2013-11-11  6:36     ` Alan McKinnon
2013-11-11  7:39       ` Dale
2013-11-11 11:18         ` Alan McKinnon
2013-11-12  1:13           ` Dale
2013-11-11 14:35     ` gottlieb
2013-11-11 14:58       ` Neil Bothwick
2013-11-11  6:24   ` Yohan Pereira
2013-11-11  7:44     ` Dale
2013-11-11  7:53       ` Yohan Pereira
2013-11-11  8:19         ` Dale
2013-11-22 12:47           ` Dale
2013-11-11 14:52       ` Bruce Hill
2013-11-11 17:13         ` Alexander Kapshuk
2013-11-11 10:11     ` Neil Bothwick
2013-11-11 18:28 ` Edward M
2013-11-11 18:50   ` Bruce Hill
2013-11-11 19:44     ` Edward M
2013-11-11 19:57       ` Alexander Kapshuk
2013-11-11 20:46         ` Edward M
2013-11-11 20:49           ` Alexander Kapshuk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52800052.1060404@staticsafe.ca \
    --to=me@staticsafe.ca \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox