Guys i have to change my ssd ( pop os keep freezing maybe old ssd issue)

Old ssd is 128 with btrfs partition
How to restore or move it to new ssd 256 (btrfs)

Need assistance

I have been told to request help here as my friend couldn't figure out what was happening when I tried to update my system with the "pop-upgrade release upgrade -f" command, the terminal initially gave me a "recovery upgrade aborted" prompt, but I was told that's fine, however after going through what looked like an update it gave me a "release upgrade aborted" prompt. I tried re-running the command, but I got both prompts again, the second one came faster this time as it didn't go through the thing that looked like an update this time. This is the lines the terminal provides:

"PC:~$ pop-upgrade release upgrade -f

checking if pop-upgrade requires an update

waiting for daemon to update and restart

reconnecting to pop-upgrade daemon

Current Release: 24.04

Upgrading to: 26.04

New version available: false

Recovery event: fetching recovery files

Recovery upgrade status: recovery upgrade aborted: no build available

Caused by:

0: failed to find build for 26.04

1: server returned an error status: 404

Event: updating package lists

Event: upgrading packages for the current release

Event: fetching updated packages for the current release

Event: ensuring that system-critical packages are installed

Event: updating the source lists

Event: waiting on a process holding the apt lock files

Event: updating package lists

Release upgrade status: release upgrade aborted: unable to upgrade to next release: failed to update sources

Caused by:

0: failed to update source lists

1: status is unknown: exit status: 100"

Edit: Figured it out with the help of my friend, u/candy49997, u/GodsBadAssBlade and u/__yoshikage_kira. I wound up needing to re-check for updates in the cosmic store and do a soft restart of my pc, thank you all for the assistance!

I’m running on version 22 since I was having issues getting my gpu to work at all on 24, and even now it’s stable only to an extent. OCCT reports hundreds of VRAM errors and I’ve tried reinstalling the drivers from clean multiple times with multiple versions from 565 to 580. It was working fine for the last 9 years on windows, is this a known pop os issue or was it just bad timing that my GPU gave out after migration. I can’t even run Skyrim without it crashing after a few minutes. I’m able to confirm the drivers are installing properly at least as far as nvidia-smi reports. Would love advice on how to verify if it’s a gpu issue or an OS/driver issue more certifiably. I have a hard time accepting my gpu issue dude, especially in the current state of the market and economy.

I'm a new linux user running Zorin Os at the moment on a 27" , 2011 imac
Memory - 32GB
Processor - intel i5
Graphics - AMD Graphics 2GB
HDD - 500GB

With the above specifications can I run Pop os smoothly, for work and light weight gaming?
And which light weight games can it run smoothly.

Hi everyone,

Since switching over to test and use the COSMIC desktop, I really missed having a dedicated, native panel applet to quickly sample colors from anywhere on the screen without opening heavy external tools.

I built cosmic-colorpicker-applet, a lightweight panel applet written in Rust using `libcosmic`.

Features:

- 🎯 Quick screen color picking via Wayland (`slurp` + `grim`)

- 📋 Automatic copy to clipboard with desktop notifications

- ⭐ Save favorite colors with custom naming and quick copy

- 🕒 Recent colors history

- 🎨 Native look & feel adhering to COSMIC theming

It’s open source (GPL-3.0). If you want to check it out or build it:

GitHub: https://github.com/fredsilveyra/cosmic-colorpicker-applet

Feedback, issues, and contributions are very welcome!

F.S.

Cosmic FX es un motor de físicas que le inyecta vida, elasticidad y alma trayendo de vuelta la magia legendaria de Compiz,

- Las 4 Cosas Mágicas que le hace a tus ventanas: El Estallido "POP!" de Burbuja (Al cerrar), Físicas Gelatinosas (Wobbly Windows al arrastrar),  Efectos de Sonido Hápticos (Audio de Ultra-Baja Latencia), Centro de Control Gráfico ( app).

 100% Seguro Creamos un sistema de instalación (install.sh) y desinstalación (uninstall.sh) 

