You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the existing issues and found none matching what I'm reporting.
Bug Description
The CPU goes crazy when the app runs its animations. Looks like the snap-store does not use my NVIDIA GPU and relies on software rendering, which results in high CPU usage.
My terminal emulator spits this: libEGL warning: egl: failed to create dri2 screen
Steps to reproduce the behavior
Open snap-store
Click on anything that have animations.
High CPU usage (100%)
Expected behavior
Moderate CPU usage on running animations
Ubuntu release
24.10
What architecture are you using?
amd64
System info
6.11.0-14-generic #15-Ubuntu SMP PREEMPT_DYNAMIC Fri Jan 10 23:48:25 UTC 2025
name: snap-store
summary: Snap Store is a graphical desktop application for discovering, installing and managing
snaps on Linux.
publisher: Canonical✓
store-url: https://snapcraft.io/snap-store
contact: https://bugs.launchpad.net/snap-store/
license: unset
description: |
Snap Store showcases featured and popular applications with useful descriptions, ratings, reviews
and screenshots.
Applications can be found either through browsing categories or by searching.
Snap Store can also be used to switch channels, view and alter snap permissions and view and
submit reviews and ratings.
Snap Store is based on GNOME Software, optimized for the Snap experience.
commands:
- snap-store.show-updates
- snap-store
snap-id: gjf3IPXoRiipCu9K0kVu52f0H56fIksg
tracking: latest/edge
refresh-date: 8 days ago, at 09:50 +0330
channels:
2/stable: 0+git.7a3a49a6 2024-12-19 (1248) 11MB -
2/candidate: ↑
2/beta: ↑
2/edge: 0+git.e2aa8b1b 2025-01-27 (1253) 11MB -
latest/stable: 41.3-72-g80e7130 2024-09-22 (1216) 12MB -
latest/candidate: ↑
latest/beta: ↑
latest/edge: 0+git.e2aa8b1b 2025-01-27 (1253) 11MB -
preview/stable: –
preview/candidate: 0.2.7-alpha 2023-02-02 (864) 10MB -
preview/beta: ↑
preview/edge: 0.3.0-alpha 2023-08-14 (1017) 11MB -
1/stable: 41.3-72-g80e7130 2024-09-22 (1216) 12MB -
1/candidate: ↑
1/beta: ↑
1/edge: 41.3-72-g80e7130 2024-09-16 (1216) 12MB -
installed: 0+git.e2aa8b1b (1253) 11MB -
---
name: snapd
summary: Daemon and tooling that enable snap packages
publisher: Canonical✓
store-url: https://snapcraft.io/snapd
contact: https://github.com/snapcore/snapd/issues
license: GPL-3.0
description: |
Install, configure, refresh and remove snap packages. Snaps are
'universal' packages that work across many different Linux systems,
enabling secure distribution of the latest apps and utilities for
cloud, servers, desktops and the internet of things.
Start with 'snap list' to see installed snaps.
type: snapd
snap-id: PMrrV4ml8uWuEUDBT8dSGnKUYbevVhc4
tracking: latest/stable
refresh-date: 25 days ago, at 03:36 +0330
channels:
latest/stable: 2.67 2025-01-11 (23545) 46MB -
latest/candidate: 2.67.1 2025-02-05 (23771) 46MB -
latest/beta: 2.67.1 2025-01-17 (23771) 46MB -
latest/edge: 2.67.1+g225.e8538f4 2025-02-06 (23918) 50MB -
installed: 2.67 (23545) 46MB snapd
Additional context
No response
The text was updated successfully, but these errors were encountered:
I don't have any information about why some systems are failing to enable hardware acceleration. As in previous cases, I try to see if other GTK applications are working, or check if in a snap the app has correct access and drivers to get acceleration.
Note this issue where a non-flutter app (Nautilus) is having similar problems.
Is there an existing issue for this?
Bug Description
The CPU goes crazy when the app runs its animations. Looks like the snap-store does not use my NVIDIA GPU and relies on software rendering, which results in high CPU usage.
My terminal emulator spits this:
libEGL warning: egl: failed to create dri2 screen
Steps to reproduce the behavior
snap-store
Expected behavior
Moderate CPU usage on running animations
Ubuntu release
24.10
What architecture are you using?
amd64
System info
Additional context
No response
The text was updated successfully, but these errors were encountered: