A project for managing all Pop!_OS sources

Last update: Jan 6, 2023

Related tags

Overview

Pop!_OS

Pop!_OS is designed for people who use their computer to create; whether it’s complicated, professional grade software and products, sophisticated 3D models, computer science in academia, or makers working on their latest invention. The Pop! user interface stays out of the way while offering extensive customization to perfect your work flow. Built on Ubuntu, you have access to vast repositories of open source software and development tools.

Pop!_OS’s first release was on October 19th, 2017. For more information, visit the Pop!_OS website and view the Pop!_OS documentation.

Purpose

The purpose of this repository is to allow easy management of all Pop!_OS related source code and assets.

Binary packages are hosted on Launchpad. Many packages have source on Github, under the Pop!_OS organization.

To view a list of all included repositories, see REPOS.md

Dependencies

You must install the following packages to use this repository:

python3-launchpadlib

Scripts

This repository contains the following commands:

scripts/clone - clone source code
scripts/debversion - show version of debian package
scripts/ignore - generate .gitignore
scripts/issues - show issues
scripts/launchpad - show PPA packages
scripts/prs - show pull requests
scripts/pull - update source code
scripts/readme - generate REPOS.md
scripts/validate - validate Pop!_OS source code for presence of LICENSE, README, and TESTING documentation

Comments

Boot freezes on: A start job is running for dev-mapper-cryptswap

Distribution: NAME="Pop!_OS" VERSION="18.04 LTS" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 18.04 LTS" VERSION_ID="18.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=bionic UBUNTU_CODENAME=bionic

Issue/Bug Description: After recent update boot freezes on A start job is running for dev-mapper-cryptswap ... / no limit. Until I press any key timer is increasing.

Expected behavior: Boot without user intervention.

Other Notes: I tried to comment swap in /etc/fstab and /etc/crypttab but after that I didn't get login screen - had to go to other terminal, remove comments in both files and reboot machine.

opened by spysiuk 112
Upgrade to 22.04 fails (failed to downgrade packages)

Distribution (run cat /etc/os-release): NAME="Pop!_OS" VERSION="21.10"

Issue/Bug Description: After clicking the "Downloading Pop!_OS 22.04"-Button in OS Upgrade & Recovery, the following error is shown: failed to upgrade OS: client error: failed to downgrade packages

But when I follow all the suggested comments in order like "apt clean", "apt update -m" and so on, no error will be prompted.

Steps to reproduce (if you know): I just used regularly "apt-get update" and "apt-get upgrade" and installed some must-have applications like VSCode via .deb packages.

opened by dlschmidt 58
Recent Pop_OS updates have been changing my GNOME settings
Distribution (run cat /etc/os-release): NAME="Pop!_OS" VERSION="22.04 LTS" ID=pop ID_LIKE="ubuntu debian" PRETTY_NAME="Pop!_OS 22.04 LTS" VERSION_ID="22.04"

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

Issue/Bug Description: When receiving relatively recent Pop_OS updates from the Pop Shop (within the past month or three), I've noticed they are altering some of my Gnome settings. These are the settings I know are being changed, because with each update I am required to manually change things back. This issue exists on both of my laptops (a Darter Pro and a Gazelle):

I don't have the Launcher, Apps or Workspaces icons on my dock, but with the recent Pop! updates have been forcing them back onto my dock requiring me to manually remove them again.

Within my power settings, I turn OFF Automatic Suspend if my machines are on wall power, however, recent Pop! updates have been forcing Automatic Suspend for both battery and wall power, wiping out my personal settings.

Steps to reproduce (if you know): Described above

Expected behavior: My personal settings should never be changed during normal maintenance fixes, which has been the practice in the past. Something changed recently where that hasn't been the case?

Other Notes:
opened by TriggerDingus 53
computer will not shut down

**Distribution POP OS newest

bug description: Upon shutdown the OS will shutdown/ however the computer will not. In fact I have tried several suggested terminal commands and None seem to do any good.

**Steps to reproduce : happens upon every shutdown

**Other Notes:**Simply trying to find a solution. The system I am running it on is several years old and WAS at one time a video editing system (custom build) AMD graphics 4 gig/ 6 core processor/ 16 gigs ram/ Not an off the shelf build

opened by Headrushindi 53
Unable to change desktop background

Distribution (run cat /etc/os-release):
NAME="Pop!_OS" VERSION="21.10" ID=pop ID_LIKE="ubuntu debian" PRETTY_NAME="Pop!_OS 21.10" VERSION_ID="21.10" 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=impish UBUNTU_CODENAME=impish LOGO=distributor-logo-pop-os

Related Application and/or Package Version (run apt policy $PACKAGE NAME): gnome-control-center: Installed: 1:40.0-1ubuntu5pop0~1637613403~21.10~2dafb76

Issue/Bug Description: On new wallpaper selection, wallpaper is not set on desktop

Steps to reproduce (if you know): 1/ Open gnome-control-center 2/ Choose desktop / background 3/ Select background

Expected behavior: Desktop background is changed upon selecting new wallpaper

Other Notes:

opened by garybowers 42

Dependency issue between nvidia-container-runtime and nvidia-docker2

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):

There is a dependency issue between nvidia-container-runtime in the PopOS PPA and nvidia-docker2 so I provide the policy of both below:

apt policy nvidia-container-runtime
nvidia-container-runtime:
  Installed: (none)
  Candidate: 3.4.0-1pop1~1601325114~20.04~2880fc6
  Version table:
     3.5.0-1 500
        500 https://nvidia.github.io/nvidia-container-runtime/stable/ubuntu18.04/amd64  Packages
     3.4.2-1 500
        500 https://nvidia.github.io/nvidia-container-runtime/stable/ubuntu18.04/amd64  Packages
     3.4.1-1 500
        500 https://nvidia.github.io/nvidia-container-runtime/stable/ubuntu18.04/amd64  Packages
     3.4.0-1pop1~1601325114~20.04~2880fc6 1001
       1001 http://ppa.launchpad.net/system76/pop/ubuntu focal/main amd64 Packages
     3.4.0-1 500
        500 https://nvidia.github.io/nvidia-container-runtime/stable/ubuntu18.04/amd64  Packages
     3.3.0-1 500
        500 https://nvidia.github.io/nvidia-container-runtime/stable/ubuntu18.04/amd64  Packages
     3.2.0-1 500
        500 https://nvidia.github.io/nvidia-container-runtime/stable/ubuntu18.04/amd64  Packages
     3.1.4-1 500
        500 https://nvidia.github.io/nvidia-container-runtime/stable/ubuntu18.04/amd64  Packages
     3.1.3-1 500
        500 https://nvidia.github.io/nvidia-container-runtime/stable/ubuntu18.04/amd64  Packages
     3.1.2-1 500
        500 https://nvidia.github.io/nvidia-container-runtime/stable/ubuntu18.04/amd64  Packages
     3.1.1-1 500
        500 https://nvidia.github.io/nvidia-container-runtime/stable/ubuntu18.04/amd64  Packages
     2.0.0+docker18.09.7-3 500
        500 https://nvidia.github.io/nvidia-container-runtime/stable/ubuntu18.04/amd64  Packages
     2.0.0+docker18.09.6-3 500
        500 https://nvidia.github.io/nvidia-container-runtime/stable/ubuntu18.04/amd64  Packages
     2.0.0+docker18.09.5-3 500
        500 https://nvidia.github.io/nvidia-container-runtime/stable/ubuntu18.04/amd64  Packages
     2.0.0+docker18.09.5-1 500
        500 https://nvidia.github.io/nvidia-container-runtime/stable/ubuntu18.04/amd64  Packages
     2.0.0+docker18.09.4-1 500
        500 https://nvidia.github.io/nvidia-container-runtime/stable/ubuntu18.04/amd64  Packages
     2.0.0+docker18.09.3-1 500
        500 https://nvidia.github.io/nvidia-container-runtime/stable/ubuntu18.04/amd64  Packages
     2.0.0+docker18.09.2-1 500
        500 https://nvidia.github.io/nvidia-container-runtime/stable/ubuntu18.04/amd64  Packages
     2.0.0+docker18.09.1-1 500
        500 https://nvidia.github.io/nvidia-container-runtime/stable/ubuntu18.04/amd64  Packages
     2.0.0+docker18.09.0-1 500
        500 https://nvidia.github.io/nvidia-container-runtime/stable/ubuntu18.04/amd64  Packages
     2.0.0+docker18.06.3-3 500
        500 https://nvidia.github.io/nvidia-container-runtime/stable/ubuntu18.04/amd64  Packages
     2.0.0+docker18.06.2-2 500
        500 https://nvidia.github.io/nvidia-container-runtime/stable/ubuntu18.04/amd64  Packages
     2.0.0+docker18.06.2-1 500
        500 https://nvidia.github.io/nvidia-container-runtime/stable/ubuntu18.04/amd64  Packages
     2.0.0+docker18.06.1-1 500
        500 https://nvidia.github.io/nvidia-container-runtime/stable/ubuntu18.04/amd64  Packages
     2.0.0+docker18.06.0-1 500
        500 https://nvidia.github.io/nvidia-container-runtime/stable/ubuntu18.04/amd64  Packages
     2.0.0+docker18.03.1-1 500
        500 https://nvidia.github.io/nvidia-container-runtime/stable/ubuntu18.04/amd64  Packages
     2.0.0+docker17.12.1-1 500
        500 https://nvidia.github.io/nvidia-container-runtime/stable/ubuntu18.04/amd64  Packages

