XWayland on the RaspberryPI

Pekka Paalanen ppaalanen at gmail.com
Tue Jan 14 00:25:01 PST 2014


On Tue, 14 Jan 2014 09:07:31 +0100
albert <skarbat at gmail.com> wrote:

> Greetings all,
> 
> I am trying to make XWayland run on a Raspberry PI, so I am building
> wayland/weston and the xserver xwayland branch from here:
> 
>   git://anongit.freedesktop.org/xorg/xserver
> 
> As well as the wlshm (now moved as wayland) driver: git://
> anongit.freedesktop.org/xorg/driver/xf86-video-wayland
> 
> When attempting to start a x11 app, the xserver effectively is
> started, the wayland x driver loads successfully but when attempting
> to "subload" the framebuffer driver, it segfaults. This fb driver has
> been built as part of this same xserver.
> 
> [  1056.806] (II) Loading sub module "fb"
> [  1056.806] (II) LoadModule: "fb"
> [  1056.808] (II) Loading /root/weston-bin/lib/xorg/modules/libfb.so
> [  1056.811] (II) Module fb: vendor="X.Org Foundation"
> [  1056.811]    compiled for 1.15.0, module version = 1.0.0
> [  1056.812]    ABI class: X.Org ANSI C Emulation, version 0.4
> [  1056.812] (==) Depth 24 pixmap format is 32 bpp
> [  1056.813] (==) wayland(0): Backing store disabled
> [  1056.813] (==) wayland(0): Silken mouse enabled
> [  1056.815] (EE)
> [  1056.815] (EE) Backtrace:
> [  1056.815] (EE)
> [  1056.816] (EE) Segmentation fault at address 0xe7933016
> [  1056.816] (EE)
> Fatal server error:
> [  1056.816] (EE) Caught signal 11 (Segmentation fault). Server
> aborting
> 
> The contents of the xorg.conf file looks like so:
> 
> Section "Device"
>         Identifier "Device"
>         Driver "wayland"
> EndSection
> 
> Any hints on what I might be missing would be greatly appreciated, or
> even hints on how to debug this fault, as there is no timeframe to
> gdb attach against the xserver before it dies.

Hi Albert,

that does not ring any bells for me. Could you attach the output of
weston-launch (both stdout and stderr together), and the whole X log.
Also check the free space in your XDG_RUNTIME_DIR, though I'd assume
running out of space would cause SIGBUS rather than SEGV.

I don't recall off-hand how to run the xwayland xserver under gdb,
maybe someone else does? Might involve a bit of hacking.


Thanks,
pq


More information about the wayland-devel mailing list