Openmoko-Today app is in tiny window of about 200px by 100px on latest images

[jon@…]

I'm running the current images Snapshot 20070916 rootfs with 20070916 kernel
fic-gta01 2.6.22.5-moko11+svnr2937-r0 and u-boot from
​http://buildhost.openmoko.org/snapshots/2007.08/images/u-boot-gta01bv4-1.2.0+git8993e54b6f397973794f3d6f47d3b3c0c98dd4f6+svn20070819-r0.bin

(known to work) ​http://buildhost.openmoko.org/snapshots/2007.08/images/

And, I have removed "console=ttySAC0,115200" from bootargs_base

After booting, i get the screenshot at the URL attached to this with what looks
like the openmoko-today app thinking the window is small.

If I change to the dialer, then its gets a bit bigger, and also the screenshot
window appears centered in the X window...so, must not be an X issue. See the
dialer:

​http://scap.linuxtogo.org/files/82cfb5c0b8893d4c937bcbb0609149ed.png

I'm trying to track this down...I'm attaching the log when I run
/etc/init.d/xserver-nodm to reboot X11

[jon@…]

This is the log of debug messages upon running xserver-nodm

[thomas@…]

I would guess that matchbox-window-manager has not started, for whatever reason.
Please try ps | grep matchbox to determine if matchbox-window-manager is
running after X starts.

[jon@…]

Ok, I did this and you are right, matchbox-window-manager is not running, so I
tried to start and got this:

root@fic-gta01:~$
(process:1188): GConf-WARNING : Client failed to connect to the D-BUS daemon:
Failed to execute dbus-launch to autolaunch D-Bus session
GConf Error: No D-BUS daemon running

xpm file invalid* glibc detected * matchbox-window-manager: double free or
corruption (top): 0x0004b3c0 *

[1] + Aborted matchbox-window-manager -display :0

So, its either the dbus connection problem or the glibc corruption...is there a fix?

Here is a backtrace, but appears that matchbox-window-manager is not in debug
mode. Is there a way to get that and/or run in debug mode.

(gdb) run -display :0
Starting program: /usr/bin/matchbox-window-manager -display :0
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)

(process:1514): GConf-WARNING : Client failed to connect to the D-BUS daemon:
Failed to execute dbus-launch to autolaunch D-Bus session
GConf Error: No D-BUS daemon running

xpm file invalid* glibc detected * /usr/bin/matchbox-window-manager: double
free or corruption (top): 0x0004b3c0 *

Program received signal SIGABRT, Aborted.
0x40331d6c in raise () from /lib/libc.so.6
(gdb) bt
#0 0x40331d6c in raise () from /lib/libc.so.6
#1 0x40333194 in abort () from /lib/libc.so.6
Backtrace stopped: frame did not save the PC

[thomas@…]

The d-bus environment variables need to be set in order for a program to connect
to d-bus. The easiest way to do this is to use dbus-launch <application>.

You need to install debug packages to enable debug information. These packages
are the same name as their normal package counterpart, but with a -dbg suffix.
e.g. you may want to install matchbox-wm-dbg.

[jon@…]

Ok, launching with dbus-launch /etc/init.d/xserver-nodm start did not fix the
problem...looking deeper...any other suggestions?

[thomas@…]

d-bus is already set up through the X server init script. I suggest you try:

DISPLAY=:0 dbus-launch gdb matchbox-window-manager

[jon@…]

This seems to work for me now...