SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am using -Current and i am using Firefox directly from Mozilla.org, not from -Current package. I upgraded my Firefox using the Automatic Updates and it worked, but when i restarted the browser, it won't load up.
It happened only on my laptop. I have successfully upgraded to Firefox 3.5 on my desktop at home and my workstation at office with the same way.
Any clues on this?
PS: The process is active and it has been granted an PID, but now window showed up.
Try creating a new profile for FF, just to rule out a corrupted profile as the source of the problem.
Also, perhaps some of your addons / extensions are problematic in FF 3.5. Creating a new profile would rule that out as well.
I am using -Current and i am using Firefox directly from Mozilla.org, not from -Current package. I upgraded my Firefox using the Automatic Updates and it worked, but when i restarted the browser, it won't load up.
You run firefox as root to do this? Or do you have it installed under your users profile? You should not be able to use the auto update unless your user have correct write perms to the installation folder. If you autoupdated a packaged firefox you just made yourself a tiny mess (easily cleaned up).
For a quick test try untarring the mozilla binary source into your home directory and run firefox from there with a fresh profile. If that works then try the old profile. Assuming that works a global install should work as well. For that remove the old installation, including the misc unpackaged files that may be in there. Then modify the firefox slackBuild to create yourself a package, or just make the package manually.
My firefox slackBuild is a slightly modified version of the official. It works across different Slackware versions.
I used to use binary package from Mozilla and use Automatic Updates after changing the ownership to my own user and group over /opt/firefox directory. This works up to 3.0.11.
i have tried to unpack the binary from mozilla into my own home dir and run it and i got exactly the same results, no output, but a new Firefox process is created.
I will probably wait until Pat releases 3.5 on -Current
It seems that i'm not the only one who had this problem on a laptop. Someone posted the same problem on his laptop, but i don't know if he's using Linux or most specifically, Slackware.
I finally find out the reason --- the tarball downloaded from www.mozilla.com is for i686, not x86_64! So it won't lunch on 64current! We have to compile it from source(it may become a nightmare according to my previous experience) or wait for Pat to have a package for it. Wish it won't be long...
# This is not a source build script. Rather, it builds a Slackware
# package from the official binary tarball available from mozilla.org.
# Using the official binaries seems like the most direct way to satify
# the Mozilla project's concerns about quality control (and thus to
# provide the most quality-certified package possible), and therefore
# be able to use the official trademarks and logos.
#
# Thanks to the folks at the Mozilla Foundation for permission to
# distribute this, and for all the great work! :-)
VERSION=3.5
ARCH=${ARCH:-i686}
BUILD=1
if [ ! -d $TMP ]; then
mkdir -p $TMP
fi
rm -rf $PKG
mkdir -p $PKG/usr/lib
( cd $PKG/usr/lib
tar xf $CWD/firefox-3.5.tar.bz2 || exit 1
mv firefox firefox-3.5
ln -sf firefox-3.5 firefox
cd firefox-3.5
zcat $CWD/mozilla-firefox-simple.diff.gz | patch -p1 --verbose --backup --suffix=.orig || exit 1
if [ ! $? = 0 ]; then
exit 1
fi
zcat $CWD/mozilla-firefox-mimeTypes-fix.diff.gz | patch -p1 --verbose --suffix=.orig || exit 1
if [ ! $? = 0 ]; then
exit 1
fi
zcat $CWD/firefox.moz_plugin_path.diff.gz | patch -p1 --verbose --suffix=.orig || exit 1
if [ ! $? = 0 ]; then
exit 1
fi
rm -f defaults/pref/firefox.js.orig
)
if [ ! $? = 0 ]; then
exit 1
fi
mkdir -p $PKG/usr/bin
( cd $PKG/usr/bin
ln -sf /usr/lib/firefox-3.5/firefox .
)
mkdir -p $PKG/usr/lib/mozilla/plugins
mkdir -p $PKG/usr/share/applications
cat $CWD/mozilla-firefox.desktop > $PKG/usr/share/applications/mozilla-firefox.desktop
mkdir -p $PKG/usr/share/pixmaps
cat $CWD/firefox.png > $PKG/usr/share/pixmaps/firefox.png
# These files/directories are usually created if Firefox is run as root, which on many
# systems might (and possibly should) be never. Therefore, if we don't see them we'll
# put stubs in place to prevent startup errors.
( cd $PKG/usr/lib/firefox-3.5
if [ -d extensions/talkback\@mozilla.org ]; then
if [ ! -r extensions/talkback\@mozilla.org/chrome.manifest ]; then
echo > extensions/talkback\@mozilla.org/chrome.manifest
fi
fi
if [ ! -d updates ]; then
mkdir -p updates/0
fi
)
Just for precaution, replace the variable for fixed 3.5 version and look your lib path -> mozilla-firefox.SlackBuild
example:
It's crude but should work on current x86_32. Copy old 3.0.11 flash plugin and don't forget to reinstall when Firefox 3.5 goes official...
The mozilla-firefox-mimeTypes-fix.diff needed a minor update before you can use the old 3.0 SlackBuild. I really don't like changing the version numbers with each update so I prefer to sed the patches.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.