I am running Fedora 37 on a desktop computer. Filelight worked on this computer up until 6 to 9 months ago, then started crashing every time I attempted to initiate it. I have not been able to send a standard report; it always hangs up. Today, I uninstalled filelight, then reinstalled it. That did not work. STEPS TO REPRODUCE 1. Attempt to start filelight; it never starts OBSERVED RESULT crash report EXPECTED RESULT start SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 37 KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
Please check out https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!
(In reply to Harald Sitter from comment #1) > Please check out > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports Thanks Harald, but I could not figure out how to create a "useful crash report" despite spending a couple hours reading and re-reading the instruction, combined with trying and -retrying. (As with many instructions,) It is probably totally clear for someone who already knows how to do it, but not clear to those of us who do not know how to do it and are not familiar with several assumptions the author takes for granted. I see no way forward unless I try to share screen with someone . . . but my Telegram ceased to be able to make calls in the last month. )-:
Is this a good trace? #0 QObject::setProperty (this=this@entry=0x0, name=name@entry=0x55555558c426 "iconName", value=...) at kernel/qobject.cpp:4067 #1 0x000055555556a1ee in Filelight::MainContext::setupActions ( engine=0x55555572fa50, this=0x7fffffffd980) at /usr/src/debug/filelight-22.12.3-1.fc37.x86_64/src/mainContext.cpp:107 #2 Filelight::MainContext::MainContext (parent=0x0, this=0x7fffffffd980) at /usr/src/debug/filelight-22.12.3-1.fc37.x86_64/src/mainContext.cpp:54 #3 main (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/filelight-22.12.3-1.fc37.x86_64/src/main.cpp:82
Yes, thank you! When you start fileight from a terminal, do you by any chance see some error printed before the crash?
(In reply to Harald Sitter from comment #6) > Yes, thank you! > > When you start fileight from a terminal, do you by any chance see some error > printed before the crash? [u@lenofedo ~]$ filelight QSocketNotifier: Can only be used with threads started with QThread QQmlComponent: Component is not ready Segmentation fault (core dumped) [u@lenofedo ~]$