|
Hi, I'm just trying to set up FluxBox over my xdm for the first time and I'm experiencing some problems. So, if there are any people knowledgeable in this matter lurking here (and I believe there are) then please do help me.
What's bugging me now is the inconsistency with my terminal windows. I've set it so that one terminal is launched at fluxbox startup and then I can open more with a hotkey. The problem is, that despite having the exactly same run command and options, they look different...
What I mean:
The top one is launched at startup, the lower one is opened by hotkey. Question: Why the hell the startup one has borders when it shouldn't?
I'll post more questions later I believe. I'm now moving to configuring my login screen...
|
I don't know that much about fluxbox, i use awesome and gnome.
terminal behaviour are usually controlled via .bashrc and terminal's profile (which sits in a folder some where in your /home)
Some terminal emulators use command line input options to control display. If you have an init script to launch things at the start, have a look into that.
|
I dont have much experience in fluxbox, i had blackbox in the past, and is basically the predecessor to fluxbox, so here is what i remember:
Each window have a remember property, i do believe is a xml and it should be on ~/.fluxbox/ or something like that. It should be a graphic menu for it too. You can decide there anything, like if you want it to stick to every desktop, if you want borders, if you want to lock it in position, etc.
|
try making your terminal wait a few seconds before starting up. maybe it's launching before fluxbox takes effect?
|
On November 05 2009 06:00 mahnini wrote: try making your terminal wait a few seconds before starting up. maybe it's launching before fluxbox takes effect?
The terminal and it's options (transparency and everything) are independent from fluxbox... http://www.afterstep.org/aterm.php
I think I'll just drop the terminal autostart.
|
On November 05 2009 06:15 Manit0u wrote:Show nested quote +On November 05 2009 06:00 mahnini wrote: try making your terminal wait a few seconds before starting up. maybe it's launching before fluxbox takes effect? The terminal and it's options (transparency and everything) are independent from fluxbox... http://www.afterstep.org/aterm.phpI think I'll just drop the terminal autostart. Fluxbox controls window borders not the terminal (this would be the issue if you were using AfterStep WM imo). In what config file do you have the startup command?
|
I think what's happening is the startup terminal is starting up and then the config gets changed to remove borders...or something like that. Try putting in a 1 second sleep before starting the terminal if you want it to start on startup, but I find that if you have it set to a key combination there's really no reason to have it there on startup since you can open it instantly anyway.
|
as said, apps dont control the borders, window manager does.
And yes, i agree that maybe is a timing thing. I think you are starting the terminal before fluxbox. Try doing this to be sure, start with another wm, open a terminal and switch to fluxbox without closing that terminal, you should see it with window border.
|
Yup. It is started before fluxbox. And apparently, there is no way to start it later (at least none I know of) since in .fluxbox/startup file, fluxbox MUST be the last thing to run.
Anyway, another question: Why the hell sounds in HoN don't work for me? I've reinstalled/reconfigured my alsa, I get all the super annoying beeps when doing something illegal in the console, speaker-test plays the femal voice all ok etc. Will have to check it out with some player I guess. Didn't even bother to install anything that plays music/videos yet.
|
you can surelly do it, dude... dont give up.
try to do it yourself... or click on the spoiler.
+ Show Spoiler +you need to edit your ~/.fluxbox/startup look for the line that reads exec fluxbox
and change it for # we start fluxbox in the background
fluxbox &
# we store fluxbox proc id, where $ (stands for the variable #named ! (wich stands for the last cli entrance))
fbid=$!
# Time out in seconds, fluxbox is already runing in back, #so you dont slower anything really # If your computer is too slow you may need to time this a little bit longer
sleep 1
{ #Here put your aplications, like aterm & #dont forget the &, so they run in background and script go on } &
#we keep all runing while fluxbox is runing
wait $fbid
Basically, you split the exec into 1 run fb in back 1.5 your custom apps 2 everything else should w8 fb
Tell me how are you doing after
edit: some code format
edit again: I am thinking in another solution + Show Spoiler +This is for sure, the before solution might be version dependant... idk much about fluxbox code. make a script like this: #!/bin/bash
sleep 5 exec aterm
make it executable, and run it with the complete route from the fluxbox script, should be something like .$HOME/scripts
the dot matters... after a few runs you will get the exact needed value for the sleep comand
|
Thanks for the advice I have given up on this already and just removed aterm from my startup file alltogether (like it was mentioned before, there is no need for it to start automatically if I can just 'alt+a' to get it).
I've also solved the sound problem (actually, my friend helped me here a bit, the solution was so simple that I wouldn't have ever thought about it), my /dev/dsp had wrong privilages set and simple chmod solved all of the problems.
Now another thing I'm having problem with: How the hell do I change the default uberugly login screen in xdm? I've read all I could about it on the web, edited my Xsetup and Xresources files in /etc/X11/xdm but to no avail
|
|
|
|