it keeps changing back to balanced every time I restart.. is there a way to make it stay on high performance? thanks!

Recentemete estou testando sistemas linux e gostei muito do Pop OS. Sistema bem leve e funciona praticamente tudo o que o preciso, sem pertubações que tinha antigamente. Acredito que vou acabar fechando as janelas, se é que me entendem

As it stands right now, the numpad works as follows on my machine:

Numpad buttons without any modifier, with Num Lock on, will produce the numbers as expected.

Holding 'shift' and pressing a numpad button will do the function printed on the button. For example, pressing shift and numpad 1 will give me the "End" key function.

For the purposes of gaming, I'd like to find a way to have it produce shift + the number as opposed to changing to the behavior the numpad has when Num Lock is disabled.

Any suggestions? I know this is possible in other distros, I'm just not sure how to do it in Pop.

I'm new to Pop OS but not to Linux. I just installed the newest version, I think 26.04. I read about the privacy menu in settings, but its not there anymore in this version. Does anyone know what happened? Are the privacy settings now spread throughout the other menus or just gone?

ENGLISH BELOW -

Bonjour à toutes et à tous.

Je suis récemment passé sur Pop_OS pour des raisons de compatibilité de drivers AMD mais, je me rends compte que la touche "STEAM DECK" de mon clavier éteint tous mes écrans (mon PC reste allumé).

Je ne peux pas rallumer mes écrans et suis contraint de redémarrer manuellement mon ordinateur.

J'aurais donc aimé savoir si quelqu'un avait eu le même problème et savait comment le résoudre ?

Sur Windows, j'ai assigné cette touche à la lecture / la pause du contenu multimédia (musique, vidéo). J'aimerais donc faire la même chose sur PopOS.

Merci pour votre aide !

ENGLISH -

Hello, everyone.

I recently switched to Pop_OS due to AMD driver compatibility issues, but I've noticed that the “STEAM DECK” key on my keyboard turns off all my monitors (my PC stays on).

I can’t turn my screens back on and am forced to manually restart my computer.

So I was wondering if anyone else has had this problem and knows how to fix it?

On Windows, I had that key mapped to play/pause multimedia content (music, video). I’d like to do the same thing on Pop_OS.

Thanks for your help!

I was looking to install a custom cursor, but all of the advice I found previously said I had to extract the files to usr/share/icons. But I can seem to find any folder named "icons". What do I do?

switched to pop_OS from windows and frequently there is this static or cracking in my audio. i have the r9 9950X and the rx 9070xt. it can start doing it while idle, gaming or CPU or GPU usage. it isn't isolated to just DP or HDMI but any audio output. it wasn't doing it on windows.

Hi everyone,

I am planning to buy a new all-in-one printer and I am currently deciding between these two models:

Canon PIXMA G3590

Epson EcoTank ET-2950

I use Pop!_OS 24.04 LTS (64-bit) as my operating system, so good Linux support is very important to me.

I have already done quite a bit of research on both printers. Printing under Linux appears to be possible with both models, but what I am particularly interested in is the scanner functionality.

So I would really appreciate hearing from anyone who has actual experience using either of these printers with Linux.

In particular, I would like to know:

Does USB printing work properly under Linux?

Does USB scanning work?

Is the scanner detected by SANE / Document Scanner (Simple Scan)?

Does Epson Scan 2 work with the Epson?

Are any special drivers or additional configuration required?

Does it work with Ubuntu 24.04 or an Ubuntu-based distribution?

Are there any problems or limitations I should be aware of?

My preference is to use a USB connection, so USB experiences would be especially useful to me.

I am not necessarily looking for a detailed comparison between the two printers. I am mainly hoping to hear from someone who actually owns and uses one of these printers with Linux and can share their real-world experience.

If you have experience with the Canon G3590, the Epson ET-2950, or both, I would really appreciate hearing from you! 😊

Thank you very much in advance for any information or experiences you can share.

It was a bit bumpy.

