刚才博客写得差不多了,firefox自动崩溃了,没有任何迹象。真的是受不了了,最近Firefox经常自动崩溃,其它时候还好,写博客的时候崩溃了,而且没保存,真的是很烦。

受不了了,最近Firefox怎么了?

One thought on “受不了了,最近Firefox怎么了?

  • July 25, 2009 at 10:40 am
    Permalink

    升级firef至3.5.1时failed了
    >>> Emerging (1 of 2) net-libs/xulrunner-1.9.1-r1
    * firefox-3.5.1-source.tar.bz2 RMD160 SHA1 SHA256 size 😉 … [ ok ]
    * xulrunner-1.9.1-patches-0.2.tar.bz2 RMD160 SHA1 SHA256 size 😉 … [ ok ]
    * checking ebuild checksums 😉 … [ ok ]
    * checking auxfile checksums 😉 … [ ok ]
    * checking miscfile checksums 😉 … [ ok ]
    >>> Unpacking source…
    >>> Unpacking firefox-3.5.1-source.tar.bz2 to /var/tmp/portage/net-libs/xulrunner-1.9.1-r1/work

    bzip2: Data integrity error when decompressing.
    Input file = /var/tmp/portage/net-libs/xulrunner-1.9.1-r1/distdir/firefox-3.5.1-source.tar.bz2, output file = (stdout)

    It is possible that the compressed file(s) have become corrupted.
    You can use the -tvv option to test integrity of such files.

    You can use the `bzip2recover’ program to attempt to recover
    data from undamaged sections of corrupted files.

    tar: Unexpected EOF in archive
    tar: Unexpected EOF in archive
    tar: Error is not recoverable: exiting now
    *
    * ERROR: net-libs/xulrunner-1.9.1-r1 failed.
    * Call stack:
    * ebuild.sh, line 49: Called src_unpack
    * environment, line 5223: Called _eapi0_src_unpack
    * ebuild.sh, line 593: Called unpack ‘firefox-3.5.1-source.tar.bz2’ ‘xulrunner-1.9.1-patches-0.2.tar.bz2’
    * ebuild.sh, line 386: Called _unpack_tar ‘bzip2’
    * ebuild.sh, line 361: Called die
    * The specific snippet of code:
    * assert “$myfail”
    * The die message:
    * failure unpacking firefox-3.5.1-source.tar.bz2
    *
    * If you need support, post the topmost build error, and the call stack if relevant.
    * A complete build log is located at ‘/var/tmp/portage/net-libs/xulrunner-1.9.1-r1/temp/build.log’.
    * The ebuild environment file is located at ‘/var/tmp/portage/net-libs/xulrunner-1.9.1-r1/temp/environment’.
    *
    !!! When you file a bug report, please include the following information:
    GENTOO_VM= CLASSPATH=”” JAVA_HOME=”/etc/java-config-2/current-system-vm”
    JAVACFLAGS=”” COMPILER=””
    and of course, the output of emerge –info

    >>> Failed to emerge net-libs/xulrunner-1.9.1-r1, Log file:

    >>> ‘/var/tmp/portage/net-libs/xulrunner-1.9.1-r1/temp/build.log’

    * Messages for package net-libs/xulrunner-1.9.1-r1:

    *
    * ERROR: net-libs/xulrunner-1.9.1-r1 failed.
    * Call stack:
    * ebuild.sh, line 49: Called src_unpack
    * environment, line 5223: Called _eapi0_src_unpack
    * ebuild.sh, line 593: Called unpack ‘firefox-3.5.1-source.tar.bz2’ ‘xulrunner-1.9.1-patches-0.2.tar.bz2’
    * ebuild.sh, line 386: Called _unpack_tar ‘bzip2’
    * ebuild.sh, line 361: Called die
    * The specific snippet of code:
    * assert “$myfail”
    * The die message:
    * failure unpacking firefox-3.5.1-source.tar.bz2
    *
    * If you need support, post the topmost build error, and the call stack if relevant.
    * A complete build log is located at ‘/var/tmp/portage/net-libs/xulrunner-1.9.1-r1/temp/build.log’.
    * The ebuild environment file is located at ‘/var/tmp/portage/net-libs/xulrunner-1.9.1-r1/temp/environment’.
    *

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.