|
Bugzilla – Full Text Bug Listing |
| Summary: | YaST Software Management has no option of disabling the "Disk Space Warning" dialog | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.3 | Reporter: | Forgotten User EGKOvZW2-J <forgotten_EGKOvZW2-J> |
| Component: | YaST2 | Assignee: | Thomas Göttlicher <tgoettlicher> |
| Status: | VERIFIED WONTFIX | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | tgoettlicher |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE 11.3 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Forgotten User EGKOvZW2-J
2010-09-05 15:36:24 UTC
The warning is displayed by YQPkgDiskUsageWarningDialog class in yast2-qt-pkg. Reassigning to yast2-qt-pkg maintainer... (In reply to comment #0) > User-Agent: Opera/9.80 (X11; Linux x86_64; U; en) Presto/2.2.15 > Version/10.11 > > I have over 99% disk usage on one of my partitions (it's supposed to be that > way). > > Each time I open YaST -> Software Management, I get an annoying "Disk Space > Warning" dialog (which is not even centered on the YaST window). There seems to > be no way to disable it permanently (like "Don't show this warning again" > checkbox or something). > You are right. You cannot disable this warning and I don't see a reason to make it configurable. I guess you don't consider usability bugs as "real" bugs? This is a usability bug, and fixing bugs is the needed reason here. If I hadn't considered this bug as a "real" bug I had closed it as INVALID. But I closed it as WONTFIX because I think there are more important bugs and I don't want to work on a bug that is a very individual concern and it doesn't make sense for most users to ignore disc space warnings. If you are really interested in a solution make the threshold for disc usage configurable. See: YQPkgDiskUsageList.cc: #define MIN_FREE_MB_WARN 400 And if you think this "fix" is worth for other users please provide a patch. We will carefully evaluate it. |