On Wed, 15 Jul 2015 09:22:44 -0700 "McGee, Art" <[email protected]> said:
> All, > > I have some new testing information. I've been using the VTC1010 for > testing. My primary choice for display output is HDMI. I have noticed > that crosswalk isn't developed for multi-screen yet and I wonder if this > could be part of the problem. I have been able to get the Landscape to > work on VGA and this can help us move forward but our target is HDMI. I > have also been able to get Landscape to work on HDMI but only under the > right conditions. When the VGA is connected the apps will lauch on the VGA > screen from the start. Once the VGA is disconnected apps will fail with > the same error message. After reconnecting the VGA screen the apps will > launch on the HDMI port. It appears the VGA must remain connected. If you > boot the box without VGA and just HDMI the apps won't start on boot. You > cannot launch the apps by hand. You then connect the VGA display and the > apps will launch on the HDMI display. I have found if you disconnect the > VGA display the app will shutdown. This is some kind of hard depenancy on > the VGA display for the VTC1010. I will post this to the JIRA but first > wanted to see what I get from the mailing list. ummm wait a sec... how does this have anything to do with crosswalk? crosswalk is - at least for you on ivi, a wayland client app. it doesn't dneed to know or care about hdmi vs vga vs dp vs cga ... all it does is create a surface. it can query what screens exist but last i knew in wayland, there is no protocol extension to specifically say "i must be on screen x/y/z" - compositor decides where you go. compositor can also even handle rotation for clients as well so portrait/landscape can be hidden from the client. so perhaps you want to bark up a different tree? not crosswalk, but your compositor (weston i think is what you are using). also if you want the wayland client to hint at what output it wants, then you are in the land of extending protocol (and thus having to generate new wayland client libs and depend on them). be careful here in simply allowing clients to specify their screen. you really want to figure this out without the client voluntarily requesting things - if your multiple screens belong to different users/people. if it's the same "user" looking at different screens (eg multiple screens on the dash right in front of them) then client request hints should be semantic, not explicit - eg "my purpose is to display driving statistics" vs "my purpose is for entertainment" as opposed to hdmi vs vga or screen 1 vs screen 2 etc. :) > Thanks > > > *Art McGee* > Infotainment Engineer > > > > Jaguar Land Rover North America, LLC > 1419 NW 14th Ave, Portland, Oregon, 97209 > Jaguar.com <http://jaguar.com> | LandRover.com <http://landrover.com> > > > On 17 June 2015 at 12:10, McGee, Art <[email protected]> wrote: > > > Ya, This is the errors I get. > > > > Jun 17 11:13:49 ivi_box dbus-daemon[414]: Successfully activated service > > 'org.crosswalkproject.Runtime1' > > Jun 17 11:13:49 ivi_box systemd[389]: Started Crosswalk. > > Jun 17 11:13:49 ivi_box xwalk[1045]: > > [0617/111349:INFO:desktop_factory_wayland.cc(17)] Ozone: > > DesktopFactoryWayland > > Jun 17 11:13:49 ivi_box amd[156]: > > [/home/abuild/rpmbuild/BUILD/vconf-buxton-0.3/src/vconf-buxton.c:767] Error > > -1 while getting buxton key db/setting/devoption/bgprocess > > Jun 17 11:13:49 ivi_box systemd[389]: Started Tizen user middleware > > services. > > Jun 17 11:13:49 ivi_box systemd[389]: Reached target Tizen user middleware > > target. > > Jun 17 11:14:14 ivi_box sh[861]: Service 'org.crosswalkproject.Runtime1' > > does could not be reached: Timeout was reached > > > > As you can see from the log the dbus service starts but it times out when > > it goes to run the application. Over the many times I tested this > > process. I find that a rendering process is started in portrate mode that > > doesn't get started in landscape mode. So I'm trying to find the code that > > launches the rendering process to catch the failure. I also would like the > > code that is ran for a rendering process. Once I can find where the accual > > code is I can get a better idea of the failure. So fare capturing code > > changes from common hasn't help the process. I have verified the dbus > > service is active. See below > > > > app@ivi_box:~$ dbus-send --session --dest=org.freedesktop.DBus > > --type=method_call --print-reply /org/freedesktop/DBus > > org.freedesktop.DBus.ListNames > > method return sender=org.freedesktop.DBus -> dest=:1.17 reply_serial=2 > > array [ > > string "org.freedesktop.DBus" > > string ":1.7" > > string "org.genivi.pulse" > > string ":1.8" > > string "org.gnome.Rygel1" > > string "org.genivi.mediamanager.Indexer" > > string ":1.9" > > string "org.tizen.phone" > > string "org.freedesktop.systemd1" > > string ":1.10" > > string "org.lightmediascanner" > > string ":1.11" > > string "org.enlightenment.Efreet" > > string ":1.12" > > string ":1.13" > > string ":1.0" > > string "org.pulseaudio.Server" > > string "org.PulseAudio1" > > string ":1.1" > > string ":1.15" > > string "org.genivi.mediamanager.Browser" > > string ":1.2" > > string ":1.16" > > string "com.intel.dleyna-renderer" > > string ":1.3" > > string "com.intel.dleyna-server" > > string ":1.17" > > string "org.crosswalkproject.Runtime1" > > string ":1.4" > > string "org.genivi.mediamanager.Player" > > string ":1.5" > > string "org.freedesktop.IBus" > > string ":1.6" > > ] > > > > There are not xwalk process until an app is launched. > > These are the xwalk process launched when an app is launched in landscape. > > app@ivi_box:~$ ps -fA | grep xwalk > > app 1089 861 0 11:59 ? 00:00:00 > > /home/app/apps_rw/xwalk-service/applications/U4VCgZDnmt.Vonsor/bin/U4VCgZDnmt.Vonsor > > `zaybxcwdveuftgsh` __AUL_DEBUG__ > > IAAAAAEEAAAOAAAAX19BVUxfREVCVUdfXwACAAAAMQA= __AUL_STARTTIME__ > > NAAAAAEEAAASAAAAX19BVUxfU1RBUlRUSU1FX18AEgAAADE0MzQ1Njc1NjQvNjQzNTU4AA== > > __AUL_CALLER_PID__ KAAAAAEEAAATAAAAX19BVUxfQ0FMTEVSX1BJRF9fAAUAAAAxMDg4AA== > > __AUL_CALLER_UID__ KAAAAAEEAAATAAAAX19BVUxfQ0FMTEVSX1VJRF9fAAUAAAA1MDAwAA== > > app 1091 406 38 11:59 ? 00:00:01 /usr/lib/xwalk/xwalk > > --external-extensions-path=/usr/lib/tizen-extensions-crosswalk > > app 1095 1091 4 11:59 ? 00:00:00 /usr/lib/xwalk/xwalk > > --type=zygote > > app 1118 1091 4 11:59 ? 00:00:00 /usr/lib/xwalk/xwalk > > --type=gpu-process --channel=1091.0.302410629 --gpu-no-context-lost > > --use-gl=egl --supports-dual-gpus=false > > --gpu-driver-bug-workarounds=1,12,38 --gpu-vendor-id=0x8086 > > --gpu-device-id=0x0f31 --gpu-driver-vendor --gpu-driver-version > > > > These are the xwalk process launched after an app fails in landscape. > > app@ivi_box:~$ ps -fA | grep xwalk > > app 1091 406 46 11:59 ? 00:00:14 /usr/lib/xwalk/xwalk > > --external-extensions-path=/usr/lib/tizen-extensions-crosswalk > > app 1095 1091 0 11:59 ? 00:00:00 /usr/lib/xwalk/xwalk > > --type=zygote > > app 1118 1091 0 11:59 ? 00:00:00 /usr/lib/xwalk/xwalk > > --type=gpu-process --channel=1091.0.302410629 --gpu-no-context-lost > > --use-gl=egl --supports-dual-gpus=false > > --gpu-driver-bug-workarounds=1,12,38 --gpu-vendor-id=0x8086 > > --gpu-device-id=0x0f31 --gpu-driver-vendor --gpu-driver-version > > > > These are the xwalk process launched when an app launches in portrate mode. > > app@ivi_box:~$ ps -fA | grep xwalk > > app 1061 859 1 12:09 ? 00:00:00 > > /home/app/apps_rw/xwalk-service/applications/U4VCgZDnmt.Vonsor/bin/U4VCgZDnmt.Vonsor > > `zaybxcwdveuftgsh` __AUL_DEBUG__ > > IAAAAAEEAAAOAAAAX19BVUxfREVCVUdfXwACAAAAMQA= __AUL_STARTTIME__ > > NAAAAAEEAAASAAAAX19BVUxfU1RBUlRUSU1FX18AEgAAADE0MzQ1NjgxOTAvNzE2MDY4AA== > > __AUL_CALLER_PID__ KAAAAAEEAAATAAAAX19BVUxfQ0FMTEVSX1BJRF9fAAUAAAAxMDQzAA== > > __AUL_CALLER_UID__ KAAAAAEEAAATAAAAX19BVUxfQ0FMTEVSX1VJRF9fAAUAAAA1MDAwAA== > > app 1063 409 12 12:09 ? 00:00:00 /usr/lib/xwalk/xwalk > > --external-extensions-path=/usr/lib/tizen-extensions-crosswalk > > app 1067 1063 3 12:09 ? 00:00:00 /usr/lib/xwalk/xwalk > > --type=zygote > > app 1090 1063 12 12:09 ? 00:00:00 /usr/lib/xwalk/xwalk > > --type=gpu-process --channel=1063.0.1910641544 --gpu-no-context-lost > > --use-gl=egl --supports-dual-gpus=false > > --gpu-driver-bug-workarounds=1,12,38 --gpu-vendor-id=0x8086 > > --gpu-device-id=0x0f31 --gpu-driver-vendor --gpu-driver-version > > app 1100 1067 15 12:09 ? 00:00:00 /usr/lib/xwalk/xwalk > > --type=renderer --enable-threaded-compositing --enable-viewport > > --js-flags=--simd_object --use-gl=egl --enable-deferred-image-decoding > > --lang=en-US --enable-pinch --enable-delegated-renderer > > --enable-impl-side-painting --num-raster-threads=1 > > --enable-gpu-rasterization --channel=1063.1.1603513789 > > > > Any ideas or support is greatly appreciated. > > > > *Art McGee* > > Infotainment Engineer > > > > > > > > Jaguar Land Rover North America, LLC > > 1419 NW 14th Ave, Portland, Oregon, 97209 > > Jaguar.com <http://jaguar.com> | LandRover.com <http://landrover.com> > > > > > > On 17 June 2015 at 09:15, Leon Anavi <[email protected]> wrote: > > > >> Hi Art, > >> > >> On 17.06.2015 18:20, McGee, Art wrote: > >> > >> I'll have to take a closer look at the code. The crosswalk rpm didn't > >> work on ivi. > >> > >> > >> Earlier today I updated the screen orientation to landscape of the > >> following basic app that I use for testing: > >> https://github.com/leon-anavi/helloTizen > >> > >> My quick tests show that this app is successfully installed and launched > >> on the following hardware: > >> * Intel NUC with Tizen Common: tizen-common_20150513.1 x86_64 default > >> * HummingBoard (Freescale i.MX6 ARM SoC) with Tizen:Common built using > >> Yocto and Crosswalk 11.40.277.0 > >> > >> I hope that this simple app might be useful for debugging of your case. > >> As Jose suggested you should run journalctl -f on the behalf of the root > >> user before launching the app to see if any errors are reported. > >> > >> Best regards, > >> Leon > >> > >> > >> > >> > >> *Art McGee* > >> Infotainment Engineer > >> > >> > >> > >> Jaguar Land Rover North America, LLC > >> 1419 NW 14th Ave, Portland, Oregon, 97209 > >> Jaguar.com <http://jaguar.com> | LandRover.com <http://landrover.com> > >> > >> > >> On 17 June 2015 at 08:05, McGee, Art <[email protected]> wrote: > >> > >>> Leon, > >>> > >>> Yes, This is the crosswalk apps running in landscape orientation. I > >>> should then use the crosswalk from common. I currently use tizen_ivi_3.0 > >>> > >>> Thanks, > >>> > >>> Art. > >>> > >>> *Art McGee* > >>> Infotainment Engineer > >>> > >>> > >>> > >>> Jaguar Land Rover North America, LLC > >>> 1419 NW 14th Ave, Portland, Oregon, 97209 > >>> Jaguar.com <http://jaguar.com> | LandRover.com <http://landrover.com> > >>> > >>> > >>> On 17 June 2015 at 03:16, Leon Anavi <[email protected]> wrote: > >>> > >>>> Hi Art, > >>>> > >>>> If you remember several weeks ago I had some issues with installing and > >>>> running HTML5 apps on Tizen:Common which were solved after updating > >>>> Crosswalk to version 11.40.277.0. Which version of Crosswalk are you > >>>> using? > >>>> > >>>> Is the screen orientation set to landscape at the config.xml of the > >>>> HTML5 applications? > >>>> > >>>> Best regards, > >>>> Leon > >>>> > >>>> > >>>> On 17.06.2015 01:55, McGee, Art wrote: > >>>> > >>>> I have run into a problem that Tizen web apps will not run when the > >>>> box has been setup in landscape mode. I have been able to launch the > >>>> same apps in portrate mode. I have been spending quite a bit of time > >>>> searching. I would input on the app_launch process when it comes to > >>>> xwalk wigits. I have been able to see that a xwalk 'renderer' process > >>>> doesn't get started and the app will shutdown after never getting a > >>>> display. and it timesout on the debus call. Any information on how the > >>>> launch process works will help me discover where the bug is accually. > >>>> > >>>> > >>>> *Art McGee* > >>>> Infotainment Engineer > >>>> > >>>> > >>>> > >>>> Jaguar Land Rover North America, LLC > >>>> 1419 NW 14th Ave, Portland, Oregon, 97209 > >>>> Jaguar.com <http://jaguar.com> | LandRover.com > >>>> <http://landrover.com> > >>>> > >>>> > >>>> > >>>> _______________________________________________ > >>>> Crosswalk-dev mailing > >>>> [email protected]https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev > >>>> > >>>> > >>>> -- > >>>> Leon Anavi > >>>> Software Engineer > >>>> Mob : +359 88 527 7901konsulko.com > >>>> > >>>> > >>> > >> > >> -- > >> Leon Anavi > >> Software Engineer > >> Mob : +359 88 527 7901konsulko.com > >> > >> > > -- Carsten Haitzler (The Rasterman) <[email protected]> _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
