tips for fluxbox [Part 1]

[bakreule]

Direct linking doesn't seem to work but if you follow this link and do a search for 'relapse' you'll find what you're looking for.
http://browse.deviantart.com/

Thanks, I found it.... Beautiful image....

[feminista]

Aterm also controls its own scrollbar, separate from any libraries/toolkits/etc. Check out the man page for configuration tips.

And, of course, if you're running any Qt apps, you'll have to change that theme too, but I wouldn't know anything about such dirtiness. ^_~

[Gentree]

seems like gtk-chtheme broke the scollbars but at least I dont have to look at them any more

I can live without them better than I could live with them for terms anyway. Other progs seem OK.


Still trying to find out what the Mod? keys are , here's half the answer:
http://fluxbox.sourceforge.net/docs/en/ ... hp#special

Oddly , since it seems to be the official doc it only says what mod1 and mod4 are.

I guess after that you have to define a key bind and experiment until you find how to trigger it.

Anyway , now I can edit my key file for my true blue IBM , non-M$ keyboard. Ha! I spit on your silly, bed-wetting window-keys.

The only things I'm not too keen on now is one-cornered resize (senselessly restrictive , it cant be that hard to code!) and that I cant find a theme with rounded corners on fluxbox.

Silly detail but I've become a bit attached to soft corners on xfce4 and sharp rectangles seem a bit austere and basic now.

Many thanks for all the tips, I've done all ten pages now and have learnt enought to get a good hold of how fluxbox works, and I like it.

[Gentree]

OK found a bit more: http://fluxbox.org/version-0.9.php

window.roundCorners:TopRight TopLeft BottomLeft BottomRight



more like window.missingCorners to my eye but I suppose it is being looked at.

Code: Select all

!menu.roundCorners:BottomLeft BottomRight
!toolbar.shaped: true

best left commented !

very pleasing how configurable all this is tho' , once you've found the doc.

coming together nicely.

[feminista]

very pleasing how configurable all this is tho' , once you've found the doc.

coming together nicely.

Glad to hear it. That's why we love the flux.

[Gentree]

One thing I cant figure out , if I try to run any X progs from a term it cant connect to the display.

In xfce for ex. I can open an xterm and issue :

Code: Select all

su prof && opera

in flux even if I su first then use fbrun to start opera it comes up as the user under which I start flux.

This is not what I need , I have a user with very ristricted rights for things like browser amule etc.

Anyone advise on what I need to do here?

TIA

[yabbadabbadont]

You might try using

Code: Select all

su - prof && opera

instead and see if it helps.

[jaanu141]

Anybody knows how ta add the same program more than once into /.fluxbox/apps ?

[Gentree]

You might try using

Code: Select all

su - prof && opera

instead and see if it helps.

No, that will change me to su shell and execute opera when I return. If you meant su - prof opera that just does the same as I posted above.

Anyone know how to drive this damn thing ? Looks light the super-light weight approach extends to the doc as well.

[revertex]

You might try using

Code: Select all

su - prof && opera

instead and see if it helps.

No, that will change me to su shell and execute opera when I return. If you meant su - prof opera that just does the same as I posted above.

Anyone know how to drive this damn thing ? Looks light the super-light weight approach extends to the doc as well.

you may consider sudo.

