unclejack
unclejack
Hasn't this been fixed by the IPAM and isolator detection code? It shouldn't be a problem any more because net-modules won't activate if the isolator/ipam is missing.
Image pulling is being fixed as part of #2461.
@diff- That problem is being worked on for issue #2461. All pull related issues with errors which contain "EOF" in them should be discussed in #2461. I'll change the title...
The underlying issue is that a large sparse file is created (approximately 32 GB), but it's not exactly a Docker bug. Docker could make an attempt to handle large sparse...
Would it not be better to use different compression altogether, rather than remove it completely?
This could be added in a new package called events. The events package would make it possible to have multiple producers and multiple consumers for events. **JSON payload** In addition...
These are the gamescope minidumps. [1702672557-gamescope-xwm-942-None.dmp](https://github.com/ValveSoftware/SteamOS/files/13690092/1702672557-gamescope-xwm-942-None.dmp) [1702673110-gamescope-xwm-3848-None.dmp](https://github.com/ValveSoftware/SteamOS/files/13690094/1702673110-gamescope-xwm-3848-None.dmp) [1702676974-gamescope-xwm-3325-None.dmp](https://github.com/ValveSoftware/SteamOS/files/13690095/1702676974-gamescope-xwm-3325-None.dmp) [1702586226-gamescope-xwm-1007-None.dmp](https://github.com/ValveSoftware/SteamOS/files/13690096/1702586226-gamescope-xwm-1007-None.dmp)
The amdgpu driver will most likely be fixed if this problem is something which can be fixed in the software. The logs show that some sensors were reporting temperatures much...
I'll post an update with the logs and the dumps if it happens again, regardless of the game.
@lostgoat: That was a different unit which has gone through RMA. The amdgpu crashed yesterday again. I'll grab the kernel's logs using journalctl and the new dumps to post them...