Bug 423844 - discover crash on cancelling snap install
Summary: discover crash on cancelling snap install
Status: RESOLVED DUPLICATE of bug 425680
Alias: None
Product: Discover
Classification: Applications
Component: Snap Backend (show other bugs)
Version: 5.19.2
Platform: Neon Linux
: NOR crash
Target Milestone: ---
Assignee: Dan Leinir Turthra Jensen
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-07-03 16:40 UTC by kinghat
Modified: 2020-11-02 21:46 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description kinghat 2020-07-03 16:40:53 UTC
SUMMARY

discover will crash if you cancel a snap during its install process via the discover cancel button.

STEPS TO REPRODUCE

1. initiate snap install
2. cancel snap install midstream

OBSERVED RESULT

discover crashes on cancellation.

EXPECTED RESULT

clean cancellation of installation progress.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.19
KDE Plasma Version: 5.19.2
KDE Frameworks Version: 5.71.0
Qt Version: 5.14.2
Kernel Version: 5.3.0-62-generic
OS Type: 64-bit
Processors: 8 × Intel® Xeon® CPU E5-1620 v3 @ 3.50GHz
Memory: 62.7 GiB of RAM
Graphics Processor: AMD Radeon ™ RX 470 Graphics

OTHER NOTES

was able to reproduce on fresh install of desktop/workstation and fresh install on thinkpad.
Comment 1 Christoph Feck 2020-07-22 18:03:42 UTC
If possible, please add the backtrace of the crash. It is possible the crash depends on the selected packagekit backend, and the backtrace can identify which component is responsible.

For more information, please see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
Comment 2 kinghat 2020-07-23 04:01:20 UTC
(In reply to Christoph Feck from comment #1)
> If possible, please add the backtrace of the crash. It is possible the crash
> depends on the selected packagekit backend, and the backtrace can identify
> which component is responsible.
> 
> For more information, please see
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/
> How_to_create_useful_crash_reports

i installed kdelibs5-dbg and i already had plasma-discover-dbgsym. the only thing in the crash handler developer tab is "Application: Discover (plasma-discover), signal: Segmentation fault" it seems there should be more to the backtrace than this.
Comment 3 Patrick Silva 2020-11-02 21:46:42 UTC

*** This bug has been marked as a duplicate of bug 425680 ***