due to security restrictions root cannot access X (at least he wouldn't).

but with "sux" you can.

first of all emerge sux it's pretty small, and have a very few dependencies,
then run what-you-want issuing "sux -e progname", like "sux -e opera"

This should work, but sudo IMHO is a lot better, you can even setup a list of apps that your user can run as sudo.

cheers

[revertex]

Anybody knows how ta add the same program more than once into /.fluxbox/apps ?

Yes, you just need to figure how to make the program identify itself with diferent n when running more than one instance.

use

Code: Select all

xprop |awk '/WM_CLASS/{print $3 $4}'

to identify the progname

Actually i can only do it with *terms.

[Gentree]

You might try using

Code: Select all

su - prof && opera

instead and see if it helps.

No, that will change me to su shell and execute opera when I return. If you meant su - prof opera that just does the same as I posted above.

Anyone know how to drive this damn thing ? Looks light the super-light weight approach extends to the doc as well.

you may consider sudo.

due to security restrictions root cannot access X (at least he wouldn't).

but with "sux" you can.

first of all emerge sux it's pretty small, and have a very few dependencies,
then run what-you-want issuing "sux -e progname", like "sux -e opera"

This should work, but sudo IMHO is a lot better, you can even setup a list of apps that your user can run as sudo.

cheers

thanks for you suggestions but what I dont get is this:

under xfce is can open a xterm ; su prof and enter opera.

Opera then starts as the user prof , end of story.

Now what is so complicated about that and why does that "fail to find the display" under flux?

It's not a kernel issue but I agree it sux.

Opera will only run as root in flux and that is definately not what I require.

Sadly the doc seems to concentrate mainly on creating menus not basic function like this.

regards

[revertex]

oh! i' m sorry, i misunderstand you!
now i see, all that you want is run opera as user " prof".
didn' t figure that " prof" is a user, stupid me.

try

Code: Select all

su prof -c opera

[Gentree]

Well thanks again for the reply.

this works fine un xfce but I get the same issue on flux, something about cant connect to display.

There must be something in flux that does not have the right permissions. In xfce gnome or kde I can just open a term, su to prof and run anything that use can access.

For the moment flux is useless to me. Any ideas where I should look to fix this?

TIA

[revertex]

Gentree,

i was the only user in my box, but i created another user called lam3_us3r, just to test it, and can launch opera as lam3_us3r under my account perfectly.

i just did "su lam3_us3r -c opera" then in opera >help > about opera it seems all paths poit to lam3_us3r homedir.
i don't believe it's fluxbox fault, but maybe b0rked with your setup.
if i can help you with some extra info get in touch please.

[Gentree]

Many thanks for sticking with this.

I am now running opera as root under flux to post the message I get from the user account

Code: Select all

bash-3.00#su prof
prof@newsys /root $ opera
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified

opera: cannot connect to X server :0.0
prof@newsys /root $ 

ie I startx as root and but cant run anything X once I do an su .

I can still do things like ls, cd , etc.

Does that make any more sense to you.

TIA.

[stahlsau]

hi,
you can do

Code: Select all

su - prof -c opera

That works for me at least.

[Gentree]

No.

"cannot connect to X server"

there seems to be something more fundemental that is not configured here.

Whatever route I take to run something as a user it fails to connect.

Thx.

[jlowe]

Addition/tweak to the wallpaper section (supposing you used fbsetbg with esetroot before);

Code: Select all

root@z10n # emerge unmerge eterm
root@z10n # emerge feh
...and recommendably:
root@z10n # emerge aterm

It's really just a personal preference, but I like aterm much more than eterm (which you'll need an alternative to, unless you can settle with xterm), and didn't really ever use eterm anyways, so I was happy when I found out I could use the lightweight imageviewer feh (which ALSO has correct fileparsing of filenames with whitespace in them... I don't know if this is still a problem with fbsetbg, but Pwnz3r pointed this out on his site, so I thought I'd just add it here as well)... we NEED fluxbox tips/info

Code: Select all

FILE: ~/.fluxbox/menu
...
[submenu] (wallpapers)
     [exec] (random) {feh -r --bg-scale ~/.fluxbox/backgrounds/}
     [wallpapers] (~/.fluxbox/backgrounds/) {feh --bg-scale}
[end]
...

The first (random) will set a random picture from ~/.fluxbox/backgrounds/ as background, and the second (wallpapers) will add all images in ~/.fluxbox/backgrounds/ to the menu, and when you click any one, it'll be set as background.
Optionally you can make fluxbox load a random wallpaper when it's started (this is what I do):

Code: Select all

FILE: ~/.fluxbox/init
...
session.screen0.rootCommand:    feh -r --bg-scale ~/.fluxbox/backgrounds/
...

I MUST ADMIT that I don't really remember if the -r flag is right (as I'm not in linux atm), please do correct me if I'm wrong though

=======

Still no enlightenment on the SETI issues with torsmo? :S

I'm getting frustrated with trying to get the wallpaper trick to work. Here is that section of my menu file:

Code: Select all

[submenu] (Wallpapers)
      [Wallpapers] (~/.fluxbox/backgrounds) {feh --bg-scale}
[end]

I have five images in that directory, but when I select the wallpaper menu item, it shows a top bar of Wallpapers, but no images listed. None of the filenames are crazy. I have no idea why this is not working. My full menu config file is here. As far as I can tell, all sections have ends, and there are not any silly mistakes in the file...but maybe I'm missing something?

Any help would be appreciated.

[feminista]

jlowe: [wallpapers] can't be capitalized, it's a special fluxbox keyword.

