How to fix Ubuntu/Firefix since last update?

Have you tried making a new profile? You can do this by renaming ~/.mozilla

I assume you do not use Thunderbird for your email client. If you do then you need to rename a different folder.

Does it help?

Affirmative: I have both tried resetting Firefox to original and deleting and creating a new profile.Neither of these has any effect. The thing is Every Time this happens (Which is every Time I start up Firefox and attempt to do anything with it which initially requires Entering a Password to log into any Web Site..
I also get The pop-Up UBUNTU has encountered an Internal Error.
Which is why this question is being asked here.
I have all error reporting notifications to Ubuntu turned on. And I replay 'Continue' to the Pop-up prompt.
But so far in the almost a month since a complete and clean reinstall of Ubuntu because this problem first presented itself after a May 2017 UBUNTU Update.. No Fix from Ubuntu for this Internal error has been forthcoming.

For diagnostic purposes please provide the output of the following commands:

uname -a
lsb_release -crid
sudo dpkg --audit
apt-cache policy Firefox

You need not use the Firefox about:config screen to disable IPV6, but you can disable IPV6 for the whole system via Ubuntu's network configuration dialogue if you want.

Are there any further details to the "Ubuntu has encountered an internal error" message?
At least the name of the package that created that crash would be important to know.

This question was expired because it remained in the 'Needs information' state without activity for the last 15 days.

uname -a
Linux (Name) 3.13.0-121-generic #170-Ubuntu SMP Wed Jun 14 09:05:46 UTC 2017 i686 i686 i686 GNU/Linux

lsb_release -crid
Distributor ID: Ubuntu
Description: Ubuntu 14.04.5 LTS
Release: 14.04
Codename: trusty

sudo dpkg --audit
(Prompts for password)
sudo dpkg –audit
no response: Cursor stops blinking until Terminal Minimized and then restored.

apt-cache policy Firefox
firefox:
  Installed: 54.0+build3-0ubuntu0.14.04.1
  Candidate: 54.0+build3-0ubuntu0.14.04.1
  Version table:
 *** 54.0+build3-0ubuntu0.14.04.1 0
        500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main i386 Packages
        500 http://security.ubuntu.com/ubuntu/ trusty-security/main i386 Packages
        100 /var/lib/dpkg/status
     28.0+build2-0ubuntu2 0
        500 http://us.archive.ubuntu.com/ubuntu/ trusty/main i386 Packages

Additionally: Friday, June 23, 2017. 07:00PM PDT. Facebook did something to Crash the Firefox Browser. Upon Reboot found that no applications will start in Ubuntu unless started in 'Recovery Mode' FSCK' at first run did not show and file errors. on a subsequent run could not resolve ./ and prompted to 'Run FSCK manually' --How do you run FSCK manually? Now Ubuntu prompts --Unknown System Error, and my installation of Synaptic Package Manager Will Not Start either in Ubuntu Normal Nor Recovery mode.

(As you might guess, I am posting this under 'Recovery Mode.')

If you get a 'Run FSCK manually' message, then you have an inconsistency problem on your hard disk.

I suggest that you boot your system from an Ubuntu installer (on DVD or bootable USB stick) in the 'Try Ubuntu without installing' mode, open a terminal window and perform a file system check with the command "sudo fsck /dev/sda1" (or /dev/sda2, or whatever the name is of the partition in question).

Thank you Manfred for the vital information on how to run FSCK manually. The 'Inconsistency' usually, and in this case, was as usual the web browser's /tmp files directory. somehow the browser had been Remotely Reset without my having done it. I had to restore all of my Clearing All Browser Settings and time frame to 'Everything' in order to delete the offending /tmp files. As well as reconfigure turning IPV6 and IPV6 notify to User Set DISABLED in about:config Yet again.

Is there an easy way to do this in the Ubuntu Linux Operating System as well? After a good number of 'people I know' had been 'Server Spoofed' via their Wireless Routers, we ONLY use HARD WIRED Cable Routers now. The problem is, 'The Industry' Still Does Not Manufacture ANY IPV6 capable Hard Wired Routers. And until they do, everyone else is attempting to Force a standard on the end users That The Industry Still Does NOT support! And they are attempting to Force IPV6 and IPV6 Notify through Cable Routers that Only Support IPV4! This leads to all sorts of Browser and Application 'Failure to Function' in Ubuntu for Hard Wired Router Users. As Example, when IPV6 is in the process of attempting to be forced in Ubuntu, No Applications can be Opened unless Ubuntu is in 'Recovery Mode' Which are loaded as READ ONLY files.

2 separate Questions: 1. How do you 'easily' turn off or Disable IPV6 NOTIFY in Ubuntu in such a way that the settings are not lost on reboot? 2.How do you 'easily' turn off or Disable IPV6 in Ubuntu in such a way that the settings are not lost on reboot?

I have read the 'threads' on disabling IPV6 in Ubuntu: but all of them are Extremely Convoluted, and always seem leave out the Critical Information (for us non techie folks) as to How to Implement the necessary File Creation and File Modifications When They Are Read Only in 'Recovery Mode'!!! There has got to be a better and easier way of implementing this for Everyone that uses Hard Wired Cable Routers...??

Additional: a majority of commentators on the Disabling IPV6 in Ubuntu Threads seemed to be of the opinion that the ascribed methods of disabling IPV6 in Ubuntu didn't seem to work, or at least not satisfactorily.

The easiest way to disable IPv6 that I know is this: https://askubuntu.com/a/768022

The interesting part is that once IPV6 has been disabled in the Firefox Browser, when I look at the Internet Connection part of the Ubuntu Desktop it shows IPV6 as being Disabled. -- I am not a techie, just someone that uses Ubuntu ever since MS used Security Essentials Updates to render THREE COA Windows XP Installations On Three Separate Computers (Which I had been using for CERN test for theory via BOINC) into Useless Bricks in attempt to FORCE sales of Windows 8...
--All Ii know is that ever since the Ubuntu Kernal and Firefox Browser updates in May of 2017. Suddenly the Browser is spending over 90 Percent (Hours) of its time Frozen in a grayed out state, with the ability to access ANY applications in Ubuntu Also Disabled. while someone or something is keeping the Hard Drive Constantly Occupied. I never had this problem with Ubuntu or Firefox before those May 2017 updates. And I want it fixed. Otherwise This operating system has also, for all practical intents and purposes, been rendered into a useless Brick!

Do other browsers work OK? Chrome etc...?

What you write is somewhat contradictory.
Why should and how could disabling IPv6 in the private settings of the firefox browser modify the system-wide network configuration?

Have you modified the grub boot command to disable IPv6?

Can you boot your system normally, or do you have to select 'recovery mode' that the system boots at all?

What is the output of the commands (when booted normally):

ifconfig -a
sudo dpkg --audit

(The second command will either produce output or will give no output at all and return to the command prompt. "Cursor stops blinking until Terminal Minimized and then restored" is completely strange.)

Friday, June 30, 2017. 04:30PM PDT. I am trying to remain using Only the Default Firefox Browser as any other normal 'non techie' user would do. I do not know the why, as to IPV6 also showing disabled in Ubuntu along with the Firefox Browser having IPV6 disabled. You'll have to ask them about that.

--Meanwhile: After installing today's Ubuntu Update at the time referenced above. I am back to square one. In normal boot I cannot open ANY applications now, and Mouse Controls and Keyboard remain Dead and Unresponsive while the hard Disk light remains in a constant state of activity. The only functionality I have now is after rebooting to 'recovery mode'. Period. --I just want this fixed.

..Okay after accessing this thread and then rebooting I managed to get Ubuntu to boot into normal mode and access some applications. Not the 'old' Ubuntu Software Center, that now remains unresponsive. However the Firefox Browser is Still having its odd behaviour that is has had since the May 2017 updates. It spends the First full Hour of time after being started Greyed Out for several minutes after ANY user interaction with any Web Page 'click on information entry box;', link to open an interactive page function, etceteras. Once it gets past that first HOUR it seems to then behave 'normally' Except.. Once every Hour Beginning from the time it was started up.. It greys out again for a Full Five Minutes disabling ALL interactions with both the browser AND ANY UBUNTU APPLICATIONS during these times.

As for the Terminal command Responses Requested by Manfred:

~$ ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:11:5b:72:b1:e3
          inet addr:192.168.1.101 Bcast:192.168.1.255 Mask:255.255.255.0
          inet6 addr: fe80::211:5bff:fe72:b1e3/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:9763 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6734 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:11490590 (11.4 MB) TX bytes:951769 (951.7 KB)

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:65536 Metric:1
          RX packets:390 errors:0 dropped:0 overruns:0 frame:0
          TX packets:390 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:32985 (32.9 KB) TX bytes:32985 (32.9 KB)

sudo dpkg –audit
No response

Ideally, Ubuntu Linux Should work flawlessly with whatever they have designated and incorporated to be their 'Default Browser' regardless the end user's overall hardware. If they can no longer accomplish doing that, then they need to drop that browser and re-designate and Incorporate into Ubuntu Linux a new 'Default Browser' that they can function adequately with.

You are misunderstanding our recommendation to try another browser.
We want to help you finding out the root cause of your problem.

If you see that strange unresponsive behaviour only with Firefox, but not with another browser like Chrome, then this is an indication that something must be wrong with your installation of the Firefox browser.
If also another browser shows the same issue, then this would be an indication that it is not firefox's fault, but something else.

I'm not trying to persuade you to use another browser. It's exploring the issue to see if it is isolated to Firefox as a browser or if the underlying issue is with the OS.

Well, here I am yet again back in 'Recovery Mode'. The browser, ANY browser is taking upwards of Twenty Minutes to even Start Up!! Then spends most, if not all of its time greyed out when attempting to key in things like merely signing into this email account for example.. The browser today began this way then.. I noticed what appeared for about a tenth of a second like a background application was being started up in the launch bar.. then the browser appeared to work normally until a Youtube video playback latched up in a 1/2 second recurring loop that required an manual restart to break out of because nothing else in the entire Ubuntu OS was allowed to function because of it. -- Once the browser does get up and running in what seems to be a proper functioning mode.. Then once every Hour it gets crashed again by something causing the Hard Drive to become busy and the browser to freeze up and become unresponsive -- And for this reason, I believe THIS Browser behaviour is being caused by something in the 'polling' that Ubuntu is doing itself.

None of this Failure to Function had been occurring prior to the Simultaneous MAY 2017 Updates of BOTH Ubuntu and the Firefox Browser. This behaviour ONLY occurred AFTER This simultaneous Update. So it is either something which Firefox did OR It Is Something Ubuntu Did in that kernal update. Personally., I just had my upper canines extracted, and am not in the mood to continually have to deal with this without a forthcoming Fix.

For diagnostic purposes I suggest the following:

Boot your system and log in. Do not yet start firefox.
Simultaneously press ctrl-alt-t to open a terminal window
issue the command "top" in this window.
This will show a system monitor with the processes sorted by CPU usage, like this:
http://3.bp.blogspot.com/-GWInIvuzs7Q/T-xpyn03cWI/AAAAAAAAEgY/ihpWGimo5qw/s1600/top-ubuntu.png
Which are the processes on top? How much CPU percentage are they using?
If the system is idle, there should not be much usage. In case that you already have high CPU usage values, then firefox seems not to be the culprit, but something else.
Now start firefox and bring the command line window with the system monitor to the front.
What are now the top processes? How much CPU percentage are they using?
Remark: to end the "top" program you have to press the "q" key.

Haven't done the resources check yet Manfred.. Something has happened that is either compounding this issue Or It may be the Cause.. Finally after several 'Recovery/(Repair of Files with FSCK) Starts. Managed to get things to appear to start normally.. But.. Although the Browser is set to Delete all History and everything on close.. When I started the browser The Default Home Page had been Changed, and NOT by myself from the Default Ubuntu Start Page I prefer to FACEBOOK!! AND all of the Facebook History which should have also been deleted was still there... These Jerks AT Facebook have been Hacking the Browser!!!

If I understand the rolling display correctly:
Compiz using about 1.5%
Firefox uses about 39%

Should the header be denoting '2 users' ? I do not share any Ubuntu User accounts on this system.

the last few days I am having another Firefox Browser related Issue as well. Firefox is messing up the ./tmp directory rather than clearing the history options correctly. I cannot directly shut down the operating system after closing all open applications because of this. I am having to reboot and go through 'Recovery Mode' FSCK to fix this every time before I can correctly shut the computer down.

This Issue IS something Ubuntu/Canonical is doing: After you start up ANY browser, then once about Every Hour, Without ANY warning to the user., They are running some Sort of Operating System Check, WHICH SINCE THE MAY 2017 UPDATE, IS NEITHER BEING DONE SILENTLY NOR IN THE BACKGROUND!! INSTEAD IT CAUSES THE BROWSER TO GREY-OUT AND FREEZE UP. AND CRASH!! IF THE USER UNFORTUNATELY HAPPENS TO BE WATCHING SOME YOUTUBE VIDEO AT THE TIME, IT NOT ONLY GREYS-OUT THE BROWSER, AND CAUSES ALL USER FUNCTIONS AND APPLICATIONS TO BECOME INACCESSIBLE, iT LOCKES THE AUDIO PLAYBACK IN A CONTINUAL 1/2 SECOND LOOP- IN EVERY CASE FORCING THE USER TO HAVE TO DO AN EMERGENCY RESTART AND TO NEED TO RUN FSCK IN RECOVERY MODE IN ORDER TO RECOVER THE OPERATING SYSTEM!!

THIS IS UNACCEPTABLE!! I WANT IT FIXED!! NOW!!

Your latest output in your other question document https://answers.launchpad.net/ubuntu/+source/ubuntu-docs/+question/644787 shows disk access error every minute.

For me this indicates that the root cause of your strange behavior are hardware problems with your hard disk (or eventually the hard disk controller).

Sunday July 09, 2017. 05:45PM PDT. --Manfred., This is the third brand new, (albeit antiquated) Hard Drive that I have done a Fresh and Clean Ubuntu Install on in the last three Months!! I believe it is something as yet Unresolved with the Recent Ubuntu Kernals in regards to addressing OLDER HARDWARE that is causing this issue rather than the hard drives themselves. --That said., I am back to square one after yet Another Failure of the Firefox Browser in its FAILING to implement its 'multitasking' correctly.. Yet again causing a complete Freeze up of Both the Firefox Browser and The Ubuntu Operating System. Forcing once again an emergency restatrt, and having to run FSCK Four Times Over to correct the Corruption of the ./tmp directory YET AGAIN!! And once more, all Ununtu Basic Applications Failing to be able to start Because of it!!

Sunday, July 09, 2017. 06:15PM PDT.
And you cannot tell me that someone has not been hacking (or attempting to hack) into your operating system (however clumsily), When while on Facebook, suddenly your screen goes black, then the Guest Log In screen comes up., And you can see them trying to remotely enter a password!! (You see asterisks being filled in into the Password box without you touching the keyboard!!!)

Also the fact that you have to run a file system check over and over again is a strong indication that there is something wrong with your hard disk (or eventually the hard disk controller).

In case that you are sure that the error was introduced with the newest version of the kernel packages, you can select booting into an older version of the kernel by selecting advanced options in the grub menu. But I do not expect that this will help.

Of course switching to an older version won't help. Because it is Camonical's aggressive scanning of the entire hard drive now at a frequency of once every half hour that is freezing up the entire operating system and not just the browser and CRASHING THEM!!! What part of three BRAND NEW IDE HARD DRIVES WITH FRESH UBUNTU INSTALLS didn't you understand. THIS ISSUE IS NOT.. NOT BEING CAUSED BY THE HARD DRIVES.. IT IS IN HOW CANONICAL IS ADDRESSING AND CRASHING THE HARD DRIVES, SINCE THEY PARTNERED WITH MICROSOFT AND RELEASED THEIR MAY 2017 UPDATES!!

Unlike the rest of you whom do not seem to be able to comprehend this, I do not have thousands and thousands of dollars to shell out for computer systems every new model or hardware that comes out. (One of the many reasons I went to a Linux distro to begin with). Neither my Hard Wired Router (The "Industry Still DOES NOT MANUFACTURE ANY IPV6 CAPABLE HARD WIRED ROUTERS) Nor my older mother Board and its BIOS (Not UEFI) can handle Either IPV6 Nor UEFI.!! Canonical in its Aggressive Half-Hourly Hard Drive Scanning is attempting to Force IPV6 through Hardware that Can NOT support it.

My motherboard and its BIOS can not even properly handle SATA so I am forced to have to use IDE. Apparently Canonical's newer incarnations, and especially its aggressive half-hourly Hard Drive Scanning routines, are no longer accounting for the possibility of interfacing with older hardware any longer.

Please stop your rant and provide facts.

The difference between IPv4 and IPv6 is found in OSI layer 3 (Network Layer). The BIOS does not interfere there. I do not understand how your BIOS should be able to handle IPv4 but not v6.
I already gave instructions how to fully disable IPv6. Have you tried doing this?
If your motherboard and its BIOS cannot handle UEFI, then you have to use "standard BIOS" installation. Why would that pose a problem? There are thousands of systems running without EFI but with standard installation.
Why are you sure that switching to an older kernel version cannot help? You always claim that your problems started with the last update.
If you have problems with your router, please do not blame Ubuntu, but direct you complaints to your provider.

I recommend that you try finding out which of the installed programs the one is that's responsible for that half-hourly disk activity increase. You can use "top" and "sudo iotop" for checking.

This behaviour did start with the May 2017. Simultaneous Ubuntu Linux and Firefox Browser update. I can't run Terminal or the Top command when this happens, because when it happens Both ALL functioning of the Operating System And the Browser become completely Disabled to ALL user input and functioning.

Please pardon my Typographical 'Language and Yelling'.. But this is going beyond Reason..

I would also really like to know precisely Who or what is causing my Hard Drive to be REMOTELY caused to become active and my Operating System DISABLED (OR CRASHED) for a full twenty minutes of time at half an hour intervals, during which they scan my hard drive -- WITHOUT ANY PROPER AND SPECIFIC U.S. ARTICLE FOUR WARRANT STATING SPECIFICALLY WHOM OR WHAT IS TO BE SEARCHED AND ALSO SPECIFICALLY WHAT IS TO BE SEARCHED FOR.

THIS IS THE ISSUE AND THE CAUSE OF THE ISSUE!

If you want to know what the process is that uses the CPU and accesses the hard disk, use top and iotop, as already written above.
If you are not able to start these programs when thy system is busy, you have to start them before and wait for the issue to appear.

Well Manfred, I did as you suggested and started the top command first. And discovered Precisely what 'Program' is causing the issue: updatedbm+ ..This 'command' is Remotely done by Canonical.

On Ubuntu systems there is a utility that helps finding files on your hard disk with the locate command.
There is a database where all file names are stored, and this database is updated periodically with the updatedb command.

There is absolutely no "This 'command' is Remotely done by Canonical" involved.
Search your cron database and you will see an entry for periodically running updatedb.

What is the output of the command
cat -n /etc/cron.daily/mlocate

Suggestions:
1. run "sudo updatedb" manually and check what there is happening
2. disable the periodic execution of the database update (with the consequence that the locate command does not produce meaningful output).

The updatedb command consumes a considerable amount of system resources. How much memory does your system have (output of the command "free")?

What is the output of the command
~$ cat -n /etc/cron.daily/mlocate
     1 #! /bin/bash
     2
     3 set -e
     4
     5 [ -x /usr/bin/updatedb.mlocate ] || exit 0
     6
     7 if which on_ac_power >/dev/null 2>&1; then
     8 ON_BATTERY=0
     9 on_ac_power >/dev/null 2>&1 || ON_BATTERY=$?
    10 if [ "$ON_BATTERY" -eq 1 ]; then
    11 exit 0
    12 fi
    13 fi
    14
    15 # See ionice(1)
    16 if [ -x /usr/bin/ionice ] &&
    17 /usr/bin/ionice -c3 true 2>/dev/null; then
    18 IONICE="/usr/bin/ionice -c3"
    19 fi
    20
    21 flock --nonblock /run/mlocate.daily.lock $IONICE /usr/bin/updatedb.mlocate

How much memory does your system have (output of the command "free")?
                    total used free shared buffers cached
Mem: 1025848 931484 94364 17820 12760 282244
-/+ buffers/cache: 636480 389368
Swap: 1999868 7396 1992472

And., Now as of the Tuesday July 18, 2017. Canonical Ubuntu update
Firefox is taking upwards of TWENTY MINUTES to Start Up after Clicking the Icon in the Launcher to Start it!!!!
(I already tried the “Restore Firefox” option when I first noticed this right after this update.. Nope Still taking TWENTY MINUTES!! (Ans this is supposedly a High Speed Internet connection so rule that out.) --So of what usefulness is Ubuntu, when they keep dumbing down or crashing the very functioning which we the average non-techie would use it for??

Note: Since Partnering with the very same Microsoft which drove me away by intentionally using their Security Essentials Updates to Brick THREE legitimate COA WindowsXP installations on Three computers in attempt to FORCE sales of Windows 8.

It seems to me that your system is running low on memory.

Summing up:
If you have only few memory installed and the system has to start swapping, this slows down the system (because hard disk access is far slower that direct memory access).
updatedb consumes much resources (memory, hard disk reads and CPU).
If updatedb is running on a system with slow CPU and low memory, this will slow down everything on the system.
If you still have hard disk access errors like shown in you r other question https://answers.launchpad.net/ubuntu/+source/ubuntu-docs/+question/644787 then this slows down the system further (because of the time needed for error recovery attempts on the hard disk).

I still cannot see why Canonical, Ubuntu or Microsoft should be blamed.

There was a second Ubuntu base update for the afternoon on Tuesday July 18, 2017. This update did seem to temporarily resolve the issues with Firefox starting up slowly or greying out and crashing.. Up to a certain point. The point at which I had been logged on to Facebook for about an hour: Then suddenly the browser greys out again and I get a pop-up telling me that 'Keyboard and Mouse controls has crashed unexpectedly'.. From this point onward when ever I log specifically on to Facebook (and no other site demonstrates this behaviour). I get not only the greying out, but Keyboard input becomes disabled, and the mouse cursor jumps about that Facebook page erratically and is also disabled from being able to 'reach' the tabs in order to close the page correctly while it is apparently being manipulated. DO NOT rule out the possibility that all of this 'Issue' might actually be the result of someone (at Facebook and on their staff) ILLEGALLY HACKING MY COMPUTER!!

Also: Gee I would love to be able to update my RAM capacity. BUT.. They no longer manufacture CL2 DDR for antique 800Mhz FSB Pentium 4HT Mother Boards any more. At least not that I can find.

Wednesday, July 19, 2017. Canonical Ubuntu just did another small 27kb Base Update. And here is PRECISELY what Ubuntu has to do with it.. Now I am once again back to Square One BECAUSE OF THIS UPDATE!! I ONLY can start up the Browser IN RECOVERY MODE after this update!! In normal mode now if I attempt to start the browser I hear a clicking sound from where the Mother Board switches itself off on shut down, No Applications Can be opened, and the Mouse and keyboard controls become DISABLED and NON Functional!! --It appears to me that just as with Microsoft before you (which you have recently partnered with) you are intentionally bricking the Functionality of the Operating system!!

I am still inclined to blame your hardware.

What is the output of
dmesg | grep ata1.00

Manfred: I just did a BRAND NEW CLEAN INSTALL on a NEW IDE DRIVE last night.. Worked Flawlessly UNTIL FACEBOOK LOADED YET ANOTHER MALWARE ENCODED AD just a few moments ago.. Had to once again go into Recovery Mode, Clear Orphaned Inodes and Recover a Corrupted Root / BECAUSE OF THEIR MALWARE!!!

IT IS NOT THE HARDWARE --IT IS ROOT VIRUSES BEING PROPAGATED BY FACEBOOK!!

I am now back to yet another BRAND NEW IDE DRIVE BEING CLOSE TO BRICKED BY FACEBOOK!!

I do not know what you are doing with Facebook.

What exactly happened that you "... Had to once again go into Recovery Mode ..."?

Well Manfred, as I have 'narrowed down the compounding issues, let me try to explain it this way. 1. The Ubuntu Linux update of Thursday, July 27, 2017. Seemed to reallocate some of the memory addressing to unused memory of the Video Card RAM. (I could tell by the change in GPU fan speed when the system had a temporary memory load that needed it). this alleviated part of the less than ideal Memory situation. 2. I replaced the ATA 133 cable to the Hard Drive this seemed to alleviate the Hard Drive addressing issue somewhat. --But then the COMPOUNDING and as yet Unresolved ISSUES: 3. Google/Youtube HACKIING ROOT in repeated Deletion of the Subscription Files of the Adblock Plus Add On. Resultantly Corrupting Root ./ every time they are doing this I have to go through Recovery Mode, and then Reinstall Adblock Plus to Restore the Missing Subscription Files.. and 4. Facebook also HACKING Root ./ in attempt to FORCE their 'Profile Picture Log In' which I decline to use, and Repeatedly have to Manually Switch off in this Settings Every Time I log in to Facebook. (When We switch this OFF in the SETTINGS They should NOT BE REPEATEDLY TOGGLING IT BACK ON). When they do this ./ Root HACKING, it also causes an entire Operating System Freeze up, and a need to do a Manually (Reset Button) switched Restart into Recovery Mode, (Hold down Shift Key during Boot) and then running FSCK to recover), Every time they do this.

There is no direct access from Facebook to the hard disk that could cause file system inconsistencies.

What exactly happens when you see a Google/Youtube/Facebook attack on you that you have to go to recovery mode and run fsck?

Do you pull the power plug while the computer is running?

This question was expired because it remained in the 'Needs information' state without activity for the last 15 days.

Just fully replaced the Hard Drive ATA 133 cable and upgraded from Ubuntu 14.04 LTS to 16.04 LTS a few days ago. I believe it was on Sunday Night/Monday morning August 14, 2017. I like that 16.04 will now automatically remove Orphaned Inodes at start up or restart. And believe me it often needs to. Because the previously defined problem with the Firefox Browser (or Facebook) still persists. However, the Firefox Browser still takes on average about two minutes from clicking on the Icon in the Unity Bar to actually bringing up the browser, and as has been the case since the May 2017. Updates, it then still remains grayed out for an additional five minutes before actually becoming user functional.

Parenthetically:
When I do Updates: I always bring up Terminal afterwards and run the following commands:
sudo apt-get install -f
sudo apt-get upgrade
sudo apt-get autoremove --purge (That’s two dashes before purge)
I need to do this mainly because there frequently are ‘upgrades’ which the updates themselves seem to miss.

All I can see from the ‘top’ command, is that when the browser issues happen Firefox is using greater than 75% of system RAM. But, the problem only seems to happen when on the Facebook Web Site and its ‘Page Script’ seems to frequently Malfunction. ..So this issue is narrowed down to either something that Facebook is doing, or that the Firefox Browser is doing. Either way, it happens like clockwork once every hour from the timing of starting up the Firefox Browser; ..it will then spend from 15 to 50 full minutes grayed out (once every hour) with all of the operating system as well becoming completely inaccessible while it brings the Hard Drive active during that time. (But at least with Ubuntu 16.04 it is no longer smashing the Hard Drive Read Head Armature against the sidewalls.) --When (the Firefox Browser or Malfunctioning Facebook page script) does this, it invariably leaves a slough of ‘Orphaned Inodes’ in its wake.. Resultantly CRASHING the Browser in a Non-Reportable manner along with the entire Ubuntu Operating System! (But about half the time it will come out of greyed out mode and resume correctly functioning).
--But at least now on restarting the System I can see it automatically cleaning up those ‘orphaned inodes’.
All I can say is this: If it messes with Hard Drives and Operating Systems and resultantly CRASHES them.. It IS a form of MALWARE!!
And It Is NOT the freaking Hard Drive!! (So stop insisting) As I have had to replace a number if them now with brand new drives-- but this Continuing Browser Behaviour Trashes Them!!

Do you have add-ons loaded in firefox?

Can you try using chrome-browser instead of firefox, and does it show the same behavior?

This question was expired because it remained in the 'Needs information' state without activity for the last 15 days.