On 11/11/2014 08:08 AM, Jussi Laako wrote: > On 10.11.2014 23:38, Eduardo Lima (Etrunko) wrote: >> Weston takes the responsibility for launching it so it can keep track of >> the execution. For instance, if the application crashes, it will be >> relaunched automatically by Weston. I think this is one good reason for >> not making it a systemd service. > > And it cannot be systemd service anyway because services cannot have > access to the display... If you have three simultaneous logins for the > same user, you would still have only one service. For which of the three > login displays it would now show the VKBD? >
Now that you mentioned it, I need to investigate further if making IBus a systemd service, is a real possibility for this use case or not. > Other than that, a tiny problem with weston and you'll have thousands of > weekeyboard instances running. Has happened to me many times... As a > result, the entire system crawls... > This sounds like a problem in Weston indeed, the application itself is not able to respawn itself again and again. -- Eduardo de Barros Lima (Etrunko) Open Source Technology Center Intel Corporation - Brazil _______________________________________________ IVI mailing list [email protected] https://lists.tizen.org/listinfo/ivi
