Comments
nemobis
As for the test failures,
/usr/lib64/chromium-browser/chrome-sandbox in chromium on x86_64 carries insecure mode 4755 but has no fileinfo rule for owner specification
Not sure what that is. A regular file.
$ LANG=en stat /usr/lib64/chromium-browser/chrome-sandbox
File: /usr/lib64/chromium-browser/chrome-sandbox
Size: 227984 Blocks: 448 IO Block: 4096 regular file
Device: 0,34 Inode: 3200314 Links: 1
Access: (4755/-rwsr-xr-x) Uid: ( 0/ root) Gid: ( 0/ root)
Context: system_u:object_r:chrome_sandbox_exec_t:s0
Access: 2024-03-23 02:00:00.000000000 +0200
Modify: 2024-03-23 02:00:00.000000000 +0200
Change: 2024-03-26 09:03:30.277487427 +0200
Birth: 2024-03-26 09:03:26.640800620 +0200
karma
Upgrade works fine. The ~/.config/chromium/screen_ai/ directory was removed and I've not seen it being recreated so far (I've only opened a couple websites and a PDF file).
BZ#2271183 chromium: downloads non-free component libchromescreenai.so without asking
karma
I confirm, unusable in KDE. 0:3.8.1-3.fc21 is perfectly functional.
karma
Forgot the last question
Works for me
BZ#1224581 ImageMagick-6.9.2-8 is available
BZ#1267391 ImageMagick 6.8.8.10 lost the support for JPEG 2000 format (jp2 extension)
Thanks a lot @than! This was amazingly fast.