Update Gnome 2.3.5 today and can't run it anymore..

[Joe Marcus Clarke]

On Wed, 1921-08-03 at 19:51, Jeremy Messenger wrote:
> I think, the issue might be has to do with devel/gnomevfs2.. Because, 
> yesterday or two days ago, I update and I can run Gnome2 until another 
> update today...

libbonobo doesn't depend on gnomevfs, so I don't think that's it.  I
don't think this is an ltmain.sh issue either.  How many ports did you
have to update to get to GNOME 2.3.5?  I have been staying pretty recent
on my -CURRENT machine, and so far, no problems.  I have not done the
gnomevfs2 update yet, however.  I'll have to look at that tomorrow.

Joe

> 
> 
> Here's what it looks like when I tried to run Gnome2:
> =====================================
> Aug  3 18:41:22 mezz kernel: pid 647 (bonobo-activation-s), uid 1001: 
> exited on
> signal 11 (core dumped)
> Aug  3 18:41:23 mezz kernel: pid 649 (bonobo-activation-s), uid 1001: 
> exited on
> signal 11 (core dumped)
> Aug  3 18:41:24 mezz kernel: pid 651 (bonobo-activation-s), uid 1001: 
> exited on
> signal 11 (core dumped)
> Aug  3 18:41:24 mezz kernel: pid 653 (bonobo-activation-s), uid 1001: 
> exited on
> signal 11 (core dumped)
> Aug  3 18:41:25 mezz kernel: pid 655 (bonobo-activation-s), uid 1001: 
> exited on
> signal 11 (core dumped)
> Aug  3 18:41:38 mezz kernel: pid 657 (bonobo-activation-s), uid 1001: 
> exited on
> signal 11 (core dumped)
> Aug  3 18:42:50 mezz kernel: pid 666 (bonobo-activation-s), uid 1001: 
> exited on
> signal 11 (core dumped)
> Aug  3 18:42:50 mezz kernel: pid 668 (bonobo-activation-s), uid 1001: 
> exited on
> signal 11 (core dumped)
> Aug  3 18:42:51 mezz kernel: pid 670 (bonobo-activation-s), uid 1001: 
> exited on
> signal 11 (core dumped)
> [...goes on...]
> =====================================
> 
> 
> Here's what I get in gdb with nautilus:
> =====================================
> (gdb) r
> Starting program: /usr/X11R6/bin/nautilus Fatal error 'gc cannot wait for a 
> signal' at line 194 in file /usr/src/lib/
> libc_r/uthread/uthread_gc.c (errno = 0)
> 
> Program received signal SIGABRT, Aborted.
> 0x28d76eef in kill () from /usr/lib/libc.so.5
> (gdb) bt
> #0  0x28d76eef in kill () from /usr/lib/libc.so.5
> #1  0x28de175c in abort () from /usr/lib/libc.so.5
> #2  0x28c304a8 in _thread_exit () from /usr/lib/libc_r.so.5
> #3  0x28c253a1 in _thread_gc () from /usr/lib/libc_r.so.5
> #4  0x28c244ee in _thread_start () from /usr/lib/libc_r.so.5
> =====================================
> 
> It looks like it's ltmain issue?
> 
> Cheers,
> Mezz
-- 
PGP Key : http://www.marcuscom.com/pgp.asc


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: This is a digitally signed message part
Url : http://lists.freebsd.org/pipermail/freebsd-gnome/attachments/20030804/c10b64c9/attachment.bin