| Summary: | KIO/KDirModel: Kate crash while trying to save a new file to a Samba share | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] frameworks-kio | Reporter: | Valdo <gnu4ever> |
| Component: | general | Assignee: | David Faure <faure> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | castro8583bennett, christoph, faure, kdelibs-bugs, nate, postix, simonandric5, tgmeadors |
| Priority: | VHI | Keywords: | drkonqi |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Neon | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | New crash information added by DrKonqi | ||
|
Description
Valdo
2018-02-11 20:34:39 UTC
@Valdo: Now this is important: Can you reproduce this issue? Could you please try very hard to reproduce this? What did you do exactly? Please also skim through bug #190535 and see whether you maybe did something similar. This bug is ~10 years old and it seems it's still not entirely fixed. So any help here would be very much appreciated!!! This seems to be a very old bug as well and is a duplicate of bug #295702 and #190535. I won't close it as duplicate yet, since #190535 is in state NEEDSINFO / WAITINGFORINFO. @dfaure: It seems even thanks to the many fixes in bug #190535, there still are cases where this bug can happen. The backtrace shows the node=0x0, and rowNumber==-1. Same as in #190535. Hi Dominik, yes I can reproduce this issue systematically. A/ Test case avoiding the bug: I can create an empty text file in the remote Samba share with Dolphin. Then open that empty file with Kate, feed it with some text and save it: no issue. B/ Test case hitting the bug: Launch Kate, type in some text, then click Save, navigate to the "Network" shortcut, then double-clicking "Samba shares": Kate crashes in less than a second. By reading the first part of bug #190535, I had the idea to launch Kate from Konsole. As soon as I click Save (to select a destination folder), this information displays in Konsole: kf5.kio.core: Refilling KProtocolInfoFactory cache in the hope to find "" kf5.kio.core: KSambaShare: Could not find smb.conf! Each time I navigate to a new local subfolder, I get this information: kf5.kio.core: Refilling KProtocolInfoFactory cache in the hope to find "" Then clicking the "Network" shortcut to the left of the Save window: kf5.kio.core: Refilling KProtocolInfoFactory cache in the hope to find "" As soon as I double-click "Samba shares" to the right, I get this in Konsole: kf5.kio.core: Refilling KProtocolInfoFactory cache in the hope to find "" kf5.kio.core: Refilling KProtocolInfoFactory cache in the hope to find "" kf5.kio.core: Refilling KProtocolInfoFactory cache in the hope to find "" kf5.kio.widgets: Items emitted in directory QUrl("smb://") but that directory isn't in KDirModel! Root directory: QUrl("smb:///") Item: QUrl("smb://workgroup") KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = kate path = /usr/bin pid = 1779 KCrash: Arguments: /usr/bin/kate KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 [2]+ Arrêté kate $ Remember my Samba share is hosted on a Linux Mint 18.3 machine. On that machine, when right-clicking the folder shared with Samba and selecting option "Sharing options" (or equivalent English translation), I can notice that message: "The share name is too long" (or equivalent English translation). In my case, the share name is "Partage Mint-land". I hope this helps. Feel free to ask for more details if needed. And thanks for your investigation. Created attachment 112601 [details]
New crash information added by DrKonqi
kwrite (18.04.1) using Qt 5.10.0
- What I was doing when the application crashed:
I was trying to access a file from a SAMBA share located on my NAS. KWrite crashed when I clicked on the NAS icon. The shares were not listed.
-- Backtrace (Reduced):
#6 KDirModelNode::rowNumber (this=0x0) at /workspace/build/src/widgets/kdirmodel.cpp:168
#7 KDirModelPrivate::indexForNode (this=0x27f13e0, node=0x0, rowNumber=-1) at /workspace/build/src/widgets/kdirmodel.cpp:349
#8 0x00007fa413a15f7a in KDirModelPrivate::_k_slotNewItems (this=<optimized out>, directoryUrl=..., items=...) at /workspace/build/src/widgets/kdirmodel.cpp:446
#9 0x00007fa4154ca7b6 in QtPrivate::QSlotObjectBase::call (a=0x7ffe2c167150, r=0x1fe0230, this=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:378
[...]
#12 0x00007fa4136a6e7a in KCoreDirLister::itemsAdded (this=<optimized out>, _t1=..., _t2=...) at /workspace/build/obj-x86_64-linux-gnu/src/core/moc_kcoredirlister.cpp:476
Looks more like an issue in the KDirModel itself. my Samba is shared when right-clicking the folder shared with Samba and selecting option "Sharing options". Castro B, https://mrpromokod.ru Git commit d219f304319cb61aa51aae78c46872cbe49f8ff0 by David Faure. Committed on 15/04/2020 at 07:54. Pushed by dfaure into branch 'master'. Avoid crash in release mode after the warning about unexpected child items The root of the issue seems to be in kio_smb though. M +1 -0 src/widgets/kdirmodel.cpp https://commits.kde.org/kio/d219f304319cb61aa51aae78c46872cbe49f8ff0 Thank you for reporting this crash in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the crash with a recent software version? If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you! Unfortunately I no longer use Samba shares and can not test this. Ok, I guess we'll close it for now, then. |