Merge branch 'master' into pang12-flex

ahoneybun · web-flow · commit 7e190f8858f6 · 2023-09-15T14:04:30.000-06:00
diff --git a/content/customize-gnome.md b/content/customize-gnome.md
@@ -18,7 +18,7 @@ section: software
 tableOfContents: true
 ---
 
-**Please note**: Pop_OS! 22.04 is based on GNOME 42 so the extension **must** support GNOME 42.
+**Please note**: Pop!\_OS 22.04 is based on GNOME 42 so the extension **must** support GNOME 42.
 
 The GNOME desktop environment is highly customizable.  With a few extensions, the desktop can look and feel like many other operating system's desktops.  Launcher bars can be added, window lists can be used, and the overall look and feel of the desktop can be changed.
 
@@ -30,7 +30,7 @@ We will share some of the more popular extensions, but there are many more to ch
 
 ## User Themes
 
-**Please note**: If you are using a custom GNOME theme in Pop_OS! 22.04, it **must** support GTK 4.
+**Please note**: If you are using a custom GNOME theme in Pop!\_OS 22.04, it **must** support GTK 4.
 
 [User Themes](https://extensions.gnome.org/extension/19/user-themes/)
 
@@ -44,6 +44,8 @@ This extension allows for the desktop to be themed in further ways than default.
 
 ![dash-to-dock](/images/customize-gnome/dash-to-dock.png)
 
+ >**Note:** Starting with version 22.04, Pop!\_OS includes Cosmic Dock, which is forked from Dash to Dock. GNOME Settings has options for customization in Settings -> Desktop -> Dock. You will want to disable Cosmic Dock in the Extension application if adding Dash to Dock.
+
 This extension brings a launcher similar to the Unity launcher on the left side, or the macOS launcher on the bottom.  It is highly customizable and allows for different locations, styles, sizes, and layouts.  This is included by default in Ubuntu 18.04 and can be added to Pop!_OS.
 
 ---
@@ -68,23 +70,15 @@ This extension adds a window list to the bottom of the monitors.  This shows wha
 
 ---
 
-## Gnomenu
-
-[Gnomenu](https://extensions.gnome.org/extension/608/gnomenu/)
-
-![gnomenu](/images/customize-gnome/gnomenu.png)
-
-This extension adds a traditionally styled, full featured menu to GNOME.  This menu is similar to a traditional Window's Start Menu, and is highly customizable for how it looks and functions.
-
----
-
 ## Appindicator Support and TopIcons Plus
 
 [Appindicator Support](https://extensions.gnome.org/extension/615/appindicator-support/)
 [Top Icons](https://extensions.gnome.org/extension/1031/topicons/)
 
 ![topicons](/images/customize-gnome/topicons.png)
 
+>**Note:** Starting with Pop!\_OS 22.04 the Ubuntu fork of this extension is included by default.
+
 Appindicator Support and TopIcons Plus both serve to add the ability for programs to use an indicator icon to show they are running.  This functionality has been removed in recent versions of GNOME, and an extension is needed for the functionality.  These 2 programs work slightly differently, and work better in some setups vs. others.  If one doesn't work, try the other one.
 
 See [blogs.gnome.org](https://blogs.gnome.org/aday/2017/08/31/status-icons-and-gnome/) for more background on the removal of the support from default GNOME environment.
@@ -121,14 +115,6 @@ CPU power meter allows for quick switching of various CPU frequency settings.
 
 ---
 
-## Extension Update Notifier
-
-[Extension Update Notifier](https://extensions.gnome.org/extension/1166/extension-update-notifier/)
-
-This extension will check the various installed extensions and present a notification that there is an update to the extensions.  Extensions are not automatically updated, so this extension provides the next best option.
-
----
-
 ## Lock Keys
 
 [Lock keys](https://extensions.gnome.org/extension/36/lock-keys/)
diff --git a/content/package-manager-pop.md b/content/package-manager-pop.md
@@ -18,7 +18,7 @@ section: software-troubleshooting
 tableOfContents: true
 ---
 
-## Apt/Dpkg (system-wide packages)
+## APT/Dpkg (system-wide packages)
 
 If your system complains about a failed upgrade, package manager conflicts, broken upgrades, or other package-related issues, there are several common fixes to these problems. Some package manager issues can be resolved with the graphical update program, but many require the command line. Try running these commands to fix your package manager:
 
@@ -112,11 +112,11 @@ apt-mark showhold
 
 If the Terminal returns nothing, no packages are held.
 
-If the Pop!_Shop indicates that some remote repositories can't be reached, open [Repoman](/articles/manage-repos-pop) and look in the **Extra Sources** page for the broken repository.  Either disable or remove the repository, or search for the software vendor to determine what has happened to their software server. Sometimes the version of the repo (xenial, bionic, focal, groovy, etc) needs changed to match the current version of the operating system.
+If the <u>Pop!_Shop</u> indicates that some remote repositories can't be reached, open [Repoman](/articles/manage-repos-pop) and look in the **Extra Sources** page for the broken repository.  Either disable or remove the repository, or search for the software vendor to determine what has happened to their software server. Sometimes the version of the repo (xenial, bionic, focal, groovy, etc) needs changed to match the current version of the operating system.
 
 ## Flatpak
 
-If the Pop!_Shop is showing an update available, but there are no updates listed on the update page, there may be a Flatpak runtime (a backend program that another Flatpak depends on) with an update available. Run these commands to update all Flatpaks and remove any Flatpak runtimes that are no longer required by any installed programs:
+If the <u>Pop!_Shop</u> is showing an update available, but there are no updates listed on the update page, there may be a Flatpak runtime (a backend program that another Flatpak depends on) with an update available. Run these commands to update all Flatpaks and remove any Flatpak runtimes that are no longer required by any installed programs:
 
 ```bash
 flatpak update
@@ -131,3 +131,22 @@ The program <u>Synaptic Package Manager</u> is a very powerful GUI frontend for
 ```bash
 sudo apt install synaptic
 ```
+
+## Sending information to support
+
+The following commands will save the output to `upgrade.txt` and `sources.txt` so that they can be attached to support emails.
+
+```bash
+sudo apt clean | tee -a ~/upgrade.txt
+sudo apt update -m | tee -a ~/upgrade.txt
+sudo dpkg --configure -a | tee -a ~/upgrade.txt
+sudo apt install -f | tee -a ~/upgrade.txt
+sudo apt full-upgrade | tee -a ~/upgrade.txt
+sudo apt autoremove --purge | tee -a ~/upgrade.txt
+
+cat /etc/apt/sources.list | tee -a ~/sources.txt
+cat /etc/apt/sources.list.d/* | tee -a ~/sources.txt
+ls /etc/apt/sources.list.d/ | tee -a ~/sources.txt
+cat /etc/apt/sources.list.d/system.sources | tee -a ~/sources.txt
+cat /etc/apt/sources.list.d/pop-os-apps.sources | tee -a ~/sources.txt
+```
diff --git a/content/package-manager-ubuntu.md b/content/package-manager-ubuntu.md
@@ -18,6 +18,8 @@ section: software-troubleshooting
 tableOfContents: true
 ---
 
+## APT/Dpkg (system-wide packages)
+
 If your system complains about a failed upgrade, package manager conflicts, broken upgrades, or other package-related issues, there are several common fixes to these problems.  Some package manager issues can be resolved with the graphical update program, but many require the command line.  If you get the red circle in the status bar, run these commands to fix your package manager:
 
 ```bash
@@ -112,7 +114,7 @@ apt-mark showhold
 
 If the Terminal returns nothing, no packages are held.
 
-If the Pop!_Shop indicates that some remote repositories can't be reached, open [Repoman](/articles/manage-repos-pop) and look in the **Extra Sources** page for the broken repository.  Either disable or remove the repository, or search for the software vendor to determine what has happened to their software server. Sometimes the version of the repo (xenial, bionic, focal, groovy, etc) needs changed to match the current version of the operating system.
+If the Ubuntu Store indicates that some remote repositories can't be reached, open <u>Software & Updates</u> and look in the **Extra Sources** page for the broken repository.  Either disable or remove the repository, or search for the software vendor to determine what has happened to their software server. Sometimes the version of the repo (xenial, bionic, focal, groovy, etc) needs changed to match the current version of the operating system.
 
 ## Snap Pacakges
 
@@ -136,3 +138,22 @@ The program <u>Synaptic</u> is a very powerful GUI of the package manager.  Pack
 ```bash
 sudo apt install synaptic
 ```
+
+## Sending information to support
+
+The following commands will save the output to `upgrade.txt` and `sources.txt` so that they can be attached to support emails.
+
+```bash
+sudo apt clean | tee -a ~/upgrade.txt
+sudo apt update -m | tee -a ~/upgrade.txt
+sudo dpkg --configure -a | tee -a ~/upgrade.txt
+sudo apt install -f | tee -a ~/upgrade.txt
+sudo apt full-upgrade | tee -a ~/upgrade.txt
+sudo apt autoremove --purge | tee -a ~/upgrade.txt
+
+cat /etc/apt/sources.list | tee -a ~/sources.txt
+cat /etc/apt/sources.list.d/* | tee -a ~/sources.txt
+ls /etc/apt/sources.list.d/ | tee -a ~/sources.txt
+cat /etc/apt/sources.list.d/system.sources | tee -a ~/sources.txt
+cat /etc/apt/sources.list.d/pop-os-apps.sources | tee -a ~/sources.txt
+```
diff --git a/content/system-firmware.md b/content/system-firmware.md
@@ -136,7 +136,8 @@ Identify the EFI partition in the list. (The EFI partition is usually the first
 #### For NVMe Drives
 
 ```bash
-sudo apt install system76-driver
+sudo apt update
+sudo apt install system76-driver system76-firmware
 sudo mkdir -p /boot/efi
 sudo mount /dev/nvme0n1p1 /boot/efi
 gnome-control-center firmware
@@ -147,7 +148,8 @@ Where `/dev/nvme0n1p1` is the EFI system partition.
 #### For SATA Drives
 
 ```bash
-sudo apt install system76-driver
+sudo apt update
+sudo apt install system76-driver system76-firmware
 sudo mkdir -p /boot/efi
 sudo mount /dev/sda1 /boot/efi
 gnome-control-center firmware
diff --git a/content/system76-driver.md b/content/system76-driver.md
@@ -20,30 +20,6 @@ This guide will show you how to add the System76 software repository and install
 
 Please note these steps are not necessary in Pop!\_OS, which includes the repository and the appropriate drivers installed by default.
 
-## Adding the Apt Preferences File
-
-If you are running Ubuntu 19.10 or later, you will need to manually add an apt preferences file to "pin" the System76 repository. This will tell apt to prefer System76 packages over standard Ubuntu packages. Installing the System76 Driver will not be possible until this step is completed.
-
-Create the apt preferences file here:
-
-```bash
-sudo gedit /etc/apt/preferences.d/system76-apt-preferences
-```
-
-Add the following six lines (seven if you count the space in the middle):
-
-```bash
-Package: *
-Pin: release o=LP-PPA-system76-dev-stable
-Pin-Priority: 1001
-
-Package: *
-Pin: release o=LP-PPA-system76-dev-pre-stable
-Pin-Priority: 1001
-```
-
-Save the file. Now you should be able to install the System76 Driver as described below.
-
 ## Installing the Driver
 
 To install our Driver you need to run the following commands in the Terminal:
@@ -56,7 +32,7 @@ sudo apt install system76-driver
 
 This installs the System76 driver and related utilities which are needed to enable full functionality for your system.
 
-## Installing the System76 NVIDIA Driver for Systems with NVIDIA GPUs
+### Installing the System76 NVIDIA Driver for Systems with NVIDIA GPUs
 
 If your system has an NVIDIA graphics card, you will want to go ahead and use this command to install the System76 Driver with NVIDIA graphics drivers built-in:
 
@@ -66,7 +42,7 @@ sudo apt-get install system76-driver-nvidia
 
 In addition to the standard packages, that will pull in the latest NVIDIA drivers as packaged by System76, and all related packages needed to take full advantage of your dedicated NVIDIA graphics card.
 
-### Install System76 Driver on Other Operating Systems
+## Install System76 Driver on Other Operating Systems
 
 **DISCLAIMER:** This section explains how to install the <u>System76 Driver</u> on Arch and Fedora.
 
@@ -78,7 +54,7 @@ The support team typically makes a best-effort attempt to offer direction or tro
 
 **Note:** At this time, it is recommended to use the NVIDIA driver from the Arch and Fedora repositories.
 
-### Arch - Manual install
+## Arch - Manual install
 
 First, install some build dependencies for the <u>System76 Firmware Daemon</u>, <u>System76 Driver</u> and the <u>Firmware Manager</u> packages:
 
@@ -91,8 +67,8 @@ sudo pacman -S --needed base-devel git linux-headers
 These commands will clone, build and install the <u>System76 Firmware Daemon</u> service.
 
 ```bash
-git clone https://aur.archlinux.org/system76-firmware-daemon.git
-cd system76-firmware-daemon
+git clone https://aur.archlinux.org/system76-firmware.git
+cd system76-firmware
 makepkg -srcif
 sudo systemctl enable --now system76-firmware-daemon
 sudo gpasswd -a $USER adm
@@ -121,7 +97,7 @@ sudo systemctl enable --now system76
 
 Reboot the system so that our user is added to the `adm` group, then we are done!
 
-### Arch - Using an AUR helper
+## Arch - Using an AUR helper
 
 Arch users can alternatively use an AUR helper to automate some of the steps for installation and upgrading; in this example, we'll use the <u>Paru</u> application. <u>Paru</u> can be installed from the AUR using these commands:
 
@@ -134,13 +110,13 @@ makepkg -si
 **Note:** By default, <u>Paru</u> uses VIM keyboard shortcuts, so when you see a `:`, press the <kbd>q</kbd> key to continue. You may also need to confirm the import of some public keys using the <kbd>y</kbd> key.
 
 ```bash
-paru -S system76-firmware-daemon
+paru -S system76-firmware-daemon-git
 sudo systemctl enable --now system76-firmware-daemon
 sudo gpasswd -a $USER adm
 ```
 
 ```bash
-paru -S firmware-manager
+paru -S firmware-manager-git
 ```
 
 ```bash
@@ -149,12 +125,11 @@ paru -S system76-driver
 sudo systemctl enable --now system76
 ```
 
-### Fedora
+## Fedora
 
 Run these commands in a <u>Terminal</u> to enable the [community Fedora COPR](https://copr.fedorainfracloud.org/coprs/szydell/system76/) and install the <u>System76 Driver</u> :
 
 ```bash
 sudo dnf copr enable szydell/system76
-sudo dnf install system76*
-sudo systemctl enable --now com.system76.PowerDaemon.service
+sudo dnf install system76-driver
 ```
diff --git a/content/system76-software.md b/content/system76-software.md
@@ -34,17 +34,17 @@ If you want to use an AUR helper like [Paru](https://github.com/Morganamilo/paru
 This command will install all of the packages using <u>Paru</u>.
 
 ```bash
-paru -S system76-firmware-daemon system76-firmware firmware-manager system76-power gnome-shell-extension-system76-power-git system76-driver system76-dkms system76-acpi-dkms
+paru -S system76-firmware-daemon system76-firmware firmware-manager system76-power gnome-shell-extension-system76-power-git system76-driver system76-dkms system76-acpi-dkms system76-io-dkms
 ```
 
-This command will install `firmware-manager` using <u>Paru</u>.
-
 **NOTE:** choose the first software option after running the <u>Paru</u> command.
 
 ```bash
 paru -S firmware-manager
 ```
 
+This command will install <u>firmware-manager</u> using <u>Paru</u>.
+
 ### System76 DKMS
 
 This package is needed for hotkeys and fan(s) on Closed Firmware systems.
@@ -155,7 +155,14 @@ paru -S system76-acpi-oled
 
 ## Fedora
 
-Be sure to install the <u>System76 Driver</u> first. The steps to do that are [here](/articles/system76-driver).
+Be sure to install the <u>System76 Driver</u> first. The steps to do that are [here](/articles/system76-driver). The commands below will install every system76 package using the wildcard(*) use the other sections to install each package on it's own if you do not want all of the packages.
+
+```bash
+sudo dnf install system76* firmware-manager
+sudo systemctl enable --now system76-firmware-daemon
+sudo systemctl mask power-profiles-daemon.service
+sudo gpasswd -a $USER adm
+```
 
 ### System76 Firmware Manager in Fedora
 
@@ -167,6 +174,12 @@ sudo systemctl enable --now system76-firmware-daemon
 sudo gpasswd -a $USER adm
 ```
 
+**NOTE:** After enabling the dkms systemd service for any of the DKMS packages you will need to reboot the system:
+
+```bash
+sudo systemctl reboot
+```
+
 ### System76 Power in Fedora
 
 Use these commands to install the <u>System76 Power</u> package and enable the service:
@@ -184,6 +197,8 @@ sudo systemctl mask power-profiles-daemon.service
 
 ### System76 Power GNOME Shell Extension in Fedora
 
+**NOTE:** Fedora uses GNOME 44 and some of the internal APIs are missing that are used in this extention. The API change happend with the release of GNOME 43. Pull requests that update to newer APIs are very welcome!
+
 These commands will download the source code for the application, build it, install it and install the <u>Extensions</u> application:
 
 ```bash
@@ -221,12 +236,6 @@ sudo dnf install system76-acpi-dkms
 sudo systemctl enable dkms
 ```
 
-**NOTE:** After enabling the dkms systemd service for either the <u>System76 DKMS</u> or the <u>System76 ACPI DKMS</u> package you will need to reboot the system:
-
-```bash
-sudo systemctl reboot
-```
-
 ### System76 Thelio Io DKMS in Fedora
 
 This command will be used to install the <u>System76 Io DKMS</u> which is used for the Thelio Io board:
@@ -235,6 +244,12 @@ This command will be used to install the <u>System76 Io DKMS</u> which is used f
 sudo dnf install system76-io-dkms
 ```
 
+**NOTE:** After enabling the dkms systemd service for any of the DKMS packages you will need to reboot the system:
+
+```bash
+sudo systemctl reboot
+```
+
 ### System76 OLED in Fedora
 
 This command will be used to install the <u>System76 OLED</u> which is used for systems with OLED panels:
diff --git a/content/wireless.md b/content/wireless.md
@@ -203,3 +203,7 @@ The newest version of the <u>linux-firmware</u> package, which contains the iwlw
 [mirrors.kernel.org/ubuntu/pool/main/l/linux-firmware](https://mirrors.kernel.org/ubuntu/pool/main/l/linux-firmware)
 
 Sometimes the newest version of the firmware will clear up occasional bugs.  Please download the newest `.deb` package.
+
+### Windows Dual Boot
+
+If you are dual booting Windows, you may lose access to your wifi card entirely after running driver/OS updates in Windows. You may be able to gain access to your wifi card again by disabling "Fast Startup" in the Windows power options before booting back into Pop!_OS.
diff --git a/layouts/default.vue b/layouts/default.vue
@@ -43,7 +43,7 @@
       url-contact="https://system76.com/contact"
       url-about="https://system76.com/about"
       url-careers="https://system76.com/careers"
-      url-specials="https://system76.com/specials"
+      url-sustainability="https://system76.com/sustainability"
       url-shipping="https://system76.com/shipping"
       url-privacy="https://system76.com/privacy-and-legal"
     />
diff --git a/package-lock.json b/package-lock.json
diff --git a/package.json b/package.json
