Ubuntu 25.10 - slow startup / freeze

Support and Help
,
1

Ubuntu Version:25.10
Desktop Environment (if applicable): GNOME
Problem Description

I made a fresh install of Ubuntu 25.10, when running any application (snap, ptyxis, LibreOffice, Firefox, etc) the startup time is very slow. As an example launching the terminal it often takes 5+ seconds until it shows up. Firefox for instance, first launch takes 5+ seconds, and quite regularly on the first launch (after reboot) it freezes on so that I have to select “Force Quit” and restart it.

I am reporting this, because in 25.04 the issue was not present.

Hardware: Asus G16, Core Ultra 9 185H, NVIDIA GeForce RTX 4070

Any advices how to debug this issue?

1 Like
2

This looks very likely GPU/driver related, especially given the RTX 4070 and that 25.04 did not show the issue.

Things to check:

  1. Run:

    glxinfo | grep "renderer"

    to verify you’re not using llvmpipe (software rendering).

  2. Check:

    nvidia-smi

    to confirm the driver is properly loaded.

  3. Check boot logs:

    journalctl -b -p 3
3

Clarification: Ubuntu Discourse is not the bug tracker. This is the wrong place to “report” an issue. This is the right place to seek troubleshooting help, including troubleshooting so you can make a good, reproducible bug report on Launchpad.

1 Like
4

@MesterPerfect Thanks for your help. Below my output to your suggestions - I don’t thing the alsa issues are related to startup?

glxinfo:

    GLX_MESA_copy_sub_buffer, GLX_MESA_gl_interop, GLX_MESA_query_renderer, 
    GLX_MESA_gl_interop, GLX_MESA_query_renderer, GLX_MESA_swap_control, 
Extended renderer info (GLX_MESA_query_renderer):
OpenGL renderer string: Mesa Intel(R) Arc(tm) Graphics (MTL)

nvidia-smi:

+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 580.126.09             Driver Version: 580.126.09     CUDA Version: 13.0     |
+-----------------------------------------+------------------------+----------------------+
| GPU  Name                 Persistence-M | Bus-Id          Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |           Memory-Usage | GPU-Util  Compute M. |
|                                         |                        |               MIG M. |
|=========================================+========================+======================|
|   0  NVIDIA GeForce RTX 4070 ...    Off |   00000000:01:00.0 Off |                  N/A |
| N/A   46C    P3             14W /   42W |      13MiB /   8188MiB |     16%      Default |
|                                         |                        |                  N/A |
+-----------------------------------------+------------------------+----------------------+

+-----------------------------------------------------------------------------------------+
| Processes:                                                                              |
|  GPU   GI   CI              PID   Type   Process name                        GPU Memory |
|        ID   ID                                                               Usage      |
|=========================================================================================|
|    0   N/A  N/A            5042      G   /usr/bin/gnome-shell                      2MiB |
+-----------------------------------------------------------------------------------------+

journalctl

kernel: ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-70)
systemd-udevd[980]: /usr/lib/udev/rules.d/90-alsa-restore.rules:18 GOTO="alsa_restore_std" has no matching label, ignoring.
systemd-udevd[980]: /usr/lib/udev/rules.d/90-alsa-restore.rules:22 GOTO="alsa_restore_std" has no matching label, ignoring.
kernel: 
kernel: iwlwifi 0000:00:14.3: BIOS contains WGDS but no WRDS
kernel: iwlwifi 0000:00:14.3: Not valid error log pointer 0x0024B5C0 for RT uCode
systemd-udevd[980]: /usr/lib/udev/rules.d/90-alsa-restore.rules:18 GOTO="alsa_restore_std" has no matching label, ignoring.
systemd-udevd[980]: /usr/lib/udev/rules.d/90-alsa-restore.rules:22 GOTO="alsa_restore_std" has no matching label, ignoring.
kernel: iwlwifi 0000:00:14.3: Not valid error log pointer 0x0024B5C0 for RT uCode
systemd-udevd[980]: /usr/lib/udev/rules.d/90-alsa-restore.rules:18 GOTO="alsa_restore_std" has no matching label, ignoring.
systemd-udevd[980]: /usr/lib/udev/rules.d/90-alsa-restore.rules:22 GOTO="alsa_restore_std" has no matching label, ignoring.
kernel: ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-70)
gdm-password][4498]: gkr-pam: unable to locate daemon control file
kernel: uvcvideo 5-1.1.2:1.1: Failed to set UVC probe control : -32 (exp. 26).
prompting-client-daemon[5832]: Failed to remove old socket file: /run/user/1000/snap.prompting-client/prompting.sock. Error: No such file or director>

@ian-weisser thanks for that information. But currently I have not a real bug, error message or something to report, but once I have more information will open a bug there.

5

You can check the current PRIME mode with:

prime-select query

If your system supports full GPU switching, you may try:

sudo prime-select nvidia
reboot

or

sudo prime-select intel
reboot

However, on newer Meteor Lake systems, GNOME typically runs on the Intel iGPU by design, and NVIDIA is used via render offload. So switching modes may not significantly change behavior.

1 Like
6

Thanks for the suggestions. As you already supposed, I did not feel any difference between the nvidia, intel and on-demand mode. If you have anything else to try out, let me know, else I will make a fresh reinstall in april with 26.04 and see if the issue has gone.

7

Something has happened to latest builds of Ubuntu 24.04 and 25.10. After installing the latest updates on 24.04, my computer started freezing after an hour or so, sometimes after a few hours. I checked hardware for faults and none were found. In frustration, I installed 25.10 clean, after reformatting the SSD. Same problem, replaced the SSD with an NVMe, same problem. This cannot be my hardware anymore. The latest releases are buggy. Developers need to take a closer look. Thanks.

8

As mentioned in post #3, you need to report bugs in the right place.

For reference:

1 Like
9

As they seldom are for this problem… It’s notoriously hard to troubleshoot. That said and as always, start by updating firmware, UEFI and of any drive, if applicable. Check temperatures.

If that was the case many people would be having problems and that’s not what we’re seeing.

10

This topic was automatically closed after 30 days. New replies are no longer allowed.