SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Running FF 3.6.13 on Slack 13.1 (32-bit). Every time that I use FF when I close it the processes that are spawned when it starts never end. I have to manually go and kill them. It is pretty annoying more than an inconvenience since I don't normally use FF. Unfortunately I have to use it, every now and then, for some things and if I need to restart it I have to open a terminal and kill the processes.
I've tried re-installing on top of the version that I have there, and actually uninstalling and installing it again (of course making sure that all of the directories are gone), I've also tried renaming my ~/.mozilla directory (in case there is a problem with the profile).
I've had this type of behaviour on-and-off over the past couple of years, on various pc's, and I've never really figured out why it happens or doesn't happen...yet, I just can't manage the switch to chrome.
The bottom line is that with FF, it could be anything, and it *probably* isn't Slack-related....
Some things to try:
Does firing up FF from a terminal provide any clues?
How about $ firefox --safe? Same behaviour?
Disable all add-ons. If this makes a difference, then re-enable them, one-by-one...
Backup/mv the *.default user in .mozilla/firefox and run firefox, see if that helps.
Does firing up FF from a terminal provide any clues?
No clues here... When I do this the "script" that fires FF never ends when I close FF. I even modified the script to enable debugging and no clues showed.
Quote:
How about $ firefox --safe? Same behaviour?
Yes
Quote:
Disable all add-ons. If this makes a difference, then re-enable them, one-by-one...
Yes same...
Quote:
Backup/mv the *.default user in .mozilla/firefox and run firefox, see if that helps.
Tried this and no help. I even just tried running FF directly from
Not what I would like to do, but I guess this will have to do for now until I get a better answer... I created an alias to kill all of the FF related processes.
Code:
alias killff='for ffpid in `ps -o pid -C firefox,firefox-bin,run-mozilla.sh --no-heading`; do kill $ffpid; done'
Not what I would like to do, but I guess this will have to do for now until I get a better answer... I created an alias to kill all of the FF related processes.
Code:
alias killff='for ffpid in `ps -o pid -C firefox,firefox-bin,run-mozilla.sh --no-heading`; do kill $ffpid; done'
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.