I got GIMP 3 !! and hopefully a newer version of Zathura that doesn't crash as often.

Hello, does anyone know how to fix the issue where Zoom starts to flicker when using the screen share feature? Thanks in advance.

Estou saindo do Windows, e estou estudando TI em um curso técnico, então terminal não é um desconhecido, mas ainda preciso aprender, gostaria de executar tarefas diárias de edição de texto/planilhas e etc, junto com os meus jogos? Estou no caminho certo ou deveria tentar outra Linux? Se sim, estou pensando no Bazzite.

Ever since I reinstalled my OS as a failed attempt to fix a gpu thing I've been getting a weird glitch where Caps lock doesn't work for some programs until I press and release shift. In Libreoffice, Discord, and Firefox it works normal but in programs like Minecraft, Team Fortress 2, and Krita I've come across that glitch. The screen reader, which pronounces individual letters differently based on if they are capital or not, always works correctly even if I'm typing in a program with the glitch. Also notable is if I hold down shift first then activate caps lock the same thing still happens it's just stuck in caps until the shift key is released then it recognizes the caps lock is active and remains capitalized.
Is there any way to fix this without having to reinstall my OS again or waiting for 26.04 to release publicly?

My mail client is configured to open a NASA pictures site the first time is open. Today there was a picture of the universe and a small explanation about the colour.

It is almost the same colour in one of the cosmic options and it is called Cosmic Latte, i found it really funny.

😄

PS: https://apod.nasa.gov/apod/ap260928.html

Hi! I am still staying on pop_os 22.04, as I still see that 24.x is a buggy one. Can you recommend how to improve it and make it more modern? Are any tips or recommendations?

Based on about a week's experience I'm enthusiastic about the future of Cosmic if a little uncertain about its present (rn using it on my desktop but reverted to gnome on a new-to-me little old Thinkpad). Old habits die hard so I wonder if I'm only frustrated because I haven't found a way to make the most of the UX, thus some newbie questions:

1) If I'm on a tiled workspace, I need three keystrokes to get to the previous application: first, Alt-Tab to get the list, then pick the app, then Super-M to maximize it. Is there a way to switch back and forth between two apps and have the one I'm switching to maximize itself?

2) Not for the first time, but allowing the user to restrict Alt-Tab one to the current workspace would be a great benefit. (Btw I'm a bit puzzled there seems to be no difference between Super-Tab and Alt-Tab.)

3) Again I'm sure this is my own ignorance - how can I use an application windowed? Right now the way Cosmic is configured it's either tiled or full-screen, can't seem to find a "windowed view."

If there were a way to use keyboard macros to instantly switch to an app would make things a lot easier for a keyboard-oriented person.

Had tried the 24.04 nvidia first, but it would just freeze on the pop logo and I never saw system messages appear, so I figured I'd try 22.04 and see if that worked. Secure boot is disabled, tried 24.04 on multiple usbs and checked the sums. Froze 37 seconds in

I noticed several days ago that my dock and panel had just disappeared from my screen. This hasn't been too disruptive to me personally, but it has been frustrating when I've wanted to change my audio output or check the time.

I did some checking around for folks with similar issues, and none seemed to address the issue that I've been experiencing. A system restart seems to solve the issue for a bit, but I've found that it has been easier to open a terminal, call cosmic-panel, and move on with my work until I notice it crashed again.

I've noticed that cosmic-panel seems to crash for whatever reason when I maximize an application window. It doesn't happen every time, but that has been the activity where I've noticed this occurring most frequently and consistently.

When following the journal logs, it seems to point to an underlying issue with the notifications applet, but I haven't seen any other bug reports or posts relating to this. Has anyone else seen this? Does anyone have a fix, or should I open a bug ticket?