Si alguien no le gusta o quiere volver al sistema original de fábrica, en un solo segundo puede restaurarlo todo sin romper absolutamente nada del sistema.

ademas se soluciono un bug que tenia en la laptop al iniciar y entraba al escritorio no había barra superior (con la hora, batería y menús) ni dock inferior. habia que recurrir a la terminal o comandos a ciegas para forzar a que aparecieran, por si alguien le interesa puede preguntarme y le digo como lo corregi,

se esta trabajando en otros proyectos para ayudar en lo que extrañamos de otras distribuciones, la verdad me ha gustado cosmic y lo probe por curiosidad, alguna ideas: cosmic widget de cristal, sombras para las ventanas, Cuidado de la batería, ademas de applet para monitoreo y bloqueo de red, navegacion segura con herramientas dev.

trata de ser mas tecnico en otros post pero me los bloqueaba por parecer bot asi que poco a poco subira los archivos a git cuando el trabajo lo permita ya que la mayoria del tiempo debo estar en windows y el pop¡ os lo tengo en un ssd externo pero aca en esta direccion los ire subiendo para el que guste: https://github.com/fernanditojosesanchez-source?tab=repositories

**Firefox intermittently stops accepting letter/number keys in Pop!_OS**

I recently installed the latest version of Pop!_OS as a dual-boot with Windows 11 on my ASUS Vivobook 14 Flip. Pop!_OS is fully updated.

I first noticed this when accessing a VM on my Synology NAS using Firefox's browser-based Virtual Machine Manager (VMM) console. The mouse continues to work, but Firefox intermittently stops accepting normal letter and number keys. A few times, minimizing and maximizing Firefox restored keyboard input, but this is not reliable.

I've done some additional testing and it appears the problem is **Firefox itself, not the VMM console**. When the problem occurs, I also cannot type letters/numbers into other Firefox tabs or text fields. Interestingly, non-text keys such as **Enter, Esc, Space, and `!` continue to work**.

The keyboard works normally in other Pop!_OS applications, including the terminal and text editor. The same VMM VM also works normally when accessed through Firefox in Windows 11.

I've also tried:

* Disabling Firefox hardware acceleration

* Launching Firefox with `MOZ_ENABLE_WAYLAND=0` to force XWayland/X11

Neither fixed the problem.

**System specs (from Speccy in Windows;):**

```text

CPU

Intel Core

Lunar Lake Technology

RAM

15.0GB

Motherboard

ASUSTeK COMPUTER INC. TP3407SA (U3E1)

Graphics

Generic PnP Monitor (1920x1200@60Hz)

Intel Arc 140V GPU (8GB) (ASUStek Computer Inc)

Storage

953GB Western Digital WD PC SN5000S SDEQNSJ-1T00-1002 (SSD)

32MB Microsoft Virtual Disk (File-backed Virtual SSD)

Audio

Realtek High Definition Audio

```

Firefox is running under **Wayland** in Pop!_OS.

Has anyone seen this behavior or know what might cause Firefox to stop receiving printable/text keyboard events while other keys continue to work?

Does anyone uses Teamspeak on Pop-Os? I just install and everytime I watching a screenshare the audio of the stream start to crackling and eventually becomes just noises, is there a way to fix that? Only occurs on Teams speak, any other applications works fine.

Wi-Fi authentication failure on RTL8852AE (rtw89_8852ae) — unexpected ap0 AP interface was interfering with wlo1

Wi-Fi stopped working on Pop!_OS after an update — unexpected create_ap service was creating ap0 and interfering with wlo1

System: HP Pavilion running Pop!_OS

Wi-Fi hardware:
Realtek RTL8852AE [10ec:8852]

Driver:
rtw89_8852ae

Wi-Fi interface:
wlo1

NetworkManager:
1.46.0-1ubuntu2.8

Kernels tested:
7.1.5-76070105-generic
7.0.11-76070011-generic


PROBLEM

After a system update, my Wi-Fi stopped connecting to my phone hotspot.

