X
點擊此處開啟此網站的行動版。
Scheduled maintenance: Wednesday, April 1, between 3:30pm and 5:30pm UTC. This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn’t solve your issue and you want to ask a question, we have our support community waiting to help you at @firefox on Twitter

技術支援討論區

Troubleshooting Information - Blank?

已張貼

I've been having no problems so far with Firefox 31.0 Beta Update Channel, however with the latest update (Beta 5) - the Troubleshooting Information page is now completely blank, when it's never been so before. Is there any way to fix this?

I've been having no problems so far with Firefox 31.0 Beta Update Channel, however with the latest update (Beta 5) - the Troubleshooting Information page is now completely blank, when it's never been so before. Is there any way to fix this?

由 Vici 於 修改

被選擇的解決方法

Just updated to Fx31b6 and now Troubleshooting Information is back to normal. Thanks for the fix. :)

從原來的回覆中察看解決方案 0

額外的系統細節

已安裝的外掛程式

  • Google Update
  • Shockwave Flash 14.0 r0
  • Adobe Shockwave for Director Netscape plug-in, version 12.1.2.152
  • NVIDIA 3D Vision plugin for Mozilla browsers
  • NVIDIA 3D Vision Streaming plugin for Mozilla browsers
  • Adobe PDF Plug-In For Firefox and Netscape 11.0.07
  • EagleGet Downloader
  • The QuickTime Plugin allows you to view a wide variety of multimedia content in Web pages. For more information, visit the QuickTime Web site.
  • VLC media player Web Plugin 2.1.3
  • The plug-in allows you to open and edit files using Microsoft Office applications
  • Office Authorization plug-in for NPAPI browsers

應用程式

  • User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Firefox/31.0

更多資訊

提出問題者

Just adding a screenshot.

Just adding a screenshot.

提出問題者

Double post. Sorry.

Double post. Sorry.

由 Vici 於 修改

alan_r 127 個解決方法 1451 個答案

Just for the record, I'm surprised to find mine blank,too(same Fx31b5).

Just for the record, I'm surprised to find mine blank,too(same Fx31b5).

選擇的解決方法

Just updated to Fx31b6 and now Troubleshooting Information is back to normal. Thanks for the fix. :)

Just updated to Fx31b6 and now Troubleshooting Information is back to normal. Thanks for the fix. :)
John99 971 個解決方法 13138 個答案

Mine is blank too. I noticed it recently and think I saw another post saying similar.

It is not something I consider important and have not yet tied down the cause, but it is profile related in so far as it is not all profiles that have this issue.

Mine is blank too. I noticed it recently and think I saw another post saying similar. It is not something I consider important and have not yet tied down the cause, but it is profile related in so far as it is not all profiles that have this issue.
alan_r 127 個解決方法 1451 個答案

Again, just for the record, mine went back to normal on the same update as Vici.

Again, just for the record, mine went back to normal on the same update as '''Vici'''.

由 alan_r 於 修改

提出問題者

Thanks John. Updated again to Fx31b7 and the Troubleshooting Information is still there. :)

Thanks John. Updated again to Fx31b7 and the Troubleshooting Information is still there. :)
John99 971 個解決方法 13138 個答案

Thanks for the feedback Alan & Viki.

Glad it is working again for you both.


On my system

Seen in Mozilla Beta

  • Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Firefox/31.0 ID:20140610163407 CSet: be2f1303b3a0

and also in Canonical Aurora & Mozilla Nightly.

    • Edit and in Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Firefox/31.0 ID:20140703154127 CSet: 56ec82ed9283

The current Mozilla Release is ok.

I am only noticing this in one particular profile. Just mentioning it because I am seeing this and it is a fault I do not normally see; or other than the recent report, recall being mentioned on the forum.

The obvious knock on effect of this is people and maybe the forums automated software may have difficulty providing Troubleshooting Information for support questions.

Especially as others are seeing this as only a temporary issue in Pre Release it is at present more of a curiosity than a problem. I have backed up the troublesome profile and if it does become a problem I should be able to reproduce & investigate.


I will leave the thread open and have marked Viki's post as the solution.

Modified July 6, 2014 9:30:55 AM BST by John99

Further modified - my typos