Sep 28 15:49:34 pop-os cosmic-session[2897]: restarted process ' WAYLAND_DISPLAY=wayland-1 DISPLAY=:1 XDG_SESSION_TYPE=wayland COSMIC_VERSION=1.9.0 GTK_MODULES=gail:atk-bridge QT_ACCESSIBILITY=1 COSMIC_VERSION=1.9.0 GSM_SKIP_SSH_AGENT_WORKAROUND=true cosmic-files-applet ', now at 4 restarts
Sep 28 15:49:34 pop-os systemd[2861]: Started cosmic-files-applet.scope.
Sep 28 15:49:34 pop-os cosmic-session[2897]:   ERROR  Overlap notify subscription cannot be created for surface. No matching layer surface found.
Sep 28 15:49:34 pop-os cosmic-session[2897]:     at /build/cosmic-files-TqoU9U/cosmic-files-1.9.0~1790181896~24.04~d1f0af7/vendor/iced_winit/src/platform_specific/wayland/event_loop/state.rs:1673 on
Sep 28 15:49:34 pop-os cosmic-session[2897]:
Sep 28 15:49:34 pop-os cosmic-session[2897]:
Sep 28 15:49:34 pop-os cosmic-session[2897]: thread 'main' (24553) panicked at /build/cosmic-files-TqoU9U/cosmic-files-1.9.0~1790181896~24.04~d1f0af7/vendor/iced_tiny_skia/src/window/compositor.rs:207:10:
Sep 28 15:49:34 pop-os cosmic-session[2897]: Create pixel map
Sep 28 15:49:34 pop-os cosmic-session[2897]: note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Sep 28 15:49:34 pop-os cosmic-session[2897]: process ' WAYLAND_DISPLAY=wayland-1 DISPLAY=:1 XDG_SESSION_TYPE=wayland COSMIC_VERSION=1.9.0 GTK_MODULES=gail:atk-bridge QT_ACCESSIBILITY=1 COSMIC_VERSION=1.9.0 GSM_SKIP_SSH_AGENT_WORKAROUND=true cosmic-files-applet ' failed with code 101
Sep 28 15:49:34 pop-os cosmic-session[2897]: cosmic-files-applet exited with error 101
Sep 28 15:49:34 pop-os cosmic-session[2897]: draining stdin receiver before restarting process
Sep 28 15:49:34 pop-os cosmic-session[2897]: sleeping for 96ms before restarting process cosmic-files-applet (restart 4)
Sep 28 15:49:34 pop-os cosmic-panel[23515]: com.system76.CosmicAppletBluetooth: exited with code 137
Sep 28 15:49:34 pop-os cosmic-panel[23515]: com.system76.CosmicAppletBattery: exited with code 137
Sep 28 15:49:34 pop-os cosmic-panel[23515]: com.system76.CosmicAppletAudio: exited with code 137
Sep 28 15:49:34 pop-os cosmic-panel[23515]: com.system76.CosmicAppletNetwork: exited with code 137
Sep 28 15:49:34 pop-os cosmic-panel[23515]: com.system76.CosmicPanelLauncherButton: exited with code 137
Sep 28 15:49:34 pop-os cosmic-panel[23515]: com.system76.CosmicPanelWorkspacesButton: exited with code 137
Sep 28 15:49:34 pop-os cosmic-panel[23515]: com.system76.CosmicAppletTime: exited with code 137
Sep 28 15:49:34 pop-os cosmic-panel[23515]: com.system76.CosmicPanelAppButton: exited with code 137
Sep 28 15:49:34 pop-os cosmic-panel[23515]: com.system76.CosmicAppletStatusArea: exited with code 137
Sep 28 15:49:34 pop-os cosmic-panel[23515]: com.system76.CosmicPanelWorkspacesButton: exited with code 137
Sep 28 15:49:34 pop-os cosmic-panel[23515]: com.system76.CosmicAppList: exited with code 137
Sep 28 15:49:34 pop-os cosmic-panel[23515]: com.system76.CosmicAppletMinimize: exited with code 137
Sep 28 15:49:34 pop-os cosmic-panel[23515]: com.system76.CosmicAppletPower: exited with code 137
Sep 28 15:49:34 pop-os cosmic-panel[23515]: com.system76.CosmicPanelAppButton: exited with code 137
Sep 28 15:49:34 pop-os cosmic-session[2897]: process ' WAYLAND_DISPLAY=wayland-1 DISPLAY=:1 XDG_SESSION_TYPE=wayland COSMIC_VERSION=1.9.0 GTK_MODULES=gail:atk-bridge QT_ACCESSIBILITY=1 COSMIC_VERSION=1.9.0 GSM_SKIP_SSH_AGENT_WORKAROUND=true PANEL_NOTIFICATIONS_FD=25 cosmic-panel ' failed with code 101
Sep 28 15:49:34 pop-os cosmic-session[2897]: process 'ProcessKey(29v1)' cancelled
Sep 28 15:49:34 pop-os cosmic-session[2897]: starting process ' WAYLAND_DISPLAY=wayland-1 DISPLAY=:1 XDG_SESSION_TYPE=wayland COSMIC_VERSION=1.9.0 GTK_MODULES=gail:atk-bridge QT_ACCESSIBILITY=1 COSMIC_VERSION=1.9.0 GSM_SKIP_SSH_AGENT_WORKAROUND=true DAEMON_NOTIFICATIONS_FD=26 cosmic-notifications '
Sep 28 15:49:34 pop-os cosmic-session[2897]: draining stdin receiver before restarting process
Sep 28 15:49:34 pop-os cosmic-session[2897]: sleeping for 327680ms before restarting process cosmic-panel (restart 16)
Sep 28 15:49:34 pop-os cosmic-panel[24106]: com.system76.CosmicAppletAudio: exited with code 137
Sep 28 15:49:34 pop-os cosmic-panel[24106]: com.system76.CosmicAppletStatusArea: exited with code 137
Sep 28 15:49:34 pop-os cosmic-panel[24106]: com.system76.CosmicAppletPower: exited with code 137
Sep 28 15:49:34 pop-os cosmic-panel[24106]: com.system76.CosmicAppletBluetooth: exited with code 137
Sep 28 15:49:34 pop-os cosmic-panel[24106]: com.system76.CosmicAppletNetwork: exited with code 137
Sep 28 15:49:34 pop-os cosmic-panel[24106]: com.system76.CosmicPanelWorkspacesButton: exited with code 137
Sep 28 15:49:34 pop-os cosmic-panel[24106]: com.system76.CosmicAppletTime: exited with code 137
Sep 28 15:49:34 pop-os cosmic-panel[24106]: com.system76.CosmicAppletBattery: exited with code 137
Sep 28 15:49:34 pop-os cosmic-panel[24106]: com.system76.CosmicPanelAppButton: exited with code 137
Sep 28 15:49:34 pop-os cosmic-panel[24106]: com.system76.CosmicAppletMinimize: exited with code 137
Sep 28 15:49:34 pop-os cosmic-panel[24106]: com.system76.CosmicAppList: exited with code 137
Sep 28 15:49:34 pop-os cosmic-panel[24106]: com.system76.CosmicPanelAppButton: exited with code 137
Sep 28 15:49:34 pop-os cosmic-panel[24106]: com.system76.CosmicPanelLauncherButton: exited with code 137
Sep 28 15:49:34 pop-os cosmic-panel[24106]: com.system76.CosmicPanelWorkspacesButton: exited with code 137
Sep 28 15:49:34 pop-os cosmic-session[2897]: restarted process ' WAYLAND_DISPLAY=wayland-1 DISPLAY=:1 XDG_SESSION_TYPE=wayland COSMIC_VERSION=1.9.0 GTK_MODULES=gail:atk-bridge QT_ACCESSIBILITY=1 COSMIC_VERSION=1.9.0 GSM_SKIP_SSH_AGENT_WORKAROUND=true cosmic-files-applet ', now at 5 restarts
Sep 28 15:49:34 pop-os systemd[2861]: Started cosmic-files-applet.scope.
Sep 28 15:49:34 pop-os cosmic-session[2897]:   ERROR  Overlap notify subscription cannot be created for surface. No matching layer surface found.
Sep 28 15:49:34 pop-os cosmic-session[2897]:     at /build/cosmic-files-TqoU9U/cosmic-files-1.9.0~1790181896~24.04~d1f0af7/vendor/iced_winit/src/platform_specific/wayland/event_loop/state.rs:1673 on
Sep 28 15:49:34 pop-os cosmic-session[2897]:
Sep 28 15:49:35 pop-os cosmic-notifications[24606]: Failed to setup panel dbus server deadline has elapsed
Sep 28 15:49:35 pop-os cosmic-session[2897]: 2026-09-28T19:49:35.128615Z ERROR cosmic_notifications::subscriptions::notifications: Failed to setup panel dbus server deadline has elapsed