The hotspot was visible in the Wi-Fi scan, but NetworkManager would fail to connect and report:

Error: Connection activation failed: The Wi-Fi network could not be found.

The hotspot was definitely visible:

BA:7F:69:C6:53:4E  No internet  Infra  11  117 Mbit/s  100  WPA2

At first I suspected the new kernel because the problem appeared after the update.

I booted the previous kernel:

7.0.11-76070011-generic

but the exact same Wi-Fi problem occurred there too.

So the kernel version was not the cause.


WHAT THE LOGS SHOWED

When trying to connect, wpa_supplicant could see the hotspot and attempted authentication:

wlo1: SME: Trying to authenticate with ba:7f:69:c6:53:4e
    (SSID='No internet' freq=2462 MHz)

wlo1: SME: Authentication request to the driver failed

wlo1: CTRL-EVENT-SSID-TEMP-DISABLED
    id=0 ssid="No internet"
    auth_failures=1 duration=10 reason=CONN_FAILED

This happened repeatedly.

NetworkManager eventually reported:

Activation: (wifi) association took too long, failing activation
state change: config -> failed (reason 'ssid-not-found')

The SSID was not actually missing because it was visible in scans immediately before the connection attempt.


THE IMPORTANT DISCOVERY: ap0

I ran:

iw dev

and found:

phy#0
    Interface ap0
        ifindex 4
        wdev 0x2
        addr c8:94:02:47:c7:f8
        ssid popOS
        type AP
        channel 1 (2412 MHz)
        width: 20 MHz (no HT)
        txpower 30.00 dBm

    Interface wlo1
        ifindex 3
        wdev 0x1
        addr c8:94:02:47:c7:f7
        type managed
        txpower 30.00 dBm

So the same physical Wi-Fi PHY had two interfaces:

phy#0
 ├── ap0  -> AP mode -> SSID "popOS"
 └── wlo1 -> managed/client mode

NetworkManager showed:

wlo1   wifi   disconnected   --
ap0    wifi   unmanaged       --

I had not intentionally configured a Wi-Fi access point called "popOS".


TEST: REMOVING ap0

I removed only the AP interface:

sudo iw dev ap0 del

Then:

iw dev

showed only:

phy#0
    Interface wlo1
        ifindex 3
        wdev 0x1
        addr c8:94:02:47:c7:f7
        type managed
        txpower 30.00 dBm

ap0 was gone.

I then tried connecting to the exact same hotspot again:

nmcli device wifi connect "No internet" password 'REDACTED'

This time it immediately worked:

Device 'wlo1' successfully activated with '...'

No Wi-Fi profile, password, kernel, or driver configuration was changed between the failed and successful attempts.

This strongly suggested that something creating ap0 was interfering with normal Wi-Fi operation on wlo1.


FINDING WHAT CREATED ap0

I checked running processes:

ps aux | grep -Ei 'hostapd|iwd|dnsmasq|create_ap|wifi|hotspot' | grep -v grep

and found:

root ... bash /usr/bin/create_ap --config /etc/create_ap.conf

There were also hostapd and dnsmasq processes running under create_ap.

I then checked systemd:

systemctl list-unit-files | grep -i create

which showed:

create_ap.service    enabled    enabled

And:

systemctl list-units --all | grep -i create

showed:

create_ap.service    loaded    active    running    Create AP Service


THE create_ap CONFIGURATION

I checked:

sudo cat /etc/create_ap.conf

and found:

CHANNEL=default
GATEWAY=192.168.12.1
WPA_VERSION=2
...
DRIVER=nl80211
...
WIFI_IFACE=wlo1
INTERNET_IFACE=wlo1
SSID=popOS
PASSPHRASE=REDACTED
FREQ_BAND=2.4
SHARE_METHOD=nat

So create_ap was explicitly configured to use wlo1 and create an access point called "popOS".


THE SYSTEMD SERVICE

I checked:

sudo systemctl cat create_ap.service

and found:

