Jump to content

Fluxbox, I need help?


jmr0311
 Share

Recommended Posts

To the fluxbox users:

 

I'm want to experiment with different windows manager, so I install Fluxbox, I'm so cautivated by the customization you can do in this environment. I just want to jump in and start customizing but here is where I get stumble. Because I don't know what to do to achieve those nice graphics like this one or maybe this one. I found them in the Fluxbox website.

 

I ask to my self if a need to be a Guru in C++ to be able to use Fluxbox, because I can't seem to understand any of the instruction I find in the internet that are related to Fluxbox. I need some guidance ( like a tutorial ) on how to deal with Fluxbox and his configuration. I think you have to install all the applications you want to use in Fluxbox using my regular KDE enviroment, But I don't know how to make them available in Fluxbox. Also I notice that a lot of the stuff some other people are using in Fluxbox , they seem to created them and placed them in ~/.fluxbox/ directory. Help please cause I've been for the last two weeks trying to accomplish something in Fluxbox with no success.

 

Javi :help:

Edited by jmr0311
Link to comment
Share on other sites

  • Replies 66
  • Created
  • Last Reply

Top Posters In This Topic

Well, lets see...

 

In the first screenshot you linked to, gdesklets are used for some of the eye candy. In the second, it almost looks like kicker is used (top left) but I could be wrong.

 

How do you start fluxbox? Through the command line with startx or through a dm? If you start through the command line, all of the programs you want to load at startup need to go in ~/.xinitrc. One per line, followed by an &, before the exec fluxbox line. Example:

 

gdesklets &

gaim &

exec fluxbox

 

If you start through a dm (graphical startup), then you need to do the same thing in ~/.fluxbox/startup. Same thing, programs need to go in there before the exec line and with an & after them.

 

You can use anything in flux that you can in any other WM/DE. Everything that is in your menu will appear when you right click on the desktop.

Link to comment
Share on other sites

When I did my installation of Fluxbox in my system it automatically created it a choice in Kdm login screen to run fluxbox. So I need to go to (~/.fluxbox/ ) and create a file call startup and then add the links to the applications the way you said in there. Then when I go to Fluxbox if I right click on the desktop and the little windows opens, the links to the applications are going to be there.

 

I was trying to install gDesklets in my system but I'm having an error when I'm doing the " ./configure --prefix=/usr --sysconfdir=/etc :

 

[jmr0311@home-desktop jmr0311]$ cd /home/jmr0311/gDesklets-0.30pre/

[jmr0311@home-desktop gDesklets-0.30pre]$ ./configure --prefix=/usr

checking for a BSD-compatible install... /usr/bin/install -c

checking whether build environment is sane... yes

/home/jmr0311/gDesklets-0.30pre/missing: Unknown `--run' option

Try `/home/jmr0311/gDesklets-0.30pre/missing --help' for more information

