The Fluxbox developers are:
The recommended fluxbox version is always the latest development version. It is the most stable available. Get it from http://fluxbox.org/download.
You can learn how to build fluxbox from source if you don't know how to do this.
If you like to test new features or help hunting down some bugs you may think about the git version of fluxbox, which is the bleeding edge release. See how to get and install git version
People used to say this because for a very long time the only "official" stable version was 1.1 and it wasn't touched for over 2 years. Now this is not true. The latest offical stable is version 1.3.1 and it is considered very stable. The latest development version is also considered to be a very stable version. Go and get it from http://fluxbox.org/download/
All *boxen were forked from Blackbox. This is long time gone and both projects have developed in different ways, added different features, had other priorities. Thus, the current states of the *boxen differ significantly.
Check here.
The fedora distribution uses a different setup. Instead of the dm-specific locations, it requires session files to be in /etc/X11/dm/Sessions.
So, to get Fluxbox into its session menu, create the file: /etc/X11/dm/Sessions/fluxbox.desktop with contents:
[Desktop Entry]Encoding=UTF-8Name=FluxboxType=ApplicationIcon=Exec=startfluxbox
You may need to put the full path to fluxbox in the Exec line if it is in a non-standard location. It is also reported that the file needs execution right:
chmod +x /etc/X11/dm/Sessions/fluxbox.desktop
One might check other files attributes.
This is a barebones entry. Hopefully one day we will be able to make a version with translations available in the main source distribution.
Create the file: /etc/gdm/Sessions/fluxbox with contents:
#!/bin/sh## /etc/gdm/Sessions/fluxbox## global fluxbox session file -- used by gdmexec /etc/X11/Xsession /usr/bin/fluxbox
Of course, change /usr/bin/fluxbox to wherever your fluxbox binary is. If the /etc/gdm directory doesn't exist, it may be /etc/X11/gdm/Sessions/fluxbox on your computer.
There are a couple of ways. You can either choose the "default" session, which should load your .xsession file and thus you'd put "exec fluxbox" at the end of that.
Or, to get a fluxbox option, go into KDE Control Center and add a session type "fluxbox".
Or, edit your kdmrc file (probably /etc/kde2/kdm/kdmrc). Find the "SessionTypes=" line, and add fluxbox to the list.
If you are running Debian (thanks Dave Selby), then after adding the fluxbox session edit /etc/kde2/kdm/kdm.options and delete the line:
generate-sessiontypes
If you don't delete this Debian will loose the entry in the KDM menu when you reboot.
That should be enough. However, some older configurations require a little more effort - you may need to find your Xsession file (e.g. /etc/X11/Xsession, or /usr/X11R6/lib/X11/xdm/Xsession) and add an option in the case statement containing other WMs, i.e.:
fluxbox) exec fluxbox ;;
No, you can't. Fluxbox is a windowmanager, compiz and beryl are window managers (combined with a composite manager). So you can only replace fluxbox with one of them. KDE, GNOME and XFCE are desktop environments, which bring a windowmanager (kwin, metacity and xfwm) along. That's why you can use them with compiz, only the windowmanager is replaced.
Fluxbox is not modular, so you can't use the fluxbox menu, toolbar, slit or anything else with compiz. You can read the eyecandy section for some nice effects with fluxbox or switch completely to compiz/beryl and miss all the great features fluxbox has.
This question is beat to death with a huge hammer in #fluxbox IRC chat. The end answer really is: Which ever one you want.
With that said there are several to choose from; you can try:
And many many others, so take your pick and find what works best for you.
Those have no UTF-8 support:
You have many choices when it comes to this. Many of the people in the fluxbox IRC room are using Irssi while still many of them use Xchat. You are by all means not even limited to just these two. You can also use:
And many others; so find the one that works best for you and use it.
And many others, take your pick and choose what works best for you.
Yes. Do ./configure --enable-kde. This makes it so that the KDE tray icons will appear in the slit.
Yes, by default. You can also add "xscreensaver &" to your ~/.fluxbox/startup file so you can lock the screen or use xscreensavers.
Yes you can. To do this simply run this command:
gnome-session-remove metacity
followed by:
fluxbox &
next you need to run:
gnome-session-properties
click the Startup Programs tab and add fluxbox click close and finally save your gnome session:
gnome-session-save
yes, just start fluxbox and then "kicker" and "kdesktop" or export KDEWM=startfluxbox in your login shell rc file (usually ~/.bashrc).
To add pixmaps to your menu you need to make sure your fluxbox has been compiled with xpm support at the very least, and imlib2 support for png icons. Run the following command
fluxbox -i
and look for XPM for xpm icon support and IMLIB2 for png support. The syntax is simple, for example:
[exec] (firefox) {firefox}
If you have an icon named firefox.xpm in your /usr/share/pixmaps dir then that will put the icon in the menu. For more help with your menu see the menu edition howto.
Take a look at the style you are currently using
grep -i stylef ~/.fluxbox/init
from there open it and add or edit the following value:
menu.itemHeight:
where
If you have started fluxbox but have an empty menu, try using the command
fluxbox-generate_menu -h
Also see this howto.
For some reason the Fedora guys decided to make the default startup file run their custom menu generator command. To prevent your changes from being over ridden open your startup file and look for
if [ -x /usr/bin/fluxbox-xdg-menu ]; then /usr/bin/fluxbox-xdg-menu --with-icons & fi
Just remove this from the startup file and your menu changes will no longer get lost on each startup.
You can make your menus transparent if you are running a recent version of fluxbox (0.9.2 or above) by changing the "Menu Alpha" value in the configure menu. 255 = Opaque, 0 = Invisible (completely transparent). A value around 160 seems to satisfy most people. You should probably also read the next question for other things you need...
Here are some things to check:
You must be running a Fluxbox version 0.9.2 or newer. 0.1.x does not contain transparency support.
Fluxbox must be restarted for changes in the alpha value to take effect (just choose restart in the menu).
You need to have the XRender extension enabled in X, and compiled into fluxbox. Running fluxbox -i and xdpyinfo | grep RENDER should both say "RENDER".
You must have set the background with an XRender-compatible tool. fbsetbg comes with fluxbox and tries to make this easy for you, try it (the web page also has list of transparency supporting background tools). Run fbsetbg -i to see if it can find a suitable tool.
These are tabs. If you have upgraded from .9.x fluxbox to a 1.0rcx or newer version of fluxbox these tabs will be enabled by default. To configure them just right click your your desktop to get the root menu, then scroll down to Fluxbox Menu -> configure -> tab options. If you want them off select tabs in titlebar and they will act like the tabs in the .9.x releases.
Because fluxbox is "only" a windowmanager and natively doesn't provide icons.
Some applications are considered to be useful for desktop-icons:
See the howto for idesk and for fbdesk for info on getting these setup.
You could also use a file manager like rox-filer or pcmafm for the icons, but they are not as flexible as the ones above and may cause some problems.
Since the 0.9.14 release the use of fonts changed a bit. Check the font howto.
Try reading the Artwiz/Fluxbox Guide.
If you like the Artwiz fonts, but don't like the way they look in terminals, consider checking out the 'LFP' Fontpack. There are two sets of fonts there, the LFP-Fixed width (good for terminals), and LFP Variable-width (good for other things).
The first thing to know about the slit is that it is NOT the fluxbox toolbar -- it is completely separate from the toolbar. If you see anyone telling anyone else that is, whack them with something painful and point them here. :)
The slit is one of the many parts of Fluxbox that has been inherited from Blackbox. It is essentially a dock: a place where dockable applications can be grouped together separately from your other windows. It is designed to hold WindowMaker Dockapps (and anything that runs in that mode which is called 'withdrawn' or occasionally 'swallowed'). Such applications often have a -w option to run in the slit, but some start automatically in withdrawn mode.
Keep in mind: The slit is invisible if nothing is in it!
In order to see it, run your dockapp and the slit will show up.
As of 0.1.10, YES!
The command to use is fbsetbg To find out how to use it either consult its man page, or take a look at this howto.
Run the command:
xrandr -s x
where
You should also read the detailed page.
Look at the grouping howTo to learn about it.
There doesn't seem to be one any more but looks like there used to be a file called "Supported_platform_success_reports.html".
Open your ~/.fluxbox/init and search for the line
session.screen0.toolbar.height
If this value is 0 then the style controls the toolbar height. if you set the value to something bigger than 0 then you will override ALL style-files with this "global height".
Open your style-file and search for the line
window.title.height
Simply change this value to your likings.
Open the your root-menu, go to the configure-Menu and DISABLE "Full Maximization", which will turn off the global switch. Then make sure you also disable "Maximize over" in the toolbar-menu and the slit-menu (also in the configure-Menu). Set the toolbar layer to Desktop, and maximize a window to check the effect.
Change this line in your init:
session.screen0.strftimeFormat: %a %d %H:%M
Two very good sources are these man pages:
man strftimeman date
You probably have an empty slit at the right edge, and the window won't maximize over it. To fix it, simply enable Menu -> Configuration -> Slit -> Maximize Over.
This behaviour is not a bug. It occurs because of the nature of outline window moving. With opaque window moving the application does not freeze (you can set it in the menu or set session.screen0.opaqueMove: true in ~/.fluxbox/init).
Long version: Outline moving works by drawing a rectangle of inverted pixels around a window. When you move the mouse, the old rectange is erased (by inverting the pixels again) and a new one drawn. Fluxbox grabs the display to freeze all the applications display windows. If it doesn't to this, then window changes can occur which change bits of the rectangles, ultimately leaving sections of rectangle randomly around the screen.
All window managers that offer outline moving need to enforce the same rule so that the display doesn't become messy with rectange fragments during or after the move operation. If you find one that doesn't, let us know :)
The author believes that applications such as XMMS whose primary function is not graphical ought to be able to continue to operate without the display updating (mplayer has a good excuse to pause). However, this behaviour is not under the control of the Fluxbox developers - you should talk to XMMS people to see if they can make it continue playing even without display updates (though I imagine this may also be a difficult problem).
You can either use the startup file, or set up your .xinitrc file.
This is a bug in versions of fluxbox prior to 0.1.8-bugfix2. Please upgrade to the latest version/bugfix before reporting this as a bug.
You may certainly, be sure to add some lines for titlebar and keygrabbing, though. It may also be wise to symlink your blackboxrc and ~/.fluxbox/init together somehow.
Yes. The tarballs for both packages should be 100% interchangeable...as long as the style was written for blackbox <=0.65.
This might be true for the Waimea and Openbox projects, although there is no guarantee. I've not seen such a promise from either of the two projects, no one can keep them from handling styles differently.
These are two more Blackbox code forks. To be perfectly precise, the only BB code Waimea uses is the Styles and Rendering engines, but that means that stylefiles should be compatible, at least.
Just link your ~/.blackboxrc -> ~/.fluxbox/init
Create ~/.gtkrc-2.0, or it probably exist, and it will look like this
# -- THEME AUTO-WRITTEN DO NOT EDITinclude "/home/yourname/.themes/Murrina-Olive/gtk-2.0/gtkrc"include "/home/yourname/.gtkrc-2.0.mine"# -- THEME AUTO-WRITTEN DO NOT EDIT
Create ~/.gtkrc-2.0.mine:
gtk-icon-theme-name = "Tango"gtk-font-name = "sans 8"gtk-toolbar-icon-size = GTK_ICON_SIZE_SMALL_TOOLBARgtk-toolbar-style = GTK_TOOLBAR_ICONS
See the GTK howto.
Alternatively, if you have GNOME installed run gnome-settings-daemon when Fluxbox starts, eg. put this into your ~/.xinitrc
# load this to have gtk2 apps look okGSDPID=`pidof gnome-settings-daemon`if [ "x$GSDPID" == "x" ]; then gnome-settings-daemon &fi
If the above code fails to work, try switching the line
gnome-settings-daemon &
with
/usr/libexec/gnome-settings-daemon &
or with the explicit path to wherever it's located on your system.
Check man page for given terminal you use. Read quick hints on aterm and xterm.
Use, eg.root-tail. For example:
root-tail -f -fn 'glisp' -g 220x10+20+50 /var/log/messages,gray,MESSAGES
Look here.
Add the following line to your .xinitrc before you exec fluxbox:
export LC_ALL=C
This should help on newer Redhats.
If your session.screen0.toolbar.tools: in ./fluxbox/init looks like this:
session.screen0.toolbar.tools: prevworkspace, workspacename, nextworkspace, clock, iconbar, systemtray, prevwindow, nextwindow,
move the “clock” parameter from the left end to the right end:
session.screen0.toolbar.tools: prevworkspace, workspacename, nextworkspace, iconbar, systemtray, prevwindow, nextwindow, clock
There should be an entry your your .fluxbox/menu file that looks like this:
[submenu] (Styles) [include] (/usr/share/fluxbox/menu.d/styles/)
Change this entry to:
[stylesdir] (/usr/share/fluxbox/styles) [stylesdir] (~/.fluxbox/styles)
Change the following entry in your ~/.fluxbox/keys from this:
# scroll on the toolbar to change workspacesOnToolbar Mouse4 :PrevWorkspaceOnToolbar Mouse5 :NextWorkspace
To this:
# scroll on the toolbar to change windowsOnToolbar Mouse4 :PrevWindowOnToolbar Mouse5 :NextWindow
Find this entry in your ~/.fluxbox/keys:
# double click on the titlebar to shadeOnTitlebar Double Mouse1 :Shade
And change it to this:
# double click on the titlebar to mazimizeOnTitlebar Double Mouse1 :Maximize
This site is hosted by errr. The admin of the site is errr. The content is provided by many many fluxbox users from all over the world. Thank you all for your hard work making this site a great source for sharing information about our favorite window manager, fluxbox.
You can!! Sicne this web site is powered directly by the content of a github repository all you need to do is fork the project, make your changes then send us a pull request
Because of spam we disabled new account creation. If you would like an account on this wiki please join the IRC chat room and request one. To find out who to ask join the room and type: ,wiki account? and fbot will tell you
The IRC channel is #fluxbox on the freenode network.
Go to http://webchat.freenode.net and use freenode's own web interface.
The main bot in the room is fbot. When he is on holiday or what ever, computer is there as a backup. Both bots have very similar syntax. To ask them a question address them:
fbot: styles?
For more information please see how to work the bots.
We have a very mature room and almost never need to have someone in the room to moderate it. Keep in mind there are several OPs in the room, they just dont wear their badges.
The #fluxbox channel is the official chat room for fluxbox support. As with any chat room there will be some off-topic discussion from time to time. This is ok, it is a chat room, and so it will happen. However, it is best to keep off-topic discussions out of #fluxbox, even if nobody else is talking, in order to avoid distracting people who are there to help. If you are being asked (or told) to go to #fluxbox-chitchat, it is because you have gone too far with an off-topic discussion. For your own safety, you should move your off-topic discussion to #fluxbox-chitchat.
The simple answer is: We dont care if you are here or there, we dont care if you are at home or school or work or where ever. We are in the room for supporting fluxbox . So disable your public away. Changing your nick is also just as bad; for example: someNick|away someNick-Away someNick|school someNick|eating the same rule applys, WE DONT CARE.