When opening discover from the notifier, and then pressing "update all", the notifier crashes. Updates proceed normally. The crash can be reproduced every time. It happens since two or three versions back ago, but as no backtrace can be produced, I did not report it earlier. Qt Version: 5.14.1 Frameworks Version: 5.69.0 Operating System: Linux 4.15.0-96-generic x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.18 -- Backtrace: A useful backtrace could not be generated
Please attach a backtrace of the crash. https://community.kde.org/Get_Involved/Issue_Reporting#Crash_reports_must_include_backtraces
Adding a backtrace is a bit difficult, as discover notifier starts up by itself and crashes when updating. DrKonqui does not get useful backtrace information. If you can give me a hint how to start it with gdb or else, I can try provide more info.
You can attach to a running executable with gdb. See https://stackoverflow.com/questions/14370972/how-to-attach-a-process-in-gdb
Created attachment 127732 [details] Error messages from running DiscoverNotifier within gdb
O.k., tried. gdb gives the following output: Attaching to process 11342 Could not attach to process. If your uid matches the uid of the target process, check the setting of /proc/sys/kernel/yama/ptrace_scope, or try again as the root user. For more details, see /etc/sysctl.d/10-ptrace.conf ptrace: Vorgang nicht zulässig. /home/martin/11342: Datei oder Verzeichnis nicht gefunden. Running as root makes it unresponsive. Quitting DiscoverNotifier and starting it with gdb works, but then it doesn't crash. I have attached all the error messages that show up in gdb. Sorry for being such a noob with this. Will try again as soon as other updates show up.
O.k., managed to attach gdb to the DiscoverNotifier process. But now it doesn't do anything any longer. Clicking results in nothing, right-click and select any option doesn't do anything. gdb gives the following error message, I don't know whether that has to do anything with the problem: Attaching to process 10600 [New LWP 10622] [New LWP 10660] [New LWP 12067] [New LWP 12068] [New LWP 12108] [New LWP 12115] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x00007fb5e29b7bf9 in __GI___poll (fds=0x557c7dc69640, nfds=3, timeout=95660) at ../sysdeps/unix/sysv/linux/poll.c:29 29 ../sysdeps/unix/sysv/linux/poll.c: Datei oder Verzeichnis nicht gefunden. Manually opening Discover and start the update process does not crash DiscoverNotifier.
Created attachment 127912 [details] DiscoverNotifier Backtrace Ok, so I finally managed to produce a backtrace. Sorry for the inconvinience, I'm new at this...
Created attachment 128212 [details] Backtrace DiscoverNotifier 2
Comment on attachment 128212 [details] Backtrace DiscoverNotifier 2 Another backtrace, this time it's shorter...
Thank you for reporting this crash in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the crash with a recent software version? If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you!
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!