Bug 461661 - Kimageformats Regression Affects Wallpaper Rendering, SDDM and Lock Screen
Summary: Kimageformats Regression Affects Wallpaper Rendering, SDDM and Lock Screen
Status: RESOLVED DOWNSTREAM
Alias: None
Product: frameworks-kimageformats
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 5.99.0
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Alex Merry
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-11-10 11:50 UTC by John
Modified: 2022-11-14 14:23 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description John 2022-11-10 11:50:05 UTC
SUMMARY

KDE is now promoting non-libre HEVC. AVIF support has benn removed from KDE, wich affects SDDM, wallpaper rendering and lock screen (all 3 suddeny gone from my system). The code for libre software- AVIF had been removed, hoping that nobody will notice deleting.

STEPS TO REPRODUCE
1. Add Avif wallper
2. Add SDDM Avif picture
3. Use Avif for Lock Screen

OBSERVED RESULT
Can't render, reverts back to other stock wallpapers after KDE update (update had regression)

EXPECTED RESULT
The Avif code had to be removed on purpose. Observe the people (promoting non-libre HEVC) and reinstate AVIF support into kdeimageformats so I do have 2.3x times smaller file to render (compared to properly made webp).

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: Arch
(available in About System)
KDE Plasma Version: 5.26.3
KDE Frameworks Version: 5.99.0
Qt Version: 5.15.7

ADDITIONAL INFORMATION
Please bear in mid, that we the users faught for many months on end to ad AV1/AVIF support to KDE(imagformats) and now someone (?) just pressed delete on that code. Not nice :(
Comment 1 Antonio Rojas 2022-11-10 12:51:46 UTC
Nobody removed anything, the code is right there
https://invent.kde.org/frameworks/kimageformats/-/tree/master/src/imageformats

Please limit yourself to reporting your issue and take the conspiracy theories elsewhere.
Comment 2 Nate Graham 2022-11-10 17:10:59 UTC
> AVIF support has benn removed from KDE
What do you mean? To my knowledge nobody has done any such thing. Can you clarify?
Comment 3 John 2022-11-12 09:26:09 UTC
After updating, yesterday, wallpaper was gone (see bug text above) and substituted without my consent to KDEs default.
After updating, yesterday, SDDM background was gone (see bug text above) and substituted without my consent to KDEs default.
 After updating yesterday, KDE lock screen background was gone (see bug text above) and became blank (PURE "SHOUTY" WHITE).
Nerve wracking as, I thougth update broke something/resetted my KDE configs. It did. I CANNOT reinstate .avif as: 1. Wallpaper, 2. SDD Background 3. Lock Screen. Webp works but is 2.3x bigger than avif.

How the file was made:
1. Creation of HQ PNG Art
2. Scaling with SINC with graphics magic [$ gm ....)
3. Using libaom avif to compress it:
$ avifenc -c aom -j all -s 0 -a aq-mode=2 -d 8 input.png output.avif

Various Test Resaults:

Info: All Files from RAW/ARW/NEF imported with dcraw preprocessed with Gimp (exposure fix for multifolder ones). Also huge NASA TIF Zero reencoding from one lossy compression to the other lossy compression. Zero defaults. Always the best parameters (--preset, --hints, scaling, sharp color conversion and multithreading for speed  - e.g. in cwebp -mt .... as well as using HQ PNG as intermediary for compression when appropriate). Always according to documentation and man pages. Visual inspection always done.

Size numbers:

tiff/jpg=14794194/2248182=6.581 (no exif, no thumbs arythmetic, color profile...)
tiff/jpg=14794194/2261881= 6.541 (full, arythmetic)
tiff/jpg=14794194/2413580=6.130 (plain, color profile)
tiff/webp=14794194/2844252=5.201 (z9, losless)
tiff/avif=14794194/158132=93.556 (avifenc -c aom -j all -s 0 -a aq-mode=2 -d 8)
web/avif=2844252/158132=17.987

In the last example you can see that AVIF was 18x smaller than webp.

I did at least 13 different photos: Picture, Photos, Text, RAW file. big HQ PNG Art, photos with more small details, photos with less details and stuff etc to see compression sizes and quality.
Comment 4 Antonio Rojas 2022-11-12 10:14:52 UTC
Post the output of `pacman -Q libavif kimageformats'
Comment 5 John 2022-11-12 10:27:15 UTC
(In reply to Antonio Rojas from comment #4)
> Post the output of `pacman -Q libavif kimageformats'
Here it is:
libavif 0.11.1-1
kimageformats 5.99.0-3.1

I have no tumbs for avif in Dolphin nor Gwenview is capable of displaying avif anymore. What happened with the update of kimageformats? No more avif support?
Comment 6 Antonio Rojas 2022-11-12 10:41:17 UTC
kimageformats 5.99.0-3.1

^ This is not Arch Linux. I suggest you report this to the bug tracker of your distribution.
Comment 7 John 2022-11-12 11:13:23 UTC
(In reply to Antonio Rojas from comment #6)
> kimageformats 5.99.0-3.1
> 
> ^ This is not Arch Linux. I suggest you report this to the bug tracker of
> your distribution.

Its a copy from official arch. ignore dash. Its exact Arch library, nothing changed. Use and see. Where is Avif and if you can use it in KDE. I'm done.
Comment 8 Antonio Rojas 2022-11-12 11:15:54 UTC
(In reply to John from comment #7)
> (In reply to Antonio Rojas from comment #6)
> > 
> > 
> > ^ This is not Arch Linux. I suggest you report this to the bug tracker of
> > your distribution.
> 
> Its a copy from official arch. ignore dash. Its exact Arch library, nothing
> changed. Use and see. Where is Avif and if you can use it in KDE. I'm done.

No, it's not. There is no "kimageformats 5.99.0-3.1" package on Arch and there never was.
Comment 9 dnovomesky 2022-11-14 14:23:47 UTC
When new libavif 0.11 got released, it didn't work with already released kimageformats 5.99

It was possible to use kimageformats 5.99 with older libavif or to backport fix into kimageformats 5.99 to allow it to work with new libavif.

Unfortunately, backporting fixes/patches is an extra work/burden on package maintainers. Beside that, libavif changes with every release, so after upgrade of libavif, it is necessary to rebuild kimageformats.

We don't know what happened in the specific distribution. For sure it was a result of technical troubles with software incompatibility and not some insidious anti-AVIF movement.