Thanks for the feedback Alan & Viki. Glad it is working again for you both. ------------- On my system Seen in Mozilla Beta *Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Firefox/31.0 ID:20140610163407 CSet: be2f1303b3a0 and also in Canonical Aurora & Mozilla Nightly. ** '''Edit''' ''and in Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Firefox/31.0 ID:20140703154127 CSet: 56ec82ed9283'' The current Mozilla Release is ok. I am only noticing this in one particular profile. Just mentioning it because I am seeing this and it is a fault I do not normally see; or other than the recent report, recall being mentioned on the forum. The obvious knock on effect of this is people and maybe the forums automated software may have difficulty providing Troubleshooting Information for support questions. Especially as others are seeing this as only a temporary issue in Pre Release it is at present more of a curiosity than a problem. I have backed up the troublesome profile and if it does become a problem I should be able to reproduce & investigate. ------- I will leave the thread open and have marked Viki's post as the solution. Modified July 6, 2014 9:30:55 AM BST by John99 Further modified - my typos

由 John99 於 修改

cor-el
  • Top 10 Contributor
  • Moderator
17851 個解決方法 161563 個答案

Did you check the Browser Console (Firefox/Tools > Web Developer) for JavaScript errors?

Did you check the Browser Console (Firefox/Tools > Web Developer) for JavaScript errors?
John99 971 個解決方法 13138 個答案

Hi cor-el

I get the following

TypeError: "Cu" is read-only resetProfile.js:7
Use of getPreventDefault() is deprecated.  Use defaultPrevented instead. about:support
A promise chain failed to handle a rejection.

Date: Mon Jul 07 2014 14:09:53 GMT+0100 (BST)
Full Message: Error: InternalError: uncaught exception: Buffer is too short (no header)
 
Hi cor-el I get the following <pre> TypeError: "Cu" is read-only resetProfile.js:7 Use of getPreventDefault() is deprecated. Use defaultPrevented instead. about:support A promise chain failed to handle a rejection. Date: Mon Jul 07 2014 14:09:53 GMT+0100 (BST) Full Message: Error: InternalError: uncaught exception: Buffer is too short (no header) </pre>
cor-el
  • Top 10 Contributor
  • Moderator
17851 個解決方法 161563 個答案

Weird error as Cu refers to Components.utils

Are you starting Firefox via a shortcut that specifies the profile (-P <profile>)?

If that is the case then try to use the Profile Manager to select the profile to see if that has any effect.

Weird error as Cu refers to Components.utils *http://mxr.mozilla.org/mozilla-beta/source/toolkit/content/resetProfile.js Are you starting Firefox via a shortcut that specifies the profile (-P &lt;profile&gt;)? If that is the case then try to use the Profile Manager to select the profile to see if that has any effect.
John99 971 個解決方法 13138 個答案

Thanks for looking that up.

It is not too important to me as it is a minor problem with one profile. I am however curious as to what is causing this.

It seems to happen regardless of the method of launching. From the CLI I get errors that, I do not understand but are apparently related when launching this profile for use by >Fx30 e.g. .

 WARNING: .... this.PromiseWalker.walkerLoop@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:742:7

See (1month) http://pastebin.mozilla.org/5532317

Background Details of Install & Launch I normally use the profile manager indirectly because I normally use a Ubuntu/Unity launcher from the Firefox install. (I do not really understand the Unity launcher.) BUT I normally use a manually modified profiles.ini to offer a selection of profiles from that launcher. My day to day working Firefox is a Canonical build of Aurora installed in /usr/lib/... I have other Mozilla Build versions installed for comparison or fallback Mozilla ESR->UX channels in /home/... usually launched by simple clickable scriptfiles or sometimes the standalone profile manager.

Thanks for looking that up. It is not too important to me as it is a minor problem with one profile. I am however curious as to what is causing this. It seems to happen regardless of the method of launching. From the CLI I get errors that, I do not understand but are apparently related when launching this profile for use by >Fx30 e.g. . WARNING: .... this.PromiseWalker.walkerLoop@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:742:7 See (1month) http://pastebin.mozilla.org/5532317 <u>Background Details of Install & Launch</u> I normally use the profile manager indirectly because I normally use a Ubuntu/Unity launcher from the Firefox install. (I do not really understand the Unity launcher.) BUT I normally use a manually modified ''profiles.ini'' to offer a selection of profiles from that launcher. My day to day working Firefox is a Canonical build of Aurora installed in ''/usr/lib/...'' I have other Mozilla Build versions installed for comparison or fallback Mozilla ESR->UX channels in ''/home/...'' usually launched by simple clickable scriptfiles or sometimes the standalone profile manager.