ubuntu-phone team mailing list archive

[Kevin Gunn <kevin.gunn@xxxxxxxxxxxxx>]

Thanks xnox
adding your response to the bug.
kg


On Thu, Feb 27, 2014 at 3:03 PM, Dimitri John Ledkov <xnox@xxxxxxxxxx>wrote:

> On 27 February 2014 18:43, Michał Sawicz <michal.sawicz@xxxxxxxxxxxxx>
> wrote:
> > On 27.02.2014 18:48, Didier Roche wrote:
> >>
> >> 3. Screen unlock often not working during the tests (Kgunn)
> >> Seems that more investigation pointed on Mir direction:
> >> https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1285215
> >
> >
> > FWIW the underlying issue are the above unity8 crashes - the socket is
> not
> > cleared like on proper exit, so prevents the next unity8 run.
> >
> > Before the proper Mir fix, we could delete the socket in unity8's
> pre-start
> > to improve the situation temporarily.
> >
>
> File socket should not be used at all, as they are known to be racy
> and can easily end up stale, instead an abstract unix domain socket
> should be used throughout.
>
> This is not the first time, where stale, and not properly cleared file
> sockets in mir are causing severe breakage on touch.
>
> With an abstract socket, there is no file on a filesystem, and thus
> when a process is gone the socket is also gone. You can see examples
> of abstract sockets in: upstart, dbus-daemon, and plenty of other
> system level daemons on ubuntu.
>
> --
> Regards,
>
> Dimitri.
>
> --
> Mailing list: https://launchpad.net/~ubuntu-phone
> Post to     : ubuntu-phone@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~ubuntu-phone
> More help   : https://help.launchpad.net/ListHelp
>