Change Details

A service usually has a proper icon somewhere on disk. `QIcon::name()` only works with theme icon names (e.g. `kate`) but not icons created from absolute path, e.g. `/some/special/icon/location/kate.png`. The latter is usually the case for containerized apps which have their icon set to some path within the application image or some container daemon location.

The previous `QIcon::name()` check wasn't sufficient as it only works with theme icon names (e.g. `kate`) but not icons created from an absolute path, e.g. `/some/special/icon/location/kate.png`. The latter is usually the case for containerized apps which have a proper application desktop file installed but their icon in some path within the application image or some container daemon location. Since we already store the information for whether we had to fall back to using the actual window pixmap, check for this before trying to serialize icon pixmap data.

A service usually has a proper icon somewhere on diskThe previous `QIcon::name()` check wasn't sufficient as it only works with theme icon names (e.g. `kate`) but not icons created from an absolute path, e.g. `/some/special/icon/location/kate.png`. `QIcon::name()` only works with theme icon names (e.g. `kate`) but not icons created from absolute path, e.g. `/some/special/icon/location/kate.png`The latter is usually the case for containerized apps which have a proper application desktop file installed but their icon in some path within the application image or some container daemon location. The latter is usually the case for containerized apps which have their icon set to some path within the application image or some container daemon location.Since we already store the information for whether we had to fall back to using the actual window pixmap, check for this before trying to serialize icon pixmap data.