Discover and Gnome Software incorrectly show an insufficient disk space error during software installation
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 141
- Forks
- 146
- Avg merge
- 11h 7m
- Merged PRs (30d)
- 407
Description
Please confirm there isn't an open report for this issue
- I have searched through bug reports
Summary
When updating my non-dev KDE Plasma system this morning using Discover I encountered an error that there was insufficient disk space, which was incorrect. The update proceeded and the system restarted (as I had requested with the dropdown) anyway. After rebooting and reopening Discover, I saw that only flatpak updates were applied. There were still the same amount of items shown for System upgrade (385)
Another user on the Polaris stable repo reported in this forum post getting an incorrect insufficient disk space error when attempting to install software using GNOME Software Center
Steps to reproduce
- Open Discover / GNOME Software Center
- Run updates or attempt to install software
Expected result
Software is updated / installed when there is free disk space
Actual result
This error appeared in Discover:
<html>No space on device left:<br/><br/>Disk error: The read operation timed out</html>
In GNOME Software Center it was
Environment
- Is system up to date?
Repo
Unstable
Desktop Environment
Plasma
System details
Operating System: Solus 4.8
KDE Plasma Version: 6.5.5
KDE Frameworks Version: 6.22.0
Qt Version: 6.10.1
Kernel Version: 6.17.8-324.current (64-bit)
Graphics Platform: Wayland
Other comments
Disk space on my system:
Filesystem Size Used Avail Use% Mounted on
/dev/nvme0n1p6 192G 149G 34G 82% /
/dev/nvme0n1p7 480G 338G 118G 75% /home
/dev/nvme1n1p1 1.6T 698G 853G 46% /data
/dev/nvme0n1p1 999M 559M 440M 56% /boot
Updates to be applied were only 4.36 GB
~ sudo eopkg up --dry-run
Place your right middle finger on the fingerprint reader
Updating repositories
Updating repository: unstable
Disabling keyboard interrupts for file operations.
eopkg-index.xml.xz.sha1sum (40.0 B)100% 0.00 --/- [--:--:--] [complete]
unstable repository information is up-to-date.
...
Total size of package(s): 4.36 GB
Disk space on the forum user's system:
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the update or installation through Discover or GNOME Software, then compare the result with the eopkg dry-run output described in the report. Check whether the reported timeout is being surfaced as an insufficient-disk-space error; done means updates or installations succeed when the listed free space is sufficient, without that misleading message.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- desktop-dev, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100