The log device files (i.e. what's needed for dlog to work) are not
writable by the app user (which is wrong and we really should document
this as a bug) so all the log writes fail.
A way to work around this is to ssh in as root (or 'su -' in the
terminal) and type 'chmod 666 /dev/log*' before running an app. These
files are created at boot time so you have to do this on each boot.
BTW... the way to fix this is to create a udev rule to assign better
permissions on the device files. Of course we would need to debate with
the security team what those permissions should be.
--rusty
On Wed, 2013-08-28 at 00:33 +0000, Li, Hao H wrote:
> Hi
>
>
>
> http://download.tizen.org/releases/milestone/tizen/ivi/tizen_20130729.2/repos/ivi/ia32/packages/i686/lemolo-0.1.3-1.1.i686.rpm
>
> During launch_app org.tizen.dialer on Tizen IVI, is there any way to
> see the log?
>
>
>
> I tried dlogutil and EINA_LOG_LEVEL=5 launch_app org.tizen.dialer,
> neither of them can see the log about dialer.
>
>
>
> Thanks!
>
>
>
> Li Hao
>
> Best Regards
>
> Email:[email protected]
>
>
>
> Tizen Enabling Team
>
> Software and Service Group
>
> Intel Asia-Pacific Research & Development Ltd.
>
> Tel: 86-21-61167039
>
>
>
>
> _______________________________________________
> General mailing list
> [email protected]
> https://lists.tizen.org/listinfo/general
_______________________________________________
General mailing list
[email protected]
https://lists.tizen.org/listinfo/general
