40826 – Galeon 1.3.10 no longer runs after upgrade mozilla to 1.6

Bug 40826 - Galeon 1.3.10 no longer runs after upgrade mozilla to 1.6

Summary: Galeon 1.3.10 no longer runs after upgrade mozilla to 1.6

Status:	RESOLVED DUPLICATE of bug 40927

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	[OLD] GNOME (show other bugs)
Hardware:	All Linux

Importance:	High major (vote)
Assignee:	Gentoo Linux Gnome Desktop Team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2004-02-08 05:42 UTC by Ooblick
Modified:	2005-07-17 13:06 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Ooblick 2004-02-08 05:42:51 UTC

My default browser is Galeon. I was running galeon 1.3.10 which depends upon mozilla 1.5. Over the weekend the stable gentoo upgraded mozilla to 1.6. This is incompatible with galeon 1.3.10.

Suggested fix -> mark galeon-1.3.12 as stable.

Reproducible: Always
Steps to Reproduce:
1. Have gnome installed with mozilla 1.5 and galeon 1.3.10
2. emerge sync && emerge -u world (upgrades mozilla to mozilla-1.6)
3. Run Galeon

Actual Results:  
Gnome produces this message:

"Application "galeon-bin" (process 4399) has crashed due to a fatal error"

Expected Results:  
Galeon 1.3.12 should have been marked as stable at the same time as mozilla-1.6.
This would have enabled galeon to be upgraded to a version compatible with
mozilla at the same time.

Portage 2.0.50 (default-x86-1.4, gcc-3.3.2, glibc-2.3.2-r9, 2.6.1-gentoo-r1)
=================================================================
System uname: 2.6.1-gentoo-r1 i686 AMD Athlon(tm) XP 2200+
Gentoo Base System version 1.4.3.10
Autoconf: sys-devel/autoconf-2.58
Automake: sys-devel/automake-1.7.7
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-march=athlon-xp -mcpu=athlon-xp -O3 -pipe -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
COMPILER="gcc3"
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config
/usr/kde/3/share/config /usr/share/config /usr/share/texmf/tex/generic/config/
/usr/share/texmf/tex/platex/config/ /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
CXXFLAGS="-march=athlon-xp -mcpu=athlon-xp -O3 -pipe -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache sandbox"
GENTOO_MIRRORS="http://www.mirror.ac.uk/sites/www.ibiblio.org/gentoo/"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY=""
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="3dnow X aalib alsa apm avi berkdb bonobo cdr crypt cups encode esd
foomaticdb gdbm gif gnome gpm gtk gtk2 gtkhtml imlib java jpeg libg++ libwww mad
mikmod mmx motif mozilla mpeg ncurses nls nptl oggvorbis opengl oss pam pdflib
perl png ppds python quicktime readline sdl slang spell sse ssl svga tcltk tcpd
tetex tiff truetype usb x86 xml2 xmms xv zlib"

Comment 1 Yi Quang (RETIRED) gentoo-dev

2004-02-08 10:37:49 UTC

Yes, the gnome team didn't have a chance to coordinate the stabilization of mozilla.  I propose that we mark 1.3.12 as stable now.

Comment 2 foser (RETIRED) gentoo-dev

2004-02-09 00:39:23 UTC


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