[gentoo-user] Firefox not killing processes on close

[gentoo-user] Firefox not killing processes on close

[Dale]

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

:-)  :-)  

-- 
I am only responsible for what I said ... Not for what you understood or how you interpreted my words!

Re: [gentoo-user] Firefox not killing processes on close

[staticsafe]

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.

Re: [gentoo-user] Firefox not killing processes on close

[Dale]

staticsafe wrote:
> 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).
>


Oh good heavens.  I have lots of add ons installed.  It would take me a
while to list them all, heck, just to get a list much list post them
here.  lol  I recall abduction, tab utilities, last pass off the top of
my head.  However, I have a test session that has very very few add ons
and it does the same way.  Also, I run into this with other processes as
well.  It seems to me that some package or the kernel is not killing
processes as it should.  I just don't know what that is. 

Also, I forgot to mention, I run into this with Seamonkey as well.  I
only have two sessions for it but don't use the 2nd one to much.  While
a bit aggravating, it is no big deal to kill the right one on it since I
usually only have one session running anyway. 

So, while it is Firefox that is buggin me, it's not only Firefox.  I
think this could be a deeper issue.  It could even be a KDE bug.  I
dunno.  I know when I go to boot runlevel, I have to kill quite a few
processes that are pretty stubborn to kill.  kill -15 usually doesn't
work so I end up using -9 to get it to die. 

Thoughts?

Dale

:-)  :-) 

-- 
I am only responsible for what I said ... Not for what you understood or how you interpreted my words!

Re: [gentoo-user] Firefox not killing processes on close

[Frank Steinmetzger]

[-- Attachment #1: Type: text/plain, Size: 2539 bytes --]

On Sun, Nov 10, 2013 at 04:07:34PM -0600, Dale wrote:

> >> 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. [...]

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

> Oh good heavens.  I have lots of add ons installed.  It would take me a
> while to list them all, heck, just to get a list much list post them
> here.

There’s an addon for that. ;-)
But if you start like that, I would recommend to thin out the list. You
never know what kind of conflicts and other interactions there might be
between addons. We could discuss this in another thread. ;-)

> lol  I recall abduction, tab utilities, last pass off the top of
> my head.  However, I have a test session that has very very few add ons
> and it does the same way.

With session you mean firefox profile? I know of no other way of having
different sets of addons simultaneously (short of Walter’s idea of using
different unix users).

> Also, I run into this with other processes as well. It seems to me
> that some package or the kernel is not killing processes as it should.
> I just don't know what that is.

What processes? If it’s Seamonkey which you mentioned elsewhere, it may
be the same problem/cause.
You could possibly identify the perpetrating process by looking at its
memory footprint. A process that is close to terminating would use much
less memory than a fully running process with tabs.

> It could even be a KDE bug.

I don’t really think so. You click the X, the window manager notifies
the program in the window to quit. The program destroys its X client,
KWin processes that event and poof. Nothing more KDE can do (IMHO).

> I know when I go to boot runlevel, I have to kill quite a few
> processes that are pretty stubborn to kill.  kill -15 usually doesn't
> work so I end up using -9 to get it to die. 

If you go to *that* length (switch to boot and kill processes manually),
why not do the *cough* Ubuntu way and simply reboot, since killing X
means killing most of your environment of running applications anyway?
-- 
Gruß | Greetings | Qapla’
Please do not share anything from, with or about me with any Facebook service.

The total intelligence on a planet is constant. Population grows...

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Firefox not killing processes on close

[Peter Weilbacher]

On 2013-11-11 23:40, Frank Steinmetzger wrote:
> On Sun, Nov 10, 2013 at 04:07:34PM -0600, Dale wrote:
> 
>> > What version of Firefox? What addons (if any) do you use with Firefox?
> 
>> Oh good heavens.  I have lots of add ons installed.  It would take me 
>> a
>> while to list them all, heck, just to get a list much list post them
>> here.
> 
> There’s an addon for that. ;-)

No need for that, just go to Help -> Troubleshooting Information and 
copy & paste the "Extensions" table.

Not that it seems to be central to answering the original problem...
    Peter.