apt policy nvidia-docker2
nvidia-docker2:
  Installed: (none)
  Candidate: 2.6.0-1
  Version table:
     2.6.0-1 500
        500 https://nvidia.github.io/nvidia-docker/ubuntu18.04/amd64  Packages
     2.5.0-1 500
        500 https://nvidia.github.io/nvidia-docker/ubuntu18.04/amd64  Packages
     2.4.0-1 500
        500 https://nvidia.github.io/nvidia-docker/ubuntu18.04/amd64  Packages
     2.3.0-1 500
        500 https://nvidia.github.io/nvidia-docker/ubuntu18.04/amd64  Packages
     2.2.2-1 500
        500 https://nvidia.github.io/nvidia-docker/ubuntu18.04/amd64  Packages
     2.2.1-1 500
        500 https://nvidia.github.io/nvidia-docker/ubuntu18.04/amd64  Packages
     2.2.0-1 500
        500 https://nvidia.github.io/nvidia-docker/ubuntu18.04/amd64  Packages
     2.1.1-1 500
        500 https://nvidia.github.io/nvidia-docker/ubuntu18.04/amd64  Packages
     2.1.0-1 500
        500 https://nvidia.github.io/nvidia-docker/ubuntu18.04/amd64  Packages
     2.0.3+docker18.09.7-3 500
        500 https://nvidia.github.io/nvidia-docker/ubuntu18.04/amd64  Packages
     2.0.3+docker18.09.6-3 500
        500 https://nvidia.github.io/nvidia-docker/ubuntu18.04/amd64  Packages
     2.0.3+docker18.09.5-3 500
        500 https://nvidia.github.io/nvidia-docker/ubuntu18.04/amd64  Packages
     2.0.3+docker18.09.5-2 500
        500 https://nvidia.github.io/nvidia-docker/ubuntu18.04/amd64  Packages
     2.0.3+docker18.09.4-1 500
        500 https://nvidia.github.io/nvidia-docker/ubuntu18.04/amd64  Packages
     2.0.3+docker18.09.3-1 500
        500 https://nvidia.github.io/nvidia-docker/ubuntu18.04/amd64  Packages
     2.0.3+docker18.09.2-1 500
        500 https://nvidia.github.io/nvidia-docker/ubuntu18.04/amd64  Packages
     2.0.3+docker18.09.1-1 500
        500 https://nvidia.github.io/nvidia-docker/ubuntu18.04/amd64  Packages
     2.0.3+docker18.09.0-1 500
        500 https://nvidia.github.io/nvidia-docker/ubuntu18.04/amd64  Packages
     2.0.3+docker18.06.3-3 500
        500 https://nvidia.github.io/nvidia-docker/ubuntu18.04/amd64  Packages
     2.0.3+docker18.06.2-2 500
        500 https://nvidia.github.io/nvidia-docker/ubuntu18.04/amd64  Packages
     2.0.3+docker18.06.2-1 500
        500 https://nvidia.github.io/nvidia-docker/ubuntu18.04/amd64  Packages
     2.0.3+docker18.06.1-1 500
        500 https://nvidia.github.io/nvidia-docker/ubuntu18.04/amd64  Packages
     2.0.3+docker18.06.0-1 500
        500 https://nvidia.github.io/nvidia-docker/ubuntu18.04/amd64  Packages
     2.0.3+docker18.03.1-1 500
        500 https://nvidia.github.io/nvidia-docker/ubuntu18.04/amd64  Packages
     2.0.3+docker17.12.1-1 500
        500 https://nvidia.github.io/nvidia-docker/ubuntu18.04/amd64  Packages

Issue/Bug Description: I think the PopOS PPA is using an outdated version of nvidia-container-runtime which should be 3.5.0 not 3.4.0. Since nvidia-docker2 requires >=3.5.0 I think the PopOS PPA should be updated?

Steps to reproduce (if you know): Follow install instructions as per the NVIDIA container toolkit guide. Since the distribution popos20.04 does not exist I substitute $ID$VERSION_ID with ubuntu20.04 so the GPG step is:

distribution=$(. /etc/os-release;echo ubuntu20.04) \
   && curl -s -L https://nvidia.github.io/nvidia-docker/gpgkey | sudo apt-key add - \
   && curl -s -L https://nvidia.github.io/nvidia-docker/$distribution/nvidia-docker.list | sudo tee /etc/apt/sources.list.d/nvidia-docker.list

Once I run sudo apt-get install -y nvidia-docker2 I get:

sudo apt-get install -y nvidia-docker2
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help resolve the situation:

The following packages have unmet dependencies:
 nvidia-docker2 : Depends: nvidia-container-runtime (>= 3.5.0) but 3.4.0-1pop1~1601325114~20.04~2880fc6 is to be installed
E: Unable to correct problems, you have held broken packages.

Expected behavior: My coworkers followed these steps some months ago without issue and have the inference server with Triton running. So, sudo apt-get install -y nvidia-docker2 should work without any workaround like the one described below.

Other Notes: I can force my way past this using

sudo apt install aptitude
sudo aptitude install nvidia-docker2

I say no to the first option and then yes to the second:

The following NEW packages will be installed:
  nvidia-docker2{b} 
0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/5,960 B of archives. After unpacking 27.6 kB will be used.
The following packages have unmet dependencies:
 nvidia-docker2 : Depends: nvidia-container-runtime (>= 3.5.0) but it is not going to be installed
The following actions will resolve these dependencies:

     Keep the following packages at their current version:
1)     nvidia-docker2 [Not Installed]                     



Accept this solution? [Y/n/q/?] n

The following actions will resolve these dependencies:

     Install the following packages:                   
1)     libnvidia-container-tools [1.4.0-1 (bionic)]    
2)     libnvidia-container1 [1.4.0-1 (bionic)]         
3)     nvidia-container-runtime [3.5.0-1 (bionic)]     
4)     nvidia-container-toolkit [1.5.0-1 (bionic, now)]



Accept this solution? [Y/n/q/?] y

This fixes my issue and then nvidia-docker2 is installed and works. But then I get this horror:

And now PopOS will no longer update.

Ok, so let's try again but say no to the first 2 options and then yes to the third:

sudo aptitude install nvidia-docker2

<say no to first 2>

The following actions will resolve these dependencies:

     Install the following packages:                                           
1)     libnvidia-container-tools [1.3.0-1pop1~1601490873~20.04~cb62a8d (focal)]
2)     libnvidia-container1 [1.4.0-1 (bionic)]                                 
3)     nvidia-container-runtime [3.4.0-1pop1~1601325114~20.04~2880fc6 (focal)] 
4)     nvidia-container-toolkit [1.3.0-1pop1~1601490793~20.04~270505a (focal)] 
5)     nvidia-docker2 [2.5.0-1 (bionic)]

Accept this solution? [Y/n/q/?] y

This not only installs nvidia-docker2 but I can go to the Pop shop and install OS updates without issue. But I think this workaround shouldn't be needed and a smooth customer experience where sudo aptitude install nvidia-docker2 just works is preferred. It used to work after all. And I'd like to see PopOS take over the world, hence the bug report.

opened by Frikster 39

Pop!_OS 18.04 LTS will not log in to the desktop environment from GDM

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 or start a conversation in our chat https://chat.pop-os.org/ - as these are the proper forums for those types of posts.

Distribution - (run cat /etc/os-release) NAME="Pop!_OS" VERSION="18.04 LTS" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 18.04 LTS" VERSION_ID="18.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=bionic UBUNTU_CODENAME=bionic

Related Application and/or Package Version - apt policy $PACKAGE NAME gdm3: Installed: 3.28.0-0ubuntu1pop2 Candidate: 3.28.0-0ubuntu1pop2 Version table: *** 3.28.0-0ubuntu1pop2 1001 1001 http://ppa.launchpad.net/system76/pop/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 3.28.0-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages pop-session: Installed: 2.0.4~1524969709~18.04~8c55250 Candidate: 2.0.4~1524969709~18.04~8c55250 Version table: *** 2.0.4~1524969709~18.04~8c55250 1001 1001 http://ppa.launchpad.net/system76/pop/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status

Issue/Bug Description

Upon typing in the password in gdm3 and attempting to log in, the computer stays at a grey screen and does not start the GNOME desktop environment.

Steps to reproduce (if you know) Power up a Pop!_OS 18.04 LTS computer, and attempt to log in normally. The computer will not enter the GNOME desktop environment.

Expected behavior The computer logs in successfully to the desktop environment.

Other Notes The solution for this issue for the time being is not click the "Not listed?" in gdm, and log in that way. This issue also only happens on my laptop with Intel graphics (I used the Intel/AMD ISO file as well)

opened by cdknight 37

Complete system freeze

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

NAME="Pop!_OS"
VERSION="18.04 LTS"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Pop!_OS 18.04 LTS"
VERSION_ID="18.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=bionic
UBUNTU_CODENAME=bionic

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

Issue/Bug Description: Computer randomly freezes, and when it does, the freeze is complete, not just a GNOME crash - keyboard completely inoperable (caps lock light doesnt show up even), no possible interaction with the computer (eg. tty), no amount of time causes it to unfreeze.

