Enhancement

Currently NetworkManager is set to fail after 4 attempts to auto-connect to a prefigured wifi connection. In rare occasions this may not be enough to ensure the computer reconnects after a power failure or other event. We should consider setting the auto-connect retry value to something higher than 4 to ensure proper reconnects.

Issue

pop-os/pop#1490

Create file /etc/NetworkManager/conf.d/pop_os-autoconnect (filename could be better) and insert the following lines:

[main]
autoconnect-retries-default = 10

Distribution (run cat /etc/os-release):

cat /etc/os-release
NAME="Pop!_OS"
VERSION="20.04 LTS"
ID=pop
ID_LIKE="ubuntu debian"
PRETTY_NAME="Pop!_OS 20.04 LTS"
VERSION_ID="20.04"
HOME_URL="https://pop.system76.com"
SUPPORT_URL="https://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal
LOGO=distributor-logo-pop-os

uname -a
Linux oryx 5.11.0-7612-generic #13~1617215757~20.04~97a8d1a-Ubuntu SMP Thu Apr 1 21:15:20 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

Related Application and/or Package Version (run apt policy $PACKAGE NAME):

apt policy pop-default-settings 
pop-default-settings:
  Installed: 4.0.6~1611854075~20.04~6a2277e
  Candidate: 4.0.6~1611854075~20.04~6a2277e
  Version table:
 *** 4.0.6~1611854075~20.04~6a2277e 1001
       1001 http://ppa.launchpad.net/system76/pop/ubuntu focal/main amd64 Packages
       1001 http://ppa.launchpad.net/system76/pop/ubuntu focal/main i386 Packages
        100 /var/lib/dpkg/status

Issue/Bug Description:

Commit 6a2277e reports:

fix: Set reasonable size for dirty bytes parameters

The kernel default is to buffer up to 10% of system RAM before flushing writes to the disk, which is insane. By setting a reasonable number of bytes for the dirty_bytes parameter, we can avoid sending the system into OOM during a large file transfer.

https://lwn.net/Articles/572911/

diff --git a/etc/sysctl.d/10-pop-default-settings.conf b/etc/sysctl.d/10-pop-default-settings.conf
index 987317f..0430a48 100644
--- a/etc/sysctl.d/10-pop-default-settings.conf
+++ b/etc/sysctl.d/10-pop-default-settings.conf
@@ -1 +1,3 @@
 vm.swappiness = 10
+vm.dirty_bytes = 16777216
+vm.dirty_background_bytes = 4194304

Unfortunately this fix has the unintended side effect of completely trashing the performance of COW filesystems like BTRFS for regular use as rootfs/home on fast SSDs!

No penalty is observed when when writing large files to a BTRFS partition, but it has very negative effects on operations that do many small writes, like touching metadata on a btrfs receive operation or even just when writing a lot of small files (e.g. untarring a big archive with complex directory structure).
It can take up to 20 times the wall-clock time of running the same operation commenting out this change (which reverts to the default vm.dirty_ratio =20 and vm.dirty_background_ratio = 10).

When using BTRFS as rootfs and home, this is even worse, as operations as simple as apt update (or packagekit doing it in the background for you), apt upgrade but also just firefox/chrome regular operation (which can do frequent writes to the local on disk cache) can result in freezes lasting from some seconds to a few minutes where the CPU is stuck in iowait and all processes on the scheduler waiting for kernel triggered IO-trashing to be over.
Operations where the user is intentionally doing a lot of writes are even worse: compiling big projects, cloning a moderate or big git repo locally, using ccache become just unbearable!

My suggestion is to revert this change, or find a different compromise that manage to fix the occasional OOM problems writing big files to slow block devices, without making it impossible to do many small writes to fast devices.

The comments on the LWN article linked in the original commit are quite enlightening on the fact that similar problem on COW filesystems were anticipated following this path and that it might be difficult to strike a good balance without reworking the issue with actual kernel changes that would make these sysfs knobs superfluos.

Steps to reproduce (if you know):

1. create a BTRFS partition on a fast SSD
2. mount it (I am using options defaults,noatime,compress=zstd but they are not particularly relevant, you can test with or without)
3. have separate terminals where you are running iotop and htop to examine CPU and IO utilization, alternatively you can also use sysstats to collect the data and visualize it afterwards
4. time (tar -xpf some_large_and_complex_archive.tar --acls --xattrs -C /path/to/mountpoint ; sync )
5. unmount the BTRFS partition
6. sudo sysctl vm.dirty_ratio = 20; sudo sysctl vm.dirty_backgroud_ratio = 20;
7. redo 1-4
8. look at the difference between the spent time for the tar extraction in the 2 cases