configure: WARNING: `missing' script is too old or missing

checking for gawk... gawk

checking whether make sets $(MAKE)... yes

checking whether to enable maintainer-specific portions of Makefiles... no

checking for style of include used by make... GNU

checking for gcc... gcc

checking for C compiler default output file name... a.out

checking whether the C compiler works... yes

checking whether we are cross compiling... no

checking for suffix of executables...

checking for suffix of object files... o

checking whether we are using the GNU C compiler... yes

checking whether gcc accepts -g... yes

checking for gcc option to accept ANSI C... none needed

checking dependency style of gcc... gcc3

checking for strerror in -lcposix... no

checking for gcc... (cached) gcc

checking whether we are using the GNU C compiler... (cached) yes

checking whether gcc accepts -g... (cached) yes

checking for gcc option to accept ANSI C... (cached) none needed

checking dependency style of gcc... (cached) gcc3

checking for gcc option to accept ANSI C... none needed

checking for perl... /usr/bin/perl

checking for a BSD-compatible install... /usr/bin/install -c

checking build system type... i686-redhat-linux-gnu

checking host system type... i686-redhat-linux-gnu

checking for a sed that does not truncate output... /bin/sed

checking for egrep... grep -E

checking for ld used by gcc... /usr/bin/ld

checking if the linker (/usr/bin/ld) is GNU ld... yes

checking for /usr/bin/ld option to reload object files... -r

checking for BSD-compatible nm... /usr/bin/nm -B

checking whether ln -s works... yes

checking how to recognise dependent libraries... pass_all

checking how to run the C preprocessor... gcc -E

checking for ANSI C header files... yes

checking for sys/types.h... yes

checking for sys/stat.h... yes

checking for stdlib.h... yes

checking for string.h... yes

checking for memory.h... yes

checking for strings.h... yes

checking for inttypes.h... yes

checking for stdint.h... yes

checking for unistd.h... yes

checking dlfcn.h usability... yes

checking dlfcn.h presence... yes

checking for dlfcn.h... yes

checking for g++... g++

checking whether we are using the GNU C++ compiler... yes

checking whether g++ accepts -g... yes

checking dependency style of g++... gcc3

checking how to run the C++ preprocessor... g++ -E

checking for g77... no

checking for f77... no

checking for xlf... no

checking for frt... no

checking for pgf77... no

checking for fort77... no

checking for fl32... no

checking for af77... no

checking for f90... no

checking for xlf90... no

checking for pgf90... no

checking for epcf90... no

checking for f95... no

checking for fort... no

checking for xlf95... no

checking for ifc... no

checking for efc... no

checking for pgf95... no

checking for lf95... no

checking for gfortran... no

checking whether we are using the GNU Fortran 77 compiler... no

checking whether accepts -g... no

checking the maximum length of command line arguments... 32768

checking command to parse /usr/bin/nm -B output from gcc object... ok

checking for objdir... .libs

checking for ar... ar

checking for ranlib... ranlib

checking for strip... strip

checking if gcc static flag works... yes

checking if gcc supports -fno-rtti -fno-exceptions... no

checking for gcc option to produce PIC... -fPIC

checking if gcc PIC flag -fPIC works... yes

checking if gcc supports -c -o file.o... yes

checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes

checking whether -lc should be explicitly linked in... no

checking dynamic linker characteristics... GNU/Linux ld.so

checking how to hardcode library paths into programs... immediate

checking whether stripping libraries is possible... yes

checking if libtool supports shared libraries... yes

checking whether to build shared libraries... yes

checking whether to build static libraries... no

configure: creating libtool

appending configuration tag "CXX" to libtool

checking for ld used by g++... /usr/bin/ld

checking if the linker (/usr/bin/ld) is GNU ld... yes

checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes

checking for g++ option to produce PIC... -fPIC

checking if g++ PIC flag -fPIC works... yes

checking if g++ supports -c -o file.o... yes

checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes

checking dynamic linker characteristics... GNU/Linux ld.so

checking how to hardcode library paths into programs... immediate

checking whether stripping libraries is possible... yes

appending configuration tag "F77" to libtool

checking whether ln -s works... yes

checking whether make sets $(MAKE)... (cached) yes

./configure: line 20382: CFLAGS: command not found

checking for python... /usr/bin/python

checking for python version... 2.3

checking for python platform... linux2

checking for python script directory... ${prefix}/lib/python2.3/site-packages

checking for python extension module directory... ${exec_prefix}/lib/python2.3/site-packages

checking for pkg-config... /usr/bin/pkg-config

checking for gnome-python-2.0 >= 2.0.0 pygtk-2.0 >= 2.0.0... yes

checking GDESKLETS_CFLAGS... -I/usr/include/pygtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include

checking GDESKLETS_LIBS... -lgobject-2.0 -lglib-2.0

checking for pygtk-2.0 glib-2.0 gdk-2.0 gtk+-2.0... yes

checking EWMH_CFLAGS... -I/usr/include/pygtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/pango-1.0 -I/usr/X11R6/include -I/usr/include/freetype2 -I/usr/include/freetype2/freetype2 -I/usr/include/atk-1.0

checking EWMH_LIBS... -Wl,--export-dynamic -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0 -lm -lpangoxft-1.0 -lpangox-1.0 -lpango-1.0 -lgobject-2.0 -lgmodule-2.0 -ldl -lglib-2.0

checking for glib-2.0 libgtop-2.0 >= 2.0.0... Package libgtop-2.0 was not found in the pkg-config search path.

Perhaps you should add the directory containing `libgtop-2.0.pc'

to the PKG_CONFIG_PATH environment variable

No package 'libgtop-2.0' found

 

configure: error: Library requirements (glib-2.0 libgtop-2.0 >= 2.0.0) not met; consider adjusting the PKG_CONFIG_PATH environment variable if your libraries are in a nonstandard prefix so pkg-config can find them.

[jmr0311@home-desktop gDesklets-0.30pre]$

 

 

Javi

Link to comment
Share on other sites

The latest gDesklets RPM is in cooker (I know, cause I installed it today), but the error you are getting can be easily fixed:

 

urpmi libgtop2.0

 

If the startup file is not in ~/.fluxbox then yes you need to create it. It should automatically be there, though.

 

.xsession is a file that is not used (to my knowledge) in Mandrake.

 