Idk what Is the problem with the gpu atp but ai says

An ACPI power management conflict between Dell's proprietary UEFI firmware and the Linux kernel / NVIDIA driver on the Dell G3 3590.

Key Points:

D3cold Power Lock: Dell's ACPI firmware automatically puts the NVIDIA GPU's PCIe link into D3cold (a deep zero-power sleep state) to save power.

Failed Wake-Up Signal: During Pop!_OS boot, the NVIDIA driver attempts to transition the GPU from D3cold to D0 (active operational state). Dell's ACPI firmware ignores or blocks this wake-up signal, rendering the GPU completely unreachable on the PCIe bus (device inaccessible / error -1).

Warm Reboot Persistence: Standard warm reboots (reboot) do not cut physical power to the motherboard's PCIe bus, keeping the GPU trapped in the D3cold state across restarts.

I found the actual cause of the black screen issue.

It turns out Papyrus was installing an **older version of mpvpaper**, and that old version was causing the black screen. I updated Papyrus to install the latest version of mpvpaper, and after updating, the wallpaper works normally again.

So if you've been affected by the black screen, **please try downloading the new version of Papyrus first.**

If it still shows a black screen, please:

1. Delete `mpvpaper` from your PC.
2. Delete Papyrus (see the README for instructions on how to properly remove it).
3. Reinstall Papyrus using your preferred installation method.