Re: [gentoo-user] Firefox not killing processes on close

[Dale]

[-- Attachment #1: Type: text/plain, Size: 3448 bytes --]

Frank Steinmetzger wrote:
> On Sun, Nov 10, 2013 at 04:07:34PM -0600, Dale wrote:
>
>>>> 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. [...]
>
>>> What version of Firefox? What addons (if any) do you use with Firefox?


This has been going on for many versions.  I'm on firefox-17.0.9 now.


>
>> Oh good heavens.  I have lots of add ons installed.  It would take me a
>> while to list them all, heck, just to get a list much list post them
>> here.
>
> There’s an addon for that. ;-)
> But if you start like that, I would recommend to thin out the list. You
> never know what kind of conflicts and other interactions there might be
> between addons. We could discuss this in another thread. ;-)

Thing is, it does it on a "profile" that doesn't have but a very few add
ons installed.  This also happens with Seamonkey and other processes.


>
>> lol  I recall abduction, tab utilities, last pass off the top of
>> my head.  However, I have a test session that has very very few add ons
>> and it does the same way.
>
> With session you mean firefox profile? I know of no other way of having
> different sets of addons simultaneously (short of Walter’s idea of using
> different unix users).

Yes, I keep getting the two confused.  One of these days.  ;-)  Just
when I do get the name of something straight, they change it.  :-p


>
>
>> Also, I run into this with other processes as well. It seems to me
>> that some package or the kernel is not killing processes as it should.
>> I just don't know what that is.
>
> What processes? If it’s Seamonkey which you mentioned elsewhere, it may
> be the same problem/cause.
> You could possibly identify the perpetrating process by looking at its
> memory footprint. A process that is close to terminating would use much
> less memory than a fully running process with tabs.
>

That is my thinking too.  See below.

>> It could even be a KDE bug.
>
> I don’t really think so. You click the X, the window manager notifies
> the program in the window to quit. The program destroys its X client,
> KWin processes that event and poof. Nothing more KDE can do (IMHO).

Thing is, the common thing to all the issues, kdeinit4 process.  The
tree looks like this.  The init process #1, kdeinit4 then other
processes that have this issue.  Be it Firefox, Seamonkey and the other
stuff.


>
>> I know when I go to boot runlevel, I have to kill quite a few
>> processes that are pretty stubborn to kill.  kill -15 usually doesn't
>> work so I end up using -9 to get it to die.
>
> If you go to *that* length (switch to boot and kill processes manually),
> why not do the *cough* Ubuntu way and simply reboot, since killing X
> means killing most of your environment of running applications anyway?

I don't reboot to much.  Bad experiences with Mandrake.  Everything
works fine, then reboot and it's busted.  You may not really want to
ask.  ;-)

I just finished a complete recompile.  It may not help but I wanted to
try it anyway, just in case.  I have had that fix some pretty weird
issues in the past.

Thanks.

Dale

:-)  :-)

-- 
I am only responsible for what I said ... Not for what you understood or
how you interpreted my words!


