Bug 428254 - Unable to install symbol packages for kdeconnectd
Summary: Unable to install symbol packages for kdeconnectd
Status: RESOLVED FIXED
Alias: None
Product: neon
Classification: KDE Neon
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Neon Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-10-26 02:22 UTC by Justin Zobel
Modified: 2020-11-01 01:21 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Screenshot (85.43 KB, image/png)
2020-10-26 02:22 UTC, Justin Zobel 		Details
attachment-16518-0.html (1.89 KB, text/html)
2020-10-30 11:00 UTC, Justin Zobel 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Justin Zobel 2020-10-26 02:22:03 UTC 
Created attachment 132745 [details]
Screenshot

Unsure if this should be in here or KDE Neon packages.

SUMMARY
Unable to install symbol packages for kdeconnectd

STEPS TO REPRODUCE
1. Crash kdeconnectd (I'm sure you know how)
2. Open kcrash dialog
3. Open Developer Information Tab and click Install Debug Symbols

OBSERVED RESULT
See screenshot

EXPECTED RESULT
Installation of debug symbols

Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.20.80
KDE Frameworks Version: 5.76.0
Qt Version: 5.15.0
Kernel Version: 5.4.0-52-generic
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-6700 CPU @ 3.40GHz
Memory: 23.4 GiB of RAM
Graphics Processor: NV136
Comment 1 Jonathan Riddell 2020-10-26 14:57:37 UTC 
The package it wants is kdeconnect-dbgsym but I don't know how kcrash works that out
Comment 2 Justin Zobel 2020-10-26 22:34:15 UTC 
(In reply to Jonathan Riddell from comment #1)
> The package it wants is kdeconnect-dbgsym but I don't know how kcrash works
> that out

Yeah I figured that. Just need to figure out why the kcrash dialog can't work that out.
Comment 3 Nate Graham 2020-10-26 22:48:32 UTC 
Over to kcrash then
Comment 4 Harald Sitter 2020-10-30 10:55:48 UTC 
Moving back to neon. The package resolution and installation is distro dependent.

What's the actual backtrace this happens with?
Comment 5 Justin Zobel 2020-10-30 11:00:02 UTC 
Created attachment 132885 [details]
attachment-16518-0.html

Any really. I've tried searching for debug symbols for a number of things
that crashed. The first one when I reported this was for KDE Connect.

On Fri, 30 Oct 2020, 9:25 pm Harald Sitter, <bugzilla_noreply@kde.org>
wrote:

> https://bugs.kde.org/show_bug.cgi?id=428254
>
> Harald Sitter <sitter@kde.org> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>          Resolution|---                         |WAITINGFORINFO
>            Assignee|faure@kde.org               |neon-bugs@kde.org
>             Product|frameworks-kcrash           |neon
>             Version|5.75.0                      |unspecified
>           Component|general                     |general
>              Status|REPORTED                    |NEEDSINFO
>
> --- Comment #4 from Harald Sitter <sitter@kde.org> ---
> Moving back to neon. The package resolution and installation is distro
> dependent.
>
> What's the actual backtrace this happens with?
>
> --
> You are receiving this mail because:
> You reported the bug.
Comment 6 Harald Sitter 2020-10-30 11:25:17 UTC 
I need a sample backtrace all the same. If I just SEGV my kdeconnectd the packages get correctly resolved.
Comment 7 Justin Zobel 2020-10-30 22:44:22 UTC 
(In reply to Harald Sitter from comment #6)
> I need a sample backtrace all the same. If I just SEGV my kdeconnectd the
> packages get correctly resolved.

Have you got a guide to doing a backtrace? Pretty new to code debug.
Comment 9 Justin Zobel 2020-11-01 01:21:54 UTC 
I haven't had the kdeconnectd crash in a while so I'm resolving this for now. Will re-raise if it starts again and provide crash logs.