Summary: | Clicking the Share Tab Crashes Dolphin | ||
---|---|---|---|
Product: | [Applications] dolphin | Reporter: | Dashon <dashonwwIII> |
Component: | general | Assignee: | Dolphin Bug Assignee <dolphin-bugs-null> |
Status: | RESOLVED DOWNSTREAM | ||
Severity: | crash | CC: | dashonwwIII, kdedev, kfm-devel |
Priority: | NOR | ||
Version First Reported In: | 25.04.3 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Dashon
2025-07-30 21:08:26 UTC
As the message at the top of the summary says, if something crashed, we need a backtrace of it so we can figure out what's going on. Without a good backtrace, I'm afraid we probably won't be able to take action on this. Could you please install debug symbols and attach a new symbolicated backtrace generated by using `coredumpctl gdb` in a terminal window? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl for details about how to do this. Thanks again! (In reply to TraceyC from comment #1) > As the message at the top of the summary says, if something crashed, we need > a backtrace of it so we can figure out what's going on. Without a good > backtrace, I'm afraid we probably won't be able to take action on this. > > Could you please install debug symbols and attach a new symbolicated > backtrace generated by using `coredumpctl gdb` in a terminal window? See > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl > for details about how to do this. Thanks again! Is there anyway to attach the automatic report that dr konqi says got sent to this bug report? Actually I just figured it out. It seems to be a problem with a third party application style that causes the crash. Closing as not a kde bug. |