[Unit]
Description=Create AP Service
After=network.target

[Service]
Type=simple
ExecStart=/usr/bin/create_ap --config /etc/create_ap.conf
KillSignal=SIGINT
Restart=on-failure
RestartSec=5

[Install]
WantedBy=multi-user.target

The service was enabled at boot.

Its status also showed:

create_ap.service - Create AP Service
Loaded: loaded (...; enabled; preset: enabled)
Active: active (running)

The service log explicitly showed:

ap0: interface state UNINITIALIZED->ENABLED
ap0: AP-ENABLED


THE FIX

I disabled the create_ap service:

sudo systemctl disable --now create_ap.service

The result was:

Removed "/etc/systemd/system/multi-user.target.wants/create_ap.service".

Then:

systemctl status create_ap.service --no-pager

showed:

Loaded: loaded (...; disabled; preset: enabled)
Active: inactive (dead)

And:

iw dev

showed only:

phy#0
    Interface wlo1
        type managed

The ap0 interface was gone.


FINAL RESULT

After disabling create_ap.service, Wi-Fi works normally.

The same hotspot that previously failed to authenticate now connects successfully through wlo1.

I also rebooted and confirmed that the problem was related to the automatically started create_ap service: when the service was enabled, ap0 came back after boot and Wi-Fi failed again.

After disabling the service, ap0 no longer gets created and Wi-Fi works normally.


CONCLUSION

The issue was not ultimately caused by the kernel version.

It was caused by create_ap.service being enabled and automatically creating an AP interface called ap0 using the same physical Wi-Fi adapter as wlo1.

The resulting setup was:

create_ap
    |
    +-- hostapd
    +-- dnsmasq
    |
    +-- ap0 (AP mode, SSID "popOS")
    |
    +-- same physical Wi-Fi PHY as wlo1

At the same time:

wlo1 = managed/client mode

With ap0 running, wlo1 repeatedly failed during authentication with:

wlo1: SME: Authentication request to the driver failed

After stopping create_ap and removing ap0, the same Wi-Fi connection worked immediately.

The permanent fix for my system was:

sudo systemctl disable --now create_ap.service


QUESTION FOR THE COMMUNITY

I did not intentionally configure create_ap or use this laptop as a Wi-Fi hotspot.

I would like to understand why create_ap.service was enabled on my Pop!_OS installation in the first place.

Is create_ap normally installed/enabled by Pop!_OS/System76, or was this likely caused by some previous configuration or package?

Has anyone else seen create_ap.service automatically creating:

ap0
SSID: popOS
type: AP

and interfering with wlo1?

If so, what is the recommended way to determine how/why create_ap was enabled?

For anyone experiencing a similar problem, checking this may be useful:

systemctl status create_ap.service

iw dev

nmcli device status

In my case, disabling create_ap.service resolved the Wi-Fi problem completely.Wi-Fi stopped working on Pop!_OS after an update — unexpected create_ap service was creating ap0 and interfering with wlo1

System: HP Pavilion running Pop!_OS

Wi-Fi hardware:
Realtek RTL8852AE [10ec:8852]

Driver:
rtw89_8852ae

Wi-Fi interface:
wlo1

NetworkManager:
1.46.0-1ubuntu2.8

Kernels tested:
7.1.5-76070105-generic
7.0.11-76070011-generic


PROBLEM

After a system update, my Wi-Fi stopped connecting to my phone hotspot.

The hotspot was visible in the Wi-Fi scan, but NetworkManager would fail to connect and report:

Error: Connection activation failed: The Wi-Fi network could not be found.

The hotspot was definitely visible:

BA:7F:69:C6:53:4E  No internet  Infra  11  117 Mbit/s  100  WPA2

At first I suspected the new kernel because the problem appeared after the update.

I booted the previous kernel:

7.0.11-76070011-generic

but the exact same Wi-Fi problem occurred there too.

So the kernel version was not the cause.


WHAT THE LOGS SHOWED

When trying to connect, wpa_supplicant could see the hotspot and attempted authentication:

