为提升您的使用体验,本站正在维护,部分功能暂时无法使用。如果本站文章无法解决您的问题,您想要向社区提问的话,请到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 提问,我们的支持社区将会很快回复您的疑问。

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

Firefox 3.6.4 linux - crashes on start

  • 9 个回答
  • 108 人有此问题
  • 3 次查看
  • 最后回复者为 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

所有回复 (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.