SUMMARY Whenever I click on the share tab in dolphin to share a folder via samba, dolphin now crashes. STEPS TO REPRODUCE 1. Open dolphin 2. Right click a folder and click on properties. 3. Go down to share tab. OBSERVED RESULT Dolphin crashes. EXPECTED RESULT Should open the share tab SOFTWARE/OS VERSIONS Operating System: EndeavourOS KDE Plasma Version: 6.4.3 KDE Frameworks Version: 6.16.0 Qt Version: 6.9.1 Kernel Version: 6.15.8-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800X 8-Core Processor Memory: 64 GiB of RAM (62.7 GiB usable) Graphics Processor: NVIDIA GeForce RTX 3080 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7C95 System Version: 1.0 Extra info: Output from terminal IFFChunk::innerFromDevice: unkwnown chunk "\x89PNG" qrc:/org.kde.filesharing.samba/qml/ACLPage.qml:23:5: QML OverlaySheet: Binding loop detected for property "implicitHeight": file:///usr/lib/qt6/qml/org/kde/kirigami/templates/OverlaySheet.qml:139:5 qrc:/org.kde.filesharing.samba/qml/ACLPage.qml:23:5: QML OverlaySheet: Binding loop detected for property "implicitHeight": file:///usr/lib/qt6/qml/org/kde/kirigami/templates/OverlaySheet.qml:139:5 qrc:/org.kde.filesharing.samba/qml/ACLPage.qml:23:5: QML OverlaySheet: Binding loop detected for property "implicitHeight": file:///usr/lib/qt6/qml/org/kde/kirigami/templates/OverlaySheet.qml:139:5 qrc:/org.kde.filesharing.samba/qml/ACLPage.qml:23:5: QML OverlaySheet: Binding loop detected for property "implicitHeight": file:///usr/lib/qt6/qml/org/kde/kirigami/templates/OverlaySheet.qml:139:5 qrc:/org.kde.filesharing.samba/qml/ACLPage.qml:23:5: QML OverlaySheet: Binding loop detected for property "implicitHeight": file:///usr/lib/qt6/qml/org/kde/kirigami/templates/OverlaySheet.qml:139:5 qrc:/org.kde.filesharing.samba/qml/ACLPage.qml:23:5: QML OverlaySheet: Binding loop detected for property "implicitHeight": file:///usr/lib/qt6/qml/org/kde/kirigami/templates/OverlaySheet.qml:139:5 KCrash: Application 'dolphin' crashing... crashRecursionCounter = 2 fish: Job 1, 'dolphin' terminated by signal SIGSEGV (Address boundary error) Dr. konqi says output not really useful even after downloading debug symbols.
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.