[Notion-general] Fwd: statusd doesn't stop with restart

[Arnout E. <no...@bz...>]

Hi,

Jeff prepared a patch to explicitly close statusd on deinit.

This was needed because when restarting notion (notioncore.restart()), we
don't quit the old notion and start a new one, but instead we just execve()
the new notion on top of the old one - which basically explains why the old
statusd didn't quit in that case.

So this should fix the multiple instances of statusd running when
restarting notion.

On a related note, eventually I'd like to see mod_statusbar evolve into a
standalone application that can be loaded into the mod_dock just like any
other panel. But that's something for another day :)


Kind regards,

Arnout


On Tue, Nov 19, 2013 at 2:20 PM, Jeff Backus <jef...@gm...> wrote:

> Hi Tot-to,
>
> Just wanted touch base. Has XRandR solved the immediate problem? Have you
> heard anything more re: ion-statusd from the project team?
>
> On Wed, Nov 13, 2013 at 6:43 PM, Jeff Backus <jef...@gm...>wrote:
>
>> I can confirm the issue you are seeing with statusd_mpd-socket. With the
>> mpd monitor enabled, I get an orphaned ion-statusd process whenever I
>> restart or exit Notion. I do not see this when I disable the mpd monitor.
>> The orphaned process on exit causes hiccups with KDM and multiple logins.
>> Looks to me like a bug in ion-statusd.
>>
>
> I don't know how much trouble the orphaned statusd process is causing you.
> I have a fix that solved the problem for me, so far. I need to study the
> issue more before submitting it to the project. I understand why my fix
> works, but I don't fully understand why this problem didn't show up before
> - and that makes me nervous. :) If this is still bothering you I can share
> the fix.
>
> Regards,
> Jeff
>
> --
> Jeff Backus
> jef...@gm...
> http://github.com/jsbackus
>
>