weston-1.4.0: rpi-backend is broken
s.jegen at gmail.com
Fri Jan 31 11:07:19 PST 2014
On Sun, Jan 26, 2014 at 09:15:50PM +0100, Yann E. MORIN wrote:
> Here's the complete log of 'weston >weston.log 2>&1' :
> Date: 2014-01-26 UTC
> [20:03:09.606] weston 1.4.0
> Bug reports to:
> [20:03:09.607] OS: Linux, 3.12.7, #1 PREEMPT Sat Jan 25 14:09:48 CET
> 2014, armv6l
> [20:03:09.608] Starting with no config file.
> [20:03:09.611] Loading module '/usr/lib/weston/rpi-backend.so'
> [20:03:09.648] initializing Raspberry Pi backend
> [20:03:09.652] Dispmanx planes are double buffered.
> [20:03:09.656] launching '/usr/libexec/weston-keyboard'
> [20:03:09.909] input device HID 046a:0023, /dev/input/event0 is a
> Failed to process Wayland connection: Connection reset by peer
> failed to create display: Connection reset by peer
> Segmentation fault
I am getting a very similar error output on my RP:
Date: 2014-01-31 UTC
[18:35:41.645] weston 1.4.0
Bug reports to: https://bugs.freedesktop.org/enter_bug.cgi?product=Wayland&component=weston&version=1.4.0
Build: 1.4.0-3-g1afb238-dirty input: Unlink saved kbd focus listener when releasing seat (2014-01-27 21:14:25 -0800)
[18:35:41.647] OS: Linux, 3.10.25+, #622 PREEMPT Fri Jan 3 18:41:00 GMT 2014, armv6l
[18:35:41.652] Using config file '/home/pi/local/etc/weston.ini'
[18:35:41.653] Loading module '/home/pi/local/lib/weston/rpi-backend.so'
[18:35:41.680] initializing Raspberry Pi backend
[18:35:41.721] Dispmanx planes are double buffered.
[18:35:41.727] launching '/home/pi/local/libexec/weston-keyboard'
[18:35:41.730] input device Logitech USB-PS/2 Optical Mouse, /dev/input/event0 is a pointer caps = relative-motion button
Failed to process Wayland connection: Broken pipe
failed to create display: Broken pipe
I am using Raspbian as user 'pi' starting weston using the (setuid-root)
Weston is not starting at all though I am quite positive that the screen
flickers briefly before I am being dropped back to the shell.
Do you think it would make sense for me to debug it? If so, how do I get
a useful backtrace using (c)gdb when weston-launch starts a different
binary? I can try to bisect the problem if you think it would be helpful.
More information about the wayland-devel