The format of the ~/.fluxbox/startup file should be as follows:

 

#!/bin/sh

 

#programs go here, as in:

 

gaim &

gdesklets &

 

#start flux

 

exec /usr/X11R6/bin/fluxbox

Edited by LiquidZoo
Link to comment
Share on other sites

I just installed fluxbox and I didn't have to create any, startup file is there by default. The best way to install gdesklets is thrue urpmi, You can check out the thread ' show off your desktop ' and there you can see the 2 gdesklets that I have. For startup programs I do this as root

 

gedit ~/.fluxbox/startup

 

Thanks where I have all my programs that I want to start upon boot this is what mine looks like,

 

# 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/X11R6/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/zero/.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 &

# And last but not least we start fluxbox.
# Because it is the last app you have to run it with ''exec'' before it.
gaim &
Eterm -x -0 --trans --buttonbar 0 --scrollbar=off &
Eterm -x -0 --trans --buttonbar 0 --scrollbar=off &
acme &
gdesklets &

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

 

as you can see at the end I have gaim, eterm and a few other applications including gdesklets. This is the best way that I know, actually the only way to start programs on start.

 

-Luis

Link to comment
Share on other sites

Thank you guys for your help. I have in the directory (~/.fluxbox/ ) three files that were created at install. They are " init ", " menu ", " keys " , there is not startup file there. Then the other day I was playing with Fluxbox changing the background and another file was created automatically " lastwallpaper " , now I can't get my background back unless I run this command ( fbsetbg -l ). Also I hear you mention cooker as a source to install packages. Let me ask you this, I heard that cooker could be unreliable sometimes, Is that true? and How can I setup one on the URPMI.

 

gedit ~/.fluxbox/startup

What this command do ? Luis101, also in your startup file this # means comment out, so is not going to be execute it.

 

The latest gDesklets RPM is in cooker (I know, cause I installed it today), but the error you are getting can be easily fixed:

 

urpmi libgtop2.0

Liquidzoo, I did install that library using URPMI, but it didn't correct my problem.

 

Javi

Edited by jmr0311
Link to comment
Share on other sites

Javi,

 

That command for me opens up my startup file, which is where I put the programs that I want to start when I start fluxbox. I got it all strait from Iphitus FAQ he has provided you a link as I can see. Also about your wall paper READ iphitus FAQ and you will see how you can make fluxbox remember your wallpaper.

 

-Luis

Link to comment
Share on other sites

Thank you for being so kind, and thanks to iphitus for that fabulous link, great info.

 

Javi :headbang:

 

SORRY

 

P.S.

How can I update to the latest Fluxbox,( I have v 0.9.8 ) What command I need to run if any, or I just need to download the .tar file and install it. Also all the command you outline in the FAQ, did they need to be run from within Fluxbox or it can be done in KDE.

Edited by jmr0311
Link to comment
Share on other sites

Javi,

 

The newest I think is 9.9 ( I think ). You can take a look at it by clicking here

I had a little problems with the .rpm had a few deps, so I downloaded the src.rpm and It minimized the deps just to 1 which you can easily download from contrib.

 

-Luis

Edited by Luis101
Link to comment
Share on other sites

I got this error when I did the " make install " of gDesklets;

 

make[2]: Leaving directory `/usr/src/RPM/SOURCES/gDesklets-0.26.2/locale'

make[1]: Leaving directory `/usr/src/RPM/SOURCES/gDesklets-0.26.2/locale'

Making install in main

make[1]: Entering directory `/usr/src/RPM/SOURCES/gDesklets-0.26.2/main'

make[2]: Entering directory `/usr/src/RPM/SOURCES/gDesklets-0.26.2/main'

make[2]: Nothing to be done for `install-exec-am'.

/bin/sh ../mkinstalldirs /usr/local/share/gdesklets/main

mkdir -p -- /usr/local/share/gdesklets/main

/usr/bin/install -c -m 644 __init__.py /usr/local/share/gdesklets/main/__init__.py

/usr/bin/install -c -m 644 Starter.py /usr/local/share/gdesklets/main/Starter.py

/usr/bin/install -c -m 644 CmdLineParser.py /usr/local/share/gdesklets/main/CmdLineParser.py

/usr/bin/install -c -m 644 admin.py /usr/local/share/gdesklets/main/admin.py

make[2]: Leaving directory `/usr/src/RPM/SOURCES/gDesklets-0.26.2/main'

make[1]: Leaving directory `/usr/src/RPM/SOURCES/gDesklets-0.26.2/main'

Making install in po

make[1]: Entering directory `/usr/src/RPM/SOURCES/gDesklets-0.26.2/po'

