Hello. When a KDE app crashes, I got a crash dialog that contains a lot of info and stacktrace. But when I read the final report - it's almost empty.
For example: I check "The crash can be reproduced every time." but it don't give me a place where I can write what exactly I did.

The stacktrace it found is perfect enough (without any debugging installations, manipulations from my side):

Code: Select all

Application: Info Center (kinfocenter), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f8fcaf2e780 (LWP 6114))]

Thread 3 (Thread 0x7f8fae241700 (LWP 6117)):
#0  0x00007f8fc79e249d in poll () from /lib64/libc.so.6
#1  0x00007f8fc3776314 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x00007f8fc377642c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0

...

#59 0x00007f8fc82ef30c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#60 0x00007f8fc829cfdb in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#61 0x00007f8fc82a4ec6 in QCoreApplication::exec() () from /usr/lib64/libQt5Core.so.5
#62 0x000000000040fb64 in ?? ()
#63 0x00007f8fc79216e5 in __libc_start_main () from /lib64/libc.so.6
#64 0x000000000040fbb9 in _start ()

And the final report that it shows to me (Russian):

Code: Select all

Application: kinfocenter (5.8.2)


Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.4.62-18.6-default x86_64
Distribution: "openSUSE Leap 42.2"


-- Information about the crash:
<Напишите подробно, что вы делали, когда произошла ошибка.>


The crash can be reproduced every time.


-- Backtrace:
A useful backtrace could not be generated


Отправить на https://bugs.kde.org/


And I can't edit it. So, its definitelly useless. I posted the bug by my hands on https://bugs.kde.org/
but I want to fix the automation.

anybody here? I reported the bug but it's still unchanged
https://bugs.kde.org/show_bug.cgi?id=381691

Psijic wrote:The stacktrace it found is perfect enough (without any debugging installations, manipulations from my side):

No, it is not:

-- Backtrace:
A useful backtrace could not be generated

You do need to install debug packages (named xxx-debuginfo in openSUSE) for a useful backtrace, and drkonqi should be able to send a proper bug report.
Actually drkonqi has a button that should do that automatically.
In openSUSE, you'd need to enable the debug repos first though (e.g. in YaST->Software Repositories).