| Summary: | Discover crashes after use "Update All" due to: "Fatal error" about unmet dependencies | ||
|---|---|---|---|
| Product: | [Applications] Discover | Reporter: | Piotr Mierzwinski <piotr.mierzwinski> |
| Component: | discover | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED MOVED | ||
| Severity: | crash | CC: | aleixpol, nate, piotr.mierzwinski |
| Priority: | NOR | ||
| Version First Reported In: | 6.5.80 | ||
| Target Milestone: | --- | ||
| Platform: | Neon | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
discover coredump.01
discover coredump.02 discover coredump.03 discover coredump.04 |
||
|
Description
Piotr Mierzwinski
2025-10-12 00:45:39 UTC
This is mostly a distro problem, but Discover definitely shouldn't crash when it happens. Can you attach a backtrace of the crash? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl You might also want to report this to the Neon folks at https://bugs.kde.org/enter_bug.cgi?classification=KDE%20Neon; they'll want to know about the packaging dependency issue. (In reply to Nate Graham from comment #1) > This is mostly a distro problem, but Discover definitely shouldn't crash > when it happens. Can you attach a backtrace of the crash? See > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl Usually I send automatic report about crash. Next time I will add my account name to the message. Anyway I meet crash of Discovery quite often and from time to time I send automatic report, but don't see any progress. For example yesterday Discover crashes and didn't happen "Fatal error" about unmet dependencies, because I was able to update distro with command: "sudo pkcon update", and today Discover didn't crashes. If you consider this is distro problem then please redirect this to Neon folks. (In reply to Nate Graham from comment #2) > You might also want to report this to the Neon folks at > https://bugs.kde.org/enter_bug.cgi?classification=KDE%20Neon; they'll want > to know about the packaging dependency issue. In the past I reported issues to Neon folks couple time, but I waited very, very long time (several months) for answer, and often I didn't get it never, so I stopped report anything to Neon. Darn. Well at the very least we can look into the issue from the Discover side. Can you attach a backtrace of the crash? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl I will attach. BTW. Today I made update of distro by Discover with success (got message and updates will be installed after restart), but when I click RMB onto icon present in tray I can see in menu option "Start Update". Isn't this a bug in Discover, or maybe is this distro problem? If you confirm me this is bug in Discover I can report this as separate bug report. Let's please focus on one issue at a time. Bug reports need to be about one issue, not many. Go ahead and move this out of the NEEDSINFO WAITINGFORINFO state when you've attached a backtrace of the crash. Thanks! Created attachment 185780 [details]
discover coredump.01
Created attachment 185781 [details]
discover coredump.02
Created attachment 185782 [details]
discover coredump.03
Created attachment 185783 [details]
discover coredump.04
(In reply to Nate Graham from comment #7) > Let's please focus on one issue at a time. Bug reports need to be about one > issue, not many. Go ahead and move this out of the NEEDSINFO WAITINGFORINFO > state when you've attached a backtrace of the crash. Thanks! Ok. Please follow the instructions on that wiki page. We don't need a whole core, just the textual backtrace of the crashing thread. The instructions guide you through getting that. (In reply to Nate Graham from comment #13) > Please follow the instructions on that wiki page. We don't need a whole > core, just the textual backtrace of the crashing thread. The instructions > guide you through getting that. And what is sent in case of automatic crash report? Usually something quite useful. If you've sent an automatic report, we don't need this one here. Have you? (In reply to Nate Graham from comment #15) > Usually something quite useful. If you've sent an automatic report, we don't > need this one here. Have you? I think for described case I sent automatic report. Then let's just track it in Sentry. |