| Summary: | Temp Info Center says my NVME can handle +65261.8°C | ||
|---|---|---|---|
| Product: | [Applications] kinfocenter | Reporter: | Paul <Sandman192> |
| Component: | general | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | minor | CC: | ahiemstra, kde, nate, sitter |
| Priority: | NOR | ||
| Version First Reported In: | 6.5.3 | ||
| Target Milestone: | --- | ||
| Platform: | Bazzite | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | Hardware Info | ||
Integer overflow error somewhere? This is sensors info, isn't it? This is what the driver reports, nothing that we can do there If we know it's an invalid value (no temperature that high inside a computer ever makes sense), can we do some blame-shifting by replacing the number with something like "invalid value from driver/sensor"? That way at least the user will know it's not our fault. Current value is sensible no? I would need to check where we surface min/max directly Ah I see kinfocenter has a "sensors" page that displays the literal output of the sensors command If it's in kinfocenter where we do no processing of the data, then indeed this has to be an upstream fix, and there's nothing we can do here. |
Created attachment 187515 [details] Hardware Info OBSERVED RESULT Temps highs +65261.8°C and lows -273.1°C EXPECTED RESULT Not to be so high and so low.