When getting openbox to start all the computer does is hang, i did a strace an it came up with: failed to open display on 0: exit group (1) I have fluxbox running so it seems like the problem is the package itself Reproducible: Always Steps to Reproduce: 1.open openbox... 2. 3. Actual Results: I got a nice background that i gave myself, nothing more. I left it for 20 mins just to check and nothing Expected Results: given me Openbox wm System uname: 2.6.8-gentoo-r7 i686 AMD Athlon(tm) XP 2400+ Gentoo Base System version 1.4.16 Autoconf: sys-devel/autoconf-2.59-r5 Automake: sys-devel/automake-1.8.5-r1 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O2 -march=athlon-xp -fomit-frame-pointer -pipe -Wno-strict-aliasing" CHOST="i686-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.3 /env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /us r/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ / usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/sha re/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=athlon-xp -fomit-frame-pointer -pipe -Wno-strict-aliasing" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache sandbox" GENTOO_MIRRORS="http://gentoo.blueyonder.co.uk" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.uk.gentoo.org/gentoo-portage" USE="3dnow X alsa apm arts avi berkdb bitmap-fonts cdr crypt cups debug dvd enco de esd f77 foomaticdb gdbm gif gpm gtk2 imlib java jpeg kde libg++ libwww mad mi kmod mmx motif mpeg msn mysql ncurses nls nptl oggvorbis opengl oss pam pdflib p erl png python qt quicktime readline sdl slang spell ssl svga tcpd tetex truetyp e x86 xml2 xmms xprint xv yahoo zlib"
Was there any other strace output? Does this still occur with a newer version of openbox (if applicable, you didn't specify your openbox version)?
For sake of reference, I talked to the bug reporter and he says that it no longer occurs.