if onlu pop os works on mac os with all the bindings and everything works it would be too damm good.

i installed cosmic on top of asahi linux and adjusted the scaling and it looks beautiful

I don't know what to say beyond the subject. I'm stunned. Stunned.

Anyone know how to set it up so I can connect to WiFi on my laptop (Helios 300) while also using it as a hotspot/repeater for my phone? I was able to do it when I was using window 10.

So, my hp mini pc died with i5-7500 I used as extra machine for dev work... it had nvme disk...

So just took disk out, added to my laptop in second nvme slot, F7 boot from Linux, just told pop os to load nvidia drivers etc and I was good to go ,).. it took me maybe 30 minutes total to open all up transfer etc

It this happened to windows, it would be a mess...

Go Linux ;)

This is the gruvbox version of theme you can use in your cosmic desktop.

Note: this is the initial setup. make further tweaks by your own;

Dark Version

COSMIC Settings:

1. Accent Color: #fabd2f (Yellow)
2. Window Background: #282828
3. Container Background: #3c3836
4. Interface Text Tint: #ebdbb2
5. Control Component Tint: #504945

Light Version

COSMIC Settings:

1. Accent Color: #d79921 (Dark Yellow)
2. Window Background: #fbf1c7
3. Container Background: #ebdbb2
4. Interface Text Tint: #3c3836
5. Control Component Tint: #d5c4a1

wallpapers made from chatgpt.

My previous post :

https://www.reddit.com/r/pop_os/s/9TvD3UxOQv

Hi everyone,

I am planning to install Pop!_OS on my system, but I have a specific display setup that usually causes "Out of Range" / "Input Not Supported" errors on Linux Live USBs due to display adapter mismatches.

My Hardware Setup:

• Monitor: BenQ G922HDAL (Native Resolution: 1366x768 @ 60Hz - VGA connection)
• GPU/CPU: Intel HD Graphics 530 (Intel Core i7-6700T)
• Display Adapters: Monitor (VGA) -> VGA to HDMI adapter -> HDMI to DisplayPort adapter -> PC (DisplayPort)

My Questions:

1. Because of the chained adapters (VGA -> HDMI -> DP), Linux EDID detection sometimes defaults to an unsupported resolution/refresh rate on first boot. How can I pass custom kernel parameters (like nomodeset or video=1366x768@60) in Pop!_OS systemd-boot before booting into the Live environment?
2. If I get an "Out of Range" black screen upon booting the installer, what is the fastest way to switch to TTY (Ctrl+Alt+F3) and set xrandr force mode?

Any advice from people using passive/active display adapters on Pop!_OS would be greatly appreciated! Thanks!

Processing img k9d9scili8yh1...

Processing img suq7pdili8yh1...

Edit: Still looking for a solution, any advice is appreciated

I'm not new to Linux, and I genuinely want to leave Windows for good. I'm a gamer first, but I use this PC for everything.

The problem is I can never make it stick. Something always breaks, usually NVIDIA drivers on my RTX 4060, and I end up crawling back to Windows because I need a machine that works.

How do you stay on Linux when things go wrong? Any tips for making the switch permanent, and has anyone gaming on pop with an NVIDIA card had a smooth experience? (I am not looking at dual booting)

I am considering buying the IdeaPad Pro 5 - Model: 83SJ001CBM with specs, but I can't seem to find any information about Linux support, any help or experience with this or similar models from this year would be of a great help!

AMD Ryzen™ AI 7 450 (8C / 16T, 2.0 / 5.1GHz, 8MB L2 / 16MB L3)

32GB Soldered LPDDR5X-8533

1TB SSD M.2 2242 PCIe® 4.0x4 NVMe®

Integrated AMD Radeon™ 860M Graphics

Note: Compatability matrix pages or documentation on the official page of the model return 403/Access Denied for some reason.

Thanks!

Hey, good folks of Reddit.

Can anyone on 26.04 please test whether Telegram notifications make a sound now?

