Bug 1708740 - libKF5IconThemes.so.5| Invalid Context= "Legacy" line for icon theme: "/usr/share/icons/Adwaita/16x16/legacy/"
Summary: libKF5IconThemes.so.5| Invalid Context= "Legacy" line for icon theme: "/usr/...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: adwaita-icon-theme
Version: 30
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Kalev Lember
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-10 17:36 UTC by H.-P. Sorge
Modified: 2020-05-26 17:32 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-05-26 17:32:54 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description H.-P. Sorge 2019-05-10 17:36:57 UTC
Description of problem:

DO a copy of /usr/share/plplot5.14.0/examples/c++ to a userPath.
change to  userPath/c++
run make qt_example
run ./qt_example

# The following warning messages are bougus:
Invalid Context= "Legacy" line for icon theme:  "/usr/share/icons/Adwaita/16x16/legacy/"
Invalid Context= "UI" line for icon theme:  "/usr/share/icons/Adwaita/16x16/ui/"
Invalid Context= "Legacy" line for icon theme:  "/usr/share/icons/Adwaita/22x22/legacy/"
Invalid Context= "Legacy" line for icon theme:  "/usr/share/icons/Adwaita/24x24/legacy/"
Invalid Context= "UI" line for icon theme:  "/usr/share/icons/Adwaita/24x24/ui/"
Invalid Context= "Legacy" line for icon theme:  "/usr/share/icons/Adwaita/32x32/legacy/"
Invalid Context= "UI" line for icon theme:  "/usr/share/icons/Adwaita/32x32/ui/"
Invalid Context= "Legacy" line for icon theme:  "/usr/share/icons/Adwaita/48x48/legacy/"
Invalid Context= "UI" line for icon theme:  "/usr/share/icons/Adwaita/48x48/ui/"
Invalid Context= "Legacy" line for icon theme:  "/usr/share/icons/Adwaita/256x256/legacy/"
Invalid Context= "Legacy" line for icon theme:  "/usr/share/icons/Adwaita/512x512/legacy/"
Invalid Context= "UI" line for icon theme:  "/usr/share/icons/Adwaita/scalable/ui/"

Version-Release number of selected component (if applicable):
kf5-kiconthemes-5.57.0-1.fc30.x86_64

How reproducible:
allays

Steps to Reproduce:
1. See description
2.
3.

Actual results:
Annoying warning messages are being shown.

Expected results:
No warning messages.


Additional info:
Analysis:
run strace ./qt_example
snip ......
openat(AT_FDCWD, "/usr/share/icons/Adwaita/index.theme", O_RDONLY|O_CLOEXEC) = 9
statx(9, "", AT_STATX_SYNC_AS_STAT|AT_EMPTY_PATH, STATX_ALL, {stx_mask=STATX_ALL, stx_attributes=0, stx_mode=S_IFREG|0644, stx_size=5167, ...}) = 0
statx(9, "", AT_STATX_SYNC_AS_STAT|AT_EMPTY_PATH, STATX_ALL, {stx_mask=STATX_ALL, stx_attributes=0, stx_mode=S_IFREG|0644, stx_size=5167, ...}) = 0
statx(9, "", AT_STATX_SYNC_AS_STAT|AT_EMPTY_PATH, STATX_ALL, {stx_mask=STATX_ALL, stx_attributes=0, stx_mode=S_IFREG|0644, stx_size=5167, ...}) = 0
read(9, "[Icon Theme]\nName=Adwaita\nCommen"..., 16384) = 5167
read(9, "", 11217)                      = 0
brk(NULL)                               = 0x12ab000
brk(0x12cc000)                          = 0x12cc000
close(9)                                = 0
statx(AT_FDCWD, "/usr/share/icons/Adwaita/8x8/emblems", AT_STATX_SYNC_AS_STAT, STATX_ALL, {stx_mask=STATX_ALL, stx_attributes=0, stx_mode=S_IFDIR|0755, stx_size=4096, ...}) = 0
statx(AT_FDCWD, "/usr/share/icons/Adwaita/8x8/legacy", AT_STATX_SYNC_AS_STAT, STATX_ALL, {stx_mask=STATX_ALL, stx_attributes=0, stx_mode=S_IFDIR|0755, stx_size=4096, ...}) = 0
statx(AT_FDCWD, "/usr/share/icons/Adwaita/16x16/devices", AT_STATX_SYNC_AS_STAT, STATX_ALL, {stx_mask=STATX_ALL, stx_attributes=0, stx_mode=S_IFDIR|0755, stx_size=12288, ...}) = 0
statx(AT_FDCWD, "/usr/share/icons/Adwaita/16x16/emblems", AT_STATX_SYNC_AS_STAT, STATX_ALL, {stx_mask=STATX_ALL, stx_attributes=0, stx_mode=S_IFDIR|0755, stx_size=4096, ...}) = 0
statx(AT_FDCWD, "/usr/share/icons/Adwaita/16x16/legacy", AT_STATX_SYNC_AS_STAT, STATX_ALL, {stx_mask=STATX_ALL, stx_attributes=0, stx_mode=S_IFDIR|0755, stx_size=20480, ...}) = 0
openat(AT_FDCWD, "/dev/tty", O_RDONLY|O_CLOEXEC) = 9
close(9)                                = 0
write(2, "Invalid Context= \"Legacy\" line f"..., 89Invalid Context= "Legacy" line for icon theme:  "/usr/share/icons/Adwaita/16x16/legacy/"
) = 89
..... /snip


