#Echofon not working update
#Echofon not working software

It gave me a persistent “401” error, which meant that it wasn’t working with Twitter’s API. *Do NOT click the Reset button on the Safe Mode start windowEarlier this afternoon, I tried to open up Echofon, my desktop Twitter client of choice. *Switch to the DEFAULT theme: Firefox/Tools > Add-ons > Appearance Start Firefox in ] to check if one of the extensions (Firefox/Tools > Add-ons > Extensions) or if hardware acceleration is causing the problem. You can delete the user.js file if you didn't create this file yourself. The user.js file is read each time Firefox is started and initializes preferences to the value specified in this file, so preferences set via user.js can only be changed temporarily for the current session. You can check its content with a plain text editor (right-click: 'Open with' do not double-click). Do NOT click the Reset button on the Safe Mode start window.Switch to the DEFAULT theme: Firefox/Tools > Add-ons > Appearance.Start Firefox in Safe Mode to check if one of the extensions (Firefox/Tools > Add-ons > Extensions) or if hardware acceleration is causing the problem.

Read this answer in context 👍 33 All Replies (9) Firefox 35 requires you to change it back. So, anybody reading this for future reference, you may or may not have changed this setting sometime in 2013. Funny thing, though, doing the opposite has been a proven solution for people having this issue in the past. I changed it to true and restarted and this fixed everything. Pretty sure they're extension-related, so I won't touch them.Īre there any media prefs that do not have the default value?Īs I said, was set to false and it was the only entry with that search term that was not set to default.

#Echofon not working software

The user.js file is only present if you or other software has created this file and normally it wouldn't be there. Your System Details list shows that you have a user.js file in the profile folder to initialize prefs each time Firefox starts. I tried turning off hardware acceleration earlier but that wasn't it either. Flash and Java have been updated to the latest versions.Ĭor-el said Start Firefox in Safe Mode to check if one of the extensions (Firefox/Tools > Add-ons > Extensions) or if hardware acceleration is causing the problem.Īs I said, safe mode does not solve the problem. I think Vimeo uses HTML5, but it's the only non-Flash video site I could find that still works. If I could just figure out which line(s) in the prefs.js file was causing the issue, I would delete/modify it myself in Notepad.įor the record, I already had set to false. It's definitely something Mozilla changed but forgot to alter/remove an old setting that's gumming up the works.

#Echofon not working update

It also downloaded the update to Firefox 35 in the background and as soon as I restarted it, the HTML5 videos were broken. I tested it with the Vine website, all videos worked. It was using version 34.0.5 and everything was fine with that version. To be absolutely certain, I turned on my laptop that had the same exact extensions and settings imported to it from this computer with FEBE a while back. I know the problem is with the update to Firefox 35 specifically because everything was working fine before and stopped working after.

The problem is solved by using a fresh profile or deleting the prefs.js file, but this is not an option for me, as restoring all my settings from scratch would be a time-consuming hassle I'd rather not deal with. Switching to safe mode does not fix the problem.

I do have NoScript, but disabling or removing it does not fix the problem. I updated to Firefox 35 recently and now HTML5 videos will not work.