fluxbox crashed with SIGABRT in XQueryExtension()

[Marcos K]

 this happened immediately at startup

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: fluxbox 1.3.1~dfsg1-2
ProcVersionSignature: Ubuntu 3.0.0-16.29-generic 3.0.20
Uname: Linux 3.0.0-16-generic i686
ApportVersion: 1.23-0ubuntu4
Architecture: i386
Date: Wed Feb 22 15:25:41 2012
ExecutablePath: /usr/bin/fluxbox
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
ProcCmdline: fluxbox -display :99
ProcCwd: /home/master/dev
Signal: 6
SourcePackage: fluxbox
StacktraceTop:
 XQueryExtension () from /usr/lib/i386-linux-gnu/libX11.so.6
 XInitExtension () from /usr/lib/i386-linux-gnu/libX11.so.6
 XextAddDisplay () from /usr/lib/i386-linux-gnu/libXext.so.6
 ?? () from /usr/lib/i386-linux-gnu/libXrandr.so.2
 XRRUpdateConfiguration () from /usr/lib/i386-linux-gnu/libXrandr.so.2
Title: fluxbox crashed with SIGABRT in XQueryExtension()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 XQueryExtension (dpy=0x0, name=0x4d2064 "RANDR", major_opcode=0xbfa04254, first_event=0xbfa04258, first_error=0xbfa0425c) at ../../src/QuExt.c:43
 XInitExtension (dpy=0x0, name=0x4d2064 "RANDR") at ../../src/InitExt.c:47
 XextAddDisplay (extinfo=0x4d20b4, dpy=0x0, ext_name=0x4d2064 "RANDR", hooks=0x4d2080, nevents=2, data=0x0) at ../../src/extutil.c:110
 XRRFindDisplay (dpy=0x0) at ../../src/Xrandr.c:232
 XRRFindDisplay (dpy=0x0) at ../../src/Xrandr.c:224

[Paul Tagliamonte (paultag)]

How exactly are you invoking this? It looks like you're in an interesting CWD and invoking it with an interesting argument set (fluxbox -display :99)

Marking incomplete (for both Ubuntu and Fluxbox, moving to the fluxbox project as well)

[Marcos K (g-ubuntu-com-y)]

For headless testing I sometimes use Xvfb on DISPLAY :99. Then I may or may not launch a lightweight Windows Manager like fluxbox or awesome, x11vnc, xload, and noninteractive web browser for automation.

However sometimes to view or interact to debug my apps, I start Xephyr on :99 instead of Xvfb (after starting Xwindows on :0 the usual way with whatever session, gnome/unity/etc.)

This may have affected fluxbox since Xephyr unlike Xvfb cannot survive without its parent Xserver, or if the Xserver at :0 is having driver issues.

[Marcos K (g-ubuntu-com-y)]

The way I invoke it indirectly happens inside a shell script that itself is scheduled via cron: (or responds to another external event noninteractively, like email triggered)

#!/bin/bash
# batchjobhandler.sh
Xvfb ${DISPLAY:=:99} -ac -shmem -screen 0 1024x768x8 &
xpid=$! ; sleep 3
at now <<< "fluxbox -display $DISPLAY &> orderlog/fluxbox.$(hostname).log" # & disown # lightweight WM
#xload -display :99 -update 5 -geometry 1100x50 &

Sometimes there may already be fluxbox or another WM on that $DISPLAY, in which I expect the above fluxbox to go ahead and fail--though I don't think that's why Apport launched this crash reporter
.

[Launchpad Janitor (janitor)]

[Expired for fluxbox (Ubuntu) because there has been no activity for 60 days.]