On Tue, 02 Feb 2010 18:35 +0200, "Yavor Doganov" <ya...@gnu.org> wrote: > So, to figure out where the problem lies, could you do the following > steps, please (performing the next step is not needed if the prior > step leads to successful results): > > 1. Do you start gdnc from your .bashrc/.xsession/etc? As you said > you've never used GNUstep apps before, I doubt it. GDNC should be > started automatically by the gnustep-base library, but the > implementation (via NSTask) is fragile, and upstream considers it > NOTABUG (i.e. they say that every GNUstep user should launch gdnc > in her init scripts explicitly). > Does the problem occur if you start gdnc in the session? > If it disappears, there's a bug in gnustep-base; and I'll send you > a test program to confirm this.
I've tried starting gdnc in my .profile, or manually in the shell instance I'm using for testing. and I still see the same segfault. To check that I'm doing this right, here are the relevant lines I see in $ ps ax in each of the two cases 28485 ? S< 0:00 /usr/bin/gdnc --daemon 28729 pts/2 S< 0:00 /usr/bin/gdnc --daemon > 2. If 1) fails, I'll send you another test program to confirm that > this is not the locking race condition that we've been bitten > before. I await the test program with interest. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
