From Bugzilla Helper: User-Agent: Mozilla/4.73C-SGI [en] (X11; U; IRIX64 6.5 IP30) BuildID: 20010509 I downloaded the RPMS for mozilla 0.9 and installed them on a RH 7.1 system with Ximian Gnome 1.4. After the installation, starting mozilla yields an error: 'Error sending command'. I removed the installation using rpm -e, but I am unable to get the previous version to work. I cannot get the build ID, as the browser won't start Reproducible: Didn't try Steps to Reproduce: 1. install mozilla 0.9 from RPMs on RH 7.1 + Ximian Gnome 1.4 2. 3. Actual Results: mozilla won't start Expected Results: mozilla would work
reporter: unfortunately this isn't enough information. please describe how you ran mozilla, and paste all console output from mozilla. Did you install mozilla as root? did you run mozilla as owner of mozilla or someone else ... ?
Assignee: asa → blizzard
Sounds like the script the RPM installs tries to run with -remote even though no mozilla is running.... Reporter, can you make sure you kill off all running mozilla processes before you try starting the browser?
Status: UNCONFIRMED → NEW
Ever confirmed: true
I have the same problem and comes from: [fpn@fpn fpn]$ /usr/lib/mozilla/mozilla-bin /usr/lib/mozilla/mozilla-bin: error while loading shared libraries: /usr/lib/libnspr4.so: undefined symbol: fstat (the /usr/bin/mozilla script hides this). COMMENT: maybe the script shouldn't hide the error messages that mozilla-bin gives?!? Quick FIX: rpm -e libnspr4-4.1-ximian.3 libnspr4-devel-4.1-ximian.3 rpm -U --force mozilla-0.9-0.i386.rpm best regards, Florian
it sounds like the dependencies aren't strong enough, perhaps blizzard's rpm's should have complained about the incompatible nspr. in general you should be running mozilla by doing: [fpn@fpn /usr/lib/mozilla/]$ ./mozilla (or wherever you choose to install mozilla) which will /try/ to configure paths that work, however ximian's nspr is installed as a system nspr and will probably be in your path earlier than mozilla =(
Are you kidding me? He used --force! How am I supposed to warn about that?
Status: NEW → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.