Expected behavior:

Using Pop!OS on a BTRFS root filesystem should be usable, and its performance not crippled to avoid rare corner cases when writing large files to slow devices.

Other Notes:

My sample .tar to debug the performance issues I was seeing, that finally brought me to isolate commit 6a2277e as the root cause, was a backup of my old rootfs partition: it doesn;t need to be huge, anything that contains a lot of files, with a lot of associated metadata, will work.
Actually the smaller the ratio between total archived data size and number of files and metadata, the more the difference should be visible.

Pleas. Create a branch ondra and enable it for my account

The pop-default-settings source package does too much. It would be nice if the packages within were broken into seperate source packages, in seperate repos. Also, the changes to base-files should be done directly, rather than with diversions.

Distribution (run cat /etc/os-release):
Pop!_OS 20.04

Issue/Bug Description:
App folders in the Activities overview are called: "Office.directory", "System.directory", and "X-GNOME-Utilities.directory". Expected "Office", "System", and "Utilities".

Distribution (run cat /etc/os-release):
Pop!_OS 20.04

Related Application and/or Package Version (run apt policy $PACKAGE NAME):
lsb_release

Issue/Bug Description:
For 20.04, add Pop!_OS specific lsb_release information so that the Distributor ID will be recognized uniquely as Pop!_OS.

Create a file like /usr/share/python-apt/templates/Ubuntu.info for Pop

Currently an "Automatic Suspend" option is enabled. On battery power the system will suspend after 20 minutes. This feature is normally disabled by default in Pop!_OS.

Java in System, Totem (Video????) out of the folder... more issues in System and Utliities --->

#!/bin/sh

APP_FOLDER="org.gnome.desktop.app-folders.folder:/org/gnome/desktop/app-folders/folders/Pop"

gsettings reset-recursively "${APP_FOLDER}-Office/"
gsettings set "${APP_FOLDER}-Office/" name "Office.directory"
gsettings set "${APP_FOLDER}-Office/" translate true
gsettings set "${APP_FOLDER}-Office/" apps "[
'libreoffice-calc.desktop',
'libreoffice-draw.desktop',
'libreoffice-impress.desktop',
'libreoffice-math.desktop',
'libreoffice-startcenter.desktop',
'libreoffice-writer.desktop'
]"

gsettings reset-recursively "${APP_FOLDER}-System/"
gsettings set "${APP_FOLDER}-System/" name "System.directory"
gsettings set "${APP_FOLDER}-System/" translate true
gsettings set "${APP_FOLDER}-System/" apps "[
'gnome-language-selector.desktop',
'gnome-session-properties.desktop',
'gnome-system-monitor.desktop',
'im-config.desktop',
'nvidia-settings.desktop',
'org.gnome.baobab.desktop',
'org.gnome.DiskUtility.desktop',
'org.gnome.PowerStats.desktop',
'seahorse.desktop',
'software-properties-gnome.desktop',
'system76-driver.desktop',
'gtkorphan.desktop',
'JB-jconsole-jdk8.desktop',
'JB-mission-control-jdk8.desktop',
'JB-controlpanel-jdk8.desktop',
'JB-policytool-jdk8.desktop',
'JB-jvisualvm-jdk8.desktop',
'JB-javaws-jdk8.desktop',
'ca.desrt.dconf-editor.desktop',
'org.gnome.Software.desktop',
'ubuntu-cleaner.desktop'
]"

gsettings reset-recursively "${APP_FOLDER}-Utility/"
gsettings set "${APP_FOLDER}-Utility/" name "X-GNOME-Utilities.directory"
gsettings set "${APP_FOLDER}-Utility/" translate true
gsettings set "${APP_FOLDER}-Utility/" apps "[
'com.github.donadigo.eddy.desktop',
'eog.desktop',
'evince.desktop',
'file-roller.desktop',
'gucharmap.desktop',
'org.gnome.font-viewer.desktop',
'org.gnome.Screenshot.desktop',
'popsicle.desktop',
'simple-scan.desktop',
'dropbox.desktop',
'yelp.desktop',
'gnome-control-center.desktop',
'org.gnome.tweaks.desktop'
]"

