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?
由 Vici 於 修改
Just updated to Fx31b6 and now Troubleshooting Information is back to normal. Thanks for the fix. :)從原來的回覆中察看解決方案 👍 0
Just adding a screenshot.
Double post. Sorry.
由 Vici 於 修改
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. :)
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.
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 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 於 修改
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)
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.
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.