| Summary: | Elisa Crashes After Launch | ||
|---|---|---|---|
| Product: | [Applications] Elisa | Reporter: | İsmail <ismailsahillioglu> |
| Component: | general | Assignee: | Matthieu Gallien <matthieu_gallien> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | grave | CC: | arojas, nate |
| Priority: | NOR | ||
| Version First Reported In: | 20.08.2 | ||
| Target Milestone: | --- | ||
| Platform: | Manjaro | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
Trace for elisa crush
Another try of backtrace |
||
|
Description
İsmail
2020-10-29 18:03:43 UTC
Can you attach a backtrace for the crash? https://community.kde.org/Get_Involved/Issue_Reporting#Crash_reports_must_include_backtraces I am now trying to generate a backtrace. When I try to generate a backtrace with GDB it doesn't produce a file but only console logs. I have drkonqi installed in the system but this crash doesn't trigger it. What should I do now? Created attachment 132875 [details]
Trace for elisa crush
Is this trace log ok?
Thanks. However I'm afraid the crash report is useless because it doesn't have debug symbols because you're using Manjaro which is an Arch-based distro and Arch-based distros don't ship debug symbols. Here are some instructions regarding how to remedy this so that you can produce useful backtraces: https://wiki.archlinux.org/index.php/Debug_-_Getting_Traces Sorry for that. I followed the instructions of gdb from the same page you stated under Getting the trace section. But I think that maybe I missed some step while I was doing it. Do you mind if I ask for you to write an example to generate a backtrace with debug symbols using gdb? You need to rebuild the package with debug symbols. The link I send should explain how, but I can't offer any further assistance as I'm not an Arch user and I'm not personally familiar with the process, sorry. Created attachment 132890 [details]
Another try of backtrace
I see, that's ok. How about this trace? If it is useless as well, I cannot go further because I don't know how to do it exactly. Please check it out then this issue can be closed because of the lack of information.
Not useful, sorry. This is my biggest frustration with arch-based distros! :( Arch users provide great QA, but the lack of debug symbols makes their crash logs useless most of the time. (In reply to Nate Graham from comment #9) > Not useful, sorry. > > This is my biggest frustration with arch-based distros! :( Arch users > provide great QA, but the lack of debug symbols makes their crash logs > useless most of the time. I understand that you may dislike the fact that we don't provide debug symbols, but please don't blame us even when it's not our fault. The first backtrace is just truncated and missing the important threads. And the second time the OP didn't even print the backtrace. In any case, this is clearly a duplicate of 427884 *** This bug has been marked as a duplicate of bug 427884 *** *** This bug has been marked as a duplicate of bug 427336 *** |