[-- Attachment #2: Type: text/html, Size: 5103 bytes --]

Re: [gentoo-user] Firefox not killing processes on close

[Walter Dnes]

On Sun, Nov 10, 2013 at 03:38:16PM -0600, 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.

  Long story short... "there can only be one" Firefox process *PER USER*
at any given time.  Seriously... as regular user open up multiple
Firefox windows, and execute...

ps -ef | grep firefox

and you'll get something like...

[i660][waltdnes][~] ps -ef | grep firefox
waltdnes 28696 11663  2 19:35 pts/22   00:00:07 firefox
waltdnes 28836 28825  0 19:39 pts/30   00:00:00 grep --color=auto firefox

  Only one Firefox process exists.  (I can't seem to prevent the grep
command from listing itself).

> This has been going on for a while.  What can I look for or do to
> correct this? 

  There is a workaround/kludge/ugly-hack.  Notice that I said one
process *PER USER*.  I have another user "user2" that I log in as to
occasionally maintain "static" stuff that I only want my regular login
to only see, but not modify/delete/etc.  If you create a second user
(let's call it "user2"), you can do the following...

# Allow other logins/users on the same machine to use your display
xhost +127.0.0.1

# Open up up an xterm/wahtever and
su - user2
# Give password, and then, as user2
firefox

  As my regular user "waltdnes", I can then...
[i660][waltdnes][~] ps -ef | grep firefox
waltdnes 28696 11663  2 19:35 pts/22   00:00:07 firefox
user2    28791 28780  2 19:38 pts/9    00:00:01 firefox
waltdnes 28836 28825  0 19:39 pts/30   00:00:00 grep --color=auto firefox

  From the "ps" output, "waltdnes" is running Firefox with pid 28696,
and "user" as pid "28791".  You can issue a "kill" command for the
appropriate pid.  Note that unless you're root, you can only kill your
own processes.

-- 
Walter Dnes <waltdnes@waltdnes.org>
I don't run "desktop environments"; I run useful applications

Re: [gentoo-user] Firefox not killing processes on close

[Dale]

Walter Dnes wrote:
> On Sun, Nov 10, 2013 at 03:38:16PM -0600, 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.
>   Long story short... "there can only be one" Firefox process *PER USER*
> at any given time.  Seriously... as regular user open up multiple
> Firefox windows, and execute...
>
> ps -ef | grep firefox
>
> and you'll get something like...
>
> [i660][waltdnes][~] ps -ef | grep firefox
> waltdnes 28696 11663  2 19:35 pts/22   00:00:07 firefox
> waltdnes 28836 28825  0 19:39 pts/30   00:00:00 grep --color=auto firefox
>
>   Only one Firefox process exists.  (I can't seem to prevent the grep
> command from listing itself).


I don't know whether to say you are wrong or on to something.  LOL  When
I have three sessions running here, I get this:

root@fireball / # ps aux | grep /usr/bin/firefox
dale       956 16.7  1.6 1461568 267380 ?      Sl   21:35   0:08
/usr/bin/firefox -p -no-remote
root      9148  0.0  0.0  10820   944 pts/2    S+   21:36   0:00 grep
--colour=auto /usr/bin/firefox
dale     18079  5.1  6.1 2396368 1016416 ?     Sl   19:00   7:59
/usr/bin/firefox -p -no-remote
dale     18394  2.0  5.1 2082772 839044 ?      Sl   19:05   3:05
/usr/bin/firefox -p -no-remote
root@fireball / # 

Note there is a process for each session running with a different PID. 
From my understanding, and the reason for me using different sessions in
the first place, each session is completely separate.  A site that I
volunteer on, I have three accounts there.  My personal account, a
moderator account and a admin account.  I have a separate session for
each one which because they use different user name/passwords must be
run separately.  At times, I need to switch between users very quickly. 
So, it appears that each process runs its own PID and is separate.  Sort
of anyway.  Again, that could be the problem but here is why I don't
think it is.  I have this same issue with Seamonkey even when there is
only one process running.  It's not as often but it does happen.  I have
also had this happen when there is only one session of Firefox running
as well.  Then there is the other processes that I have trouble getting
to die as well.  Some not even related to a GUI.  When I switch to the
boot runlevel, I have to manually kill several processes to get down to
the things that should be running and nothing else. 

Oh, even if I close all the sessions, I still run into the issue of
having to kill the processes.  When they die, they all die as they
should.  When it is not dying as it should, none of them die until I
kill them.  It's either feast or famine. 

Again, could be on to something or maybe not.  Open to ideas tho.  I'm
hoping the new info may help. 

>
>> This has been going on for a while.  What can I look for or do to
>> correct this? 
>   There is a workaround/kludge/ugly-hack.  Notice that I said one
> process *PER USER*.  I have another user "user2" that I log in as to
> occasionally maintain "static" stuff that I only want my regular login
> to only see, but not modify/delete/etc.  If you create a second user
> (let's call it "user2"), you can do the following...
>
> # Allow other logins/users on the same machine to use your display
> xhost +127.0.0.1
>
> # Open up up an xterm/wahtever and
> su - user2
> # Give password, and then, as user2
> firefox
>
>   As my regular user "waltdnes", I can then...
> [i660][waltdnes][~] ps -ef | grep firefox
> waltdnes 28696 11663  2 19:35 pts/22   00:00:07 firefox
> user2    28791 28780  2 19:38 pts/9    00:00:01 firefox
> waltdnes 28836 28825  0 19:39 pts/30   00:00:00 grep --color=auto firefox
>
>   From the "ps" output, "waltdnes" is running Firefox with pid 28696,
> and "user" as pid "28791".  You can issue a "kill" command for the
> appropriate pid.  Note that unless you're root, you can only kill your
> own processes.
>

I almost always have a Konsole running as root.  Seems there is always
something that requires root permission to do. 

Open to ideas still.  It's annoying so I'd like a fix.  ;-)  I may have
a idea tho.  Hey guys, watch this.  O_O

Dale

:-)  :-) 

-- 
I am only responsible for what I said ... Not for what you understood or how you interpreted my words!

Re: [gentoo-user] Firefox not killing processes on close

[Alan McKinnon]

On 11/11/2013 05:53, Dale wrote:
>>   Only one Firefox process exists.  (I can't seem to prevent the grep
>> > command from listing itself).
> 
> I don't know whether to say you are wrong or on to something.  LOL  When
> I have three sessions running here, I get this:
> 
> root@fireball / # ps aux | grep /usr/bin/firefox
> dale       956 16.7  1.6 1461568 267380 ?      Sl   21:35   0:08
> /usr/bin/firefox -p -no-remote
> root      9148  0.0  0.0  10820   944 pts/2    S+   21:36   0:00 grep
> --colour=auto /usr/bin/firefox
> dale     18079  5.1  6.1 2396368 1016416 ?     Sl   19:00   7:59
> /usr/bin/firefox -p -no-remote
> dale     18394  2.0  5.1 2082772 839044 ?      Sl   19:05   3:05
> /usr/bin/firefox -p -no-remote
> root@fireball / # 


You are looking at the process list without any information about parent
and child processes.

Use pstree or pc with the -f option to see what is really going on

-- 
Alan McKinnon
alan.mckinnon@gmail.com

Re: [gentoo-user] Firefox not killing processes on close

[Dale]

Alan McKinnon wrote:
> On 11/11/2013 05:53, Dale wrote:
>>>   Only one Firefox process exists.  (I can't seem to prevent the grep
>>>> command from listing itself).
>> I don't know whether to say you are wrong or on to something.  LOL  When
>> I have three sessions running here, I get this:
>>
>> root@fireball / # ps aux | grep /usr/bin/firefox
>> dale       956 16.7  1.6 1461568 267380 ?      Sl   21:35   0:08
>> /usr/bin/firefox -p -no-remote
>> root      9148  0.0  0.0  10820   944 pts/2    S+   21:36   0:00 grep
>> --colour=auto /usr/bin/firefox
>> dale     18079  5.1  6.1 2396368 1016416 ?     Sl   19:00   7:59
>> /usr/bin/firefox -p -no-remote
>> dale     18394  2.0  5.1 2082772 839044 ?      Sl   19:05   3:05
>> /usr/bin/firefox -p -no-remote
>> root@fireball / # 
>
> You are looking at the process list without any information about parent
> and child processes.
>
> Use pstree or pc with the -f option to see what is really going on
>


I had forgot about the pstree command. I don't have a pc command. What
package does it belong too? Here is a snippet of pstree.

├─kdeinit4─┬─firefox─┬─plugin-containe───8*[{plugin-containe}]
│ │ └─25*[{firefox}]
│ ├─firefox───28*[{firefox}]
│ ├─firefox───26*[{firefox}]


That is with three sessions of Firefox running. The only process deeper
than kdeinit is init itself. It seems that Seamonkey and Firefox both
run under kdeinit. It also seems to me that each one has its own process
and run separately. Does that mean this is a kdeinit or Firefox issue?
Am I looking at this correctly?

Thanks.

Dale

:-) :-)