By the way, that tip rocks. I mean, fbsetbg is easy, but that's PAINFULLY easy.

[jlowe]

jlowe: [wallpapers] can't be capitalized, it's a special fluxbox keyword.

By the way, that tip rocks. I mean, fbsetbg is easy, but that's PAINFULLY easy.

Thanks! I will try this out tomorrow... I figured it was something simple I was overlooking.

[edit]

That works perfectly. I now have a list of wallpapers to choose from.

[jlowe]

Now, I'm having a different problem. I want conky to start up with fluxbox. So, naturally, I edit ~/.fluxbox/startup. I add a line 'conky &' and save. But when I startup fluxbox, it never starts. I even tried something simple like making aterm start with fluxbox, but nothing seems to work. I'm baffled. My older pc with fluxbox, I never had a problem with startup programs. Here is my startup file:

Code: Select all

# fluxbox startup-script:
#
# Lines starting with a '#' are ignored.

# You can set your favourite wallpaper here if you don't want
# to do it from your style.
#
# bsetbg -f ~/pictures/wallpaper.png

# This sets a black background

#/usr/bin/bsetroot -solid black

# This shows the fluxbox-splash-screen
# fbsetbg -C /usr/share/fluxbox/splash.jpg

# Other examples. Check man xset for details.
#
# Turn off beeps:
# xset -b
#
# Increase the keyboard repeat-rate:
# xset r rate 195 35
#
# Your own fonts-dir:
# xset +fp /home/joshua/.font
#
# Your favourite mouse cursor:
# xsetroot -cursor_name right_ptr
#
# Change your keymap:
# xmodmap ~/.Xmodmap



# Applications you want to run with fluxbox.
# MAKE SURE THAT APPS THAT KEEP RUNNING HAVE AN ''&'' AT THE END.
#
# unclutter -idle 2 &
# wmnd &
# wmsmixer -w &
# idesk &
conky &

# And last but not least we start fluxbox.
# Because it is the last app you have to run it with ''exec'' before it.
exec /usr/bin/fluxbox
# or if you want to keep a log:
# exec /usr/bin/fluxbox -log ~/.fluxbox/log

[yabbadabbadont]

Conky probably needs the root window to already be created and painted. I found that starting fluxbox first, sleeping for two seconds, then starting everything else, then waiting on the fluxbox pid to end worked better.

Code: Select all

# fluxbox startup-script:
#
# Lines starting with a '#' are ignored.

# You can set your favourite wallpaper here if you don't want
# to do it from your style.
#
# bsetbg -f ~/pictures/wallpaper.png
#
# This sets a black background

/usr/bin/bsetroot -solid black

# This shows the fluxbox-splash-screen
# fbsetbg -C /usr/share/fluxbox/splash.jpg

# Other examples. Check man xset for details.
#
# Turn off beeps:
xset -b
#
# Increase the keyboard repeat-rate:
xset r rate 250 30
#
# Your own fonts-dir:
# xset +fp /home/yoiks/.font
#
# Your favourite mouse cursor:
# xsetroot -cursor_name right_ptr
#
# Change your keymap:
# xmodmap ~/.Xmodmap

/usr/bin/fluxbox &
fluxpid=$!

# Give fluxbox a chance to startup and draw the root background
sleep 2

# Applications you want to run with fluxbox.
# MAKE SURE THAT APPS THAT KEEP RUNNING HAVE AN ''&'' AT THE END.
#
# unclutter -idle 2 &
# wmnd &
# wmsmixer -w &

gkrellm2 &
sleep 1
idesk &
sleep 1
adesklets

# And last but not least we start fluxbox.
# Because it is the last app you have to run it with ''exec'' before it.

# exec /usr/bin/fluxbox
# or if you want to keep a log:
# exec /usr/bin/fluxbox -log ~/.fluxbox/log

wait $fluxpid

[jlowe]

Conky probably needs the root window to already be created and painted. I found that starting fluxbox first, sleeping for two seconds, then starting everything else, then waiting on the fluxbox pid to end worked better.

I tried this, but it still did not work. It doesn't make any sense that even if I put 'aterm &' in the startup file, nothing starts up with fluxbox. I'm not sure what the problem is, but seeing how this is a tips thread, I don't want to keep on about it.

If anyone has other suggestions, I would appreciate it.

[dswissmiss]

I start all my programs in ~/.xinitrc, so I have the line

Code: Select all

conky &

in there.