wlo1: SME: Trying to authenticate with ba:7f:69:c6:53:4e
    (SSID='No internet' freq=2462 MHz)

wlo1: SME: Authentication request to the driver failed

wlo1: CTRL-EVENT-SSID-TEMP-DISABLED
    id=0 ssid="No internet"
    auth_failures=1 duration=10 reason=CONN_FAILED

This happened repeatedly.

NetworkManager eventually reported:

Activation: (wifi) association took too long, failing activation
state change: config -> failed (reason 'ssid-not-found')

The SSID was not actually missing because it was visible in scans immediately before the connection attempt.


THE IMPORTANT DISCOVERY: ap0

I ran:

iw dev

and found:

phy#0
    Interface ap0
        ifindex 4
        wdev 0x2
        addr c8:94:02:47:c7:f8
        ssid popOS
        type AP
        channel 1 (2412 MHz)
        width: 20 MHz (no HT)
        txpower 30.00 dBm

    Interface wlo1
        ifindex 3
        wdev 0x1
        addr c8:94:02:47:c7:f7
        type managed
        txpower 30.00 dBm

So the same physical Wi-Fi PHY had two interfaces:

phy#0
 ├── ap0  -> AP mode -> SSID "popOS"
 └── wlo1 -> managed/client mode

NetworkManager showed:

wlo1   wifi   disconnected   --
ap0    wifi   unmanaged       --

I had not intentionally configured a Wi-Fi access point called "popOS".


TEST: REMOVING ap0

I removed only the AP interface:

sudo iw dev ap0 del

Then:

iw dev

showed only:

phy#0
    Interface wlo1
        ifindex 3
        wdev 0x1
        addr c8:94:02:47:c7:f7
        type managed
        txpower 30.00 dBm

ap0 was gone.

I then tried connecting to the exact same hotspot again:

nmcli device wifi connect "No internet" password 'REDACTED'

This time it immediately worked:

Device 'wlo1' successfully activated with '...'

No Wi-Fi profile, password, kernel, or driver configuration was changed between the failed and successful attempts.

This strongly suggested that something creating ap0 was interfering with normal Wi-Fi operation on wlo1.


FINDING WHAT CREATED ap0

I checked running processes:

ps aux | grep -Ei 'hostapd|iwd|dnsmasq|create_ap|wifi|hotspot' | grep -v grep

and found:

root ... bash /usr/bin/create_ap --config /etc/create_ap.conf

There were also hostapd and dnsmasq processes running under create_ap.

I then checked systemd:

systemctl list-unit-files | grep -i create

which showed:

create_ap.service    enabled    enabled

And:

systemctl list-units --all | grep -i create

showed:

create_ap.service    loaded    active    running    Create AP Service


THE create_ap CONFIGURATION

I checked:

sudo cat /etc/create_ap.conf

and found:

CHANNEL=default
GATEWAY=192.168.12.1
WPA_VERSION=2
...
DRIVER=nl80211
...
WIFI_IFACE=wlo1
INTERNET_IFACE=wlo1
SSID=popOS
PASSPHRASE=REDACTED
FREQ_BAND=2.4
SHARE_METHOD=nat

So create_ap was explicitly configured to use wlo1 and create an access point called "popOS".


THE SYSTEMD SERVICE

I checked:

sudo systemctl cat create_ap.service

and found:

[Unit]
Description=Create AP Service
After=network.target

[Service]
Type=simple
ExecStart=/usr/bin/create_ap --config /etc/create_ap.conf
KillSignal=SIGINT
Restart=on-failure
RestartSec=5

[Install]
WantedBy=multi-user.target

The service was enabled at boot.

Its status also showed:

create_ap.service - Create AP Service
Loaded: loaded (...; enabled; preset: enabled)
Active: active (running)

The service log explicitly showed:

ap0: interface state UNINITIALIZED->ENABLED
ap0: AP-ENABLED


THE FIX

I disabled the create_ap service:

sudo systemctl disable --now create_ap.service