-- 
I am only responsible for what I said ... Not for what you understood or how you interpreted my words!

Re: [gentoo-user] Firefox not killing processes on close

[Alan McKinnon]

On 11/11/2013 09:39, Dale wrote:
>> Use pstree or pc with the -f option to see what is really going on
>> >
> 
> I had forgot about the pstree command. I don't have a pc command. What
> package does it belong too? Here is a snippet of pstree.

s/pc/ps/

typo. muscle memory. sorry.


-- 
Alan McKinnon
alan.mckinnon@gmail.com

Re: [gentoo-user] Firefox not killing processes on close

[Dale]

Alan McKinnon wrote:
> On 11/11/2013 09:39, Dale wrote:
>>> Use pstree or pc with the -f option to see what is really going on
>> I had forgot about the pstree command. I don't have a pc command. What
>> package does it belong too? Here is a snippet of pstree.
> s/pc/ps/
>
> typo. muscle memory. sorry.
>
>

Ahh.  Typo on your end and to sleepy on my end to figure it out.  o_O 

Reminding me of pstree was good tho.  That at least let me see that it
is a separate process or seems to be.  I did a emerge -e system last
night, started a emerge -ev world this morning.  It's still working on
that.  This should tell me if it is just some mismatch between two or
more packages.  I hope.  If not, then figure out what is failing and
file a bug somewhere.  I'm thinking it is kdeinit since it is not just
Firefox or Seamonkey.  Just my thinking tho.  Sometimes that ain't worth
much.  ;-) 

Dale

:-)  :-) 

-- 
I am only responsible for what I said ... Not for what you understood or how you interpreted my words!

Re: [gentoo-user] Firefox not killing processes on close

[gottlieb]

On Sun, Nov 10 2013, Dale wrote:

> Walter Dnes wrote:
>> On Sun, Nov 10, 2013 at 03:38:16PM -0600, Dale wrote
>>
>> ps -ef | grep firefox
>>
>> and you'll get something like...
>>
>> [i660][waltdnes][~] ps -ef | grep firefox
>> waltdnes 28696 11663  2 19:35 pts/22   00:00:07 firefox
>> waltdnes 28836 28825  0 19:39 pts/30   00:00:00 grep --color=auto firefox
>>
>>   Only one Firefox process exists.  (I can't seem to prevent the grep
>> command from listing itself).

I'll leave the heavy listing to alan, but to avoid listing the grep, I
believe you want

    ps -ef | grep firefox | grep -v grep

allan

Re: [gentoo-user] Firefox not killing processes on close

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 394 bytes --]

On Mon, 11 Nov 2013 09:35:11 -0500, gottlieb@nyu.edu wrote:

> I'll leave the heavy listing to alan, but to avoid listing the grep, I
> believe you want
> 
>     ps -ef | grep firefox | grep -v grep

I see a lot of wheels being reinvented...


-- 
Neil Bothwick

NOTE: In order to control energy costs the light at the end
of the tunnel has been shut off until further notice...

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Firefox not killing processes on close

[Yohan Pereira]

On 10/11/13 at 08:07pm, Walter Dnes wrote:
> [i660][waltdnes][~] ps -ef | grep firefox
> waltdnes 28696 11663  2 19:35 pts/22   00:00:07 firefox
> waltdnes 28836 28825  0 19:39 pts/30   00:00:00 grep --color=auto firefox
> 
>   Only one Firefox process exists.  (I can't seem to prevent the grep
> command from listing itself).

Try this hack :)

$ ps -ef | grep [u]rxvt
yohan     3559     1  0 11:50 ?        00:00:00 urxvt
yohan     3667     1  0 11:52 ?        00:00:00 urxvt

-- 

- Yohan Pereira

The difference between a Miracle and a Fact is exactly the difference
between a mermaid and a seal.
                -- Mark Twain

Re: [gentoo-user] Firefox not killing processes on close

[Dale]

