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.
When the router is disconnected, seamonkey hangs for 10 seconds on launch.
It will spawn a zombie process which dies in exactly 10 seconds, every time.
If the router is connected, seamonkey starts instantly, with no zombie process.
I don't think it was doing it on previous versions.
Distribution: Slackware 15.0 x64, Slackware Live 15.0 x64
Posts: 618
Rep:
Seamonkey has been leaving a single zombie process on my system randomly for the past few weeks. No idea why, no idea how it's doing it. I don't need to mess with the router to make it happen...it just happens, randomly, like I said. It's such a PITA that I've resorted to using PaleMoon mostly now.
I can replicate this on the same system 32 bit 14.1 even if I rename ~/.mozilla profile.
Also happens with icecat-38.4.0 and mozilla-firefox-38.5.0esr fresh compiled from source.
Note that I've just built icecat-38.4.0 with the same slackbuild on 64 bit -current and it starts instantly with no delay.
I guess it's probably something misconfigured in my local 14.1 install, unless someone else can replicate, that's why I posted here.
Found the cause after a while, seemed very strange how it never happened on -current while there was no diff in configuration.
Changing routes and gateways did not help, and I almost give up on this, which is when I found the changes in nsswitch.conf did not reflect to user programs at all.
It was falling back to dns (instead of files) every time, and since the cable was out there was no dns, hence the delay.
The cause : all user programs lacked permission to access host file, only root had access.
The solution : simple 'chmod 644' and it's now working as expected.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.