Bug#463416: Does not start

[Vincent Fourmond <fourmond@debian.org>]

Yavor Doganov wrote:
> Vincent Fourmond wrote:
>> zsh: abort      Shisen
> 
>> Versions of packages shisen.app depends on:
>> pn  gnustep-back0.12        <none>           (no description available)
>> pn  gnustep-base-runtime    <none>           (no description available)
>> pn  gnustep-gpbs            <none>           (no description available)
>> pn  gnustep-gui-runtime     <none>           (no description available)
>> ii  libc6                   2.7-6            GNU C Library: Shared libraries
>> ii  libgcc1                 1:4.3-20080127-1 GCC support library
>> pn  libgnustep-base1.14     <none>           (no description available)
>> pn  libgnustep-gui0.12      <none>           (no description available)
>> pn  libobjc2                <none>           (no description available)
> 
> Do you really don't have the dependencies installed?  If so, that's
> expected.

  Well, no ;-)... I messed up with reportbug...

> If not, I suspect a known bug in gnustep-base.  Can you show the
> output of
> 
> ps | grep gdnc
> ls -l /tmp/GNUstepSecure*/NSMessagePort/ports/

  That gives nothing (even with ps ax). Does a gnustep daemon of some
kind need to be running for Shisen.app to work correctly ? I'm not
running GNUStep at all (but fvwm2); could that be the problem ?

  If that is the case, the debian manual page should be updated (Barry,
if you please...), as that is really not clear at all.

  By the way, the debugging output you suggested does not show anything
as well:

 ~ Shisen --GNU-Debug=NSDistributedNotificationCenter \
          --GNU-Debug=NSMessagePort
zsh: abort      Shisen --GNU-Debug=NSDistributedNotificationCenter
--GNU-Debug=NSMessagePort

  Thanks !

	Vincent

-- 
Vincent Fourmond, Debian Developer
http://vince-debian.blogspot.com/
-- pretty boring signature, isn't it ?