https://bugs.kde.org/show_bug.cgi?id=498207
--- Comment #2 from Henner Zeller <h.zel...@acm.org> ---
Interesting. I can also confirm that Version 24.12.1 of `kolourpaint` also
shows the png garbled ... but only on one of my machines, but correctly on
another machine (Both running NixOS. Both machines show the issue on the
konsole).
Might indicate some non-initialized value/buffer overflow somewhere ?
To test if this is an issue with Qt `QImage`, I've compiled the following
super-simple program in Qt5 and Qt6 to see if the image loading is an issue
there.
Both show `bug/original-image.png` correctly. So it does _not_ look like
something with basic QImage.
I made it as self-compiling c++ 'script', for ease of reproducability (Replace
Qt6 with Qt5 in the pkg-config call to compile with qt5):
```c++
#if 0 // Invoke with /bin/sh or simply add executable bit on this file on Unix.
B=${0%%.cc}; [ "$B" -nt "$0" ] || c++ -o"$B" "$0" $(pkg-config --cflags --libs
Qt6Widgets) && exec "$B" "$@";
#endif
#include <QApplication>
#include <QLabel>
#include <QPixmap>
int main(int argc, char *argv[]) {
QApplication app(argc, argv);
const char *path = argc > 1 ? argv[1] : "bug/original-image.png";
QPixmap image(path);
QLabel imageLabel;
imageLabel.setPixmap(image);
imageLabel.show();
return app.exec();
}
```
So maybe not a Qt issue, but whatever image loading `kolourpaint` and `konsole`
use to decode images is the culprit. And the inconsistency
--
You are receiving this mail because:
You are watching all bug changes.
