SUMMARY *** I would like to help provide a back trace with debug symbols for Discover Notifier's segmentation crashes. However, I seem to be caught in a catch-22 situation, that is the consistently failing app, Discover, is the one needed for installing kdebugssettings to debug Discover Notifier, which fails to install kdebugssettings which are .... STEPS TO REPRODUCE Note: I am afraid I am not good enough at command line work to understand sufficiently the instructions I found on line for creating a segmentation fault in an app. So, I have not attempted to reproduce this by that means. If supplied a precise step by step example to follow I would have a better chance. However, Discover Notification and some other apps do fail without meaningful backtraces about every two days, so it reproduces itself in a fairly consistent fashion. In that case: 1. When Discover Notifier crashes, note the kcrash reports it cannot supply a backtrace and recommends downloading and installing debug tools. 2. Navigate to https://apps.kde.org/kdebugsettings/ [I am not a developer so this seemed to be what is available for users.] 3. Note the [Install on Linux] button only works with Discover which is the app manager for Ubuntu Studio, 4. Click [Install on Linux] 5. "Open with ... -- Portal" only shows a button titled [Software] 6. Click [Software], Note that the pointer shows it is a link, but the app "Software" does not open. 7. Click [Discover] in the line "More applications are available in [Discover]." 8. The GNOME application manager opens with the message "Failed to install: not supported." 9. Search in both the discover and GNOME package managers for both "kdebugssettings" or "x-scheme-handler/appstream" as the name is shown in the Open with portal. 10. Receive "not found" messages for each. OBSERVED RESULT[S] 1. Kcrash consistently cannot supply a meaningful backtrace beyond ---------------------------------------------------------------- Application: DiscoverNotifier (5.24.7) Qt Version: 5.15.3 Frameworks Version: 5.92.0 Operating System: Linux 5.15.0-60-lowlatency x86_64 Windowing System: X11 Distribution: Ubuntu 22.04.2 LTS DrKonqi: 5.24.5 [KCrashBackend] The reporter is unsure if this crash is reproducible. -- Backtrace: A useful backtrace could not be generated Report to https://bugs.kde.org/ ------------------------------------------------------------------------------------------------------ 2. The Install on Linux button in https://apps.kde.org/kdebugsettings/ which is supposed to open Discover opens "Open with ... -- Portal" instead. 3. The button titled [Software] does not open an app. 4. The button titled [Discover]" opens the GNOME application manager. 5. The GNOME application manager displays the message "Failed to install: not supported." 6. The Discover and GNOME package managers return "not found" for searches for "kdebugssettings" or "x-scheme-handler/appstream" EXPECTED RESULT 1. Kcrash supplies a meaningful back trace and continues the automatic reporting procedure. 2. The [Install on Linux] button in https://apps.kde.org/kdebugsettings/ opens Discover unless the "Open with ... -- Portal" is the correct app. 3. "Open with ... -- Portal" The button titled [Software] opens an app capable of installing "kdebugssettings". 4. "Open with ... -- Portal" shows a button titled [Discover] as well as [Software] or instead of [Software]. 5. The current "Open with ... -- Portal" button titled [Discover] opens Discover. 5. The GNOME application manager should not called in any of the above cases* 6. The Discover package manager lists "kdebugssettings" or "x-scheme-handler/appstream" for installation and successfully installs same. SOFTWARE/OS VERSIONS Operating System: Ubuntu Studio 22.04 KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-60-lowlatency (64-bit) Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 7900X 12-Core Processor Memory: 31.1 GiB of RAM Graphics Processor: llvmpipe ADDITIONAL INFORMATION * Unless the GNOME application manager is supposed to be compatible with the [Install on Linux] button and that would be a separate bug. If my assumption that kdebugsettings is the appropriate tool is in error, please advise as to the correct tool and the steps necessary to install and use it correctly. Also, If this needs to be separated into more than one bug report. Is there a way to do so while maintaining the relationships or dependency of one bug on another. My apologies to the triage crew. My brain is more attuned to visual physics than languages and programming
> My apologies to the triage crew. My brain is more attuned to visual physics than languages and programming No worries, I get it. This stuff is complicated! You don't need to install kdebugssettings to debug Discover. If it's not installable on your system for any reason, that's a distro packaging bug. If for some reason the distro has also not set up the system properly for debug symbols, that's also a distro configuration issue. Thankfully, https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Ubuntu-based_distros_(Ubuntu,_Kubuntu,_KDE_Neon,_Linux_Mint) tells me that things are better in version 22.10 of Ubuntu Studio. But unfortunately you're on version 22.04 so you don't benefit from those improvements. I would recommend upgrading to Ubuntu Studio 22.10 if you're able. In general using newer software rather than older software will make your life better. :) No need to report the crash bug to KDE because you're using an old version of Discover that's out of support. Your options are to upgrade to a newer, more supported version (i.e. Discover from Plasma 5.26 or Plasma 5.27) or ask the Ubuntu Studio folks for support. Good luck!
2023-03-07: I just tried installing kdebugsettings and I have the same "Failed to install: not supported" message. If this is necessary for getting meaningful backtrace info when Discover Notify crashes again or any other KDE app including crash and is not a bug, please help me understand how do I or what do I do to provide the information requested. Or to whom I should be reporting this problem. Note, Present logs System Log 3/7/23 10:26 PM l-g905 gnome-software[49452] failed to convert URL to GsApp: no application was created for running url-to-app on plugin=packagekit with dedupe-flags=7 with timeout=60 with search=appstream://org.kde.kdebugsettings/, elapsed time since creation 392ms Jurnal Log 3/7/23 10:26 PM user@1000.service failed to convert URL to GsApp: no application was created for running url-to-app on plugin=packagekit with dedupe-flags=7 with timeout=60 with search=appstream://org.kde.kdebugsettings/, elapsed time since creation 392ms
I did the install of kdebugsettings using the the [install on Linux] button once again on the kdebugsettings site, where it also states that it works with Discover implying it does not work with Software 41.5. The error message is from Software 41.5 and not as would be expected Discover. If the first problem is that The [install on Linux] buttons call is to the wrong app or there is a glitch in Ubuntu Studio that is connecting the call to the wrong app. Who's realm is that process and how do I alert them of what is happening.
These aren't KDE issues, they're Ubuntu Studio issues. Like I said I recommend upgrading Ubuntu Studio to get the new version that makes this better. If you need further support, please direct it to the Ubuntu Studio team. Thanks!
Thank You, especially for the wrong version alert! I somehow managed to download the wrong ISO in early January this year for my new computer thinking I had the latest. My Bad. Will upgrade to 22.10 immediately. Also for the link, and explanation about how it is more likely a Distro error. I have Guidelines and HOWTOs/Debugging/How to create useful crash reports open and see it is the latest revision. Upgrade to 22.10 then lots of reading and learning to do. Thanks for your patience