Slack 12.2 and Firefox
Leonard the Committed
irritating. Can someone please tell me what I need to fix this? It
happens on MANY websites, most of which are left unviewable due to this
quirk.
Dan C
Looks like video (or X) corruption. Might be video driver problem, try
reloading Nvidia/ATI driver if you're using one of them.
You could always upgrade to Slack 13, too.
--
"Ubuntu" -- an African word, meaning "Slackware is too hard for me".
"Bother!" said Pooh, as he garotted another passing Liberal.
Usenet Improvement Project: http://twovoyagers.com/improve-usenet.org/
notbob
FF sucks. Use Seamonkey.
nb
Douglas Mayne
Sorry, no solution, but I have seen this glitch, and it was discussed on
this thread:
http://groups.google.com/group/alt.os.linux.slackware/msg/b6b8b57ff2984d7f
I have seen it crop up on both ati and nvidia, but not intel hardware.
It also seems to be something introduced with Firefox 3.5.x. From the
screenshot, it appears that you are running that series. I guess one
option is to go back to version 3.0.x. Also, for whatever reason, 3.5.4
did not remain -current for long- 3.5.5 was released yesterday. Perhaps,
try that update??
I modified the slackbuild yesterday and created the tgz:
http://www.xmission.com/~ddmayne/slackware/mozilla-firefox-3.5.5-i686-1-dm.tgz
http://www.xmission.com/~ddmayne/slackware/mozilla-firefox-3.5.5-i686-1-dm.tgz.md5
The package's md5sum is:
7605a02240bc38712cb1abfa5aba658f mozilla-firefox-3.5.5-i686-1-dm.tgz
Note: I haven't tested if this will fix this specific problem.
--
Douglas Mayne
Leonard the Committed
>
> http://www.xmission.com/~ddmayne/slackware/mozilla-firefox-3.5.5-i686-1-
dm.tgz
> http://www.xmission.com/~ddmayne/slackware/mozilla-firefox-3.5.5-i686-1-
dm.tgz.md5
>
> The package's md5sum is:
> 7605a02240bc38712cb1abfa5aba658f mozilla-firefox-3.5.5-i686-1-dm.tgz
>
> Note: I haven't tested if this will fix this specific problem.
My guess is that I need to install the nvidia driver. It's not been put
on because my video needs are basic, no fancy screen savers or heavy 3D
use. Thanks for the buildscript! I much prefer 12.2 right now and compiz,
KDE4 and such dont interest me.
What I see is updates on build scripts pretty much stop half way through
the next current cycle. As to compiling, I'm rather ignernt at it, and
every time I see error messages flying by then cant get it to run, I drop
off my interest. That slackbuild is WAY cool. Thanks!
Douglas Mayne
To followup: I tested firefox-3.5.5 on Slackware 12.2 with an ATI rage128
video board. This setup still shows the corruption on certain webpages,
including www.slackware.com.
I decided to check if the flaw shows up under Slackware 13.0. I upgraded
the above system to 13.0, and retested. This appears to fix the bug.
Slackware 13.0 includes a lot of upgrades to X. This was my first 13.0
install and it works very smoothly.*
*I did run into the "black screen" flaw discussed here on an earlier
thread. Luckily, it was fixed when I deleted xorg.conf and /* did not */
run xorgsetup, as is usually done. Apparently, The new x.org works without
the file, xorg.conf.
--
Douglas Mayne
goarilla
yeah it does and i don't really like it
Leonard the Committed
> yeah it does and i don't really like it
I'm not a big fan of "automagic" I'd much rather edit a simple file in mc
and be off and running without quirks.
Leonard the Committed
installed the new Firefox package. NADA! I've got a bigger better card,
but I'm running a VERY quiet IBM Netvista (tower version) with a puny
165w PS. Plenty for what I need, and am afraid my 5200 with 128mb of RAM
might tax it. No, I do not want to buy another power supply! See
quietness quote above.
Mikhail Zotov
goarilla <kevin....@skynet.remove-this.be> wrote:
> On Fri, 06 Nov 2009 20:54:02 +0000, Douglas Mayne wrote:
...
> > Apparently, The new x.org works without the file, xorg.conf.
>
> yeah it does and i don't really like it
The fact x.org can work w/o xorg.conf does not anyhow mean it
cannot work with xorg.conf any more.
--
Mikhail
Mikhail Zotov
> Thanks for the buildscript!
Where did you find the build script? I haven't found any on Douglas'
site or inside the package. Or, is it just a build script that comes
with Slack64 with a couple of trivial changes?
--
Mikhail
barnabyh
A while ago I dropped in the one from 12.2 (same machine and config at
the time, and still is).
Started experiencing random freezes between a few minutes to 3 days
after boot up.
rm'd the xorg.conf and since then everything appears fine again. I'ld
rather have a config file though, I'm sure there will be occasions when
this will become necessary.
--
5 years using Linux - and loving it.
Douglas Mayne
I did not post the build script, just the package. The build script that I
made is a trivial modification of the one provided by Slack 13.0. The
slackbuild provided by Slackware64 actually builds from the source code;
The one provided by Slack 13.0 uses a compiled binary obtained directly
from Mozilla. The build script applies some patches and some directory
fixups. AFAIK, the only other file which must be patched is
mozilla-firefox-simple.diff.gz
That file only requires a trivial change, then a re-gzip.
Here is the Slackbuild for completeness:
<begin mozilla-firefox.Slackbuild>
#!/bin/sh
CWD=`pwd`
TMP=${TMP:-/tmp}
PKG=$TMP/package-mozilla-firefox
# 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! :-)
#
# Non-Official Slackware Modifications:
# 2009-11-05: by D. Mayne
# Update for version 3.5.5;
# Fix package format to tgz to allow install under Slack 12.2;
VERSION=3.5.5
ARCH=${ARCH:-i686}
BUILD=1-dm
if [ ! -d $TMP ]; then
mkdir -p $TMP
fi
rm -rf $PKG
mkdir -p $PKG/usr/lib
( cd $PKG/usr/lib
tar xf $CWD/firefox-$VERSION.tar.bz2 || exit 1
mv firefox firefox-$VERSION
ln -sf firefox-$VERSION firefox
cd firefox-$VERSION
zcat $CWD/mozilla-firefox-simple.diff.gz | patch -p1 --verbose --backup --suffix=.orig || exit 1
# Clean up if the above patch was successful:
rm -f firefox.orig
#zcat $CWD/mozilla-firefox-mimeTypes-fix.diff.gz | patch -p1 --verbose --suffix=.orig || exit 1
zcat $CWD/firefox.moz_plugin_path.diff.gz | patch -p1 --verbose --suffix=.orig || exit 1
rm -f defaults/pref/firefox.js.orig
cd $PKG/usr/lib/firefox-$VERSION
# There's really no reason to save this .orig:
#mv defaults/profile/mimeTypes.rdf defaults/profile/mimeTypes.rdf.orig || exit 1
zcat $CWD/mimeTypes.rdf > defaults/profile/mimeTypes.rdf || exit 1
) || exit 1
mkdir -p $PKG/usr/bin
( cd $PKG/usr/bin
ln -sf /usr/lib/firefox-$VERSION/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-$VERSION
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
)
mkdir $PKG/install
cat $CWD/slack-desc > $PKG/install/slack-desc
cd $PKG
makepkg -l y -c n $TMP/mozilla-firefox-$VERSION-$ARCH-$BUILD.tgz
<end Slackbuild>
--
Douglas Mayne
Mikhail Zotov
Douglas Mayne <inv...@invalid.com> wrote:
> On Sat, 07 Nov 2009 11:43:40 +0300, Mikhail Zotov wrote:
>
> > On Fri, 06 Nov 2009 18:52:10 GMT
> > Leonard the Committed <leoth...@gmail.com> wrote: ...
> >> Thanks for the buildscript!
> >
> > Where did you find the build script? I haven't found any on Douglas'
> > site or inside the package. Or, is it just a build script that comes
> > with Slack64 with a couple of trivial changes?
> >
> I did not post the build script, just the package. The build script that I
> made is a trivial modification of the one provided by Slack 13.0. The
> slackbuild provided by Slackware64 actually builds from the source code;
> The one provided by Slack 13.0 uses a compiled binary obtained directly
> from Mozilla. The build script applies some patches and some directory
> fixups. AFAIK, the only other file which must be patched is
> mozilla-firefox-simple.diff.gz
Thank you for the reply, Douglas. I have recently played a bit with
compiling FF from source. I was surprised to find out there are just
one or two FF build scripts available in the Net other than the one
that ships with Slack64. (I don't mean a script to repack tarballs
provided by mozilla.org.) That's why I was interested to look at
another one, from a trusted source :-)
Thank you!
--
Regards,
Mikhail
Leonard the Committed
> On Fri, 06 Nov 2009 18:52:10 +0000, Leonard the Committed wrote:
>
>>> I modified the slackbuild yesterday and created the tgz:
>>>
>>> http://www.xmission.com/~ddmayne/slackware/mozilla-firefox-3.5.5-
i686-1-
>> dm.tgz
>>> http://www.xmission.com/~ddmayne/slackware/mozilla-firefox-3.5.5-
i686-1-
>> dm.tgz.md5
>>>
>>> The package's md5sum is:
>>> 7605a02240bc38712cb1abfa5aba658f mozilla-firefox-3.5.5-i686-1-dm.tgz
>>>
>>> Note: I haven't tested if this will fix this specific problem.
>>
>> My guess is that I need to install the nvidia driver. It's not been put
>> on because my video needs are basic, no fancy screen savers or heavy 3D
>> use. Thanks for the buildscript! I much prefer 12.2 right now and
>> compiz, KDE4 and such dont interest me.
>>
>> What I see is updates on build scripts pretty much stop half way
>> through the next current cycle. As to compiling, I'm rather ignernt at
>> it, and every time I see error messages flying by then cant get it to
>> run, I drop off my interest. That slackbuild is WAY cool. Thanks!
>>
> To followup: I tested firefox-3.5.5 on Slackware 12.2 with an ATI
> rage128 video board. This setup still shows the corruption on certain
> webpages, including www.slackware.com.
>
> I decided to check if the flaw shows up under Slackware 13.0. I upgraded
> the above system to 13.0, and retested. This appears to fix the bug.
> Slackware 13.0 includes a lot of upgrades to X. This was my first 13.0
> install and it works very smoothly.*
>
> *I did run into the "black screen" flaw discussed here on an earlier
> thread. Luckily, it was fixed when I deleted xorg.conf and /* did not */
> run xorgsetup, as is usually done. Apparently, The new x.org works
> without the file, xorg.conf.
Moved over to Slack 13 on a spare partition and installed KDE3. All is
good now. BTW, Xorg did NOT pick up my card and the new xorg file looked
a bit unfamiliar to me so I copied my xorg.conf file over to 13 and it
works.
Eef Hartman
> Thank you for the reply, Douglas. I have recently played a bit with
> compiling FF from source. I was surprised to find out there are just
> one or two FF build scripts available in the Net other than the one
> that ships with Slack64
That is, among others, because Mozilla very much frowns on "other then
their own" versions of Firefox/Thunderbird etc (even to the point that
they forbid you to use the NAME Firefox (etc.) for it).
As they currently do not supply 64-bit versions the 64-bit builds are
tolerated, but almost all of the distributions use "repacked binaries"
for the 32-bit version to avoid those (copyright) problems with the
Mozilla team.
I must admit I can understand their reasons a bit, this way you got
a "standard" version of Firefox etc. on all Linux distro's.
--
*******************************************************************
** Eef Hartman, Delft University of Technology, dept. SSC/ICT **
** e-mail: E.J.M....@tudelft.nl - phone: +31-15-278 82525 **
*******************************************************************