Yohan Pereira wrote:
> On 10/11/13 at 08:07pm, Walter Dnes wrote:
>> [i660][waltdnes][~] ps -ef | grep firefox
>> waltdnes 28696 11663  2 19:35 pts/22   00:00:07 firefox
>> waltdnes 28836 28825  0 19:39 pts/30   00:00:00 grep --color=auto firefox
>>
>>   Only one Firefox process exists.  (I can't seem to prevent the grep
>> command from listing itself).
> Try this hack :)
>
> $ ps -ef | grep [u]rxvt
> yohan     3559     1  0 11:50 ?        00:00:00 urxvt
> yohan     3667     1  0 11:52 ?        00:00:00 urxvt
>

That one didn't return anything.  I got plenty of output without the
grep tho.  Sort of close to what I usually get with ps aux. 

Dale

:-)  :-) 

-- 
I am only responsible for what I said ... Not for what you understood or how you interpreted my words!

Re: [gentoo-user] Firefox not killing processes on close

[Yohan Pereira]

On 11/11/13 at 01:44am, Dale wrote:
> Yohan Pereira wrote:
> > On 10/11/13 at 08:07pm, Walter Dnes wrote:
> >> [i660][waltdnes][~] ps -ef | grep firefox
> >> waltdnes 28696 11663  2 19:35 pts/22   00:00:07 firefox
> >> waltdnes 28836 28825  0 19:39 pts/30   00:00:00 grep --color=auto firefox
> >>
> >>   Only one Firefox process exists.  (I can't seem to prevent the grep
> >> command from listing itself).
> > Try this hack :)
> >
> > $ ps -ef | grep [u]rxvt
> > yohan     3559     1  0 11:50 ?        00:00:00 urxvt
> > yohan     3667     1  0 11:52 ?        00:00:00 urxvt
> >
> 
> That one didn't return anything.  I got plenty of output without the
> grep tho.  Sort of close to what I usually get with ps aux. 
> 
> Dale
 
I'm sorry, that was a hack to prevent grep from listing it self in the
ps out-put, nothing to do with your problem specifically, should've made
that clear :).

-- 

- Yohan Pereira

The difference between a Miracle and a Fact is exactly the difference
between a mermaid and a seal.
                -- Mark Twain

Re: [gentoo-user] Firefox not killing processes on close

[Dale]

Yohan Pereira wrote:
> On 11/11/13 at 01:44am, Dale wrote:
>> Yohan Pereira wrote:
>>> On 10/11/13 at 08:07pm, Walter Dnes wrote:
>>>> [i660][waltdnes][~] ps -ef | grep firefox
>>>> waltdnes 28696 11663  2 19:35 pts/22   00:00:07 firefox
>>>> waltdnes 28836 28825  0 19:39 pts/30   00:00:00 grep --color=auto firefox
>>>>
>>>>   Only one Firefox process exists.  (I can't seem to prevent the grep
>>>> command from listing itself).
>>> Try this hack :)
>>>
>>> $ ps -ef | grep [u]rxvt
>>> yohan     3559     1  0 11:50 ?        00:00:00 urxvt
>>> yohan     3667     1  0 11:52 ?        00:00:00 urxvt
>>>
>> That one didn't return anything.  I got plenty of output without the
>> grep tho.  Sort of close to what I usually get with ps aux. 
>>
>> Dale
>  
> I'm sorry, that was a hack to prevent grep from listing it self in the
> ps out-put, nothing to do with your problem specifically, should've made
> that clear :).
>


Oh OK.  That doesn't bother me.  I just ignore it.  Heck, it's a process
just like anything else.  LOL 

My next plan, I'm going to create three thingys on my desktop.  One for
each session.  I'm hoping that the session will be listed in the command
so that at least I know which is which in the ps list.  I just got to
google up the proper command. 

Thanks for the help tho.  Right now, I'm doing a emerge -e system and
plan to start a emerge -e world when I leave in the AM to take my bro to
the Doctor.  It may not help one dang bit but what the heck.  I need to
break in this new CPU/cooler grease anyway.  ;-) 

Dale

:-)  :-) 

-- 
I am only responsible for what I said ... Not for what you understood or how you interpreted my words!

Re: [gentoo-user] Firefox not killing processes on close

[Dale]

