Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Firefox 3.6.4 linux - crashes on start

  • 9 ŋuɖoɖowo
  • 108 masɔmasɔ sia le wosi
  • 1 view
  • Nuɖoɖo mlɔetɔ AnonymousUser

more options

Updated FF from 3.6.3 to 3.6.4, linux version. Wouldn't open.

From terminal, this error occurs:

./firefox-bin: error while loading shared libraries: ./libxul.so: cannot restore segment prot after reloc: Permission denied

Roll back to 3.6.3 immediately, at least the Linux version, as 3.6.4 release was clearly a colossal botch-up and an epic testing fail.


This happened

Every time Firefox opened

Updated FF from 3.6.3 to 3.6.4, linux version. Wouldn't open. From terminal, this error occurs: ./firefox-bin: error while loading shared libraries: ./libxul.so: cannot restore segment prot after reloc: Permission denied Roll back to 3.6.3 immediately, at least the Linux version, as 3.6.4 release was clearly a colossal botch-up and an epic testing fail. == This happened == Every time Firefox opened

All Replies (9)

more options

Thanks for the information. How do i rollback to 3.6.3

thx.

yashesh bhatia venuslabs web solutions.

more options

I have the same problem. I can't find any solution.

more options

If SELinux is installed and in enforcing mode, try:

  '# chcon -t texrel_shlib_t /path/to/firefox/libxul.so'

Thanks.

more options

Hi,

It could be related to iMacros for Firefox, please see http://forum.iopus.com/viewtopic.php?f=11&t=10372

Of course, we are working on this with top priority!

Mathias

more options

Afsar Uddin, changing the context of libxul.so fixed this problem on my machine. Thanks very much Steven Lilley sk8geek FC6

more options

The fix by Afsar Uddin also worked for me. Thanks.

more options

Afsar Uddin - you rock! Your fix worked on my machine as well.

more options

Afsar Uddin, Your solution fixed the problem on my machine. I run CentOS Linux. Thank you.

more options

Changing context solved the problem on my machine.