This isn't possible on 24.04, and I'm wondering if this has been fixed (though it may be a Cosmic issue, and it's unrelated to an underlying Pop_OS update).

The recent update has broken Control Resonant and hasn't done anything positive for me, is there a way i can rollback the update?

howdy howdy, just wanted to ask if the timeline here is being updated any more or if im just being impatient, from the looks of it, it hasnt been updated in months. please let me know if im wrong!

Hi everyone! I’ve released Papyrus 2.0.0, a free, open-source wallpaper manager for Linux desktops.

Papyrus lets you use video and image files as wallpapers, with per-monitor settings and playlist rotation. This release adds a few ways to make the app easier to use and more efficient:

- Search, filters, and sorting for your wallpaper library

- Smart Auto-Pause to pause playback when windows cover a display or a fullscreen app is active, helping reduce resource use

- Frosted-glass fallback that keeps the interface looking right even when no wallpaper is set

- Custom app backdrop so you can choose the image shown behind the frosted-glass panels

- Fedora COPR packaging alongside the existing installation options

Papyrus is built around mpvpaper and targets Wayland compositors that support wlr-layer-shell. COSMIC-specific wallpaper color theming is included too. There are no accounts, cloud services, or telemetry.

Project: https://github.com/PSGtatitos/papyrus

Fedora COPR: https://copr.fedorainfracloud.org/coprs/psgtatitos/papyrus/

I’d love feedback, especially from people using different Wayland compositors. What would you like to see in a future release?

System configuration

• Laptop: GIGABYTE G5 KF
• OS: Pop!_OS 26.04 (COSMIC / Resolute)
• GPU: NVIDIA GeForce RTX 4060 Laptop GPU
• NVIDIA driver: 595.104.02 (open kernel modules)
• Original kernel: 7.1.5-76070105-generic
• Updated kernel: 7.2.6-76070206-generic
• Root filesystem: ext4 on LVM inside a LUKS-encrypted NVMe partition
• Bootloader: systemd-boot with kernelstub-managed EFI files

Symptoms

Normal boot would hang during early initialization while waiting for:

/dev/mapper/data-root

The LUKS password prompt appeared, but the encrypted root volume did not become available and the system could not finish booting.

Increasing Dracut's retry timeout was considered, but the system was already waiting for several minutes, making a simple timeout issue unlikely.

Troubleshooting

We verified that:

• The NVMe drive and encrypted partition were detected.
• The LUKS mapping and LVM logical volume worked during successful boots.
• The initramfs contained the required crypt, lvm, and NVMe components.
• The NVIDIA 595 module was installed for the running kernel.
• The LVM udev rules and lvm_scan script matched between the old and new initramfs images.

A particularly useful test was booting with rd.break=pre-trigger. After typing exit and entering the LUKS password, the system booted successfully.

Kernel stack trace

During a failing boot, we reached the Dracut initqueue shell and found a blocked udev worker.

Its kernel stack included NVIDIA functions such as:

• kgspInitRm_IMPL
• RmInitAdapter
• nv_start_device
• nv_open_device
• nvkms_open_gpu
• nv_drm_register_drm_device

The kernel also reported a udev worker blocked on an rw-semaphore, likely owned by a kernel worker.

This provided strong evidence of a hang during NVIDIA GPU initialization. We could not conclusively prove that this was the direct cause of the missing LUKS/LVM root device, but it gave us a much more specific lead than the earlier LVM investigation.

Workaround that worked

We added the following parameter to the normal EFI boot entry's options line:

rd.driver.blacklist=nvidia,nvidia_drm,nvidia_modeset,nvidia_uvm

This tells Dracut not to load those NVIDIA modules during the initramfs stage. Dracut documents rd.driver.blacklist for preventing modules from loading during early boot.

Documentation: https://github.com/dracut-ng/dracut/blob/main/man/dracut.usage.adoc

The system then booted normally without manually stopping at a Dracut breakpoint. NVIDIA loaded later, and nvidia-smi worked.

Results

The workaround was tested successfully with:

1. Kernel 7.1.5-76070105-generic
2. Kernel 7.2.6-76070206-generic

For both, NVIDIA 595.104.02 loaded successfully after boot, and nvidia-smi recognized the RTX 4060.

The kernel update also completed successfully, including the DKMS build of NVIDIA 595 for kernel 7.2.6.

Important persistence detail

This system uses kernelstub to manage the EFI kernel and initramfs files. During the kernel update, kernelstub regenerated the default boot entry and removed the blacklist parameter we had added manually.

We restored the parameter in both:

• /boot/efi/loader/entries/Pop_OS-current.conf — the normal boot entry
• /boot/efi/EFI/Pop_OS-<machine-id>/cmdline — kernelstub's command-line configuration

After restoring the parameter in both places, the system successfully booted kernel 7.2.6 with NVIDIA 595.104.02.

If you try this workaround, verify your own bootloader's configuration and ensure the parameter survives kernel updates. Do not copy the example paths blindly.

Current status

• Normal boot works without a manual Dracut breakpoint.
• Kernel 7.2.6 is running.
• NVIDIA 595.104.02 and nvidia-smi work.
• The encrypted LUKS/LVM root filesystem mounts successfully.
• The previous-kernel fallback and recovery entry were retained.

Caveat

This is a workaround, not a confirmed root-cause fix. The evidence strongly suggests a problem involving NVIDIA initialization during early boot, but we did not identify the precise driver bug or prove the complete causal chain.

If anyone has seen similar NVIDIA 595 hangs involving kgspInitRm_IMPL, RmInitAdapter, or blocked udev workers on GIGABYTE G5 KF hardware, I'd be interested to know whether this workaround helps or whether a more permanent fix is available.

The screenshot shows the blocked udev worker's kernel stack trace for anyone interested

I have been using Pop OS for years and love the progress with COSMIC. I also recognize this issue may not pertain to Pop OS specifically, but the fixes I have seen are not seeming to work on Pop OS 24.04 so I am curious to see if y'all have found a fix for this.

The crux of the issue is that my new steam controller thinks its in 'Desktop Mode' when I am playing games, and the B button is mapped to Escape, so it pauses all the games when I press b.

From what I can tell, the main point of the issue is that Steam cannot tell what window is active in Wayland, so Steam Input is falling back to the generic Desktop Mode.

I have tried un-mapping the B button in Desktop Mode under the advanced controller settings with no success.

I tried env -u WAYLAND_DISPLAY %command% and PROTON_ENABLE_WAYLAND=0 %command% in the command line options for some of my games to try to force the game to be rendered through XWayland with no success.

I have also tried the wrapper script mentioned in this github issue comment with no results. I did notice that there are some interesting things happening since the wrapper script exposes what %command% is. From what I can tell, Steam is trying to use some 32-bit .so files, but I am not sure if that really is the case. Here are some lines from the log from the wrapper script that show some linker issues due to the shared libraries being referenced are 32-bit (from what I can understand).

11:00:46 [wrap] start appid=367520 output=DP-2 cmd=gamemoderun /home/isaacsmith/.local/share/Steam/ubuntu12_32/steam-launch-wrapper -- /home/isaacsmith/.local/share/Steam/ubuntu12_32/reaper SteamLaunch AppId=367520 -- /home/isaacsmith/.local/share/Steam/steamapps/common/SteamLinuxRuntime_4/_v2-entry-point --verb=waitforexitandrun -- /home/isaacsmith/.local/share/Steam/steamapps/common/Proton 11.0/proton waitforexitandrun /home/isaacsmith/.local/share/Steam/steamapps/common/Hollow Knight/hollow_knight.exe
ERROR: ld.so: object '/home/isaacsmith/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/isaacsmith/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/isaacsmith/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.

Anyone else experience this same behavior?

Since we received the 7.2 kernel update, or I should say the update containing the 7.2 kernel, my screen will blank out for a couple of seconds randomly and then come back. It may do this once or twice, or maybe a half dozen times, before settling down. I can find no reason for it, no specific applications or tasks I'm performing. This only happens under Wayland thought. I switched from COSMIC back to Xfce and I haven't had the issue since.

Computer is a Thelio Mira 13700K with Nvidia 4060ti running pop 24.04.

An unrelated item, Zoom Workspace has been terrible under Wayland lately. The latest client is unusable with the application crashing when I create or edit a meeting. Not a PopOS issue, a Zoom one, but thought I'd point it out. It's another reason I'm back on Xfce for a while - that's a major workflow issue for me.

Hello. I have downloaded an AppImage file yesterday, Bluestar Manager, and for whatever reason it won't launch. I did what I did before and was told by a friend, which was go into the AppImage's properties and change the permissions to everything be read and write and allow execute as program, but I try double clicking and nothing happens. It's not a major deal as it's just to mod a video game, but I want to try and get it sorted before I throw in the towel

Hi, I need these functionalities in Pop!_OS: - Simple screen recording application - I've tried OBS, it works but it's too complicated. I want something simple like it is in windows. I tried Kooha but it was crashing. - A keycaster to display my keystrokes (like KeyViz).

Nothing, just a little bit of customisation.

1. DE : Cosmic
2. Icon theme : Papirus
3. Gnome like quick settings : quick settings applet from Cosmic store.
4. Colors: accent color yellow, background pitch black
5. Wallpaper : ml4w GitHub wallpapers.
6. Workspace applet: from cosmic store.

Note: turn off frosted glass to look more beautiful.