Dale wrote:
> Thanks for the help tho. Right now, I'm doing a emerge -e system and
> plan to start a emerge -e world when I leave in the AM to take my bro
> to the Doctor. It may not help one dang bit but what the heck. I need
> to break in this new CPU/cooler grease anyway. ;-) Dale :-) :-) 

Small update.  The emerge -e world helped some.  It still does it but
not as often.  Still annoying tho.  So, still got something not right
somewhere. 

Dale

:-)  :-) 

-- 
I am only responsible for what I said ... Not for what you understood or how you interpreted my words!

Re: [gentoo-user] Firefox not killing processes on close

[Bruce Hill]

On Mon, Nov 11, 2013 at 01:44:10AM -0600, Dale wrote:
> > On 10/11/13 at 08:07pm, Walter Dnes wrote:
> > Try this hack :)
> >
> > $ ps -ef | grep [u]rxvt
> > yohan     3559     1  0 11:50 ?        00:00:00 urxvt
> > yohan     3667     1  0 11:52 ?        00:00:00 urxvt
> >
> 
> That one didn't return anything.  I got plenty of output without the
> grep tho.  Sort of close to what I usually get with ps aux. 

He intended for you to do:
ps -ef | grep [f]irefox
-- 
Happy Penguin Computers               >')
126 Fenco Drive                       ( \
Tupelo, MS 38801                       ^^
support@happypenguincomputers.com
662-269-2706 662-205-6424
http://happypenguincomputers.com/

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting

Re: [gentoo-user] Firefox not killing processes on close

[Alexander Kapshuk]

On 11/11/2013 04:52 PM, Bruce Hill wrote:
> On Mon, Nov 11, 2013 at 01:44:10AM -0600, Dale wrote:
>>> On 10/11/13 at 08:07pm, Walter Dnes wrote:
>>> Try this hack :)
>>>
>>> $ ps -ef | grep [u]rxvt
>>> yohan     3559     1  0 11:50 ?        00:00:00 urxvt
>>> yohan     3667     1  0 11:52 ?        00:00:00 urxvt
>>>
>> That one didn't return anything.  I got plenty of output without the
>> grep tho.  Sort of close to what I usually get with ps aux. 
> He intended for you to do:
> ps -ef | grep [f]irefox
Nice one. I was going to suggest this one, ps xwww|awk '/firefox/ &&
!/awk/', but your suggestion is more succinct.
Thanks.

Re: [gentoo-user] Firefox not killing processes on close

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 518 bytes --]

On Mon, 11 Nov 2013 11:54:57 +0530, Yohan Pereira wrote:

> >   Only one Firefox process exists.  (I can't seem to prevent the grep
> > command from listing itself).  
> 
> Try this hack :)
> 
> $ ps -ef | grep [u]rxvt
> yohan     3559     1  0 11:50 ?        00:00:00 urxvt
> yohan     3667     1  0 11:52 ?        00:00:00 urxvt

Or avoid hacks with "man pgrep" :)

e.g. pgrep -fl firefox


-- 
Neil Bothwick

It is impossible to fully enjoy procrastination
unless one has plenty of work to do.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Firefox not killing processes on close

[Edward M]

[-- Attachment #1: Type: text/plain, Size: 1204 bytes --]

On 11/10/2013 1:38 PM, Dale wrote:
>   When it does not kill correctly and I try to restart that
> session, I get the error that the session is already running.

      Hello,:-)
/
/The following article explains how to deal with "Firefox is already 
running" message.hope it helps out

        "Run *strace -o ~/ff.strace firefox* and then investigated the 
strace file. My hunch was that one or other file lock
        wasn't being relinquished properly, perhaps from an earlier 
crashed firefox process. I grepped through the log, looking for file 
opens, and eventually found this:/
open("/home/matthew/.mozilla/firefox/2z7l4uii.default/.parentlock", 
O_WRONLY|O/CREAT|O/TRUNC, 0666) = 4/
         Bingo! I checked; and even with no firefox process running, 
this file existed. It was an empty lock file, so I deleted it. That did 
the trick --- now FireFox runs again!

          So in summary; if you have this problem, check your .mozilla 
