Closed Bug 202762 Opened 22 years ago Closed 20 years ago

mozilla crashes on startup when used with any gtk theme based on pixmap theme engine e.g, BeeOrbit, BumbleBee, Crystal or TrueBlue

Categories

(Core Graveyard :: GFX: Gtk, defect)

HP
HP-UX
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: sauravs, Assigned: blizzard)

Details

(Keywords: crash, stackwanted)

User-Agent: Mozilla/5.0 (X11; U; HP-UX 9000/785; en-US; rv:1.3b; MultiZilla v1.4.0.3H) Gecko/20030321 Build Identifier: Mozilla/5.0 (X11; U; HP-UX 9000/785; en-US; rv:1.3b; MultiZilla v1.4.0.3H) Gecko/20030321 Mozilla crashes on startup (on when gtk theme is changed in gnome control centre) when used with a gtk theme based on pxmap theme engine eg, BeeOrbit, BumbleBee, Crystal or TrueBlue. Reproducible: Always Steps to Reproduce: 1.Change the gtk theme in gnome control centre to any theme based on pixmap theme engine eg BeeOrbit, BumbleBee, Crystal or TrueBlue. 2. Start mozilla 3. Actual Results: mozilla crashes with the following error message: /usr/lib/dld.sl: Unresolved symbol: gdk_imlib_destroy_image (code) from /opt/gnome/lib/gtk/themes/engines/libpixmap.sl /usr/lib/dld.sl: Unresolved symbol: gdk_imlib_set_image_border (code) from /opt/gnome/lib/gtk/themes/engines/libpixmap.sl /usr/lib/dld.sl: Unresolved symbol: gdk_imlib_move_mask (code) from /opt/gnome/lib/gtk/themes/engines/libpixmap.sl /usr/lib/dld.sl: Unresolved symbol: gdk_imlib_render (code) from /opt/gnome/lib/gtk/themes/engines/libpixmap.sl /usr/lib/dld.sl: Unresolved symbol: gdk_imlib_set_cache_info (code) from /opt/gnome/lib/gtk/themes/engines/libpixmap.sl /usr/lib/dld.sl: Unresolved symbol: gdk_imlib_get_colormap (code) from /opt/gnome/lib/gtk/themes/engines/libpixmap.sl /usr/lib/dld.sl: Unresolved symbol: gdk_imlib_get_visual (code) from /opt/gnome/lib/gtk/themes/engines/libpixmap.sl /usr/lib/dld.sl: Unresolved symbol: gdk_imlib_move_image (code) from /opt/gnome/lib/gtk/themes/engines/libpixmap.sl /usr/lib/dld.sl: Unresolved symbol: gdk_imlib_free_pixmap (code) from /opt/gnome/lib/gtk/themes/engines/libpixmap.sl /usr/lib/dld.sl: Unresolved symbol: gdk_imlib_load_image (code) from /opt/gnome/lib/gtk/themes/engines/libpixmap.sl /usr/lib/dld.sl: Unresolved symbol: gdk_imlib_init (code) from /opt/gnome/lib/gtk/themes/engines/libpixmap.sl /usr/lib/dld.sl: Unresolved symbol: gdk_imlib_init (code) from /opt/gnome/lib/gtk/themes/engines/libpixmap.sl /var/preserve/mozilla/run-mozilla.sh: line 72: 6452 ABORT instruction (core dumped) "$prog" ${1+"$@"} Oh no! /var/preserve/mozilla/mozilla-bin just dumped a core file. Do you want to debug this ? You need a lot of memory for this, so watch out ? [y/n] y /usr/local/bin/ddd /var/preserve/mozilla/mozilla-bin core Program terminated with signal 6, Aborted. Unable to find __dld_flags symbol in object file. #0 0xc002e438 in ?? () Expected Results: mozilla should have started normally and its widgets etc should have been rendered according to the gtk theme selected. I was using pinball theme but I think the problem would repeat with other themes also.
does it happen with 1.3 or 1.4a and an up-to-date MultiZilla version ? Do you have GTK >= 1.2.10 ?
Keywords: crash
Summary: mozilla crashes on startup when used with any gtk theme based on pixmap theme engine e.g, BeeOrbit, BumbleBee, Crystal or TrueBlue → mozilla crashes on startup when used with any gtk theme based on pixmap theme engine e.g, BeeOrbit, BumbleBee, Crystal or TrueBlue
does it happen with 1.3 or 1.4a and an up-to-date MultiZilla version ? Do you have GTK >= 1.2.10 ? I tried it with the mozilla 1.3 release for HP-UX in mozilla.org's ftp server, but the about:mozilla shows it as version 1.3b. same with 1.4a. And I installed the latest multizilla. The problem remains same. And I have Ximian gnome 1.4 installed on my machine. So it has GTK = 1.2.10.
.
Assignee: asa → blizzard
Component: Browser-General → GFX: Gtk
Keywords: stackwanted
QA Contact: asa → ian
This should have been fixed a while ago. Probably by 1.3.
does it happen with a fresh profile (given you test 1.3 or 1.4a) "mozilla -profilemanager" ?
bryner: What happend to the request to provide a command-line switch or env variable to turn-off GTK+ themeing support ?
it happens even with a fresh profile
saurav, does the fresh profile show 1.4a in about:mozilla ?
I am currently using 1.3 and the fresh profile shows 1.3 while the old profile shows 1.3b. So I think 1.4a will show up as 1.4a. Also, I noticed that another gtk application that crashes with my gtk theme switching is gvim.
This could be HP-UX specific. It looks like symbols in imlib referenced from the theme libraray aren't being found. jdunn or wtc, do you know of anything specific that we'd need to do to ensure that the symbols are in scope? I'm a bit confused because we don't open the theme library directly (it's all done by GTK), so I'm not sure why other GTK applications would work.
How (on hpux) do I change the theme? If someone can give VERY detailed steps, I can try to reproduce this.
If Ximian GNOME is installed, then first install the theme in /opt/gnome/share/theme directory. Then open GNOME control centre->Desktop-> Theme Selector and choose the installed theme and press Ok. Ig GNOME is not installed, then theme can be applied by modifying the $HOME/.gtkrc file as follows: include "/opt/gnome/share/themes/ThinIce-Watercolor/gtk/gtkrc" where you have to substitute the appropriate gtkrc path name.
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → EXPIRED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.