February 18 Upgrades now Ubuntu and Browser Repeatedly Crashing Frequently

Both (Not 'Bot) UPGRADES (Not Updates).

What is the output of:

lsb_release -a; uname -a; apt-cache policy firefox

Thanks

2019-02-21
The following packages will be upgraded:
  base-files ghostscript ghostscript-x libgs9 libgs9-common
5 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

After this 'upgrade' Now even the Facebook Website (Which Was working perfectly fine with the Default Firefox Browser before this 'Upgrade') is repeatedly freezing up the Ubuntu Linux Operating System and Crashing it!!

So which of you are Either going to FIX this back to previous Operability, or give me the Thousands of US Dollars (which I do not have at today's overly Inflated Prices due to Crypto Currency Miners) for a New Computer?!!

Just make this Existing Hardware work like it did Before Inconsiderate others Screwed it up!

Actionpartnership (andrew-woodhead..

lsb_release -a; uname -a; apt-cache policy firefox
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.6 LTS
Release: 16.04
Codename: xenial
Linux bear 4.15.0-45-generic #48~16.04.1-Ubuntu SMP Tue Jan 29 18:03:19 UTC 2019 i686 i686 i686 GNU/Linux
firefox:
  Installed: 65.0+build2-0ubuntu0.16.04.1
  Candidate: 65.0+build2-0ubuntu0.16.04.1
  Version table:
 *** 65.0+build2-0ubuntu0.16.04.1 500
        500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages
        500 http://security.ubuntu.com/ubuntu xenial-security/main i386 Packages
        100 /var/lib/dpkg/status
     45.0.2+build1-0ubuntu1 500
        500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages

I'm a user like you. I don't even code applications as part of my job as a Linux engineer

Calm down

Hi actionpartnershi (Andrew-Woodhead.. I understand that. So just for the record I am providing some Additional Information:

2019-02-22 Additional Information: Somewhere in the time frame of anywhere between 5 to 15 minutes prior to each Crash. Each Ubuntu Operating System Freeze-up and complete Crash, had been proceeded by the opening of Google owned YouTube in a separate browser Tab: Searching for a specific YouTube Video, Pausing the Playback of that video while the page completed its lengthy loading process: The copying of the Url of that Youtube Video to the buffer, and the pasting of that Url link to a Facebook Post or Comment. Then the subsequent closing of that separate YouTube Browser Tab. I suspect the Crashing of the Entire Operating System being due to Google/YouTube’s leaving numerous numbers of ‘Orphaned Inode’ (Incomplete video) strings, (such as in ‘Incomplete strings’ from Forced Ad Loads), Intentionally and purposefully being done on the part of Google/Youtube to Crash the Ubuntu Linux Operating System. Because That Is the Result. The purposeful (and Repeated) ‘Hacking and Crashing’ of Hardware (Computers) Which They Do Not have the Ownership of.

You are confusing things.

A file system inconsistency (like 'orphaned inode') cannot be caused by a valid operation in a program. And aborting the loading of the page when browsing youtube videos, or closing a browser tab are valid operations. Orphaned inodes and similar file system inconsistencies can only be caused by hardware problems or by crashes of the operating system that have lead to partial save operations on the hard disk. No application program has the authority and possibility to cause a file system inconsistency by itself.

So, Open the Default Firefox browser. Go Directly to the Google/YouTube Web Site. And before they have even completed the loading of their Home/Landing page, they have DISABLED all Keyboard and Mouse Functioning, and frozen ANy browser response with between Three to Seven Incomplete Strings of 'Orphaned Inodes' as displayed when you are Forced to reboot to recover your Operating System.

ONLY Firefox Accessing THIS Google/YouTube web site does this, (Sometimes after a 5 to 15 minute delay as explained earlier).

Manfred claims Something 'is broken'? When will it be fixed?
It is more likely a purposeful 'Hacking' and Crashing of Operating System (Which They Do Not Own) being Repeatedly conducted in Forcing "Invalid Operation" of these Incomplete Strings by Google/YouTube.

If as Manfred claims "It is hardware" As previously stated on numerous occasions The Hardware WAS working perfectly BEFORE certain "UPGRADES" When will this be fixed? OR, as also previously asked, So which of you are Either going to FIX this back to previous Operability, or give me the Thousands of US Dollars (which I do not have at today's overly Inflated Prices due to Crypto Currency Miners) for a New Computer?!!

Just make this Existing Hardware work like it did Before Inconsiderate others Screwed it up!

'Orphaned Inodes' cannot be caused by Firefox, but are created by you when you switch the computer off in mid-operation.

You should never pull the plug when your system is running, because this is the main reason for file system inconsistencies.

In case that the system is unresponsive, you should at least try the REISUB emergency procedure.

Manfred: When the system is UNRESPONSIVE (All User Keyboard and Mouse Input DISABLED Which is typically the case) Is where I am thus Forced to have to do a Restart Key Press on the Computer front panel. This is where I can then see the 'Orphaned Inodes' First the Journaling of them, and then a second proper Ubuntu restart which clears the 'Orphaned Inodes' and shows the drive then as 'Clean' on the 2nd restart. I am unfamiliar with this "REISUB" you mention, nor have I the slightest clue how to go about such WITH THE SYSTEM COMPLETELY FROZEN AND ALL KEYBOARD AND MOUSE FUNCTIONS DISABLED.

(I assume Since January 2019)
Current Linux Firefox version with Crashing Issues
firefox:
  Installed: 65.0+build2-0ubuntu0.16.04.1

So I assume that I need to roll back to a Previous Version of Mozilla Firefox that actually “Worked with my Hardware” WITHOUT ISSUES on Google owned YouTube:
But, I cannot precisely determine which Mozilla archive file from the Mozilla Numbering System..

Is this Possibly the Previous Version 65.0+build1 (32 bit English US) that I am looking for?
https://ftp.mozilla.org/pub/firefox/releases/
https://ftp.mozilla.org/pub/firefox/releases/65.0/linux-i686/en-US/

Would you please confirm if this is the correct Mozilla Archive file?
If it is not, would you please direct me to the correct Mozilla Archive file?

SysRq-REISUB is a function that should work even if keyboard and mouse seem unresponsive.

Please see
https://en.wikipedia.org/wiki/Magic_SysRq_key
https://www.reddit.com/r/Ubuntu/comments/6qphtj/psa_use_reisub_when_ubuntu_stops_responding/
and similar articles.

Manfred, Thank you for the information. I wrote down the reddit version in my notebook, i haven't tried it yet but it's worth a shot next time I get a complete unresponsive freeze-up, which seems to happen about every 3 to 5 minutes on Google owned YouTube while they Literally 'decompose' parts of the Firefox browser.

I just had to do a complete reinstall of what version of Ubuntu I had on hand on a bootable Flash Drive (16.04LTS). During the 435 'Upgrades' I noticed "Initializing Friendly Recovery" I think the latest libc upgrades (Wed Feb 27, 2019 in the middle of the night Pacific time) before I had to do this reinstall have broken that, which is why I had to reinstall.

No longer does Ubuntu automatically clear 'Orphaned Inodes' whatsoever! Instead it only bring you to a command prompt at reboot. Same with holding down the SHIFT key during reboot trying to enter recovery mode. the old Recovery Mode Selection GUI appears BUT is overwritten by that same Bringing You to a command Prompt and the underlying selection menu is now completely disabled. Oddly, the exact Same thing happens now when you attempt to use a bootable Install Flash Drive, Try Ubuntu, and then Terminal attempting to run fsck ? What possible recovery options are left to the users now?

I do not have Thousands of Dollars for New Hardware. My Older Mother board has its MAXIMUM of 2GB Ram (Which all checks out fine). On this reinstall of Ubuntu I increased the sda1 Swap File Partition to 4096 MB, The sda2 /Partition to 40960 MB and the Remainder of the Hard Drive sda3 to /Home. (3 Primary Partitions).

Does Ubuntu even correctly utilize the Swap Partition any longer.. (Especially and Specifically with the Firefox Browser?) Is there anything that can currently be done to Keep The Firefox Browser's RAM hogging TO UNDER 1GB rather than these all too frequent Issues?

About the Failures to clear 'Orphaned Inodes', I think this upgrade MIGHT have had something to do with it: Prompted to use autoremove to remove libllvm5.0:i386 (1:5.0-3~16.04.1)

Which is then replaced with the 'upgrade' libgd3

Manfred: Have already had plenty of opportunities to try the REISUB approach. So far it has ONLY worked ONCE about the fifth time out of greater than 20 or more. and that was using the LEFT ALT key.

Seems even some local coastal 'Live Cam's' are causing the Firefox Browser to either crash or irrecoverably Freeze up the entire Ubuntu Operating System. However I was provided (only twice) with opportunities to send Ubuntu System Error Detected reports.

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