gsettings reset org.gnome.desktop.interface scaling-factor

This tweak makes Gnome-Extentions like "App-Folders" unuseable.

Maybe delete this Bash and let it all as default. If we want make folders, we install the Extention.

Distribution (run cat /etc/os-release):
Pop!_OS 20.04

Issue/Bug Description:
Upon upgrade from 18.04 to 20.04, some programs are no longer in the appropriate folder in teh applications overview.

18.04:

20.04:

My initial thought is that programs that are no longer in the correct folder have moved because the name of the program changed or it is a new program added since 18.04.

Steps to reproduce (if you know):
Upgrade system

Distribution (run cat /etc/os-release):

NAME="Pop!_OS"
VERSION="20.04 LTS"
ID=pop
ID_LIKE="ubuntu debian"
PRETTY_NAME="Pop!_OS 20.04 LTS"
VERSION_ID="20.04"
HOME_URL="https://pop.system76.com"
SUPPORT_URL="https://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal
LOGO=distributor-logo-pop-os

Related Application and/or Package Version (run apt policy $PACKAGE NAME):

pop-default-settings:
  Installed: 4.0.6~1598555768~20.04~0ebd76e
  Candidate: 4.0.6~1598555768~20.04~0ebd76e
  Version table:
 *** 4.0.6~1598555768~20.04~0ebd76e 1001
       1001 http://ppa.launchpad.net/system76/pop/ubuntu focal/main amd64 Packages
       1001 http://ppa.launchpad.net/system76/pop/ubuntu focal/main i386 Packages
        100 /var/lib/dpkg/status

Issue/Bug Description:

pop-default-settings is blocking package updates as it currently seems to fail post-installation.

$ sudo apt install
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 to upgrade, 0 to newly install, 0 to remove and 29 not to upgrade.
10 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up pop-default-settings (4.0.6~1598555768~20.04~0ebd76e) ...
Leaving 'diversion of /etc/gdm3/custom.conf to /etc/gdm3/custom.conf.diverted by pop-default-settings'
Leaving 'diversion of /etc/issue to /etc/issue.diverted by pop-default-settings'
Leaving 'diversion of /etc/issue.net to /etc/issue.net.diverted by pop-default-settings'
Leaving 'diversion of /etc/update-motd.d/10-help-text to /etc/update-motd.d/10-help-text.diverted by pop-default-settings'
Leaving 'diversion of /etc/update-motd.d/50-motd-news to /etc/update-motd.d/50-motd-news.diverted by pop-default-settings'
Leaving 'diversion of /etc/lsb-release to /etc/lsb-release.diverted by pop-default-settings'
Leaving 'diversion of /etc/os-release to /etc/os-release.diverted by pop-default-settings'
Leaving 'diversion of /usr/lib/os-release to /usr/lib/os-release.diverted by pop-default-settings'
Warning: apt-key should not be used in scripts (called from postinst maintainerscript of the package pop-default-settings)
gpg: invalid key resource URL '/etc/apt/trusted.gpg.d/home:ungoogled_chromium.gpg'
gpg: keyblock resource '(null)': General error
gpg: key 02456C79B2FD48BF: 1 signature not checked due to a missing key
gpg: key 3B4FE6ACC0B21F32: 3 signatures not checked due to missing keys
gpg: key D94AA3F0EFE21092: 3 signatures not checked due to missing keys
gpg: key 871920D1991BC93C: 1 signature not checked due to a missing key
gpg: Total number processed: 30
gpg:       skipped new keys: 30
dpkg: error processing package pop-default-settings (--configure):
 installed pop-default-settings package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 pop-default-settings
E: Sub-process /usr/bin/dpkg returned an error code (1)

Steps to reproduce (if you know):

Expected behavior:

It should not block installation of other packages nor should it fail.

Other Notes:

I noticed a recent update here that reenabled wayland.

Ubuntu is sticking with Xorg for this release, and I feel that pop should do the same.

There are tons of issues, like gnome not starting on nvidia cards, poor performance from gnome, and complications in optimus systems.

Distribution (run cat /etc/os-release):
Pop!_OS 20.04

Issue/Bug Description:
Currently the output of lsb_release -a has a "Description: " of "Pop!_OS 20.04". This description should say "Pop!_OS 20.04 LTS"

