Note: This isn't a very urgent question, as I am posting this from a fully functional Fluxbox installation. Just out of curiosity though: does anyone here run Openbox? The pedantic minimalist in me likes the fact that it was apparently retro-written completely in C instead of C++ like its ancestors. I tried a couple of days ago to run it on the minimum installation "project" I was working on but couldn't resolve an issue with the DISPLAY variable not being set. It seems that an xorg.conf file is absolutely essential to run it. It doesn't even run on my current install (for today at least; I'm very finicky and impulsive when it comes to my computer sometimes) and falls victim to the same errors. Which kind of annoys me in that it seems I could've kept my previous small install and just run Fluxbox on that.

Has anyone gotten a non-fatal error about an 'fbdev' module and a fatal error about not being able to set the display from the DISPLAY variable when trying to start Openbox? How did you fix it? Or what does your xorg.conf file look like?

I use openbox frequently without any xorg.conf file at all.

Also, anyone using Xorg on a recent Slackware installation without an xorg.conf file will get a non-fatal error about fbdev. Xorg tries to load fbdev by default, and xf86-video-fbdev just isn't included in Slackware any more.

But what about the display error? I got it on my minimal system so I assumed I had disabled an important package, but when I did a "full" install (all of a, ap, d, n, l, x) I get that same error. I've learned to live with the fbdev one.

I don't get the DISPLAY error. How are you starting X and openbox? Are you using kdm? startx? What does your .xinitrc file look like?

Adam

I used to use openbox for a long time, then I switched to fluxbox. Fluxbox runs at around 2% less cpu and 50mb less ram. Openbox has the nice feature of supporting application's transparency settings, though, instead of requiring you to set transparency with the apps file, which I liked.

I have used OpenBox extensively, both on systems with xorg.conf files (for an NVidia card) and without (for Intel integrated video). I have never gotten the DISPLAY error.

Note that on Slackware 13.37, the DISPLAY variable is set in /etc/profile.

Another happy Openbox (3.4.11, works great and I don't see a reason to update to 3.5) user here, no issues. Are you installing slackbuild, binary or manually building from source?

I use Openbox as well. I built it using the slackbuilds on 13.37-x64 and have never had any issues regarding Xorg.conf or $DISPLAY..

Hey guys, thanks for the replies!

I just made a post in member success stories about a more minimal install of Slack I did last night and have decided my window manager will (eventually) be dwm. I had been interested in Openbox because I was under the impression that it would be considerably lighter than other *boxes, but I seem to have been mistaken. So unfortunately I no longer have that particular xinit on my system. I will tell you that 1) all I did to the default .xinitrc was add "exec openbox-session", 2) I used the 'startx' command and 3) I used the Slackbuild.org slackbuild for it (though come to think of it I'm not sure if it was the 13.37 build or not). So at this point I'm not much use in my own thread anymore...

I'll put more thought in before I start a new thread, I promise.