After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 56111 - Crash during galeon startup
Crash during galeon startup
Status: RESOLVED DUPLICATE of bug 55726
Product: ORBit
Classification: Deprecated
Component: general
0.5
Other other
: Normal critical
: ---
Assigned To: Matt Aubury
Matt Aubury
: 58485 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2001-06-13 10:59 UTC by weilbach
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description weilbach 2001-06-13 10:59:55 UTC
Package: galeon
Severity: critical
Version: 0.11.0
Synopsis: Crash during galeon startup
Bugzilla-Product: galeon
Bugzilla-Component: general

Description:
I compiled galeon from sources using the binary mozilla-0.9.1 distrib, and mozilla-devel-0.9.1-0 RPMs for RadHat 6.X. To circumvent the strange test

checking Mozilla version... 0.9.1
configure: error: 
   *** This version of Mozilla has a bug in libgtksuperwin that
   *** causes galeon to crash when used with tabbed mode.
   *** http://bugzilla.mozilla.org/show_bug.cgi?id=79022
   *** contains a patch (with a spelling error)
   *** s/gtk_window_remove_filter/gdk_window_remove_filter/.

I deleted the exit 1 in ./configure, as that error seems to be fixed in the distributed mozilla-0.9.1.

I am running on SuSE 6.2, but I think I have every (GNOME) library required (according to the README), compiled from Source.


Debugging Information:

(no debugging symbols found)...0x407d07a9 in __wait4 () from /lib/libc.so.6
  • #0 __wait4
    from /lib/libc.so.6
  • #1 __DTOR_END__
    from /lib/libc.so.6
  • #2 waitpid
    at wrapsyscall.c line 134
  • #3 gnome_segv_handle
    at gnome-init.c line 661
  • #4 pthread_sighandler
    at signals.c line 89
  • #5 __restore
    at ../sysdeps/unix/sysv/linux/i386/sigaction.c line 125
  • #6 ORBit_POA_release
    at orbit_poa.c line 342
  • #7 ORBit_POA_new
    at orbit_poa.c line 322
  • #8 CORBA_ORB_resolve_initial_references
    at orb.c line 1044
  • #9 main
  • #10 main
  • #11 __libc_start_main
    at ../sysdeps/generic/libc-start.c line 90
  • #0 __wait4
    from /lib/libc.so.6
  • #1 __DTOR_END__
    from /lib/libc.so.6
  • #2 waitpid
    at wrapsyscall.c line 134
  • #3 gnome_segv_handle
    at gnome-init.c line 661
  • #4 pthread_sighandler
    at signals.c line 89
  • #5 __restore
    at ../sysdeps/unix/sysv/linux/i386/sigaction.c line 125
  • #6 ORBit_POA_release
    at orbit_poa.c line 342
  • #7 ORBit_POA_new
    at orbit_poa.c line 322




------- Bug moved to this database by unknown@bugzilla.gnome.org 2001-06-13 06:59 -------

The original reporter (weilbach@uni-sw.gwdg.de) of this bug does not have an account here.
Reassigning to the exporter, unknown@bugzilla.gnome.org.
Reassigning to the default owner of the component, matt@ookypooky.com.

Comment 1 Matt Aubury 2001-06-13 11:05:13 UTC
What versions of ORBit and OAF are you using? I have :
ORBit-0.5.8-ximian.2
oaf-0.6.5-ximian.3
Comment 2 weilbach 2001-06-13 11:15:30 UTC
I have ORBit-0.5.4 and oaf-0.6.5, both compiled from Sources.
Comment 3 Yanko Kaneti 2001-06-13 12:04:47 UTC
i would certainly suspect strongly the old ORBit
please upgrade to 0.5.8
Comment 4 weilbach 2001-06-13 12:51:28 UTC
That's not it. ORBit-0.5.8 installed, ldconfig, logout, login, and I
still get the bug-buddy crash window (backtrace info below). Which
components should I check next?

no debugging symbols found)...0x407db7a9 in __wait4 () from /lib/libc.so.6
  • #0 __wait4
    from /lib/libc.so.6
  • #1 __DTOR_END__
    from /lib/libc.so.6
  • #2 waitpid
    at wrapsyscall.c line 134
  • #3 gnome_segv_handle
    at gnome-init.c line 661
  • #4 pthread_sighandler
    at signals.c line 89
  • #5 __restore
    at ../sysdeps/unix/sysv/linux/i386/sigaction.c line 125
  • #6 ORBit_POA_release
    at orbit_poa.c line 342
  • #7 ORBit_POA_new
    at orbit_poa.c line 322
  • #8 CORBA_ORB_resolve_initial_references
    at orb.c line 1045
  • #9 main
  • #10 main
  • #11 __libc_start_main
    at ../sysdeps/generic/libc-start.c line 90
  • #0 __wait4
    from /lib/libc.so.6
  • #1 __DTOR_END__
    from /lib/libc.so.6
  • #2 waitpid
    at wrapsyscall.c line 134
  • #3 gnome_segv_handle
    at gnome-init.c line 661
  • #4 pthread_sighandler
    at signals.c line 89
  • #5 __restore
    at ../sysdeps/unix/sysv/linux/i386/sigaction.c line 125
  • #6 ORBit_POA_release
    at orbit_poa.c line 342
  • #7 ORBit_POA_new
    at orbit_poa.c line 322

Comment 5 Matt Aubury 2001-06-13 14:10:19 UTC
I'm a teeny bit suspicious that the line numbers in orbit_poa.c
haven't changed; are you sure it hasn't installed itself in /usr/local
or something daft? Please excuse me if this is a stupid question, I
just want to be sure.
Comment 6 weilbach 2001-06-13 14:27:01 UTC
Sorry, I am not a programmer and do not really understand these
backtraces anyway. But it seems that orbit_poa.c has only changed in
lines 712 from 0.5.4 to 0.5.8:
$ diff -s src/orb/orbit_poa.c
../../../01UnInstalled/ORBit-0.5.4/src/orb/orbit_poa.c
712,713d711
< 		if(!retval)
< 	
	return NULL;

And it is indeed using 0.5.8 where I would expect it. While the
bug-buddy screen is up:
$ lsof | grep galeon | grep ORBit
galeon-bi 16010 weilbach  mem    REG        0,6  175947  608835
/otherfs/USW/packages/gnome/lib/libORBitCosNaming.so.0.5.8 
galeon-bi 16010 weilbach  mem    REG        0,6  946725  608594
/otherfs/USW/packages/gnome/lib/libORBit.so.0.5.8 
galeon-bi 16010 weilbach  mem    REG        0,6   45468  608686
/otherfs/USW/packages/gnome/lib/libORBitutil.so.0.5.8 

Any other tests I could do?
Comment 7 Matt Aubury 2001-06-13 15:40:35 UTC
I'm afraid I'm stumped :-( Changing product to ORBit in the vain hope
that the ORBit people will recognise the problem.
Comment 8 Elliot Lee 2001-09-11 04:22:06 UTC
Sorry, no clues here either. If you come up with a small test program 
that can reproduce the problem, I'll be glad to look into it.
Comment 9 Elliot Lee 2001-09-11 04:47:59 UTC
*** Bug 58485 has been marked as a duplicate of this bug. ***
Comment 10 Ben FrantzDale 2002-07-31 05:04:59 UTC

*** This bug has been marked as a duplicate of 55726 ***