Similarly the PRETTY_NAME shown in /etc/os-release is "Pop!_OS 20.04". It should also say Pop!_OS 20.04 LTS".

Default color #574f4a is way too light, causes readability issues in Terminal. Should be #333.

Distribution (run cat /etc/os-release):
Pop!_OS 19.10

Issue/Bug Description:
Selecting isos opens in nautilus not popsicle.

Fix coming soon

Distribution (run cat /etc/os-release):

$ cat /etc/os-release
NAME="Pop!_OS"
VERSION="19.04"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Pop!_OS 19.04"
VERSION_ID="19.04"
HOME_URL="https://system76.com/pop"
SUPPORT_URL="http://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=disco
UBUNTU_CODENAME=disco

Related Application and/or Package Version (run apt policy $PACKAGE NAME):

$ apt policy irqbalance
irqbalance:
Installed: 1.5.0-3ubuntu1
Candidate: 1.5.0-3ubuntu1
Version table:
*** 1.5.0-3ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
100 /var/lib/dpkg/status

Issue/Bug Description:

as per konkor/cpufreq#48 and http://konkor.github.io/cpufreq/faq/#irqbalance-detected

irqbalance is technically not needed on desktop systems (supposedly it is mainly for servers), and may actually reduce performance and power savings. I am unsure as to what it actually does, and what benefits it actually provides to a desktop or laptop system.

Steps to reproduce (if you know):

This is potentially an issue with all default installs.

Expected behavior:

n/a

Other Notes:

I can safely remove it via "sudo apt purge irqbalance" without any apparent adverse side-effects. If someone is running a situation where they need it, then they always have the option of installing it from the repositories. I didn't even knew it existed and there is very little discussion about its existence. If it is truly a server-oriented package, then it shouldn't be installed by default on a desktop/laptop system.

This involves design work - deciding which icons are part of the folders, as well as work in this repository to set the values correctly.

Distribution NAME="Pop!_OS"
VERSION="20.04 LTS"
ID=pop
ID_LIKE="ubuntu debian"
PRETTY_NAME="Pop!_OS 20.04 LTS"
VERSION_ID="20.04"
HOME_URL="https://system76.com/pop"
SUPPORT_URL="http://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal
LOGO=distributor-logo-pop-os

Related Application and/or Package Version (run apt policy $PACKAGE NAME):

Issue/Bug Description:
Mouse Accelaration is on by default
Giphy https://giphy.com/gifs/fSpC99mtw0WRxWj0J1

**Steps to reproduce (if you know):

1. Upgrading from 19.04**

Expected behavior:
Mouse Accelaration should off be default

**Other Notes:
I was able to resolve the issue by following this guide.
http://www.webupd8.org/2016/08/how-to-completely-disable-mouse.html

To completely disable mouse acceleration, create a file called "50-mouse-acceleration.conf" in xorg.conf.d. The path to xorg.conf.d can vary depending on the Linux distribution you use. For instance, in Ubuntu, Linux Mint, and derivatives, it's /usr/share/X11/xorg.conf.d/. On Arch Linux, it's /etc/X11/xorg.conf.d/.

To open an empty 50-mouse-acceleration.conf file in /usr/share/X11/xorg.conf.d/ with Nano (command line text editor; should be installed by default in most Linux distributions), use the following command:

sudo nano /usr/share/X11/xorg.conf.d/50-mouse-acceleration.conf

And in this file, paste the following:

Section "InputClass"
Identifier "My Mouse"
MatchIsPointer "yes"
Option "AccelerationProfile" "-1"
Option "AccelerationScheme" "none"
Option "AccelSpeed" "-1"
EndSection

Then save the file (to save the file in Nano, use Ctrl + o, then press Enter; to exit, use Ctrl + x). Note that the section just needs an identifier, but the actual name doesn't matter, so you don't have to replace "My Mouse" with anything.

Once you're done, restart the session (logout/login). That's it!

Using this, the Touchpad acceleration is left unchanged.

**

Distribution (run cat /etc/os-release):
Pop!_OS 20.04

Related Application and/or Package Version (run apt policy $PACKAGE NAME):
gnome-shell (gnome-shell-extension-prefs)

Issue/Bug Description:
With GNOME 3.36, gnome-shell-extension-prefs(org.gnome.Extensions.desktop) is a graphical program that is included with GNOME Shell to help manage GNOME Shell extensions. This program should probably be stored in one of the app folders, either "System" or "Utilities".

