These are the debug traces of the application: DM-37x# ./weston-fullscreen -w 800 -h 600 [3469999.819] -> wl_display@1.get_registry(new id wl_registry@2) [3470006.899] -> wl_disp...@1.sync(new id wl_callback@3) [3470013.399] wl_display@1.delete_id(3) [3470014.620] wl_registry@2.global(1, "wl_compositor", 3) [3470019.106] -> wl_regis...@2.bind(1, "wl_compositor", 3, new id [unknown]@4) [3470024.782] wl_registry@2.global(2, "wl_subcompositor", 1) [3470027.895] -> wl_regis...@2.bind(2, "wl_subcompositor", 1, new id [unknown]@5) [3470032.442] wl_registry@2.global(3, "wl_scaler", 2) [3470036.318] wl_registry@2.global(4, "presentation", 1) [3470039.156] wl_registry@2.global(5, "wl_data_device_manager", 2) [3470042.940] -> wl_regis...@2.bind(5, "wl_data_device_manager", 2, new id [unknown]@6) [3470045.870] wl_registry@2.global(6, "wl_shm", 1) [3470046.755] -> wl_regis...@2.bind(6, "wl_shm", 1, new id [unknown]@7) [3470047.915] wl_registry@2.global(7, "wl_output", 2) [3470048.769] -> wl_regis...@2.bind(7, "wl_output", 2, new id [unknown]@8) [3470056.246] wl_registry@2.global(8, "wl_seat", 4) [3470060.122] -> wl_regis...@2.bind(8, "wl_seat", 4, new id [unknown]@9) [3470064.669] -> wl_data_device_manager@6.get_data_device(new id wl_data_device@10, wl_seat@9) [3470067.446] -> wl_compositor@4.create_surface(new id wl_surface@11) [3470069.948] wl_registry@2.global(9, "_wl_fullscreen_shell", 1) [3470074.831] wl_callb...@3.done(1) [3470078.890] -> wl_shm@7.create_pool(new id wl_shm_pool@3, fd 8, 4096) [3470090.792] -> wl_shm_pool@3.resize(8832) [3470096.163] -> wl_shm_pool@3.resize(18624) [3470250.551] -> wl_regis...@2.bind(9, "_wl_fullscreen_shell", 1, new id [unknown]@12) [3470256.075] -> wl_compositor@4.create_surface(new id wl_surface@13) [3470257.448] -> _wl_fullscreen_shell@12.present_surface(wl_surface@13, 0, nil) [3470259.157] -> wl_compositor@4.create_region(new id wl_region@14) [3470260.103] -> wl_reg...@14.add(0, 0, 800, 600) [3470276.644] -> wl_shm@7.create_pool(new id wl_shm_pool@15, fd 10, 1920000) [3470280.947] -> wl_shm_pool@15.create_buffer(new id wl_buffer@16, 0, 800, 600, 3200, 0) [3470285.036] -> wl_surface@13.frame(new id wl_callback@17) Segmentation fault
2015-10-13 15:23 GMT+02:00 Joaquim Duran <jduran...@gmail.com>: > This is the backtrace but not much information is provided: > > Starting program: /usr/var/lib/weston-fullscreen > [Thread debugging using libthread_db enabled] > [New Thread 0x40105000 (LWP 325)] > > Program received signal SIGSEGV, Segmentation fault. > [Switching to Thread 0x40105000 (LWP 325)] > 0x00000008 in ?? () > (gdb) where > #0 0x00000008 in ?? () > #1 0x00000006 in ?? () > #2 0x00000006 in ?? () > Backtrace stopped: previous frame identical to this frame (corrupt stack?) > > Joaquim Duran > > > 2015-10-13 14:58 GMT+02:00 Joaquim Duran <jduran...@gmail.com>: >> Pekka, >> >> Thanks for your information. I've compiled simple clients and I've >> executed fullscreen clients: >> >> DM-37x# ./weston-fullscreen >> Segmentation fault >> >> And finishes with a segmentation fault. I'll rerun with debug >> information to provide more information. >> >> >> 2015-10-13 14:37 GMT+02:00 Pekka Paalanen <ppaala...@gmail.com>: >>> On Tue, 13 Oct 2015 14:26:21 +0200 >>> Joaquim Duran <jduran...@gmail.com> wrote: >>> >>>> Hello, >>>> >>>> We could execute the Weston compositor (using fbdev backend) in a >>>> terminal, we could execute the weston-info client and it prints >>>> information, however when we execute the weston-terminal client, it >>>> couldn't open a window on the compositor. >>>> >>>> We start the Weston compositor in a terminal: >>>> >>>> mkdir -p /var/lib/xdg >>>> chmod 0700 /var/lib/xdg >>>> export XDG_RUNTIME_DIR=/var/lib/xdg >>>> mkdir -p /usr/share/X11/xkb >>>> >>>> weston --tty=1 --backend=fbdev-backend.so --shell=fullscreen-shell.so >>>> Date: 2015-10-13 UTC >>>> [14:16:17.765] weston 1.9.0 >>>> http://wayland.freedesktop.org >>>> Bug reports to: >>>> https://bugs.freedesktop.org/enter_bug.cgi?product=Wayland&component=weston&version=1.9.0 >>>> Build: 1.9.0 configure.ac: bump to version 1.9.0 for >>>> the official release (2015-09-21 18:11:26 -0700) >>>> [14:16:17.772] OS: Linux, 3.0.101-BSP-dm37x-2.4-4, #33 Tue Oct 13 >>>> 12:33:51 CEST 2015, armv7l >>>> [14:16:17.777] Starting with no config file. >>>> [14:16:17.781] Loading module '/usr/lib/weston/fbdev-backend.so' >>>> [14:16:17.810] Output repaint window is 7 ms maximum. >>>> [14:16:17.814] initializing fbdev backend >>>> [14:16:17.820] Creating fbdev output. >>>> [14:16:17.823] Opening fbdev frame buffer. >>>> [14:16:17.826] Calculating pixman format from: >>>> - type: 0 (aux: 0) >>>> - visual: 2 >>>> - bpp: 32 (grayscale: 0) >>>> - red: offset: 16, length: 8, MSB: 0 >>>> - green: offset: 8, length: 8, MSB: 0 >>>> - blue: offset: 0, length: 8, MSB: 0 >>>> - transp: offset: 0, length: 0, MSB: 0 >>>> [14:16:17.829] Mapping fbdev frame buffer. >>>> [14:16:17.834] fbdev output 800×600 px >>>> guessing 60 Hz and 96 dpi >>>> [14:16:17.863] input device 'NOVATEK USB Keyboard', /dev/input/event2 >>>> is tagged by udev as: Keyboard >>>> [14:16:17.866] input device 'NOVATEK USB Keyboard', /dev/input/event2 >>>> is a keyboard >>>> [14:16:17.881] input device 'NOVATEK USB Keyboard', /dev/input/event3 >>>> is tagged by udev as: Keyboard >>>> [14:16:17.884] input device 'NOVATEK USB Keyboard', /dev/input/event3 >>>> is a keyboard >>>> [14:16:17.898] input device 'twl4030_pwrbutton', /dev/input/event1 is >>>> tagged by udev as: Keyboard >>>> [14:16:17.900] input device 'twl4030_pwrbutton', /dev/input/event1 is a >>>> keyboard >>>> [14:16:17.914] input device 'ft5x06-i2c', /dev/input/event0 is tagged >>>> by udev as: Keyboard Touchscreen >>>> [14:16:17.918] input device 'ft5x06-i2c', /dev/input/event0 is a keyboard >>>> [14:16:17.921] input device 'ft5x06-i2c', /dev/input/event0 is a touch >>>> device >>>> [14:16:17.931] Compositor capabilities: >>>> arbitrary surface rotation: yes >>>> screen capture uses y-flip: yes >>>> presentation clock: CLOCK_MONOTONIC_RAW, id 4 >>>> [14:16:17.940] Loading module '/usr/lib/weston/fullscreen-shell.so' >>> >>> Hi, >>> >>> you are using the fullscreen-shell.so, so this is not a bug. >>> weston-terminal (clients/window.c to be more specific) does not >>> implement support for the fullscreen-shell. >>> >>> You have to either use a program specifically written to use the >>> fullscreen-shell protocol, or use desktop-shell.so instead. >>> >>> Grep for _wl_fullscreen to see which Weston demo programs support >>> running on fullscreen-shell. >>> >>> weston-info is different, because it never even tries to create a >>> window. The shell protocol is needed to properly create and show a >>> window. >>> >>> (Your other bug reports do look valid at first hand.) >>> >>> >>> Thanks, >>> pq _______________________________________________ wayland-devel mailing list wayland-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/wayland-devel