Steps to reproduce (if you know): The issue occurs randomly. However, this will also often happen several times in a row upon reaching the login screen when attempting to recover from the freeze after holding down the power button: the computer will boot normally, Ill enter the disk decrypt key, the login screen will appear, and the moment it does, the entire system freezes. After some number of tries, it will usually eventually allow me into the computer, and work fine from there. But then every now and then it freezes randomly. It happened 4 times today randomly (the first two about 20 minutes apart), and each time it took over 10 tries (reach login screen, freeze, hold power button, reach login screen, freeze, etc.) to finally make it in.

Unfortunately, I cannot reliably reproduce this issue. Near the end of the work day today it froze, so I held the power button and just left. Coming home now to turn it back on, and it booted up & logged in without issue.

Expected behavior: Not freezing

Other Notes: uname -r: 4.15.0-36-generic

Misc info:

Dell XPS 9560 (i7 7700HQ, 32GB RAM, GTX 1050)
I routinely have multiple displays attached, as well as 3-4 USB devices (using a hub), but the freezes occur even when nothing is plugged in

Heres the output from syslog immediately before the latest freeze occurred:

Oct  8 19:21:00 pop-os kernel: [17541.323846] [UFW BLOCK] IN=wlp2s0 OUT= MAC=01:00:5e:00:00:fb:9c:e3:3f:6a:52:1e:08:00 SRC=10.0.1.100 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=65494 PROTO=2 
Oct  8 19:21:24 pop-os gvfsd[1859]: PTP: reading event an error 0x01 occurred
Oct  8 19:21:24 pop-os kernel: [17565.317139] usb 1-2.4: USB disconnect, device number 10
Oct  8 19:21:24 pop-os gvfsd[1859]: message repeated 20 times: [ PTP: reading event an error 0x01 occurred]
Oct  8 19:21:24 pop-os gvfsd[1859]: PTP: reading event an error 0x05 occurred
Oct  8 19:21:24 pop-os upowerd[1293]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.4/1-2.4:1.0
Oct  8 19:21:24 pop-os upowerd[1293]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.4
Oct  8 19:21:24 pop-os gnome-shell[1853]: Object Gio.Settings (0x5618f09a2480), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs
Oct  8 19:21:24 pop-os gnome-shell[1853]: Object Gio.Settings (0x5618da7ac9c0), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs
Oct  8 19:21:24 pop-os org.gnome.Shell.desktop[1853]: == Stack trace for context 0x5618d7d2a340 ==
Oct  8 19:21:24 pop-os org.gnome.Shell.desktop[1853]: #0 0x5618d81f1bf8 i   resource:///org/gnome/shell/ui/messageTray.js:235 (0x7f241ac9d098 @ 22)
Oct  8 19:21:24 pop-os org.gnome.Shell.desktop[1853]: #1 0x7fff21bf0be0 I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f241aeb5de0 @ 71)
Oct  8 19:21:24 pop-os org.gnome.Shell.desktop[1853]: #2 0x5618d81f1b58 i   resource:///org/gnome/shell/ui/messageTray.js:812 (0x7f241aca0098 @ 28)
Oct  8 19:21:24 pop-os org.gnome.Shell.desktop[1853]: #3 0x7fff21bf17c0 I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f241aeb5de0 @ 71)
Oct  8 19:21:24 pop-os org.gnome.Shell.desktop[1853]: #4 0x5618d81f1ab8 i   /home/yonil/.local/share/gnome-shell/extensions/[email protected]/extension.js:236 (0x7f24180c7230 @ 22)
Oct  8 19:21:24 pop-os org.gnome.Shell.desktop[1853]: #5 0x5618d81f1a28 i   resource:///org/gnome/shell/ui/components/autorunManager.js:291 (0x7f241807b4d8 @ 61)
Oct  8 19:21:24 pop-os org.gnome.Shell.desktop[1853]: #6 0x7fff21bf2720 I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f241aeb5de0 @ 71)
Oct  8 19:21:24 pop-os org.gnome.Shell.desktop[1853]: #7 0x5618d81f19a0 i   resource:///org/gnome/shell/ui/components/autorunManager.js:194 (0x7f241807b120 @ 25)
Oct  8 19:21:24 pop-os org.gnome.Shell.desktop[1853]: #8 0x7fff21bf3310 I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f241aeb5de0 @ 71)
Oct  8 19:21:24 pop-os org.gnome.Shell.desktop[1853]: #9 0x7fff21bf33e0 b   self-hosted:918 (0x7f241aef12b8 @ 394)
Oct  8 19:21:24 pop-os org.gnome.Shell.desktop[1853]: == Stack trace for context 0x5618d7d2a340 ==
Oct  8 19:21:24 pop-os org.gnome.Shell.desktop[1853]: #0 0x5618d81f1bf8 i   resource:///org/gnome/shell/ui/messageTray.js:236 (0x7f241ac9d098 @ 42)
Oct  8 19:21:24 pop-os org.gnome.Shell.desktop[1853]: #1 0x7fff21bf0be0 I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f241aeb5de0 @ 71)
Oct  8 19:21:24 pop-os org.gnome.Shell.desktop[1853]: #2 0x5618d81f1b58 i   resource:///org/gnome/shell/ui/messageTray.js:812 (0x7f241aca0098 @ 28)
Oct  8 19:21:24 pop-os org.gnome.Shell.desktop[1853]: #3 0x7fff21bf17c0 I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f241aeb5de0 @ 71)
Oct  8 19:21:24 pop-os org.gnome.Shell.desktop[1853]: #4 0x5618d81f1ab8 i   /home/yonil/.local/share/gnome-shell/extensions/[email protected]/extension.js:236 (0x7f24180c7230 @ 22)
Oct  8 19:21:24 pop-os org.gnome.Shell.desktop[1853]: #5 0x5618d81f1a28 i   resource:///org/gnome/shell/ui/components/autorunManager.js:291 (0x7f241807b4d8 @ 61)
Oct  8 19:21:24 pop-os org.gnome.Shell.desktop[1853]: #6 0x7fff21bf2720 I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f241aeb5de0 @ 71)
Oct  8 19:21:24 pop-os org.gnome.Shell.desktop[1853]: #7 0x5618d81f19a0 i   resource:///org/gnome/shell/ui/components/autorunManager.js:194 (0x7f241807b120 @ 25)
Oct  8 19:21:24 pop-os org.gnome.Shell.desktop[1853]: #8 0x7fff21bf3310 I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f241aeb5de0 @ 71)
Oct  8 19:21:24 pop-os org.gnome.Shell.desktop[1853]: #9 0x7fff21bf33e0 b   self-hosted:918 (0x7f241aef12b8 @ 394)
Oct  8 19:21:24 pop-os kernel: [17565.454403] [UFW BLOCK] IN=wlp2s0 OUT= MAC= SRC=fe80:0000:0000:0000:b20a:e318:239e:8809 DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=58203 PROTO=UDP SPT=8612 DPT=8612 LEN=24 
Oct  8 19:21:24 pop-os kernel: [17565.454413] [UFW BLOCK] IN=wlp2s0 OUT= MAC= SRC=fe80:0000:0000:0000:b20a:e318:239e:8809 DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=627639 PROTO=UDP SPT=8612 DPT=8610 LEN=24 
Oct  8 19:21:24 pop-os kernel: [17565.464497] [UFW BLOCK] IN=wlp2s0 OUT= MAC= SRC=fe80:0000:0000:0000:b20a:e318:239e:8809 DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=58203 PROTO=UDP SPT=8612 DPT=8612 LEN=24 
Oct  8 19:21:24 pop-os kernel: [17565.464505] [UFW BLOCK] IN=wlp2s0 OUT= MAC= SRC=fe80:0000:0000:0000:b20a:e318:239e:8809 DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=627639 PROTO=UDP SPT=8612 DPT=8610 LEN=24 
Oct  8 19:21:25 pop-os gvfsd[1859]: Android device detected, assigning default bug flags

EDIT: (I had my phone plugged in at the time of this log, hence the last line about the Android device. My phone was not plugged in during any other freezes)

If theres any other info I can provide that would be useful let me know.

Thanks!

opened by yonilerner 31

How do you add minimize button to the window?

in other os - even linux there is a way to have three buttons at the top left or right of a window allowing you to close/minimize/or maximize

my pop_os seem to have only 'x' on the top right side of the windows.

which settings do i need to use in order to add those other functions?

cheers

opened by wisdomlight 31
Problems after dist upgrade to 21.04, apt, sound, boot... - not find a distribution template for Pop/hirsute
Distribution (run cat /etc/os-release):

DISTRIB_ID=Pop DISTRIB_RELEASE=21.04 DISTRIB_CODENAME=hirsute DISTRIB_DESCRIPTION="Pop!_OS 21.04"

Related Application and/or Package Version (run apt policy $PACKAGE NAME): Grub, Grub2, apt, gnome, alsamixer, pulseaudio

Issue/Bug Description:

aptsources.distro.NoDistroTemplateException: Error: could not find a distribution template for Pop/hirsute And...

Can't boot, I need to select "old kernel" on PC starts

Can't find Grub or Grb config files do fix the first item

Sound, USB Headset recognition problems, frequently needs restart.

Can't manage packages.

Error in apt:

