Closed
Bug 87178
Opened 23 years ago
Closed 23 years ago
Cannot start mozilla [missing libgdk_pixbuf.so.2]
Categories
(SeaMonkey :: Build Config, defect)
Tracking
(Not tracked)
People
(Reporter: aroy, Assigned: cls)
Details
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; SunOS 5.8 sun4u; en-US; m18) Gecko/20010307 Netscape6/6.01 BuildID: 20010608 Installed mozilla (0.9.1) cannot start when I type ./run-mozilla.sh Reproducible: Always Steps to Reproduce: Cd to mozilla type ./run-mozilla.sh Actual Results: Mozilla fails to start because it cannot find a library Error message: nsNativeComponentLoader: SelfRegisterDll(/nfs/home/users/aroy/mozilla/components/libgfx_gtk.so) Load FAILED with error: ld.so.1: ./mozilla-bin: fatal: libgdk_pixbuf.so.2: open failed: No such file or directory ************************************************** Expected Results: It should start. Here is the information returned when I start mozilla: prefix [~/mozilla]% ./run-mozilla.sh MOZILLA_FIVE_HOME=. LD_LIBRARY_PATH=.:./plugins:/local/apps/Libraries/gtk+/lib:/local/apps/Libraries/glib/lib: LIBRARY_PATH=.:./components SHLIB_PATH=. LIBPATH=. ADDON_PATH=. MOZ_PROGRAM=./mozilla-bin MOZ_TOOLKIT= moz_debug=0 moz_debugger= ************************************************** nsNativeComponentLoader: SelfRegisterDll(/nfs/home/users/aroy/mozilla/components/libgfx_gtk.so) Load FAILED with error: ld.so.1: ./mozilla-bin: fatal: libgdk_pixbuf.so.2: open failed: No such file or directory **************************************************
.
Assignee: asa → cls
URL: http://N/A
Component: Browser-General → Build Config
QA Contact: doronr → granrose
Summary: Cannot start mozilla → Cannot start mozilla [missing libgdk_pixbuf.so.2]
Comment 2•23 years ago
|
||
This was fixed when XIE was removed from the tree. gdkpixbuf was removed as a requirement, too. *** This bug has been marked as a duplicate of 83920 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•