-
-
Notifications
You must be signed in to change notification settings - Fork 28
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.
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
Display storage stats in Troubleshooting #224
Comments
Can you please run the following in a terminal and navigate to that area. what is reported in the terminal?
|
|
ok - thanks. Can reproduce. Will throw a fix soonest which will resolve in the next day or so. |
Should now be fixed in v0.8.5 of budgie-welcome that has been rolled out to all supported versions of UB |
Hmm... ok so you have a very different issue which I cannot reproduce :( Will need to work with you to run some test python based scripts to narrow this down. |
Ah. Wait. In your git clone version, can you run the app in a terminal to see if there is anymore info reported
|
Same issue, and no additional output I'm afraid. |
Please copy & paste into a new text file called "storage.py" and save to a folder In your terminal navigate to that folder and execute the file
What is the output?
|
|
That's rather interesting. You appear to be running on a disk type that the code doesnt know about. What is the output of the following?
|
|
ok - looks ok - what is the output of:
also just:
|
|
very interesting! so your install is on /dev/nvme0n1p2 but it for nvme disks that is very odd partition not a standard partition - your actual disk is nvme0n1 i.e. without the "p2". Hence the current code can't cope with this odd naming convention. Need some magical thoughts here on how to resolve :) |
Thanks for looking. No idea why it's that partition structure. |
I don't see any stats when looking at the Storage section, just the names of the sections. I'm not sure if I'm missing some software that should be displaying this data or what.
The text was updated successfully, but these errors were encountered: