beta | apt | |
---|---|---|
53 | 18 | |
358 | 2 | |
1.1% | - | |
1.8 | 0.0 | |
about 2 years ago | about 2 years ago | |
C++ | ||
- | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
beta
-
how to fix this Pop!_Shop
I actually reported this issue a couple months ago
-
22.04 dependency upgrade issue
Initially the when the "upgrade" for 22.04 was available, it went smooth, but after the restart of the OS and before the full install of 22.04 I had some dependency issues I ran into. I found something similar on the github for popos 22.04 beta here: https://github.com/pop-os/beta/issues/370
-
Does anyone experience this weird behavior concerning active windows? Or just me?
I have this weird behavior: When I go to an empty workspace and come back, the window I currently use is deactivated. Only clicking on it activate it. More info here: https://github.com/pop-os/beta/issues/415 This behavior is consistent through recovery and live iso. I don't know it's a new feature or a bug. If a feature, not so good. I mean it's not a deal-breaker, but... Please if you have the same behavior, write here. Here some of my system specs (if it's anyhow related to my system):
-
[22.04] After update, workspaces bugged
I think it's the same bug, can you confirm? : https://github.com/pop-os/beta/issues/415
-
Is there any way set a separate locale for cosmic-dock in 22.04?
There is an issue regarding (afaik) Turkish locale in cosmic-dock: ref1 ref2 And it appears that we can fix that issue when we set the locale English temporarily. So here my question: Is there any way to set a separate locale for just cosmic-dock, like putting "LC_ALL=C" somewhere, until the issue can be fixed permanently?
-
Dock doesn't appear
Is there any indication of an error in the extensions app? Like this one: https://github.com/pop-os/beta/issues/414
-
PopOS 22.04 LTS comes in 3 days.
My experience going from 21.10 to the third beta - it took a couple tries, but my system survived intact. Initially what happened was I went through the entire upgrade process... And booted back into 21.10. It took some finagling in the terminal, but following the instructions Seibz gave on the Github got me to 22.04 without issue.
- How can I fix this?
- How to solve this on 22.04 LTS beta?
-
Why is giving me this error?
22.10 beta shouldn't be out afaik. Their Beta page on GitHub has tle latest beta release at 22.04, since that's the one in testing for release soon.
apt
-
How to remove pop-desktop completely
And if that's not enough, you yourself seem to have been responsible that exactly this change was added to apt. If I may refresh your memory: https://github.com/pop-os/apt/pull/1 It even links to upstream Debian work mentioning exactly this method: https://salsa.debian.org/apt-team/apt/-/merge_requests/196
-
win x lin
And no matter how hard it is, if it's possible to break it, someone will find their way to completely breaking the system. Look at what Linus had to do to break his Pop!_OS install - go to the terminal (which already renders it far out of reach for the average user), run sudo apt install steam, and ignore a giant error. And that wouldn't work anymore anyway, because Pop now uses a version of APT that completely forbids breaking the system unless specifically configured to allow it - so there is now an extra step in there, telling APT not to preserve pop-desktop.
-
Confessions of a self admitted gatekeeper
This isn't locking it down. This is about providing sensible defaults like I mentioned before. For power users, the control is still there. It's easy enough to create the `/etc/apt/break-my-system` file so that you can shoot yourself in the foot if you wanted to. This is not similar to what ChromeOS or Android is doing at all.
-
I think what Linus and Luke at LTT are doing is incredibly important.
ah, I thought you mean https://github.com/pop-os/apt/pull/1
-
System76 Contributions and Collaborations
- Improve the GUI package manager error message: https://github.com/pop-os/shop/pull/302 - Make the apt message more explicit and make the bypass much harder: https://github.com/pop-os/apt/pull/1
-
Now that we have a baby-sitter with apt, how do we remove it?
https://github.com/pop-os/apt/pull/1/files Here is the code change. Note line 311.
-
The Linux community is growing – and not just in numbers
They have already committed a fix that improves things dramatically.
- Whose fault do you think that Linus ended up with a nuked DE and why?
-
What happened with LTT is our fault
And they already issued a "fix" to prevent people to easily "break" it.
-
System76: A Case Study on How Not To Collaborate With Upstream
And their fix for the issue Linus had is downstream only. Not a word said about working with Debian on this.
What are some alternatives?
goxlr-on-linux - Documentation and scripts to make the GoXLR and GoXLR Mini useful on Linux.
ungoogled-chromium - Google Chromium, sans integration with Google
linux - Pop!_OS fork of https://launchpad.net/ubuntu/+source/linux
shop - Pop!_Shop
AppImageLauncher - Helper application for Linux distributions serving as a kind of "entry point" for running and integrating AppImages
fwupd - A system daemon to allow session software to update firmware
docs - System76 support documentation site
flatpak-external-data-checker - A tool for checking if the external data used in Flatpak manifests is still up to date
kwin - Easy to use, but flexible, X Window Manager and Wayland Compositor
upgrade - Utility for upgrading Pop!_OS and its recovery partition to new releases.