file (or the Windows equivalent) for any 'lock' files --- quit any mozilla
           applications, then delete the lock files and try again. That 
should fix the problem!"


http://xania.org/200604/firefox-woesfirefox-is-already-running-when-it%27s-not

//

[-- Attachment #2: Type: text/html, Size: 2299 bytes --]

Re: [gentoo-user] Firefox not killing processes on close

[Bruce Hill]

On Mon, Nov 11, 2013 at 10:28:19AM -0800, Edward M wrote:
> On 11/10/2013 1:38 PM, Dale wrote:
> >   When it does not kill correctly and I try to restart that
> > session, I get the error that the session is already running.
> 
>       Hello,:-)
> /
> /The following article explains how to deal with "Firefox is already 
> running" message.hope it helps out
> 
>         "Run *strace -o ~/ff.strace firefox* and then investigated the 
> strace file. My hunch was that one or other file lock
>         wasn't being relinquished properly, perhaps from an earlier 
> crashed firefox process. I grepped through the log, looking for file 
> opens, and eventually found this:/
> open("/home/matthew/.mozilla/firefox/2z7l4uii.default/.parentlock", 
> O_WRONLY|O/CREAT|O/TRUNC, 0666) = 4/
>          Bingo! I checked; and even with no firefox process running, 
> this file existed. It was an empty lock file, so I deleted it. That did 
> the trick --- now FireFox runs again!

Couldn't you just issue:
find .mozilla/firefox/ -iname '*.parentlock' 2>/dev/null
rather than running strace?
-- 
Happy Penguin Computers               >')
126 Fenco Drive                       ( \
Tupelo, MS 38801                       ^^
support@happypenguincomputers.com
662-269-2706 662-205-6424
http://happypenguincomputers.com/

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting

Re: [gentoo-user] Firefox not killing processes on close

[Edward M]

On 11/11/2013 10:50 AM, Bruce Hill wrote:
> Couldn't you just issue:
> find .mozilla/firefox/ -iname '*.parentlock' 2>/dev/null
> rather than running strace?
        Hello:-)
       It may work. never tried it
      Now I'm thinking probably using a  shell script like the 
following, can be used  instead of  strace .

        #!/bin/bash
         p_lock=`find  ~/.mozilla -name "*lock"'
         for file in `echo $p_lock`
         do
               rm "$file"

           done

Re: [gentoo-user] Firefox not killing processes on close

[Alexander Kapshuk]

On 11/11/2013 09:44 PM, Edward M wrote:
> On 11/11/2013 10:50 AM, Bruce Hill wrote:
>> Couldn't you just issue:
>> find .mozilla/firefox/ -iname '*.parentlock' 2>/dev/null
>> rather than running strace?
>        Hello:-)
>       It may work. never tried it
>      Now I'm thinking probably using a  shell script like the
> following, can be used  instead of  strace .
>
>        #!/bin/bash
>         p_lock=`find  ~/.mozilla -name "*lock"'
>         for file in `echo $p_lock`
>         do
>               rm "$file"
>
>           done
>
Alternatively, to the best of my knowledge, that could be shortened down to:

rm `find  ~/.mozilla -name "*lock"`

Re: [gentoo-user] Firefox not killing processes on close

[Edward M]

On 11/11/2013 11:57 AM, Alexander Kapshuk wrote:
> Alternatively, to the best of my knowledge, that could be shortened down to:
>
> rm `find  ~/.mozilla -name "*lock"`
      Thanks for sharing:-)

      After a little modification, tried it in a script on different 
files and they deleted.

Re: [gentoo-user] Firefox not killing processes on close

[Alexander Kapshuk]

On 11/11/2013 10:46 PM, Edward M wrote:
> On 11/11/2013 11:57 AM, Alexander Kapshuk wrote:
>> Alternatively, to the best of my knowledge, that could be shortened
>> down to:
>>
>> rm `find  ~/.mozilla -name "*lock"`
>      Thanks for sharing:-)
>
>      After a little modification, tried it in a script on different
> files and they deleted.
>
>
No worries.