KDevelop's background parser crashes. (Somewhere in the bowels of QFileInfo > QDateTime > tzset.) This happens with 100% reliability and has been happening for quite some time. (Possibly since KDE 4.x.) Reproducible: Always Steps to Reproduce: 1. Boot a Fedora 42 KDE Spin live image 2. (as root) `dnf install kdevelop` 3. (as liveuser) `git clone http://gitlab.kitware.com/cmake/cmake.git` 4. Run KDevelop 5. Import the clone of CMake as a project 6. (Ignore the SSL-related configure error) 7. Wait for KDevelop to fully parse the project sources Actual Results: KDevelop crashes. For me, this is 100% reproducible on multiple computers. CMake isn't the only repository that causes it, but seems to be a 100% reliable reproducer, whereas it is hit-or-miss with other projects. Expected Results: KDevelop doesn't crash. Additional Information: Upstream developers are unable to reproduce the issue and cannot find any logical cause for the resulting backtrace. I suspect this may be caused by Fedora-specific patches. (Probably to Qt or another system library, but filing it on the application since I don't know where the problem actually lies.) See upstream report for backtrace.
This message is a reminder that Fedora Linux 42 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 42 on 2026-05-13. 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 'version' of '42'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 42 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.