SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
For sometime now about every other time I start Firefox a empty window comes up and it is necessary to kill it and try again.
This has happened with Firefox 5 through and including 6.02, and in Xfce 4.6.2, 4.8.x, and KDE 4.7.0 and 4.7.1.
Has anyone else encounter this problem?
Last edited by cwizardone; 09-09-2011 at 10:57 PM.
I didn't notice this was the Slackware forum or that the user's profile had Slackware in it since I was browsing this on my phone earlier.
Originally Posted by Konphine
Do you have a different firefox window open when you open it?
That shouldn't cause it in the least.
@marrowsuck i3, while not being as good as wmii (:P), shouldn't cause that either.
I'm not having this problem on Slackware64 13.37. Might be nice to narrow this down to either Slack64-current or the multilib. Anyone on Slack64-current vanilla (no multilib support added-on) having this problem?
Distribution: Slackware 14 (Server),Suse 13.1 (Desktop),, Mepis on the wifes lappy
I have seen this problem and it turned out to be incorrect nameserver entry in /etc/resolv.conf.
Dont know why, but cleaning out that file then restarting the network seemed to do the job. I would have expected FF to throw up some sort of error, but none was present so it threw me for quite a while.