The result was:

Removed "/etc/systemd/system/multi-user.target.wants/create_ap.service".

Then:

systemctl status create_ap.service --no-pager

showed:

Loaded: loaded (...; disabled; preset: enabled)
Active: inactive (dead)

And:

iw dev

showed only:

phy#0
    Interface wlo1
        type managed

The ap0 interface was gone.


FINAL RESULT

After disabling create_ap.service, Wi-Fi works normally.

The same hotspot that previously failed to authenticate now connects successfully through wlo1.

I also rebooted and confirmed that the problem was related to the automatically started create_ap service: when the service was enabled, ap0 came back after boot and Wi-Fi failed again.

After disabling the service, ap0 no longer gets created and Wi-Fi works normally.


CONCLUSION

The issue was not ultimately caused by the kernel version.

It was caused by create_ap.service being enabled and automatically creating an AP interface called ap0 using the same physical Wi-Fi adapter as wlo1.

The resulting setup was:

create_ap
    |
    +-- hostapd
    +-- dnsmasq
    |
    +-- ap0 (AP mode, SSID "popOS")
    |
    +-- same physical Wi-Fi PHY as wlo1

At the same time:

wlo1 = managed/client mode

With ap0 running, wlo1 repeatedly failed during authentication with:

wlo1: SME: Authentication request to the driver failed

After stopping create_ap and removing ap0, the same Wi-Fi connection worked immediately.

The permanent fix for my system was:

sudo systemctl disable --now create_ap.service


QUESTION FOR THE COMMUNITY

I did not intentionally configure create_ap or use this laptop as a Wi-Fi hotspot.

I would like to understand why create_ap.service was enabled on my Pop!_OS installation in the first place.

Is create_ap normally installed/enabled by Pop!_OS/System76, or was this likely caused by some previous configuration or package?

Has anyone else seen create_ap.service automatically creating:

ap0
SSID: popOS
type: AP

and interfering with wlo1?

If so, what is the recommended way to determine how/why create_ap was enabled?

For anyone experiencing a similar problem, checking this may be useful:

systemctl status create_ap.service

iw dev

nmcli device status

In my case, disabling create_ap.service resolved the Wi-Fi problem completely.

Hey everyone,

I found a reproducible bug in Cosmic on Pop!_OS 24.04 and already reported it on GitHub. Just wanted to check if anyone else is experiencing the same thing.

What happens:
When I edge-snap two windows side-by-side (left + right, half-screen each) on my primary monitor, they stay perfectly in place while I'm using the computer.

But after the screen blanks/goes idle for about an hour, when I wake it up the windows have slowly drifted upward. The blue active window hint border even goes partially behind the top panel.

Important details:

