[19:42] [telegram] @mitya57 Added you to https://bugs.kde.org/show_bug.cgi?id=465548 because it's a pretty nasty digiKam bug hitting the beta in Kinetic. I don't have a way to test it on Lunar as it seems to be affecting this guy's Athlon system. [19:43] [telegram] digiKam says "Not our fault" but it only shows up on their app so.... 🤷 [19:44] [telegram] They're blaming the way we compile Qt. [19:46] Eickmeyer: I suspect that code is actually in digikam and not Qt. The location is the header file [19:46] (I mean in the binary) [19:46] fvogt: Exactly, but they're saying "Nope, not our problem." [19:46] So it wouldn't be the way Qt is compiled but the way digikam is compiled [19:47] * Eickmeyer[m] posted a file: rules (2KiB) < https://libera.ems.host/_matrix/media/v3/download/matrix.org/ldIoyrTLaXuJAgkPXOoAkZzd > [19:47] There's the d/rules file. [19:47] There's nothing weird about it. [19:49] The build log might be interesting, especially the gcc invocations [19:49] https://launchpadlibrarian.net/650327303/buildlog_ubuntu-kinetic-amd64.digikam_4%3A8.0.0~+beta1-0ubuntu0.22.10.1_BUILDING.txt.gz [19:50] -- MediaPlayer flags : -msse4.1 [19:53] They're trying to get around ffmpeg5 compatibility issues on their end. [19:54] https://invent.kde.org/graphics/digikam/-/blob/master/core/cmake/macros/MacroSSE.cmake#L40 [19:54] Looks like it uses the SSE info from the build host [19:55] That seems a little odd. [19:55] Yep [19:55] Either build generically or use -march=native... [19:56] Seems like they're making a lot of assumptions lately that they shouldn't be. I've found that whenever I try to report a bug that they're being generally hostile toward distributions. [19:56] Yep, it's been that way for quite a while [19:57] Most of KDE isn't that way, but digiKam definitely is.