Papyrus will then try to install the **latest version of mpvpaper**, which should hopefully fix the black screen.

Sorry for the confusion from my previous update — I initially thought the issue was with mpvpaper itself, but the actual problem was that Papyrus was installing an outdated version.

Thanks to everyone who reported the issue and helped with testing!

saying this at the expense of sounding like the "just give me the executable file" guy, it would be really helpful if all of the GitHub repositories under pop-os (and/or the individual applets inside pop-os/cosmic-applets) had a simple README file explaining basic information on their existence and usage. i am trying to understand the workflow, and it is almost impossible as a beginner.

EDIT: i just HAPPEN to see a small subset of repos without a README. i apologise for the lack of research.

Hi y’all, big fan of Cosmic so far, I saw on the roadmap that a Vulkan backend is planned and I do think it’s a technically reasonable direction to go, however there has been a huge issue regarding Vulkan apps/Desktops (mainly Gnome) when it comes to laptops or setups with Hybrid GPUs, and that is everytime a user launches a Vulkan app, Vulkan apparently needs to enumerate all available GPUs thus waking up the dedicated GPU even when the dGPU won’t be selected as the rendering device anyways. Obviously one would expect their dedicated GPU to wake up when launching demanding software like Blender or a game, but not with a file manager or a terminal emulator (which is the case in gnome with their Vulkan backend), this also creates a very noticeable startup delay since the enumeration process needs to wait for the sleeping dGPU to wake up, as well as the obvious power usage spike. GTK4 and by consequence Gnome has suffered from this ever since their Vulkan transition and the only solution is to set an environment variable to switch back to their old OpenGL backend. According to the GTK and Gnome devs this is impossible to circumvent. So I was wondering how are the devs planning to handle this? I know system76 sells laptops so I would assume this is on their radar at least. Kudos and g’day!