md5=5489aa88535780013d5f183b4fa08393 008-Firefox-32.0.3-en-US-i686-1sw.xzm
md5=a95e36ac4464e93b5ab6baba7dd2cdc4 008-Firefox-32.0.3-fr-i686-1sw.xzm
md5=539d49d155c42e9da41a842d3258c8e2 008-Firefox-32.0.3-it-i686-1sw.xzm
md5=f67398f4092cbd39bb77fb6e72d769dc 008-Firefox-32.0.3-es-i686-1sw.xzm
md5=a24d39b1e866a6f23540c06cd3d53991 008-Firefox-32.0.3-ro-i686-1sw.xzm
https://mediencenter.t-online.de/auth/g ... EEB9B6F88A
Firefox Release 32.0.3 en-US/fr/it/es/ro
-
- Full of knowledge
- Posts: 2564
- Joined: 25 Jun 2014, 15:21
- Distribution: 3.2.2 Cinnamon & KDE5
- Location: London
Re: Firefox Release 32.0.3 en-US/fr/it/es/ro
Thanks for ff32.0.3. SeaMonkey couldn't make it past Telekom, so had to use distro ff to reach file. Couldn't open menu on distro ff. However ff32.0.3 worked, but unfortunately terribly slow sometimes taking up to a minute to respond to horizontal scroll. Obviously some sort of looping going on, which only noticeable on slighltly outdated m/c. Distro Opera also had same problem.
Linux porteus 4.4.0-porteus #3 SMP PREEMPT Sat Jan 23 07:01:55 UTC 2016 i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB
- Ole
- Black ninja
- Posts: 73
- Joined: 01 Aug 2014, 21:12
- Distribution: Porteus 32 / Wifislax / Slackw
- Location: Bochum - Germany
Re: Firefox Release 32.0.3 en-US/fr/it/es/ro
Hi Bogomips... there is no way to reproduce the described malfunction on my side. Only a deeper analyze could bring light.
All modules are directly compiled from Mozilla source, verified and testeted for basic functions with 3.0.1 KDE...
You are the first and only with this report.
My read is another problem with this behavior as one visible result.
Let me know if there is no progress with this at all.
All modules are directly compiled from Mozilla source, verified and testeted for basic functions with 3.0.1 KDE...
You are the first and only with this report.
My read is another problem with this behavior as one visible result.
Let me know if there is no progress with this at all.