broke fluxbox

drkstr · 08-09-2006, 02:18 AM

I got a little over zealous in removing un needed libraries, and now my fluxbox will only load with the default window settings (no borders and ugly colors) I turned on logging, and while it tells me what's happening, it doesn't really say why. Any one have an ideas about where I can start looking for the source? I can usually figure something out, but I don't even know where to start looking on this one.

Thanks!
...drkstr

Code:

------------------------------------------
Log File: /home/webuser/.fluxbox/log
Fluxbox version: 1.0rc2
Compiled: Jul 26 2006 16:31:58
Compiler: GCC
Compiler version: 3.4.6

Defaults:
    menu: /usr/X11R6/share/fluxbox/menu
   style: /usr/X11R6/share/fluxbox/styles/Clean
    keys: /usr/X11R6/share/fluxbox/keys
    init: /usr/X11R6/share/fluxbox/init
    nls: /usr/X11R6/share/fluxbox/nls

Compiled options (- => disabled): 
-DEBUG
EWMH
GNOME
-IMLIB2
KDE
NLS
REMEMBER
RENDER
SHAPE
SLIT
TOOLBAR
XFT
XINERAMA
XMB
XPM

------------------------------------------
Failed to read: session.tabs
Setting default value
Failed to read: session.ignoreBorder
Setting default value
Failed to read: session.forcePseudoTransparency
Setting default value
Failed to read: session.numLayers
Setting default value
Failed to read: session.tabPadding
Setting default value
Failed to read: session.focusTabMinWidth
Setting default value
Failed to read: session.styleOverlay
Setting default value
Failed to read: session.slitlistFile
Setting default value
Failed to read: session.groupFile
Setting default value
Failed to read: session.appsFile
Setting default value
Failed to read: session.tabsAttachArea
Setting default value
Failed to read: session.modKey
Setting default value
apps file failure
Failed to read: session.screen0.imageDither
Setting default value
Failed to read: session.screen0.opaqueMove
<SNIP - you get the idea>

**edit**
Also, I am using the same fluxbox config files in my home directory that I have been using, but I might be usig a newer version of flux (from Slack-current from 08/07/06)

Randux · 08-09-2006, 07:41 AM

That's a tough one, but I've been there. The only advice I have since I don't know fluxbox internals is to download fluxbox from either 10.2 or current again and extract the tar in a work area. Then compare the contents with what you have installed and add modules from the tar, one by one, until it works.

Paring down systems is pretty nerve-wracking but it's interesting work

tobyl · 08-09-2006, 01:33 PM

I think it is this one:

init: /usr/X11R6/share/fluxbox/init

if you have an init file in your ~/.fluxbox

try copying it to /usr/X11R6/share/fluxbox/

and see what you get. I think you can specify most flux config files in init, but perhaps not init iself?

tobyl

drkstr · 08-09-2006, 01:42 PM

Thanks again for you help Ranux, it's always worthwhile. This is good advice, I will try it.

regards,
...drkstr

drkstr · 08-09-2006, 01:46 PM

Quote:

I think it is this one:

init: /usr/X11R6/share/fluxbox/init

if you have an init file in your ~/.fluxbox

try copying it to /usr/X11R6/share/fluxbox/

and see what you get. I think you can specify most flux config files in init, but perhaps not init iself?

Thanks Tobyl, I will try this as well. I had it working previously with the same set up, but maybe something has changed. I will try playing around with the file location to see if I can narrow it down. I will also try copying the actual style to ~/.fluxbox/ and point to it in the ~/.fluxbox/init to see if that helps. If all else fails, I can just start over from scratch and compare the diff.

tobyl · 08-09-2006, 02:03 PM

sorry i think i was wrong
init is sourced in ~/.fluxbox on my system too.
I can only guess that the new fluxbox version has parameters in init that you did not have in the old version.
But you will have fixed that by now :-)
tobyl

drkstr · 08-09-2006, 09:26 PM

Copying the style to the ~/.fluxbox directory and then pointing the ~/.fluxbox/init to it did the trick. I'm not sure why it wouldn't read it in the standard directory though. Probably a permissions problem somewhere, but I'm not going to worry about it since it's working now.

Thanks everyone for your help!
...drkstr

Randux · 08-10-2006, 05:08 AM

Quote:

Originally Posted by drkstr

Thanks again for you help Ranux, it's always worthwhile. This is good advice, I will try it.

regards,
...drkstr

Thanks for the nice comments. The great user community is one of the things that makes Slackware the best distro