Summary: | Dolphin crash when creating a new tab when the current tab is sshfs host not found | ||
---|---|---|---|
Product: | [Applications] dolphin | Reporter: | simonpatp |
Component: | general | Assignee: | Dolphin Bug Assignee <dolphin-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | kdedev, kfm-devel |
Priority: | NOR | Keywords: | drkonqi |
Version First Reported In: | 22.12.3 | ||
Target Milestone: | --- | ||
Platform: | Debian stable | ||
OS: | Linux | ||
See Also: | https://bugs.kde.org/show_bug.cgi?id=490130 | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
simonpatp
2024-07-13 04:49:47 UTC
Thank you for the bug report! Unfortunately I can't reproduce the crash myself on current git master, (Plasma 6 session, where the handling of mounting sshfs mounts is different) and the backtrace is incomplete and missing debug symbols for the following lines that we need to figure out exactly what's going wrong: #6 0x00007fe39fa855c8 in ?? () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 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! This bug looks related to bug 490130 ๐๐งน โ ๏ธ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone! Annoyingly I can't seem to reproduce this since I installed the debug symbols. I have caused it to crash multiple times before, but it's a specific network error that seems to cause this. ๐๐งน โ ๏ธ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone! ๐๐งน This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME. I was so excited I reproduced this this morning, until the bug report utility crashed trying to upload the new stack trace. Is there some place I can look for the stack trace? Thanks for being willing to add your backtrace. Take a look at this to see how to get it from disk: https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl? Unfortunately, it looks like that list caught the drkonqi crash, but not the dolphin crash. I will hope it crashes again soon . ๐๐งน โ ๏ธ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone! ๐๐งน This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME. |