Pop!_OS 17.10 Beta (build 27)
The plymouth text boot screen shows
Pop!_OS17.10

I think it would look better (and match the Settings>Details>About screen) if there was a space between OS and 17.10.

Distribution (run cat /etc/os-release):
Pop!_OS 19.10

Related Application and/or Package Version (run apt policy $PACKAGE NAME):
TeXInfo

Issue/Bug Description:
An application called TeXInfo is installed by default on Pop!_OS 19.10 when it never was (or at least never had a desktop icon) in previous versions of Pop!_OS.

Distribution (run cat /etc/os-release):
18.04

Issue/Bug Description:
I noticed this morning patches such as 07b30cc have not been applied to the bionic_master branch as well. I was about to create a pr to fix that, when I realized a number of changes (that don't appear to be specific to 19.04/18.10 have not been ported back to 18.04 (such as 4f4a1db)

I could go ahead with a pr for fixing the Popsicle renaming (which I see as a more crucial bug than the feature request for Allowing folder edits by only setting pop app folders on first login).

But I think the bigger issue making sure we apply all necessary patches and not apply patches we don't need in bionic.

Distribution (run cat /etc/os-release):
Pop!_OS 20.04

Related Application and/or Package Version (run apt policy $PACKAGE NAME):
eog

Issue/Bug Description:
In 20.04, Eye of GNOME is not in the Utilities folder like it was for previous Pop!_OS releases.

RTIRQ "rtirq is a simple init script, which main purpose is about to setup IRQ service thread priorities in such a reasonable ordering for general audio workstation." This is a subtle but important change in the underlying subsystem at boot to give audio threads greater priority and preemption capacity.

Add and maintain the latest version of RTIRQ in the repositories, and make sure it gets installed as a dependency or a -recommends with the low-latency kernel.

Furthermore: it may be even better to have it installed by default, as there should be no noticeable adverse effects for users and will contribute significantly to "out the box" lowlatency performance, and also more responsive glitch-free audio in more general use cases. It is LSB compliant.

https://www.rncbc.org/drupal/node/1979 contains the latest, as does
https://www.rncbc.org/archive/#rtirq

They are compiled for RPM. I am happy to compile from source for .deb and be the maintainer for this package if you point me toward a workflow and guidelines for that. I have never built "official" packages for a repository before.

I am also happy to test for any adverse effects. I have used it for years and have not noticed it negatively impacting any other work in the system in any way.

"System Tools" gets truncated and the full name is never shown.

Should be set to dark mode by default.

If this is a bug, please use the template below. If this is a question, or a general discussion topic - please post on our subreddit https://reddit.com/r/pop_os - as that is the proper forum for those types of posts.

Issue/Bug Description
When creating the first 18.04 iso for release, change VERSION to 18.04 LTS and PRETTY NAME to Pop!_OS 18.04 LTS

Add to gsettings override file this lines to fix bugs (gedit no letters in dark mode):
[org.gnome.desktop.wm.preferences]
button-layout='close:appmenu'

[org.gnome.settings-daemon.plugins.xsettings]
overrides={'Gtk/ShellShowsAppMenu': <0>}

[org.gnome.gedit.preferences.editor]
scheme='pop'

To fix sytem 76 logo missing in gdm:
And make symlink from /usr/share/plymouth/themes/system76-logo/shutdown-animation01.png to /usr/share/plymouth/system76-logo/system76_logo.png

gsettings set org.gnome.settings-daemon.plugins.print-notifications active false supposedly works but we need to check if it disables other useful notifications as well.

I've been documenting these and trying to wrangle them with any obvious improvements.

WIP Google Doc

Distribution (run cat /etc/os-release):

18.04 LTS

Related Application and/or Package Version (run apt policy $PACKAGE NAME):

pop-default-settings:
Installed: 3.0.1154204013018.04~37479c7

Issue/Bug Description:

When trying to install and configure pop-default-settings, apt-key would fail with the following error
gpg: keyserver receive failed: Server indicated a failure

Steps to reproduce (if you know):

Upgrade 17.10 to 18.04 through the command line with do-release-upgrade after getting the rest of the packages upgraded.

Expected behavior:

Other Notes:

I was able to bypass the issue by modifying line 25 of /var/lib/dpkg/info/pop-default-settings.postinst to the following;

apt-key adv --keyserver "hkp://keyserver.ubuntu.com:80" --recv-keys "${KEY}"
I added hkp:// and :80 and that seemed to solve it.

Distribution (run cat /etc/os-release):

NAME="Pop!_OS"
VERSION="20.04 LTS"
ID=pop
ID_LIKE="ubuntu debian"
PRETTY_NAME="Pop!_OS 20.04 LTS"
VERSION_ID="20.04"
HOME_URL="https://pop.system76.com"
SUPPORT_URL="https://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal
LOGO=distributor-logo-pop-os

Related Application and/or Package Version (run apt policy $PACKAGE NAME):

pop-upgrade:
  Installed: 0.1.0~1600134377~20.04~9c2a95e
  Candidate: 0.1.0~1600134377~20.04~9c2a95e
  Version table:
 *** 0.1.0~1600134377~20.04~9c2a95e 1001
       1001 http://ppa.launchpad.net/system76/pop/ubuntu focal/main amd64 Packages
        100 /var/lib/dpkg/status

Issue/Bug Description:

Warning come from apt-get upgrade which look like:

W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list:5 and /etc/apt/sources.list:36
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list:5 and /etc/apt/sources.list:36
W: Target Translations (main/i18n/Translation-en_US) is configured multiple times in /etc/apt/sources.list:5 and /etc/apt/sources.list:36
...

because once in a while automatically the following line gets added to the end of /etc/apt/sources.list:

deb http://apt.pop-os.org/proprietary focal main

Steps to reproduce (if you know):

Near the top of /etc/apt/sources.list, change this line:

deb http://apt.pop-os.org/proprietary focal main

into:

deb [arch=amd64] http://apt.pop-os.org/proprietary focal main

This argument is usually added to speed up apt-get upgrade as it only retrieves information suitable for that architecture.

Expected behavior:

Adding [arch=amd64] to the pop's proprietary repo should not trigger re-adding that repo. The trigger doing this should be extended to be able to cope with these architecture arguments.

Other Notes:

I suspect package pop-upgrade is related, if not, please add which package is.

Can we get tilix in as our program? Many users have requested to use Tilix.

This can be done using the gsetting override:

[org.gnome.Terminal.Legacy]
theme-variant = 'dark'

Not required, but would be nice.

https://www.freedesktop.org/software/systemd/man/os-release.html#LOGO=

We use this in some elementary software like the settings plug and onboarding.

If this is a bug, please use the template below. If this is a question, or a general discussion topic - please post on our subreddit https://reddit.com/r/pop_os - as that is the proper forum for those types of posts.

Issue/Bug Description
Change VERSION and PRETTY NAME of Pop!_OS 18.04 appropriately when releasing testing isos.

Expected behavior
When releasing test isos the name(PRETTY NAME) should be something along the lines of Pop!_OS 18.04 LTS (Testing) or Pop!_OS 18.04 LTS (Test release) or something along those lines.

VERSION should probably be something like 18.04 LTS (Testing)

/etc/xdg/autostart/pop-app-folders.desktop

is missing this line
NoDisplay=true

Adding that line will keep pop-app-folders from showing in Startup Applications. It's not something I think you want users to be easily disabling.

You talk about geary. But in default you use evolution. Chenge evolution.desktop to geary.desktop in dash apps in gnome

Since someone's keyboard (like my Logitech!) might have the "Explorer" key, we should keep it in addition to adding Super + F to launch Files

Carl is up in the air about it, but I think it makes sense to ship it. :P It's where you go to get your apps, and the default set of apps is intentionally a bit sparse.

As a long time Ubuntu user, I was surprised that Ctrl+Alt+T didn't work to open a terminal.

As long as there is only one keyboard shortcut allowed for this action (see #12), I recommend using Ctrl+Alt+T for backwards compatibility.

The "Automatic Suspend" feature is currently enabled by default on battery power for 20 minutes. It is desired to disable this feature out of the box.

Distribution (run cat /etc/os-release):
Pop!_OS 19.04

Related Application and/or Package Version (run apt policy $PACKAGE NAME):
gedit

Issue/Bug Description:
The highlight color in gedit with the Pop Light theme appears to be darker than that same similarly colored blue when highlighting in other applications. Potentially this also applies to the Pop Dark theme as well.