[wellington]% sudo add-apt-repository ppa:teejee2008/ppa [sudo] senha para wellington: Traceback (most recent call last): File "/usr/bin/add-apt-repository", line 330, in <module> addaptrepo = AddAptRepository() File "/usr/bin/add-apt-repository", line 35, in __init__ self.distro.get_sources(self.sourceslist) File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 91, in get_sources raise NoDistroTemplateException( aptsources.distro.NoDistroTemplateException: Error: could not find a distribution template for Pop/hirsute

Steps to reproduce (if you know): Update to PoP!_OS 21.04

Expected behavior:

Boot working after update

Without package update problems

What to fiz Grub...

Other Notes: Thanks!
opened by wellington1993 28
Broken audio control after upgrade from 21.10 to 22.04
Distribution: NAME="Pop!_OS" VERSION="22.04 LTS" ID=pop ID_LIKE="ubuntu debian" PRETTY_NAME="Pop!_OS 22.04 LTS" VERSION_ID="22.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=jammy UBUNTU_CODENAME=jammy LOGO=distributor-logo-pop-os

Issue Description: Hello guy, I've upgraded from 21.10 to 22.04 and now my audio control is broken, it looks like there are no input/output devices. The sound from both input and output devices of my laptop work, no external mic/headphone though. I have to mention that in the live recovery partition everything looks fine.

What I need is to be able to control the input/output sound devices once again :)

If I try to reinstall pulseaudio I get the following errors:

> sudo apt install pulseaudio Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: pop-desktop : Conflicts: pulseaudio Recommends: io.elementary.sideload but it is not installable Conflicts: pulseaudio:i386 E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.

Any ideas on what can I do?
opened by pvl26 27
PopOS image won't run after "Try or Install PopOS"
PopOS 22.04 LTS

Issue/Bug Description: Black screen after booting live USB and selecting "Try or Install PopOS"

Steps to reproduce (if you know):

Booting a drive running PopOS 22.04 LTS image

Select "Try or Install PopOS"

Expected behavior:

I guess the Desktop Environment should start running?

Other info: I disabled Secure Boot. I tried both Intel and NVIDIA's images thinking it was a graphics driver issue without success. I tried switching to a different USB port, I tried different USB sticks.

Specs: ASUS TUF Dash F15 i7-12650H 3060 Laptop 2x512GB drives 16GB of DDR5 RAM
opened by EmanueleSpadaro 0
Dark theme of okular and kolourpaint don't work properly

Distribution: NAME="Pop!_OS" VERSION="22.04 LTS"

Related Application and/or Package Version: kolourpaint 22.12.10 okular 22.12.10

Issue/Bug Description: When switched to dark theme, icons and text are also black, making them unreadable

Steps to reproduce: For okular, choose color scheme → breeze dark

Expected behavior: Some icons and texts should be different colors.

Example photos

opened by gdnzz 0

Touchpad not working properly on a dell vostro laptop

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

NAME="Pop!_OS"
VERSION="22.04 LTS"
ID=pop
ID_LIKE="ubuntu debian"
PRETTY_NAME="Pop!_OS 22.04 LTS"
VERSION_ID="22.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=jammy
UBUNTU_CODENAME=jammy
LOGO=distributor-logo-pop-os

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

Issue/Bug Description: Installed Pop!_OS on a Dell Vostro 14-3468, everything seems ok but the touchpad is not behaving properly. I can move the cursor on screen using the touchpad easily and tap to click and double-finger-tap to right click works fine.

When pressing the bottom-left and bottom-right on the touchpad I can hear a button press sound but nothing happens on screen and hence I can't use the touchpad to drag and drop icons or resize windows.

Essentially the touchpad is working partially and the clicks at the bottom don't work.

Steps to reproduce :

Get your hands on a Dell Vostro 14-3468
Nuke windows and install Pop!_OS on it.
Touchpad click on pressing the bottom stops working

Expected behavior: Expecting the bottom left click to work so that I can hold it to resize windows or drag stuff.

Other Notes:

Tried using xev, clicking the button does nothing.
xinput output

⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ Synaptics TM3252-001                    	id=11	[slave  pointer  (2)]
⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
    ↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
    ↳ Video Bus                               	id=7	[slave  keyboard (3)]
    ↳ Sleep Button                            	id=9	[slave  keyboard (3)]
    ↳ Intel HID events                        	id=12	[slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard            	id=14	[slave  keyboard (3)]
    ↳ Power Button                            	id=8	[slave  keyboard (3)]
    ↳ Power Button                            	id=6	[slave  keyboard (3)]
    ↳ Integrated_Webcam_HD: Integrate         	id=10	[slave  keyboard (3)]
    ↳ Dell WMI hotkeys                        	id=13	[slave  keyboard (3)]

I have tried changing gnome tweaks mouse emulation settings, it does not help.

opened by gswebspace 0

POP OS Bluetooth Headset options not available (HSP/HFP - mSBC)

Discussed in https://github.com/pop-os/pop/discussions/2739

^{Originally posted by SuperNolvas December 30, 2022}

Issue/Bug Description

Hello. I have noticed that POP OS defaults to AD2P ONLY for any Bluetooth headset connection meaning any microphone input is not available. The option for Handsfree is not available at all and can't be enabled. The handsfree options usually give HSP/HFP , codec mSBC or HSP/HFP, codec CVSD. I have tried editing Wireplumber config and Pipewire but to no avail. I also tested Fedora on the same hardware and this worked on the Live ISO but when installed reverted to the behaviour POP OS is showing. I also tried Garuda Linux (Arch based) on this hardware and it behaved corrected and gave Headset/Handsfree options and also configuration options in the Output section for CODECS for AD2P. I also tested Ubuntu 22.10 on my laptop so different hardware to the PC and it works fine. I do know that my ear buds work correctly and my bluetooth hardware works correctly as I have proven this by using Garuda and Ubuntu.

To show a comparison I will first show screenshots of POP OS illustrating the limited option of AD2P. Then I will show screenshots of Ubuntu with the expected behaviour. I have also made a pipewire configuration dump using the command line program pw-dump on both operating systems for comparison if that helps with the troubleshooting. I have also included the output of patcl list cards for each OS.

System details

My PC is Ryzen 5 3600 GTX 3060 12GB Intel Wireless AC 9260 with Bluetooth 5.1

Distribution

cat /etc/os-release NAME="Pop!_OS" VERSION="22.04 LTS" ID=pop ID_LIKE="ubuntu debian" PRETTY_NAME="Pop!_OS 22.04 LTS" VERSION_ID="22.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=jammy UBUNTU_CODENAME=jammy LOGO=distributor-logo-pop-os

POP OS - Fault behaviour - Headset ONLY, Handsfree is not available

POP OS - pactl list cards output - headset-head-unit profile is missing

POP OS Pipewire config dump

pop_os_22.04_pipewire_config.txt

Expected behaviour as illustrated by Ubuntu 22.10 system. Headset and Handsfree Input / Output settings - these options are missing from POP OS

Ubuntu pactl list cards output, headset-head-unit profile exists

Ubuntu pipewire config

ubuntu_22.10_pipewire_config.txt

Lastly I have looked at the pipewire version, bluez version and wireplumber versions and they differ between Ubuntu, POP OS and Garuda. Garuda having all the latest versions, POP OS some newer/older and Ubuntu some newer/older. So I haven't found any common rationale for this not working but I have seen the same behaviour in other operating systems. I believe this is arising because of a combination of bluez, pipewire and wireplumber configurations but the answer to what is wrong is beyond my troubleshooting capabilities. I would be grateful if the community could look at this issue and I can provide further logs from POP OS and Ubuntu if required.

opened by SuperNolvas 0
Automatic screen blanking stopped working
Distribution (run cat /etc/os-release): NAME="Pop!_OS" VERSION="22.04 LTS" ID=pop ID_LIKE="ubuntu debian" PRETTY_NAME="Pop!_OS 22.04 LTS" VERSION_ID="22.04" BUG_REPORT_URL="https://github.com/pop-os/pop/issues" VERSION_CODENAME=jammy UBUNTU_CODENAME=jammy LOGO=distributor-logo-pop-os

Related Application and/or Package Version (run apt policy $PACKAGE NAME): Power / Privacy-Screen settings

Issue/Bug Description: Screen not blanking, despite putting in 3 minutes in both:

Power / Screen blank

Privacy / Screen / Blank Screen Delay

Privacy / Screen / Automatic Screen Lock Delay

Steps to reproduce (if you know):

set screen blank settings as above

set privacy / Screen settings as above

wait for specified time

screen does not blank

Expected behavior: Screen should go black as before

Other Notes: Use to work, not anymore

CPU Model name: AMD Ryzen 5 2600 Six-Core Processor CPU family: 23 Model: 8 Thread(s) per core: 2

Graphics Card NVIDIA GeForce GTX 1660

Graphics Driver NVIDIA driver version: 525.60.11 NVML version: 12.525.60.11
opened by GerardWassink 1
Shutdown problem with latest kernel

Distribution (run cat /etc/os-release): NAME="Pop!_OS" VERSION="22.04 LTS" ID=pop ID_LIKE="ubuntu debian" PRETTY_NAME="Pop!_OS 22.04 LTS" VERSION_ID="22.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=jammy UBUNTU_CODENAME=jammy LOGO=distributor-logo-pop-os

Related Application and/or Package Version (run apt policy $PACKAGE NAME): Kernel version 6.0.6-76060006-generic

Issue/Bug Description: System does not shut down anymore, hangs "forever" waiting for several processes (NetworkManager, wifi-supplicant) on a intel NUC12WSHi7

Steps to reproduce (if you know): Fresh install, then sudo apt-update and sudo apt-full-upgrade

Expected behavior: System shuts down and powers off

Other Notes:

opened by bitwerkstatt 3