try to attach gdb on X then:
Did that already.
#0 0xb5b35521 in xcb_cursor_images_load_cursor (wm=0x83b7030, images=0x0) at
window-manager.c:182
#1 0xb5b355d6 in xcb_cursor_library_load_cursor (wm=0x83b7030, file=0xb5b3ea94
"top_side") at window-manager.c:207
#2 0xb5b371ab in weston_wm_c
On 09/04/2012 11:04 PM, Knut Petersen wrote:
I don't think the hardware is the problem.
You're compiling Xwayland without debugging symbols so it's a bit
tricky to tell what's going on, but my guess is that you're facing the
same issues other guys had here on the ml; try to check if you're
usi
I don't think the hardware is the problem.
You're compiling Xwayland without debugging symbols so it's a bit tricky to
tell what's going on, but my guess is that you're facing the same issues other
guys had here on the ml; try to check if you're using the correct version of
libxtrans:
Sorr
On 09/04/2012 06:56 PM, Knut Petersen wrote:
System: Pentium M Dothan, i915GM, linux 3.6-rc*, xorg and wayland/weston
fresh git.
Could anybody please confirm that xwayland does (or does not) work on
that hardware?
I don´t have problems to build the software, but any starting x client
immediately
System: Pentium M Dothan, i915GM, linux 3.6-rc*, xorg and wayland/weston fresh
git.
Could anybody please confirm that xwayland does (or does not) work on that
hardware?
I don´t have problems to build the software, but any starting x client
immediately kills xwayland:
[17:52:09.475] weston 0.9
