Bug 466061 - The generated crash information is not useful Possible cause: repository 'http://ddebs.ubuntu.com $(lsb_release Release' lacks a Release file [Ubuntu Studio].
Summary: The generated crash information is not useful Possible cause: repository 'htt...
Status: RESOLVED DOWNSTREAM
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-02-19 08:54 UTC by L P Luigi Espenlaub
Modified: 2023-02-22 15:23 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description L P Luigi Espenlaub 2023-02-19 08:54:27 UTC
SUMMARY
***
I wanted to supply a backtrace with my report of a Plasma crash in Ubuntu Studio.
What happened is I am unable to attach a backtrace with debug symbols. Receiving instead  "The generated crash information is not useful" 

Confused about whether Ubuntu Studio 22.04 had the DEBUGINFOD_URLS function I attempted to install the dbgsym-packages. 
Then found following error which might explain why I was receiving the above error message.

"E: The repository 'http://ddebs.ubuntu.com $(lsb_release Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.

 I am puzzled that after receiving the message 
"I: All needed dbgsym packages are already installed." 
the automatic report system has been disabled in this case.

I admit in attempting the following procedures I found myself confused at times. 
I have saved most of what command line work and results if that might clarify where I went wrong, if I did.
So any help in ensuring that I do have a working DEBUGINFOD_URLS function for the next crash whether Plasma or other applications, would help me to help you.
***
I encountered this error while attempting to report a Application: Plasma (plasmashell), signal: Segmentation fault
However in attempting to produce crash information I kept getting 
 "The generated crash information is not useful"
The KDE Crash Handler listed these as missing.
/usr/bin/plasmashell
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
/usr/lib/x86_64-linux-gnu/qt5/plugins/xcbglintegrations/libqxcb-glx-integration.so
/lib/x86_64-linux-gnu/libgio-2.0.so.0
/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
/lib/x86_64-linux-gnu/libQt5Core.so.5
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
/lib/x86_64-linux-gnu/libQt5Gui.so.5
/lib/x86_64-linux-gnu/libQt5DBus.so.5
/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
/lib/x86_64-linux-gnu/libGLX_mesa.so.0
/lib/x86_64-linux-gnu/libxcb.so.1
/lib/x86_64-linux-gnu/libkcupslib.so
/lib/x86_64-linux-gnu/libQt5Qml.so.5
/lib/x86_64-linux-gnu/libusbmuxd-2.0.so.6
/lib/x86_64-linux-gnu/libQt5Quick.so.5

Am I in error in assuming the above list is the same as those in,   "I: All needed dbgsym packages are already installed."

I tried and was unsuccessful in finding the [.so.5] versions listed in Synaptic Package Manager
I used "kstart5 plasmashell" to restart plasma and I followed the instructions in the sites listed in "Instructions followed" Below which should have installed the above missing packages.

Unsure if the Error "$(lsb_release Release' does not have a Release file." was the cause of an unusable trace file,  I ran ~$ find-dbgsym-packages [core_path|running_pid|binary_path]
. . .and received "I: All needed dbgsym packages are already installed."
I clicked [Reload] in the "Crash Reporting Assistant of the Kde Crash Handler"
and still received
 "The generated crash information is not useful"
and the same list of missing packages.

I backed up in the assistant to the first step and found the automated process UN-enabled and the following report
-----------------------------------------------------------------------
Application: plasmashell (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.1 LTS
DrKonqi: 5.24.5 [KCrashBackend]

-- Information about the crash:
<In detail, tell us what you were doing  when the application crashed.>

The reporter is unsure if this crash is reproducible.

-- Backtrace:
A useful backtrace could not be generated

Report to https://bugs.kde.org/
----------------------------------------------------------------------------------------
I am missing something, as these conflicting messages are confusing and me unsure what is causing which.
Any way I can help to clarify this, please ask.

Pages consulted and Instructions followed
 https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
https://wiki.ubuntu.com/Debug%20Symbol%20Packages
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Install_debugging_packages
https://ubuntu.com/server/docs/service-debuginfod [1]
https://manpages.ubuntu.com/manpages/trusty/man1/gdb.1.html

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

         [1] In https://ubuntu.com/server/docs/service-debuginfod I was advised, " If you use Bash, you can do that by adding the following snippet to your ~/.bashrc:
         export DEBUGINFOD_URLS="https://debuginfod.ubuntu.com"
 but neither Files or Dolphin can show any [.] files in [/] or a ".bashrc:" in Home where [.] files are shown. 
As this is a 22.04 version is such an addition even necessary I wonder?
Comment 1 Nate Graham 2023-02-22 15:23:22 UTC
It's a shame the process of getting a backtrace with debug symbols has become such an ordeal! I would recommend that you contact the Ubuntu Studio developers about it, as it really should be easier. If and when you manage to get the backtrace with debug symbols, feel free to submit a new bug report here for it.