From: faeychild on


The short story to skip the pain.

I was modifying the 'about:config" settings and Firefox refused to start. I
have tracked the problem down to

network.dns.disableIPv6 in prefs.js

If set to true Firefox wont start.
If stared from the desktop icon I have to wait for it to time out
If started from the command line It reports a segmentation fault.

If disableIPv6 is set false, firefox starts OK

ideas anyone?

--
faeychild
Running kde on 2.6.29.6-desktop-3mnb kernel.
Mandriva Linux release 2009.1 (Official) for i586

From: Bit Twister on
On Fri, 26 Feb 2010 17:16:07 +1100, faeychild wrote:
>
>
> The short story to skip the pain.
>
> I was modifying the 'about:config" settings and Firefox refused to start. I
> have tracked the problem down to
>
> network.dns.disableIPv6 in prefs.js
>
> If set to true Firefox wont start.
> If stared from the desktop icon I have to wait for it to time out
> If started from the command line It reports a segmentation fault.
>
> If disableIPv6 is set false, firefox starts OK
>
> ideas anyone?

Get newer release :)
# grep -i ipv6 ~browser/.mozilla/firefox/*default/prefs.js
user_pref("network.dns.disableIPv6", true);
From: Bit Twister on
On Fri, 26 Feb 2010 08:14:20 +0000 (UTC), Bit Twister wrote:
> On Fri, 26 Feb 2010 17:16:07 +1100, faeychild wrote:
>>
>>
>> The short story to skip the pain.
>>
>> I was modifying the 'about:config" settings and Firefox refused to start. I
>> have tracked the problem down to
>>
>> network.dns.disableIPv6 in prefs.js
>>
>> If set to true Firefox wont start.
>> If stared from the desktop icon I have to wait for it to time out
>> If started from the command line It reports a segmentation fault.
>>
>> If disableIPv6 is set false, firefox starts OK
>>
>> ideas anyone?
>
> Get newer release :)
> # grep -i ipv6 ~browser/.mozilla/firefox/*default/prefs.js
> user_pref("network.dns.disableIPv6", true);

Maybe an ipv6 on the default home page or because of a safebrowsing
scan of a link or scan.

I also set/add
user_pref("browser.download.manager.scanWhenDone", false);
user_pref("browser.safebrowsing.enabled", false);
user_pref("browser.safebrowsing.malware.enabled", false);
user_pref("browser.search.update", false);
user_pref("geo.enabled", false);
user_pref("network.dns.disableIPv6", true);
user_pref("network.dns.disablePrefetch", true);
user_pref("network.prefetch-next", false);

Have you disabled ipv6 on 2009.1. I have used these in the past.
echo "install ipv6 /bin/true" >> /etc/modprobe.conf
echo "alias net-pf-10 off" >> /etc/modprobe.conf
echo NETWORKING_IPV6=no >> /etc/sysconfig/network

For 2010.x I use
echo "alias ipv6 off" >> /etc/modprobe.conf
From: faeychild on
Bit Twister wrote:


>>
>> Get newer release :)

Ha Ha I am full of those ideas.


>> # grep -i ipv6 ~browser/.mozilla/firefox/*default/prefs.js
>> user_pref("network.dns.disableIPv6", true);

I understand the first line but the purpose of the second has me confused.


>
> Maybe an ipv6 on the default home page or because of a safebrowsing
> scan of a link or scan.
>
> I also set/add
> user_pref("browser.download.manager.scanWhenDone", false);
> user_pref("browser.safebrowsing.enabled", false);
> user_pref("browser.safebrowsing.malware.enabled", false);
> user_pref("browser.search.update", false);
> user_pref("geo.enabled", false);
> user_pref("network.dns.disableIPv6", true);
> user_pref("network.dns.disablePrefetch", true);
> user_pref("network.prefetch-next", false);

I will check these out coupled with the list in Linux gazette
>
> Have you disabled ipv6 on 2009.1. I have used these in the past.
> echo "install ipv6 /bin/true" >> /etc/modprobe.conf
> echo "alias net-pf-10 off" >> /etc/modprobe.conf
> echo NETWORKING_IPV6=no >> /etc/sysconfig/network
>
> For 2010.x I use
> echo "alias ipv6 off" >> /etc/modprobe.conf

I only had one of these entries. It's strange what you imagine you have done
only to find out you didn't.

Well after all the IPv6 lines were written and IPv6 was disabled on Firefox,
the browser started. (surprise)

But wouldn't connect :-(. While on the way to check resolv.conf I had a
look at hosts.
The entire formatting was scrambled "AGAIN". No separate entry of one per
line, just a big scrambly block of text.
Quite an achievement considering that after the last time it happened I left
the file permissions read only.

After copying over the bakup file, Firefox runs OK.
I can't see how the hosts file would have made any difference to Firefox

So thanks Bits. We are back on the air again.


--
faeychild
Running kde on 2.6.29.6-desktop-3mnb kernel.
Mandriva Linux release 2009.1 (Official) for i586

From: Bit Twister on
On Sat, 27 Feb 2010 10:10:21 +1100, faeychild wrote:
> Bit Twister wrote:
>
>
>>>
>>> Get newer release :)
>
> Ha Ha I am full of those ideas.
>
>
>>> # grep -i ipv6 ~browser/.mozilla/firefox/*default/prefs.js
>>> user_pref("network.dns.disableIPv6", true);
>
> I understand the first line but the purpose of the second has me confused.

That was the result from the grep to show you I was using the same
keyword and value which are working for me. Your change(s) in
about:config get written into prefs.js.

> Well after all the IPv6 lines were written and IPv6 was disabled on Firefox,
> the browser started. (surprise)
>
> But wouldn't connect :-(. While on the way to check resolv.conf I had a
> look at hosts.
> The entire formatting was scrambled "AGAIN". No separate entry of one per
> line, just a big scrambly block of text.

Sounds like you are using 127.x.x.x for blocking ad sites and whatnot.
I use privoxy with http://www.neilvandyke.org/privoxy-rules/ to block
ad sites. Using https://www.opendns.com dns servers to help block
malware sites.

> Quite an achievement considering that after the last time it happened I left
> the file permissions read only.

Oh yeah, the famous /etc/hosts dinked up by MCC networking gui tool
Feature. :(