make[2]: Entering directory `/usr/src/RPM/SOURCES/gDesklets-0.26.2/po'

make[2]: Nothing to be done for `install-exec-am'.

make[2]: Nothing to be done for `install-data-am'.

make[2]: Leaving directory `/usr/src/RPM/SOURCES/gDesklets-0.26.2/po'

make[1]: Leaving directory `/usr/src/RPM/SOURCES/gDesklets-0.26.2/po'

Making install in sensor

make[1]: Entering directory `/usr/src/RPM/SOURCES/gDesklets-0.26.2/sensor'

make[2]: Entering directory `/usr/src/RPM/SOURCES/gDesklets-0.26.2/sensor'

make[2]: Nothing to be done for `install-exec-am'.

/bin/sh ../mkinstalldirs /usr/local/share/gdesklets/sensor

mkdir -p -- /usr/local/share/gdesklets/sensor

/usr/bin/install -c -m 644 __init__.py /usr/local/share/gdesklets/sensor/__init__.py

/usr/bin/install -c -m 644 DefaultSensor.py /usr/local/share/gdesklets/sensor/DefaultSensor.py

/usr/bin/install -c -m 644 Menu.py /usr/local/share/gdesklets/sensor/Menu.py

/usr/bin/install -c -m 644 Sensor.py /usr/local/share/gdesklets/sensor/Sensor.py

/usr/bin/install -c -m 644 SensorConfigurator.py /usr/local/share/gdesklets/sensor/SensorConfigurator.py

make[2]: Leaving directory `/usr/src/RPM/SOURCES/gDesklets-0.26.2/sensor'

make[1]: Leaving directory `/usr/src/RPM/SOURCES/gDesklets-0.26.2/sensor'

Making install in tools

make[1]: Entering directory `/usr/src/RPM/SOURCES/gDesklets-0.26.2/tools'

/bin/sh ../libtool --mode=link gcc -Wall -Wstrict-prototypes -Wmissing-prototypes -DG_DISABLE_DEPRECATED -DGDK_DISABLE_DEPRECATED -DGDK_PIXBUF_DISABLE_DEPRECATED -DGTK_DISABLE_DEPRECATED `pkg-config --cflags glib-2.0 gnome-vfs-module-2.0` -g -O2 -o gdesklets-display-thumbnailer `pkg-config --libs glib-2.0 gnome-vfs-module-2.0` gdesklets-display-thumbnailer.o

gcc -Wall -Wstrict-prototypes -Wmissing-prototypes -DG_DISABLE_DEPRECATED -DGDK_DISABLE_DEPRECATED -DGDK_PIXBUF_DISABLE_DEPRECATED -DGTK_DISABLE_DEPRECATED -D_REENTRANT -DORBIT2=1 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gnome-vfs-2.0 -I/usr/include/gnome-vfs-module-2.0 -I/usr/lib/gnome-vfs-2.0/include -I/usr/include/bonobo-activation-2.0 -I/usr/include/orbit-2.0 -g -O2 -o gdesklets-display-thumbnailer -Wl,--export-dynamic gdesklets-display-thumbnailer.o -pthread /usr/lib/libgnomevfs-2.so /usr/lib/libgconf-2.so /usr/lib/libxml2.so -lz -lssl -lcrypto -lrt /usr/lib/libbonobo-activation.so /usr/lib/libORBitCosNaming-2.so /usr/lib/libORBit-2.so /usr/lib/libpopt.so /usr/lib/libgobject-2.0.so /usr/lib/libgthread-2.0.so -lpthread -lm /usr/lib/libgmodule-2.0.so -ldl /usr/lib/libglib-2.0.so

/usr/lib/libgnomevfs-2.so: undefined reference to `g_str_has_prefix'

collect2: ld returned 1 exit status

make[1]: *** [gdesklets-display-thumbnailer] Error 1

make[1]: Leaving directory `/usr/src/RPM/SOURCES/gDesklets-0.26.2/tools'

make: *** [install-recursive] Error 1

[root@home-desktop gDesklets-0.26.2]#

 

Javi

Link to comment
Share on other sites

To resolve that error, try installing glibc-devel and gtk-devel

 

urpmi glibc-devel && urpmi libgtk+2.0_0-devel

 

Also, I strongly suggest that until you become more familiar with Linux that you stick with urpmi and the current release. Try to steer away from the 'latest and greatest' which is sure to be unstable. But, then again, that's the best way to learn: the hard way (not meant to be insulting or sarcastic). I'm sure there are plenty of 'us' that would help you along the way.

Edited by Steve Scrimpshire
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share


×
×
  • Create New...