Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
Ok, so not years, but I switched from KDE to get away from this kind of thing. I'm using XDM to login and it appears as though fluxbox begins to load immediatly, so I think if there is a problem, it occurs after fluxbox has begun loading. I just need a little help getting pointed in the right direction. There is a .xsession-errors file created when I log in, and here it is:
Failed to load groupfile:
BScreen::BScreen: managing screen 0 using visual 0x22, depth 24
Although the second entry looks less like an error than the first, I have failed to resolve either. Is this related to my slow load times?
I brought the system down to runlevel 3 then issued the 'startx' command which just loads xdm. It takes about 5 seconds for xdm to load, and another 45 for fluxbox to load after I log in. The screen immediatly changes and is blank for a while, then I get the toolbar (with the exception of the workspace name box) and then after the 45 is up, I can finally read the text in the workspace name box and access my menus.
I'm new to the xinit procedures, I basically know what happens when, but actual details are fuzzy at best. Should I use the stock Fedora scripts (with all the error checking) or should I try to strip them down to something much cleaner?
it shouldn't load xdm at all, when you issue the command, it loads whatever window manager you set up as default, so it loads for you Fluxbox, for me it loads xfce4. Is fluxbox a heavy environment, similar to Gnome or KDE? XFCE loads up in seconds on my 200mhz computer. Oh, and btw, congrats, another Minnesotan!
Originally posted by r_jensen11 Is fluxbox a heavy environment, similar to Gnome or KDE? XFCE loads up in seconds on my 200mhz computer.
Not at all. Something's radically wrong. Flux should load virtually instantly - faster than XFCE and *far* faster than KDE. The only thing necessary is an ~/.xinitrc with the single line invoking fluxbox. (You'll want much more, of course, but that will be enough to invoke flux.) However, Fedora may have a screwy set of wrappers. r_jensen's absolutely right - xdm has no business running from 'startx'.
xinit `which fluxbox`
(I dunno where yours is) is the most minimal flux launch I can think of. For the error message (more informational, really), I think doing 'touch ~/.fluxbox/groups' will do it if that file doesn't already exist. (You may need to edit ~/.fluxbox/init to point to that file but probably not.) The second thing is purely informational. But none of this should be slowing flux down. And it's not exactly dependent on a whole lot of libs, so I don't see loading that as creating a problem. I don't really know what's wrong, but something is. Flux is fast.
Do you have any other window managers, like Ice or something? Is everything slow or just flux and KDE?
I confess, it was I who set up xdm to run out of /etc/X11/xinit/xinitrc, like I said this process is still kind of ambigous to me, so I wasn't sure where to tell xdm to run.
So am I causeing the problem by running xdm out of the wrong place?
I think so. If you're starting out in runlevel 3, there's no reason to have a session manager start up before you load your window manager.
I've been using Fluxbox for most of my Linux life, and never had trouble with it starting up slowly...even with the extra startup poop I've been experimenting with.
I also see "BScreen::BScreen: managing screen 0 using visual 0x22, depth 24" every time it starts up...it's just telling you that's what its visual settings are.