The content of /usr/share/icons/Adwaita/index.theme and the corresponding directory information / directory structure
match. There no indication of missing or wrong data in any of the the related path.

Removing the entry 
[8x8/legacy]   
Context=Legacy 
Size=8         
Type=Fixed     

from 
/usr/share/icons/Adwaita/index.theme
will eliminate the corresponding warning message. 
However the above entry (as well as the other entries related to the warnings) seem to be correct.

run grep "Invalid Context=" /lib64/* 2>&1| grep -v grep
Binary file /lib64/libKF5IconThemes.so matches
Binary file /lib64/libKF5IconThemes.so.5 matches
Binary file /lib64/libKF5IconThemes.so.5.57.0 matches
Binary file /lib64/libkdeui.so.5 matches
Binary file /lib64/libkdeui.so.5.14.38 matches

Only /lib64/libKF5IconThemes.so is being loaded by qt_example.
Hence libKF5IconThemes.so is buggy.

Comment 1 Rex Dieter 2019-05-10 18:47:50 UTC
In this case, according to 
https://standards.freedesktop.org/icon-theme-spec/icon-theme-spec-latest.html#context
at least, Context=Legacy and/or Context=UI are indeed not valid.

(though I'll look into if it's easy and worth blacklisting this warning, I don't see it serving a useful purpose to the average end-user)

Triaging to adwaita-icon-theme

Comment 2 Rex Dieter 2019-05-10 18:52:11 UTC
Interestingly, the code accepts more than what's included in the specification:

    enum Context {
        Any,           ///< Some icon with unknown purpose.
        Action,        ///< An action icon (e.g. 'save', 'print').
        Application,   ///< An icon that represents an application.
        Device,        ///< An icon that represents a device.
        FileSystem,    ///< An icon that represents a file system. @deprecated Use Place instead.
        MimeType,      ///< An icon that represents a mime type (or file type).
        Animation,     ///< An icon that is animated.
        Category,      ///< An icon that represents a category.
        Emblem,        ///< An icon that adds information to an existing icon.
        Emote,         ///< An icon that expresses an emotion.
        International, ///< An icon that represents a country's flag.
        Place,         ///< An icon that represents a location (e.g. 'home', 'trash').
        StatusIcon     ///< An icon that represents an event.
    };

Comment 3 Ferry Huberts 2019-07-17 19:41:52 UTC
I'm experiencing this bug too, on Fedora 30, running under X, when starting kdiff3

Invalid Context= "Legacy" line for icon theme:  "/usr/share/icons/Adwaita/8x8/legacy/"
Invalid Context= "Legacy" line for icon theme:  "/usr/share/icons/Adwaita/16x16/legacy/"
Invalid Context= "UI" line for icon theme:  "/usr/share/icons/Adwaita/16x16/ui/"
Invalid Context= "Legacy" line for icon theme:  "/usr/share/icons/Adwaita/22x22/legacy/"
Invalid Context= "Legacy" line for icon theme:  "/usr/share/icons/Adwaita/24x24/legacy/"
Invalid Context= "UI" line for icon theme:  "/usr/share/icons/Adwaita/24x24/ui/"
Invalid Context= "Legacy" line for icon theme:  "/usr/share/icons/Adwaita/32x32/legacy/"
Invalid Context= "UI" line for icon theme:  "/usr/share/icons/Adwaita/32x32/ui/"
Invalid Context= "Legacy" line for icon theme:  "/usr/share/icons/Adwaita/48x48/legacy/"
Invalid Context= "UI" line for icon theme:  "/usr/share/icons/Adwaita/48x48/ui/"
Invalid Context= "Legacy" line for icon theme:  "/usr/share/icons/Adwaita/256x256/legacy/"
Invalid Context= "Legacy" line for icon theme:  "/usr/share/icons/Adwaita/512x512/legacy/"
Invalid Context= "UI" line for icon theme:  "/usr/share/icons/Adwaita/scalable/ui/"

Comment 4 Rex Dieter 2019-07-18 13:33:24 UTC
Added patch to kf5-kiconthemes-5.60-2 to as workaround to treat this output with qDebug (ie, is silenced in production builds).

%changelog
* Thu Jul 18 2019 Rex Dieter <rdieter> - 5.60.0-2
- silence log spam wrt "Invalid Context..." (#1708740)

This should come as an update soon.

Comment 5 markusN 2019-10-18 09:50:31 UTC
(In reply to Rex Dieter from comment #4)
> This should come as an update soon.

Looking fwd to it - any ETA?

Comment 6 Rex Dieter 2019-10-18 18:23:52 UTC
Sorry for the delay, I can't commit to a firm eta either (depends largely on free time and f31 development status, blockers).  Soon(ish).

Comment 7 Ben Cotton 2020-04-30 20:55:29 UTC
This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '30'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 30 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 8 Ben Cotton 2020-05-26 17:32:54 UTC
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.