.. _pureos_troubleshooting:

Troubleshooting
===============

This guide describes known issues and how to fix them.


.. _pureos_troubleshooting_installation:

Installation
------------


.. _pureos_troubleshooting_installation_boot_options:

PureOS boot screen does not appear
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

**Problem**:

The PureOS boot screen does not appear after booting into a USB flash drive.

**Solution**:

Try the following:

#. Disable secure boot/UEFI boot on your computer's BIOS and try again
#. Make sure you followed the desired procedure to create a bootable USB drive:
    * :ref:`Etcher <pureos_installation_prepare_sd_etcher>`
    * :ref:`GNOME Disks <pureos_installation_prepare_sd_gnome_disks>`
    * :ref:`dd command <pureos_installation_prepare_sd_dd>`
#. ISO image you burned to your USB might not be downloaded correctly, ensure the download is okay by :ref:`verifying its sha256 checksum <pureos_image_verify>`


.. _pureos_troubleshooting_installation_incomplete:

Installation was incomplete
^^^^^^^^^^^^^^^^^^^^^^^^^^^

Installation process stopped before completion.

**Problem**

Installation freezes between 40% and 60%.
If encryption is DISABLED, installation goes fine.

**Solution**

This can occur if the system has run out of entropy ("randomness") while creating the encrypted partition.
Don't interrupt the setup, but simply open a text editor and start typing random text.
You can also move the cursor around to generate more entropy.

If you wish to measure how much entropy you have available, you can run this commans on the command line:

.. code-block:: bash

   cat /proc/sys/kernel/random/entropy_avail


.. _pureos_troubleshooting_drivers:

Drivers
-------


.. _pureos_troubleshooting_drivers_byd:

No touchpad settings available in GNOME control center
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

**Problem**

No touchpad settings are available in GNOME control center.
This occurs when the BYD touchpad on Librem 13 rev1/Librem 15v2 is not detected/recognized.

**Check**

Check if the touchpad driver is loaded (execute this command in your terminal):

.. code-block:: bash

   cat /sys/bus/serio/devices/serio1/protocol

If the command returns **ImPS/2**, then the BYD touchpad driver is not loaded.

**Solution**

.. note::
   This only applies to laptops with BYD touchpads, notably **Librem 13 rev1** and **Librem 15 rev2**.

Create a file (if doesn't exist) ``/etc/rc.local`` with the following content:

.. code-block:: bash

   #!/bin/bash
   echo -n byd > /sys/bus/serio/devices/serio1/protocol

The file must be executable.

Terminal command to do all this:

.. code-block:: bash

   sudo touch /etc/rc.local
   sudo sh -c 'echo "#!/bin/bash\necho -n byd > /sys/bus/serio/devices/serio1/protocol" > /etc/rc.local'
   sudo chmod +x /etc/rc.local

Restart the computer for this to take effect.


.. _pureos_troubleshooting_drivers_missing_firmware:

Missing firmware
^^^^^^^^^^^^^^^^

Missing firmware for a device

**Problem**

A device on my computer does not work with PureOS.
Logs say something about missing firmware.

**Check**

PureOS is designed to support only devices which do not require non-free/proprietary binary drivers or firmware, meaning it *does not have* such drivers/firmware.
Check if your computer have such devices (AMD or nVidia graphics, Intel or newer Broadcom wireless LAN cards, etc).

**Solution**

Check if the ``firmware-linux-free`` package is installed.
If it is not installed, install it.
If the device requires non-free/proprietary binary drivers/firmware, it will not work in PureOS.


.. _pureos_troubleshooting_gnome:

GNOME
-----


.. _pureos_troubleshooting_gnome_missing_dirs:

Apps don't see my folders for music, videos, etc.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

**Problem**

Some of your apps cannot access your media directories (aka XDG directories).
For example, you can't choose picture from Pictures folder when setting background:

.. image:: img/gnome-photos/Screenshot_from_2017-06-20_19-18-32.png
   :scale: 50%
   :alt: gnome-photos: No pictures found

**Solution**

This usually happens if the xdg rules are missing.
You can fix this by creating a file within ``$HOME/.config/user-dirs.dirs`` with the following content:

.. code-block::

   XDG_DESKTOP_DIR="$HOME/Desktop"
   XDG_DOCUMENTS_DIR="$HOME/Documents"
   XDG_DOWNLOAD_DIR="$HOME/Downloads"
   XDG_MUSIC_DIR="$HOME/Music"
   XDG_PICTURES_DIR="$HOME/Pictures"
   XDG_PUBLICSHARE_DIR="$HOME/Public"
   XDG_TEMPLATES_DIR="$HOME/Templates"
   XDG_VIDEOS_DIR="$HOME/Videos"

Log out and then log back in.
GNOME software will now detect your media files:

.. image:: img/gnome-photos/Screenshot_from_2017-06-20_19-26-11.png
   :scale: 50%
   :alt: gnome-photos: Pictures found


.. _pureos_troubleshooting_gnome_gdm3_fails:

GNOME login screen does not appear
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

**Problem**

The system successfully booted, but the GNOME display manager (``gdm3``) login screen does not launch.
Only a black screen with a login prompt appears:

.. code-block::

   PureOS GNU/Linux librem14 tty2
   
   librem14 login:

**Solution**

In some cases it might help to reconfigure the GNOME login manager.

#. Login with your username/password at the prompt:

   .. code-block::

      PureOS GNU/Linux librem14 tty2
   
      librem14 login: pureos
      Password:

#. Run the following command:

   .. code-block:: bash

      sudo dpkg-reconfigure gdm3

#. Restart the computer to see if it fixes the problem.

.. seealso::
   If the problem happened occurs a system upgrade, refer to :ref:`pureos_troubleshooting_system_upgrade_failure`.


.. _pureos_troubleshooting_gnome_mouse_issue:

Right-clicking on the touchpad behaves as a left-click
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

**Problem**

Following a software update, the secondary touchpad button (right click) behaves like a primary (left click) button click when pressing on the right side of the touch pad.

**Cause**

This is an upstream issue.
After an update, the upstream package overwrites the user preference (or changes the default behavior).

**Solution**

Change the mouse settings in **GNOME Tweaks** back to ``Area``.

.. image:: img/gnome-tweaks/Screenshot_from_2018-03-05_22-02-19.png
   :scale: 50%
   :alt: gnome-tweaks: Keyboard & Mouse settings

.. _pureos_troubleshooting_gnome_no_logs:

No logs displayed in GNOME Logs
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
**Problem**

GNOME Logs does not display any logs or crash reports.
It may not launch at all (running ``gnome-logs`` from terminal may report a segfault).

**Cause**

Your user likely does not have permissions to read **journal** logs.

**Solution**

#. Add your user to the ``systemd-journal`` group:

.. code-block:: bash

   sudo usermod -aG systemd-journal USERNAME

...where ``USERNAME`` is your username.
You can find it by running the command:

.. code-block:: bash

   whoami

.. note::
   You must restart your computer for the group edit to be applied.


.. _pureos_troubleshooting_gnome_application_menu_extension:

Application Menu Extension
^^^^^^^^^^^^^^^^^^^^^^^^^^

**Problem**

You want to use the GNOME Applications menu but see in `Tweaks <https://tracker.pureos.net/w/pureos/desktop/tweak_tool>`_ that the GNOME Application Menu extension has not loaded and cannot be enabled.

**Solution**

#. From **Show Applications**, open the **Utilities** folder and open a terminal emulator.
#. Copy and paste the following into the terminal emulator:

   .. code-block:: bash

      sudo apt install gnome-menus

#. Press ``Enter``.
#. Enter your password and follow the prompts.
#. Once it has completed, log out and log back into PureOS.
#. After the computer has booted, go into **Tweaks** and you should now be able to enable the Applications menu extension for GNOME.


.. _pureos_troubleshooting_gnome_web_audio_peaking:

GNOME Web jumps to maximum audio volume
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

**Problem**

GNOME Web jumps to maximum audio volume when playing sound

**Cause**

This is an issue that can occur when watching videos in GNOME Web.
It is due to a configuration in the PulseAudio Daemon configuration.

**Solution**

#. Open the terminal emulator and run the following command to edit the configuration file:

   .. code-block:: bash

      sudo nano /etc/pulse/daemon.conf

#. You will be prompted for your user password; type it and press ``Enter``.
#. Edit this line, from:

   .. code-block:: bash

      ; flat-volumes = yes

   to:

   .. code-block:: bash

      flat-volumes = no

#. Press ``Ctrl+X`` to exit ``nano``.
#. You will be prompted to save the file. Press ``y`` and then press ``Enter`` to save the file without modifying the filepath. The editor will close.
#. Reboot the device to apply the changes.


.. _pureos_troubleshooting_power:

Power Management
----------------


.. _pureos_troubleshooting_power_suspend_resume:

Suspend-Resume issues
^^^^^^^^^^^^^^^^^^^^^

**Problem**

Suspend/resume do not work.

**Cause**

There was a kernel regression causing suspend/resume issues with certain hardware.

**Solution**

Some suspend/resume issues are fixed when downgrading your kernel to 4.9.x.

.. seealso::
   https://forums.puri.sm/t/problem-with-librem-13-v2-and-samsung-960-pro-with-temp-fix


.. _pureos_troubleshooting_network:

Network
-------


.. _pureos_troubleshooting_network_no_wifi:

No internet access when connected to WiFi
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

**Problem**

THe system is successfully connected to a wireless network, but there is no Internet connectivity.
The same WiFi connection is working on other devices.

**Check**

Check DNS settings.

#. Run the following command in a terminal emulator:

   .. code-block:: bash

      cat /etc/resolv.conf

**Solution**

#. Run the following command in a terminal emulator:

   .. code-block:: bash

      dpkg-reconfigure resolvconf

#. If this does not help, you can try manually adding another DNS address to the ``resolv.conf`` file.
   This may fix your connection.
   For example, you can add Google's public DNS (``8.8.8.8``) or choose a DNS from the OpenNIC DNS list `here <https://www.opennic.org>`_ (simply choose the first address).
#. Execute the following command in a terminal emulator to add this new DNS address to your ``/etc/resolv.conf`` file:

   .. code-block:: bash

      sudo sh -c 'echo "nameserver 8.8.8.8" > /etc/resolv.conf'

   The effect of this change will be visible immediately.

If you now have internet access, the problem was your DNS (or the network stack that did not update it correctly).
Make sure to update your system later!


.. _pureos_troubleshooting_network_firewall:

PureOS 10 has new firewall tools
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

In PureOS 10, ``iptables`` was moved to ``nftables``.
``nftables`` is the preferred in kernel packet filter and ``firewalld`` is the tool for controlling firewalls on the desktop.


.. _pureos_troubleshooting_system:

System
------


.. _pureos_troubleshooting_system_sudo_permissions:

Cannot run commands as sudo
^^^^^^^^^^^^^^^^^^^^^^^^^^^

**Problem**

You receive the following error when trying to sudo run a command:

.. warning::
   <USERNAME> is not in the sudoers file. This incident will be reported

**Solution**

To add your username to sudoers list, add your username to ``sudo`` group:

#. Open Terminal app and log into root session with:

   .. code-block:: bash

      su

#. Enter your password once prompted.
#. Run the following command:

   .. code-block:: bash

      usermod -a -G sudo username

   ...where ``username`` is your login name (username).
#. Log out and then log back in.

You can now run commands using ``sudo``.


.. _pureos_troubleshooting_system_upgrade_failure:

Fixing a failed/partial system upgrade
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

**Problem 1**

The system **can** boot but GNOME does not start.

**Solution**

#. Press ``Ctrl+Alt+F2`` to open another virtual terminal.
   You will see this screen:

   .. code-block::

      PureOS GNU/Linux librem14 tty2
   
      librem14 login:

#. Login by entering your username (press **Enter** afterwards), then enter your password (press **Enter** to login):

   .. code-block::

      PureOS GNU/Linux librem14 tty2
   
      librem14 login: pureos
      Password:

#. You are now logged in and you should see something like this:

   .. code-block::

      PureOS GNU/Linux librem14 tty2
      
      librem14 login: pureos
      Password:
      Last login: Mon Apr  2 19:00:45 CEST 2018 on tty1
      Linux librem14 4.15.0-2-amd64 #1 SMP Debian 4.15.11-1 (2018-03-20) x86_64
      
      The programs included with the PureOS GNU/Linux system are free software;
      the exact distribution terms for each program are described in the
      individual files in /usr/share/doc/*/copyright.
      
      PureOS GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
      permitted by applicable law.
      pureos@librem14:~$

#. Type in the following command and press **Enter**, then enter your password and press **Enter**:

   .. code-block:: bash

      sudo dpkg --configure -a`

   .. code-block::

      PureOS GNU/Linux librem14 tty2
      
      librem14 login: pureos
      Password:
      Last login: Mon Apr  2 19:00:45 CEST 2018 on tty1
      Linux librem14 4.15.0-2-amd64 #1 SMP Debian 4.15.11-1 (2018-03-20) x86_64
      
      The programs included with the PureOS GNU/Linux system are free software;
      the exact distribution terms for each program are described in the
      individual files in /usr/share/doc/*/copyright.
      
      PureOS GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
      permitted by applicable law.
      pureos@librem14:~$ sudo dpkg --configure -a
      [sudo] password for pureos: _

#. When the above command finishes, run the :ref:`command to upgrade your system again <pureos_sw_update_terminal>`:

   .. code-block:: bash

      sudo apt update && sudo apt full-upgrade

#. Re-install the ``pureos-gnome`` package:

   .. code-block:: bash

      sudo apt-get install pureos-gnome

**Problem 2**

The system cannot boot at all.
Only a black screen is shown after the disk is unlocked.

**Solution**

#. Restart your computer, then wait until BIOS/Coreboot messages disappear and immediately press **ESC** to enter the boot loader menu.
#. Using the UP and DOWN arrow keys in the keyboard to navigate, select the **Advanced Options** menu item and press **Enter**.
#. Select one of the older kernel options from the list (lower on the list) and press **Enter** to boot it.
#. If you manage to boot into graphical interface, open your terminal and run:

   .. code-block:: bash

      sudo update-initramfs -u

#. Restart the system to see if it will boot normally.


.. _pureos_troubleshooting_system_slow_boot:

Slow system startup
^^^^^^^^^^^^^^^^^^^

**Problem**

The system takes several minutes to start, but eventually it does get to the graphical user interface.

**Check**

You can check how much time the system exactly needed to start if you run this command in terminal:

.. code-block:: bash

   systemd-analyze

It will output something like this:

.. code-block:: 

   mladen@librem13:~$ systemd-analyze
   Startup finished in 3.517s (kernel) + 21.498s (userspace) = 25.015s
   graphical.target reached after 21.490s in userspace
   mladen@librem13:~$

To see how long each of the services took to start, run:

.. code-block:: bash

   systemd-analyze blame

which should give:

.. image:: img/sstd2.png
   :scale: 50%
   :alt: Terminal output for systemd-analyze blame

Use the UP and DOWN arrow keys on your keyboard to scroll the output.
Press the ``q`` key to exit the command.

To output this into a text file, use:

.. code-block:: bash

   systemd-analyze blame > startup.log

which will create a ``startup.log`` text file in the directory you are currently in.

**Solution**

If you see some service took suspiciously longer time to start, you have to search the system logs to see if there is any particular problem.
For example, running:

.. code-block:: bash

   sudo journalctl -x -b -u NetworkManager-wait-online.service

will list logs just for this service, while running:

.. code-block:: bash

   sudo journalctl -x -b

will allow you to examine all logs for the current boot session to see if there is any particular problem causing the slow system start.


.. _pureos_troubleshooting_system_failed_boot:

Failed boot
^^^^^^^^^^^

**Problem**

The system is not booting..
It hangs after successful unlock of the disk encryption, and the Purism logo is displayed.
Pressing the **ESC** key only shows a black screen with ``cryptsetup (sda5_crypt): set up successfully`` in the upper left corner.

**Cause**

This can happen when the system upgrade was interrupted or otherwise unsuccessful.
Please see :ref:`pureos_troubleshooting_system_upgrade_failure` for a solution.


.. _pureos_troubleshooting_system_cryptsetup_deprecated:

Cryptsetup setting deprecated
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

**Problem**

The following warning is displayed in a terminal emulator following a system update:

.. warning::
   Setting CRYPTSETUP in ``/etc/initramfs-tools/initramfs.conf`` is deprecated and will stop working in the future.
   Use /etc/cryptsetup-initramfs/conf-hook instead.

**Solution**

#. Add ``CRYPTSETUP=y`` in ``/etc/cryptsetup-initramfs/conf-hook`` using the following command:

.. code-block:: bash

   sudo sh -c 'echo "CRYPTSETUP=y" >> /etc/cryptsetup-initramfs/conf-hook'


.. _pureos_troubleshooting_system_forgotten_passwd:

Forgotten user password
^^^^^^^^^^^^^^^^^^^^^^^

**Problem**

You have forgotten your user password.

**Solution**

Reset your user password.

#. Boot PureOS in recovery mode.

   .. note::
      If you are using **PureBoot**, it is quite simple to enter to a recovery mode.
      From the main menu, select: ``Options`` → ``Boot options`` → ``Show OS boot menu`` → select "recovery" mode to boot (don't make it default).

   You will be asked to enter your disk password, type it in and press ``Enter``.
   You will see this text:

   .. code-block::

      You are in rescue mode. After logging in, type "journalctl -xb" to view
      system logs, "systemctl reboot" to reboot, "systemctl default" or "exit"
      to boot into default mode.
      Press Enter for maintenance
      (or press Control-D to continue):

#. Press ``Enter``.
#. You will get into a terminal session. Type:

   .. code-block::

      passwd USERNAME

   ...where ``USERNAME`` is your username (NOT your full name).
   If you forgot your username, type:

   .. code-block::

      ls /home

   ...which will show your home folder.
   Its path contains your username.

#. Type the new password and press ``Enter``.
#. Type it again to confirm and press ``Enter``.
#. Type:

   .. code-block::

      systemctl reboot

   ...and press ``Enter`` to reboot.
   Proceed as usual.


.. _pureos_troubleshooting_browser:

Browser
-------


.. _pureos_troubleshooting_browser_firefox_high_cpu:

Firefox ESR consumes excessive CPU
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

**Problem**

Firefox ESR shows high CPU usage.

**Solution**

Try to enable hardware acceleration:

#. Open a new tab in Firefox ESR
#. Navigate to about:config
#. Accept the warning to continue
#. Search for ``vaapi`` (Video Acceleration API)
#. Change the flag to ``true`` (from ``false``)
#. Fully close and restart Firefox ESR

.. note::
   Make sure you have the ``gstreamer1.0-vaapi`` package installed.


.. _pureos_troubleshooting_browser_purebrowser_to_firefox:

PureBrowser to Firefox ESR
^^^^^^^^^^^^^^^^^^^^^^^^^^

This guide describes the migration from a PureBrowser Profile (bookmarks, history, addons, etc) into Firefox ESR.

Method 1 (Command Line)
"""""""""""""""""""""""

#. Launch PureBrowser
#. Click the menu button on the top right - Help - Troubleshooting Information.

   The Troubleshooting Information tab will open.
   Your Profile Directory will be listed under the Application Basics section.
   Take note of path to the profile directory: ``/home/USER/.purism/purebrowser/USERSTRING.default``

   * If you have already migrated to Firefox, run ``cd ~/.purism/purebrowser/`` and ``ls -al``. This will list all files and directories. The directory named ``USERSTRING.default`` is the one you are looking for.
   * If you have multiple ``USERSTRING.default``, find the one with the date of the last time you used PureBrowser. 

#. Open a terminal emulator and run ``cd ~/.purism/purebrowser/`` and find the ``USERSTRING.default`` directory.
#. Run the update in Software, or apt, to now migrate to Firefox ESR. 
#. Run ``cp -r USERSTRING.default ~/.mozilla/firefox/`` to move the profile folder.
#. Now run ``firefox -P`` 
#. Select **Create Profile** and then **Next**
#. Enter a profile name or leave as it. Then select **Choose Folder**.
#. Click on your the ``USERSTRING.default`` directory that you just moved over and press **Open**. 
#. Click **Finish** and **Start Firefox**.
#. Firefox should load with all the tabs you had open before and everything else will have come over from PureBrowser. You are done! 

.. note::
   If wanting to use a search engine other than Google, you'll need to go into the menu button on the top right - Preferences - Search - select your Search Engine of choice from the drop down.

.. note::
   We have transitioned from uBlock Origin to EFF's Privacy Badger.
   That should be the only difference in addons you see. 

.. seealso::
   `Mozilla Firefox Knowledge Base <https://support.mozilla.org/en-US/kb/profiles-where-firefox-stores-user-data>`_


Method 2 (GUI)
""""""""""""""

Another way to relocate your old Purebrowser profile to the new Firefox one is to move certain parts of the Purebrowser profile folder to Firefox:

#. Open your Files manager in your ``home`` folder and press ``Ctrl+h``. This will show you the hidden folders.

   .. tip::
      Hidden folders/files always start with a ``.`` before the name.

   You will see the folders ``.purism`` and  ``.mozilla``

   .. image:: img/firefox-esr/nautilus-dotfiles.png
      :scale: 50%
      :alt: .purism and .mozilla folders in nautilus

   .. caution::
      Make a copy of both these folders as a backup before proceeding.

#. Close **Firefox** if it is open.
   If you need to have access to this tutorial during this process then, print this page as a PDF.
#. Open the ``.mozilla`` folder, then ``Firefox``, then open the folder that has a name ending in ``default-esr``
#. Delete the content of the folder that has a name ending in ``default-esr`` but do not delete the folder itself.

   .. image:: img/firefox-esr/delete-profile-contents.png
      :scale: 50%
      :alt: Deleting folder contents

#. Open the folder ``.purism`` and then ``purebrowser`` and you will see a folder that also has a name that ends in ``default``.
   Copy the contents of that folder to inside the folder ``default-esr`` in ``.mozilla/firefox/somestring.default-esr``.
#. Restart Firefox.

   You should now see:

   .. image:: img/firefox-esr/new-firefox-tab.png
      :scale: 50%
      :alt: Firefox-ESR

.. note::
   Firefox uses Google as its default search engine.
   We recommand you select DuckDuckGo to replace Google as the default search engine.


.. _pureos_troubleshooting_browser_firefox_compat:

Firefox compatibility mode
^^^^^^^^^^^^^^^^^^^^^^^^^^

Cannot install Firefox add-ons


Enable Firefox Compatibility Mode to install add-ons from `Mozilla add-ons website <https://addons.mozilla.org>`_.

.. note::
   You can search for web extensions available from the PureOS repo by running ``apt search webext`` in a terminal emulator.

#. Open **PureBrowser** and type ``about:config`` into the location bar, then press ``Enter``. A warning will appear:

   .. image:: img/firefox-esr/ff1.png
      :scale: 50%
      :alt: firefox-esr warning

#. Click the **I'll be careful, I promise!** button.
#. Type **//useragent.compat//** into the search bar.
#. Double-click the preference to change its value to ``true``:

   .. image:: img/firefox-esr/ff2.png
      :scale: 50%
      :alt: firefox-esr useragent setting

   .. note::
      This is already set to ``true`` in recent versions of PureBrowser, so you don't have to change it.

#. Change your `useragent string <https://en.wikipedia.org/wiki/User_agent#Format_for_human-operated_web_browsers>`_ to install Firefox addons.
    #. Open ``about:config``
    #. Right-click and select **New** -> **String**
    #. Within ``general.useragent.override``, enter ``Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/68.0.2`` as a string value.
    #. Click **Okay** and reload the page.


.. _pureos_troubleshooting_browser_purebrowser_first_start:

Testing PureBrowser first start issues
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

**Question**

I noticed an issue with PureBrowser the first time I started it and reported it.
Since then I have been using PureBrowser and modified my browser profile such that the issue no longer occurs.

An update has landed and I want to confirm the fix.
How can I do this without losing my new profile settings?

**Answer**

You can create a fresh profile.
Launch PureBrowser, then delete the profile:

#. Close any running instances of PureBrowser
#. Start with ``purebrowser --ProfileManager``
#. In the profile manager window, create a new profile "temp"
#. Click **Start PureBrowser**

You can now test for the first-start issue. When you are done...

#. Close any running instances
#. Start with ``urebrowser --ProfileManager``
#. Delete the profile "temp" (delete profile and files)
#. Close the profile manager window


.. _pureos_troubleshooting_misc:

Miscellaneous
-------------


.. _pureos_troubleshooting_misc_screen_flicker:

Screen flickering with Intel graphics
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

**Problem**

The screen is flickering on devices with Intel graphics.

**Solution**

A possible cause can be buggy Intel graphics power management.
You can try disabling it by adding the ``i915.enable_rc6=0`` boot flag.

#. To do this from a running system and make it permanent, run the following terminal command:

   .. code-block::

      EDITOR=gedit sudo -e /etc/default/grub

   Feel free to replace ``gedit`` with the editor of your choice.
   The file ``/etc/default/grub`` will be opened in ``gedit`` with administrator privileges (so be careful with the next step).

#. Locate the ``GRUB_CMDLINE_LINUX`` line
#. Change it to look like this:

   .. code-block::

      GRUB_CMDLINE_LINUX="i915.enable_rc6=0"

#. Save the file.
#. Run the following command in your terminal application:

   .. code-block:: bash

      sudo update-grub

#. Restart for this to take effect.


.. _pureos_troubleshooting_misc_hplip:

HP printer not working after upgrade
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

**Problem**

After upgrading from PureOS 9 to PureOS 10, an HP printer does not work despite being recognized properly.

**Solution**

It has been reported that removing ``ipp-usb`` is a workaround for this problem.
Run this command:

.. code-block:: bash

   sudo apt remove ipp-usb && sudo apt install hplip-gui