On Thursday, May 07, 2015 09:37:06 AM Thomas Taylor wrote:

On Thu, 07 May 2015 11:43:58 -0400

Bob Rea wrote:

...

I restarted os 12.3 because the system was operation sluggishly, especially firefox. When I restarted firefox offered to restore windows but before I could reply, it started showing error message, the standard one, crash reporter. I tried to start firefox and it told me it was already running, and I needed to close it to start anew. I tried to kill all firefox processes, but the last of these showed:

ob@gandalf:~> ps ax |grep firefox

4028 pts/0 S+ 0:00 grep --color=auto firefox

bob@gandalf:~> ps ax |grep firefox

4103 pts/0 S+ 0:00 grep --color=auto firefox

bob@gandalf:~> kill 4028 4103 bash: kill: (4028) - No such process bash: kill: (4103) - No such process

Each time, It shows a new process that does not exist. It just keeps doing this. top does not show firefox, nor does ksysguard. What can I do about this?

Have you tried renaming/removing your FF profile, thus forcing FF to create a new profile?

Not sure what to remove. .mozilla/firefox has crash reports and profiles.ini, and two folders ending with defaults.What of this do I need to get rid of? crash reports too as well as profiles? any other of the defaults? --Bob Rea mailto:gapetard@stsams.org http://www.petard.us http://www.petard.us/blog http://www.petard.us/gallery What do you say to Jesus when he comes again? Where have you been? You said you were coming right back. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Thursday, May 07, 2015 02:32:49 PM Anton Aylward wrote:

On 05/07/2015 12:37 PM, Thomas Taylor wrote:

...

...

bob@gandalf:~> ps ax |grep firefox

4028 pts/0 S+ 0:00 grep --color=auto firefox

bob@gandalf:~> ps ax |grep firefox

4103 pts/0 S+ 0:00 grep --color=auto firefox

bob@gandalf:~> kill 4028 4103 bash: kill: (4028) - No such process bash: kill: (4103) - No such process

That makes perfect sense to me.

The result of the command is saying that there is no firefox process running. You then try killing the GREP. Why do you want to kill the GREP? I don't understand?

My stupid. sorry, was getting panicy and desperate. --Bob Rea mailto:gapetard@stsams.org http://www.petard.us http://www.petard.us/blog http://www.petard.us/gallery What do you say to Jesus when he comes again? Where have you been? You said you were coming right back. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Thursday, May 07, 2015 02:40:11 PM Anton Aylward wrote:

Try this

ps ax | grep file | grep fox

*IF* this is a firefox running then the

ps ax | grep fire

will show it up and the complete string "firefox" will appear as output. Pass that though a "grep fox" filter will still return the string "firefox".

So, betcha there's no output :-)

Right, no output

...

...

...

What can I do about this?

Have you tried renaming/removing your FF profile, thus forcing FF to create a new profile?

Try "firefox -ProfileManager"

brings up mozilla crash reporter

I got that by RTFM. RTFM and "Go Google" can resolve many matters :-)

I still have the firefox icon on the panel, and if I click it, it brings up the crash reporter. -- Bob Rea mailto:gapetard@stsams.org http://www.petard.us http://www.petard.us/blog http://www.petard.us/gallery What do you say to Jesus when he comes again? Where have you been? You said you were coming right back. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Or that's what It seems for me. If I wait a bit it seems that the FF shutdown "completes".

Alternatively a kill/crash (or kernel panic) of the right type might prevent the lock file being cleared so prevent FF starting up the next time.

Where do I look for the lock file? -- Bob Rea mailto:gapetard@stsams.org http://www.petard.us http://www.petard.us/blog http://www.petard.us/gallery What do you say to Jesus when he comes again? Where have you been? You said you were coming right back. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Thu, 7 May 2015 23:24, Anton Aylward wrote:

On 05/07/2015 04:31 PM, Robert Rea wrote:

...

...

Or that's what It seems for me. If I wait a bit it seems that the FF shutdown "completes".

Alternatively a kill/crash (or kernel panic) of the right type might prevent the lock file being cleared so prevent FF starting up the next time.

Where do I look for the lock file?

Under ~/.mozilla/firefox/ there will be a directory for each profile. If FF is running or if its crashed or not shut down properly the lock file will be in the directory corresponding to the profile that FF was running under.

It should be a symbolic link to something,

Of course googling for your problem leads to, among other places, the Mozilla help files, including http://kb.mozillazine.org/Profile_in_use and links to other information such as the location of the lock file.

Another hint: Mozilla Firefox has more than one executable. Base directory for 32 bit: /usr/lib/firefox/ 64 bit: /usr/lib64/firefox/ there you find as "executeables": crashreporter firefox firefox.sh firefox-bin mozilla-xremote-client plugin-container webapprt-stub A quick check for any of those still running: ls -l /proc/*/exe 2>/dev/null|grep '/usr/lib[0-9]*/firefox/' With your comment about the Icon still there in the panel, and the crashreporter comming up, I'd point to the "crashreporter" binary still running, or maybe the "plugin-container". A pure search for firefox will not find that, the quick check above will find these (at least for the SUSE package) - Yamaban. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org