New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[gdk-pixbuf] wxWidgets wxCheckBox is not rendered properly on Kubuntu 22.04 (KDE) because loaders.cache file is empty and/or not found #38012
Comments
Does GTK use plugins? It's your responsibility to make sure they are available in runtime. |
Unfortunately, can't answer this question, but on the same system the application built with vcpkg has this issue, and another one built with system-wide libraries doesn't have it. |
Related: altf4/libmelee#74 (comment) |
Ok, theoretically, I can fix this next way:
|
Ok, short summary before I'm ready with the clean PR. The overall issue is next. |
…rsvg as a dependency to gdk-pixbuf. This changes the behavior of librsvg to be able to be built without gdk-pixbuf support (to avoid circular dependency) when built statically, and gdk-pixbuf to be built with librsvg support. librsvg is optional when building gdk-pixbuf dynamically, and enabled by default when building statically. This fixes microsoft#38012. Signed-off-by: Vitalii Koshura <[email protected]>
…rsvg as a dependency to gdk-pixbuf. This changes the behavior of librsvg to be able to be built without gdk-pixbuf support (to avoid circular dependency) when built statically, and gdk-pixbuf to be built with librsvg support. librsvg is optional when building gdk-pixbuf dynamically, and enabled by default when building statically. This fixes microsoft#38012. Signed-off-by: Vitalii Koshura <[email protected]>
…rsvg as a dependency to gdk-pixbuf. This changes the behavior of librsvg to be able to be built without gdk-pixbuf support (to avoid circular dependency) when built statically, and gdk-pixbuf to be built with librsvg support. librsvg is optional when building gdk-pixbuf dynamically, and enabled by default when building statically. This fixes microsoft#38012. Signed-off-by: Vitalii Koshura <[email protected]>
…rsvg as a dependency to gdk-pixbuf. This changes the behavior of librsvg to be able to be built without gdk-pixbuf support (to avoid circular dependency) when built statically, and gdk-pixbuf to be built with librsvg support. librsvg is optional when building gdk-pixbuf dynamically, and enabled by default when building statically. This fixes microsoft#38012. Signed-off-by: Vitalii Koshura <[email protected]>
…rsvg as a dependency to gdk-pixbuf. This changes the behavior of librsvg to be able to be built without gdk-pixbuf support (to avoid circular dependency) when built statically, and gdk-pixbuf to be built with librsvg support. librsvg is optional when building gdk-pixbuf dynamically, and enabled by default when building statically. This fixes microsoft#38012. Signed-off-by: Vitalii Koshura <[email protected]>
…rsvg as a dependency to gdk-pixbuf. This changes the behavior of librsvg to be able to be built without gdk-pixbuf support (to avoid circular dependency) when built statically, and gdk-pixbuf to be built with librsvg support. librsvg is optional when building gdk-pixbuf dynamically, and enabled by default when building statically. This fixes microsoft#38012. Signed-off-by: Vitalii Koshura <[email protected]>
…rsvg as a dependency to gdk-pixbuf. This changes the behavior of librsvg to be able to be built without gdk-pixbuf support (to avoid circular dependency) when built statically, and gdk-pixbuf to be built with librsvg support. librsvg is optional when building gdk-pixbuf dynamically, and enabled by default when building statically. This fixes microsoft#38012. Signed-off-by: Vitalii Koshura <[email protected]>
…rsvg as a dependency to gdk-pixbuf. This changes the behavior of librsvg to be able to be built without gdk-pixbuf support (to avoid circular dependency) when built statically, and gdk-pixbuf to be built with librsvg support. librsvg is optional when building gdk-pixbuf dynamically, and enabled by default when building statically. This fixes microsoft#38012. Signed-off-by: Vitalii Koshura <[email protected]>
…rsvg as a dependency to gdk-pixbuf. This changes the behavior of librsvg to be able to be built without gdk-pixbuf support (to avoid circular dependency) when built statically, and gdk-pixbuf to be built with librsvg support. librsvg is optional when building gdk-pixbuf dynamically, and enabled by default when building statically. This fixes microsoft#38012. Signed-off-by: Vitalii Koshura <[email protected]>
Describe the bug
I found a very strange bug with wxWidgets 3.2.4 (not sure related to this particular version, a topic to double check) built with vcpkg on Kubuntu 22.04 (KDE).
wxCheckBox is not rendered properly (label is visible, but checkbox itself is completely invisible but reacts on mouse).
When wxWidgets is built the normal way (using Makefile and/or cmake), this issue is not present, and wxCheckBox is rendered properly.
I have a strong feeling that this is not related to the wxWidgets itself, but to the way GTK3 is built by vcpkg, because I see these two warnings in the console (not sure these are really related to this issue, but they appear only on the vcpkg build):UPDATE: The Gtk-Warning is important, it basically shows the root cause of the issue.
test.cpp
CMakeLists.txt
vcpkg.json
I'll update this ticket if I find new useful information, but I'd be very happy if someone could at least give me a hint what to check to find out the root case of this issue.
Environment
gcc 11.4.0
was usedTo Reproduce
Steps to reproduce the behavior:
Expected behavior
wxCheckBox is correctly displayed
Failure logs
N/A
Additional context
Update 1:
After I remove
libcolorreload-gtk-module.so
, I see the same Gtk-Message is the 'good' application built without vcpkg, but wxCheckBox is still rendered properly. So this first message is not related to this issue.Update 2: Looks like the real issue is with gdk-pixbuf that can't find loaders.cache file or because it's empty.
The text was updated successfully, but these errors were encountered: