On Tue, Oct 13, 2015 at 03:23:12PM +0200, Joaquim Duran wrote: > 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?)
Try 'bt full'? > 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 _______________________________________________ wayland-devel mailing list wayland-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/wayland-devel
