Ticker

6/recent/ticker-posts

Ad Code

Responsive Advertisement

Fix: This Page is Having a Problem – Error Code: SIGILL

When trying to load any website on chromium-based browsers, such as Google Chrome, Microsoft Edge, and Brave. You may experience an error message that reads “This page is having a problem”, which is accompanied by an Error Code named “SIGILL”.

Fix Error Code SIGILL on Linux
Fix Error Code SIGILL on Linux

It mainly occurs on Linux and its distros, such as Ubuntu and Fedora Linux. Many users have reported that this error started occurring after they updated their Fedora Linux to Fedora 37 or 38.

To help you resolve this error, we’ve prepared this guide which will show you all possible solutions for the SIGILL Error Code.

1. Update your Browser

A large number of Linux distros users have been experiencing the SIGILL error on their Chromium-based browsers, and have been reporting it on forums. Due to the sheer amount of reports on these forums, Microsoft, Brave, and many other developers have quickly released updates to their browsers that fix this issue. 

Therefore, before you try any complicated troubleshooting method, the first thing you should do is download the latest version of your browser. This will most likely resolve the issue for you.

But if the error does not go away even after you’ve updated your browser, try the solutions we’ve listed below.

2. Set Security to No Protection (For Google Chrome Users)

If you’re experiencing this error on your Google Chrome browser specifically, a solution that has worked for many people online is to set the Security Level of the browser to No Protection.

While this may seem like a dangerous thing to do, as long as you have an Antivirus and/or a Firewall software active, your browsing experience will remain perfectly safe even if you set Chrome Security to No Protection. 

Follow the steps we’ve listed below to set Google Chrome’s Security Level to No Protection:

  1. Open Google Chrome.
  2. Click on the three dots at the top-right corner of the Window and select Settings.
    Opening Google Chrome Settings
    Opening Google Chrome Settings
  3. Click on Privacy and Security in the list of options on the left.
  4. Select Security.
    Opening Chrome Security Settings
    Opening Chrome Security Settings
  5. Select No Protection.
    Setting Security to No Protection
    Setting Security to No Protection

After following these steps, load a website and see if you’re experiencing the same error. If the error continues to occur, try the next solution we’ve listed below.

3. Downgrade to an Older Version of the Browser

If you’re experiencing this error on Linux, Ubuntu, or Fedora Linux, the error could be a result of an incompatibility issue between your browser and OS. 

Therefore, downgrading to an older version of your browser has a high chance of fixing your issue. 

An easy way to downgrade your browser is to enter a command in the Linux terminal. First, open a terminal window by pressing Ctrl + Alt + T at the same time. 

Opening Linux Terminal
Opening Linux Terminal

If you’re using Microsoft Edge, paste the following command into the terminal and press enter. This will roll back your browser to version 112.0.1722.48, which is a perfectly stable version. 

sudo apt install microsoft-edge-stable=112.0.1722.48-1

If you’re using the Beta or Dev version of Edge, simply replace “stable” with “beta” or “dev” in the above command. 

And If you’re using any other browser, such as Mozilla Firefox, you will have to enter the following commands: 

apt-cache policy firefox 
wget https://ftp.mozilla.org/pub/firefox/releases/91.0/linux-x86_64/en-US/firefox-91.0.tar.bz2 
dpkg -i firefox-91.0.tar.bz2

The apt-cache policy command is used to find the latest version of the browser that is installed on your system. The wget command is used to download the older version of the browser from the internet. And the dpkg -i command is used to install the downloaded package.

4. Install the Beta or Dev Version of Microsoft Edge

According to many reports online, users have solved this issue by simply installing the Beta or Dev version of Microsoft Edge. These versions of Microsoft Edge are regularly updated with features that the normal version does not have. 

There seems to be a compatibility issue between the normal version of Edge and the latest builds of Linux distros. Therefore, installing either the Beta or Dev version of the browser can solve your issue.

To download any one of these versions, visit this website. Make sure to click on the arrow next to “Download” and select the Linux version.

Downloading the Linux version of Edge
Downloading the Linux version of Edge

Alternatively, you can simply enter this command into the terminal to install Edge Dev or Beta:

sudo apt install microsoft-edge-dev
sudo apt install microsoft-edge-beta

Once it’s downloaded and installed on your computer, you should be able to browse the internet without any issues.

5. Roll Back to an Older Version of Fedora Linux (If Applicable)

If you’re using the Fedora Linux OS, rolling back/downgrading to an older version of the OS has a high chance of fixing your issue. This is because this error seems to be associated with versions 37 and 38 of Fedora Linux. Therefore, rolling back to a previous version can get rid of the error.

Before you roll back, make sure to back up your data. This is important because downgrading Fedora Linux can potentially damage your system. You can use a variety of tools to back up your data, such as the tar command or dedicated backup software.

Once you’re ready to perform the rollback, there are two ways you can do it. You can either do a temporary rollback or a permanent one.

To do a temporary rollback, restart your system and hold the Shift key on your keyboard while the OS is booting. This will cause the bootloader to appear which will allow you to select the previous OS deployment.

To do a permanent rollback, first, you’ll have to open the terminal (press Ctrl + Alt + T) and execute the following commands:

sudo systemctl stop zincati.service
sudo rpm-ostree rollback -r

The first command disables automatic updates while the second command marks the previous OS deployment as the default OS, and instantly restarts into it.

If you have any further inquiries on the rollback process, you can visit the official website of the Fedora project for help.

The post Fix: This Page is Having a Problem – Error Code: SIGILL appeared first on Appuals.com.

Enregistrer un commentaire

0 Commentaires