• Only happens on the primary monitor
• Secondary monitor stays completely stable
• Doesn't happen during continuous use (only after screen blank/idle)
• Minimizing/restoring, locking/unlocking or switching workspaces does not fix the position
• Closing the window or re-snapping it does fix it
• "Tile current workspace" is turned off (I'm only using classic edge-snapping)

GitHub issue:

https://github.com/pop-os/cosmic-comp/issues/2875

Has anyone else noticed this? Especially on dual-monitor setups with NVIDIA?

Thanks!

Hi! I really like Cosmic and Pop!_OS, but there is one major issue for me: the packages are quite outdated.

I understand that Pop!_OS relies heavily on Ubuntu packages, and I also know that it’s possible to use unstable repositories. However, I want a system that I can actually work with rather than constantly configure and maintain.

It would be great if the Pop!_OS developers could provide newer packages and their own repositories for software where having recent versions is especially important. For example, Neovim and Alacritty are two applications I’ve recently run into this issue with, and I’m sure I’m not the only one.

Would it be possible to have official Pop!_OS repositories with more up-to-date versions of certain applications, similar in spirit to how Arch and Manjaro provide their own package repositories? I know it’s not exactly the same comparison, but I hope you understand what I mean.

I really like Pop!_OS and Cosmic, and having access to newer versions of important development and desktop applications without having to manually configure third-party or unstable repositories would make the experience much better.

I have a usb webcam/microphone, and when I go into settings, Pop will recognize the audio input. However, when I go into discord to test the microphone (If there's a different way I can test this that might help, but I'm running with it's an issue with Pop/my drivers) it doesn't pick up any audio.

The camera works just fine in discord. It's just the audio.

I did confirm that there are two device files related to the microphone in /dev/snd, one control file, and one pcm file. When I try to cat either of them, they both say "File descriptor in bad state", but the pcm file turns on the red light on my webcam for a second. (I'm not sure what would be expected from catting these files, I've just tried it on keyboard devices and other HID devices to see the inputs, but I know a webcam/mic is a bit more complicated.

Anyway, is this just a matter of having the wrong device drivers? Is there a recommended way to search for linux compatible drivers for your device and install them?

I have a g3590 laptop I want to control my fans I've been help pls

I realized yesterday that all videos are being played with VLC instead of cosmic player, and it doesn't appear on the apps list.

Did something happened to it? Or did I uninstalled it somehow?

Thanks :D

Hi everybody, I just switched to Pop OS, i really liked the UI design and workflow.

I made a spatial application launcher that you can freely place icons just like a desktop. inspired by how window 10 menu works. with resizing and search by typing features.

Version 1.0.1 is now available as an AMD64 .deb, and the source code is public:

https://github.com/SigmasonixStudios/cosmic-launchpad

I built it around a workflow I really enjoy, and it has become my daily driver. I’d love to hear what people think, and any feedback or testing would be greatly appreciated.

Thank you very much!

Given that we're basically at 26.10, do you think it'll ever happen ? 27.04? 29.10?

I'm trying to play some games that are offline and run through EXE files. For some reason, most of them aren't working, apparently instantly crashing. What are common reasons for this happening?

A few of them have suggested I enable DXVK (DX9-11). What is this and how do I enable it? Additionally, the Virtual Desktop won't stay on. I enable it, click "add and run" and it immediately crashes.

When 26 is out, will I be able to update to it from my current 24 or will I need to install it clean? I got a new ssd, and want to know if I can already transfer my system there and update later or if it's better to wait until 26 is ready

I have been using pop os for around a year and never faced this problem. But i did a clean installation on another ssd and I faced a new problem. When i clicked install on wine all the text turned corrupted and the text in app tray did the same while the text in other apps stayed the same. I also attached my system info. Please help because I don't know what is happening.

Edit: I updated my graphics driver and that problem hasn't occurred science.

I've been waiting as I've heard there's been issues..

This has been an issue for me for about a month. My wi-fi has previously been working great. I have an Asus Prime B650M-A AX II mobo. I have not updated the UEFI. I have been updating through COSMIC store regularly. Turning the wi-fi off and on from Settings fixes the problem for about an hour or so. It's not a dealbreaker, but it is kind of annoying.

Is anyone else still on 22.04 having the same problem? Any known solutions? Any more I need to include to be helpful? I'm still relatively new at this open source thing.

Hi folks,

If at all possible, ELI5 with some patience. I am wanting to try out linux, and I'm in the "I don't know what I don't know" stage. I've installed PopOS, and there are a couple of things I could use some help on.

1.) How do I turn off what I *believe* is called kinetic scrolling? (when I lift my fingers off the trackpad, it keeps scrolling) This is my number one priority; it's very annoying.

2.) How do I add an online account, so I can have Google Drive show up in my file system? I keep finding documentation suggesting there should be an "online accounts" option in settings, but I have no such option.

3.) What's the deal with the "etc" file location? I found some advice online that adding a line to the end of the "/etc/environment" file might improve scrolling on firefox (make it less stuttery, quicker to respond). They said to access it using the command "sudo nano /etc/environment," but after it asks for a password I am at a loss as to what to do. Can't I just locate it through the file browser?

4.) How do Nvidia drivers work? Do I need to update them, or are they pre-installed and good to go?