Hi Roman and thanks for taking the time to debug this, It looks like your tz-launcher hangs during the touch/click event. This should not happen with every icon. But if this happens always with the same icon, it *may* be related to a dump bug I just found and fixed : https://review.tizen.org/gerrit/#/c/21236/
As soon as this is accepted and merged, you will be able to install the fixed tz-launcher with zypper. 2014-05-15 18:47 GMT+02:00 Roman Kubiak <[email protected]>: > Here is the stack dump of the tz-launcher app, it starts but clicking on > any icon in it, it segfaults: > root@10:~# gdb --args tz-launcher > /usr/share/applications/weston-terminal.desktop > GNU gdb (GDB) 7.5.1 > Copyright (C) 2012 Free Software Foundation, Inc. > License GPLv3+: GNU GPL version 3 or later > <http://gnu.org/licenses/gpl.html> <http://gnu.org/licenses/gpl.html> > This is free software: you are free to change and redistribute it. > There is NO WARRANTY, to the extent permitted by law. Type "show copying" > and "show warranty" for details. > This GDB was configured as "i686-tizen-linux-gnu". > For bug reporting instructions, please see: > <http://www.gnu.org/software/gdb/bugs/><http://www.gnu.org/software/gdb/bugs/> > ... > Reading symbols from /usr/bin/tz-launcher...(no debugging symbols > found)...done. > (gdb) r > Starting program: /usr/bin/tz-launcher > /usr/share/applications/weston-terminal.desktop > warning: Could not load shared library symbols for linux-gate.so.1. > Do you need "set solib-search-path" or "set sysroot"? > warning: File "/lib/libthread_db.so.1" auto-loading has been declined by > your `auto-load safe-path' set to "$debugdir:$datadir/auto-load". > To enable execution of this file add > add-auto-load-safe-path /lib/libthread_db.so.1 > line to your configuration file "/root/.gdbinit". > To completely disable this security protection add > set auto-load safe-path / > line to your configuration file "/root/.gdbinit". > For more information about this security protection see the > "Auto-loading safe path" section in the GDB manual. E.g., run from the > shell: > info "(gdb)Auto-loading safe path" > warning: Unable to find libthread_db matching inferior's thread library, > thread debugging will not be available. > > Program received signal SIGSEGV, Segmentation fault. > 0x0804f87c in launcher_touch_up_handler () > (gdb) bt > #0 0x0804f87c in launcher_touch_up_handler () > #1 0x08053c7c in touch_handle_up () > #2 0x42544666 in ffi_call_SYSV () from /lib/libffi.so.6 > #3 0x425443eb in ffi_call () from /lib/libffi.so.6 > #4 0x429383a5 in wl_closure_invoke () from /lib/libwayland-client.so.0 > #5 0x42935973 in dispatch_queue () from /lib/libwayland-client.so.0 > #6 0x429366d0 in wl_display_dispatch_queue () from > /lib/libwayland-client.so.0 > #7 0x429367b2 in wl_display_dispatch () from /lib/libwayland-client.so.0 > #8 0x0805484b in handle_display_data () > #9 0x08058ddc in display_run () > #10 0x0805019a in tz_launcher_wl_run () > #11 0x0804ec95 in main () > (gdb) > > > On 05/15/2014 05:24 PM, Manuel Bachmann wrote: > > Hi Roman, > > I provided most of the code for the "tz-launcher" program you are > referring to. > > I just started a Weston with the FBDev backend, verified that GL rendering > was inactive, and "tz-launcher" worked as expected. It was on a real > device, though ; VMWare may be different. > > So in order to help you, my questions will be : > > 1) Do you see the background ? (gulf sea with some islands) > > 2) Are you able to run tz-launcher in a reduced mode with this command > (switch to a VT by doing "Ctrl-Alt-F2" e.g.) : > $ tz-launcher /usr/share/applications/weston-terminal.desktop > > 3) If it segfaults, could you post a backtrace of the following : > $ zypper install gdb > $ gdb tz-launcher > $ run /usr/share/applications/weston-terminal.desktop > (it crashes) > $ bt > > Regards, > > > 2014-05-15 16:51 GMT+02:00 Stanislav Vorobiov <[email protected]>: > >> Hi, please see below >> >> On 05/15/2014 06:42 PM, Roman Kubiak wrote: >> > Helo again. >> > >> > I ditched vmware due to licensing issues for now, but thank you for the >> help i know how to fix it and i understand how to get things running. >> > >> > I jumped to our own emulator based on qemu (there is a very fresh piece >> of code on tizen.org). I got it to build and run the Common image, >> weston shows up but starting anything is causing a segfault in the >> tz-launcher process. >> > Though i was not able to start weston with the DRM backend, it's >> running on fbdev. The VIGS/Yagl implementation in the kernel/qemu might not >> be wayland ready, >> Actually, VIGS/YaGL already runs wayland, you can refer to Tizen IVI >> emulator, it uses tizen.org QEMU and runs Tizen IVI image. I'm not sure >> about Common, I never >> actually tried it. >> >> > but the FBDEV stuff seems to work fine. I don't know what tz-launcher >> is doing that it's doing a >> > segfault, i was able to start a weston terminal and that seems to work. >> > >> > The small fix i had to do was adding the display user to the video >> group. Also the kernel for the emulator needs to be rebuilt (the default >> config in the emulator-kernel repo assumes that the root disk is /dev/vda >> and has that hard-coded in a minimal >> > initramfs that builds with the kernel) >> > >> > Could someone tell me if tz-launcher might need DRM and that's why it's >> crashing or is that something else i'd need to check ? >> > >> > best regards >> > >> > On 05/14/2014 07:15 PM, VanCutsem, Geoffroy wrote: >> >> >> >> Quick update: >> >> >> >> >> >> >> >> I got the Tizen Common Weston desktop up and running under VMware >> using this image: >> http://download.tizen.org/releases/daily/tizen/common/common-wayland-x86_64/tizen_20140513.6/ >> >> >> >> >> >> >> >> The quickest way is to modify the /boot/extlinux/extlinux.conf file >> and add ‘security=none’ to the kernel command-line (workaround for >> https://bugs.tizen.org/jira/browse/TIVI-2964), a more permanent >> workaround (but not a complete fix) would be to modify >> >> the kernel config to have vmwgfx built-in (instead of a module). I >> have also verified that such modifications solves the issue (and you can >> keep security turned on in that case which you really really want). >> >> >> >> >> >> >> >> I can push a patch to have ‘vmwgfx’ built-in to Tizen Common. In >> general, it may be good to re-use some of the specific kernel configs that >> are described here also in the Tizen Common kernel: >> >> https://wiki.tizen.org/wiki/IVI/artem-kernel#Kernel_configuration(look >> >> for those that are documented as useful for VMware). >> >> >> >> >> >> >> >> Geoffroy >> >> >> >> >> >> >> >> *From:*Dev [mailto:[email protected]] *On Behalf Of >> *VanCutsem, Geoffroy >> >> *Sent:* Wednesday, May 14, 2014 5:56 PM >> >> *To:* Roman Kubiak; [email protected] >> >> *Subject:* Re: [Dev] Common/Generic profile images usability >> >> >> >> >> >> >> >> Hi Roman, >> >> >> >> >> >> >> >> If you’re interested, I used to keep some ‘recipes’ on how to run >> Tizen IVI 2.0 (based on X) under VMware, it’s described here: >> https://wiki.tizen.org/wiki/IVI/IVI_2.0_VMware. Back then, I had to >> provide the xorg-x11-drv-vmware driver (as you have >> >> pointed out below) and I also had to modify some of the build options >> used for mesa and libdrm. Feel free to take a look there if you want to get >> that working but as pointed out by Dominique, we are not focused on X in >> Tizen 3.0 so I’m not sure where >> >> this would lead you to. >> >> >> >> >> >> >> >> A more interesting path would be to get the Wayland image running on >> VMware. I have quickly looked at the kernel used in Common and the vmwgfx >> driver is built as a module which means we could be hitting >> https://bugs.tizen.org/jira/browse/TIVI-2964 >> >> <https://bugs.tizen.org/jira/browse/TIVI-2964>. I’ll see if I can >> run a quick test on my side to validate this. If that’s the problem, you >> could try to turn security off (add ‘security=none’ at the kernel >> command-line) or rebuild the kernel with the >> >> ‘vmwgfx’ driver built-in. >> >> >> >> >> >> >> >> Geoffroy >> >> >> >> >> >> >> >> *From:*Dev [mailto:[email protected]] *On Behalf Of *Roman >> Kubiak >> >> *Sent:* Wednesday, May 14, 2014 4:07 PM >> >> *To:* [email protected] <mailto:[email protected]> >> >> *Subject:* Re: [Dev] Common/Generic profile images usability >> >> >> >> >> >> >> >> Just to update the Xorg image won't work either, there is only one >> driver included in the image for Xorg and that's the intel_drv.so (bit >> selfish i think) no fbdev or vmware drivers are present so Xorg will never >> start. >> >> Also i can't any service in systemctl that could be some sort of a >> windows manager. >> >> >> >> best regards >> >> Roman Kubiak >> >> >> >> On 05/14/2014 03:59 PM, Dominig ar Foll (Intel OTC) wrote: >> >> >> >> >> >> Le 14/05/2014 15:38, Roman Kubiak a écrit : >> >> >> >> I got the images running before (the IVI profile) on VMware, >> so VMware itself is not an issue. >> >> My question was really, SHOULD I see something in the image, >> is there a UI in the common profile at all or is this a bare bones sort of >> OS image that contains no UI experience at all. >> >> >> >> When booting Tizen Common you should have a test UX (basic >> Weston) with several user pre-logged on the system. >> >> The background show the sea and several islands. >> >> >> >> >> >> >> >> >> >> My question about Xorg is still not answered, what is the UI for >> Xorg i should expec t to find in the common image (is there some sort of >> default WM that should launch?) >> >> >> >> We currently do not build a Tizen Common for X but only Wayland 32 >> and 64 nits for IA and 32 bits for ARM (work in progress) >> >> If someone is interested to take the responsibility of building >> and maintain X Common images, thanks to speak up. >> >> >> >> Regards >> >> >> >> Dominig >> >> >> >> >> >> >> >> >> >> _______________________________________________ >> >> >> >> Dev mailing list >> >> >> >> [email protected] <mailto:[email protected]> >> >> >> >> https://lists.tizen.org/listinfo/dev >> >> >> >> >> >> >> >> -- >> >> -------------- >> >> Roman Kubiak >> >> -------------- >> >> >> >> Intel Corporation NV/SA >> >> Kings Square, Veldkant 31 >> >> 2550 Kontich >> >> RPM (Bruxelles) 0415.497.718. >> >> Citibank, Brussels, account 570/1031255/09 >> >> >> >> This e-mail and any attachments may contain confidential material for >> the sole use of the intended recipient(s). Any review or distribution by >> others is strictly prohibited. If you are not the intended recipient, >> please contact the sender and delete all >> >> copies. >> >> >> >> Intel Corporation NV/SA >> >> Kings Square, Veldkant 31 >> >> 2550 Kontich >> >> RPM (Bruxelles) 0415.497.718. >> >> Citibank, Brussels, account 570/1031255/09 >> >> >> >> This e-mail and any attachments may contain confidential material for >> the sole use of the intended recipient(s). Any review or distribution by >> others is strictly prohibited. If you are not the intended recipient, >> please contact the sender and delete all >> >> copies. >> >> >> > >> > -- >> > -------------- >> > Roman Kubiak >> > -------------- >> > >> > >> > >> > _______________________________________________ >> > Dev mailing list >> > [email protected] >> > https://lists.tizen.org/listinfo/dev >> > >> >> _______________________________________________ >> Dev mailing list >> [email protected] >> https://lists.tizen.org/listinfo/dev >> > > > > -- > Regards, > > > > *Manuel BACHMANN Tizen Project VANNES-FR* > > > -- > -------------- > Roman Kubiak > -------------- > > > _______________________________________________ > Dev mailing list > [email protected] > https://lists.tizen.org/listinfo/dev > > -- Regards, *Manuel BACHMANN Tizen Project VANNES-FR*
_______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
