8000 Vitals stopped reporting Disk data on Fedora 42 · Issue #477 · corecoding/Vitals · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Vitals stopped reporting Disk data on Fedora 42 #477

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
2 tasks done
carlosvalin94 opened this issue Apr 15, 2025 · 6 comments
Open
2 tasks done

Vitals stopped reporting Disk data on Fedora 42 #477

carlosvalin94 opened this issue Apr 15, 2025 · 6 comments
Labels
bug Something isn't working

Comments

@carlosvalin94
Copy link
carlosvalin94 commented Apr 15, 2025 •
edited
Loading

Has this issue been covered in the Wiki?

  • I have read the Wiki and my issue is not covered.

Is there an existing issue reported already?

  • I have searched the existing issues, it does not exist.

What is the unexpected behavior?

After I upgraded from Fedora 41 to 42 (Silverblue) Vitals suddenly stopped reporting disk usage.

Steps to reproduce the unexpected behavior.

Upgrade to Fedora 42

Relevant log output

rpm-ostree db diff | grep sensors
  lm_sensors-libs 3.6.0-20.fc41 -> 3.6.0-22.fc42

rpm-ostree db diff | grep libgtop
  libgtop2 2.41.3-2.fc41 -> 2.41.3-3.fc42

What distribution and version of Linux are you using?

Fedora 42 Silverblue

What version of Gnome are you using?

48
@carlosvalin94 carlosvalin94 added the bug Something isn't working label Apr 15, 2025
@axeleroy
Copy link
axeleroy commented Apr 22, 2025 •
edited
Loading

This is probably linked to composefs being enabled in Fedora Atomic Desktops 42.

@carlosvalin94
Copy link
Author

@axeleroy I think that could be the case, is there a way to fix this?

@axeleroy
Copy link
axeleroy commented Apr 23, 2025 •
edited
Loading

Fixing it only requires going into Vital's settings and changing the storage path from / to /sysroot. From the Fedora Wiki:

User experience

The main visible change will be that the root filesystem (/) is now small and full (a few MB, 100% used). The real root is mounted in /sysroot and most of the data is stored in /var.

@carlosvalin94
Copy link
Author
carlosvalin94 commented Apr 23, 2025 •
edited
Loading

It worked perfectly, thanks!!!

Last question, do you think there is a way to fix this so the extension detects the path automatically by default?

This way other users don't experience this issue.

@axeleroy
Copy link

I honestly don't know, I have very limited knowledge on GNOME extension development and looking at the extension's code I understand that the default value is hard-coded (though I might have misunderstood).

@corecoding
Copy link
Owner

I can look into seeing if I can detect composefs. Or perhaps it is as simple as seeing if the path exists, and if so, use it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@axeleroy @corecoding @carlosvalin94
0