Version: (using KDE 4.0.83) Installed from: Unlisted Binary Package OS: Linux When I try to access a password-protected samba share, I get the authorization dialog, but when I put my user and password, I get "The file or folder smb://..... does not exist." I seems that when using an url of the form smb://user@computer/, after being asked for the password it always gives this error (on all shares, not only the password-protected ones); using smb://computer/ works, but not with password-protected shares. I get this both with openSUSE 11.0 and Kde4daily. Strangely, this was working two days ago with openSUSE 10.3 and KDE 4.0.2 or 4.0.3 so I'm unsure if a bugfix caused this, or some new samba version that comes with 11.0 (and also with kubuntu, from which kde4daily is built).
I confirm the bug. It worked with OpenSuSE 11 and KDE 4.1 RC 1 but after the last update, dolphin crashes with: Application: Dolphin (dolphin), signal SIGSEGV [?1034h(no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb62526d0 (LWP 3464)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [KCrash handler] #6 0xb7d7d736 in ?? () from /usr/lib/libkio.so.5 #7 0xb7d7ea74 in ?? () from /usr/lib/libkio.so.5 #8 0xb75893fa in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #9 0xb7589972 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #10 0xb774f6b3 in KJob::result () from /usr/lib/libkdecore.so.5 #11 0xb774fb52 in KJob::emitResult () from /usr/lib/libkdecore.so.5 #12 0xb7d53b05 in KIO::SimpleJob::slotFinished () from /usr/lib/libkio.so.5 #13 0xb7d53c4e in KIO::ListJob::slotFinished () from /usr/lib/libkio.so.5 #14 0xb7d5c183 in KIO::ListJob::qt_metacall () from /usr/lib/libkio.so.5 #15 0xb75893fa in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #16 0xb7589972 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #17 0xb7dfe3d7 in KIO::SlaveInterface::finished () from /usr/lib/libkio.so.5 #18 0xb7e00eef in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.5 #19 0xb7dfec77 in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.5 #20 0xb7df1880 in KIO::Slave::gotInput () from /usr/lib/libkio.so.5 #21 0xb7df1bf3 in KIO::Slave::qt_metacall () from /usr/lib/libkio.so.5 #22 0xb75893fa in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #23 0xb7589972 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #24 0xb7d23777 in KIO::Connection::readyRead () from /usr/lib/libkio.so.5 #25 0xb7d251b2 in ?? () from /usr/lib/libkio.so.5 #26 0xb7d25806 in KIO::Connection::qt_metacall () from /usr/lib/libkio.so.5 #27 0xb758433b in QMetaCallEvent::placeMetaCall () from /usr/lib/libQtCore.so.4 #28 0xb7585ed1 in QObject::event () from /usr/lib/libQtCore.so.4 #29 0xb6a0aecc in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #30 0xb6a1131e in QApplication::notify () from /usr/lib/libQtGui.so.4 #31 0xb7b2183d in KApplication::notify () from /usr/lib/libkdeui.so.5 #32 0xb7577b51 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #33 0xb7578411 in QCoreApplicationPrivate::sendPostedEvents () from /usr/lib/libQtCore.so.4 #34 0xb75a032a in QEventDispatcherUNIX::processEvents () from /usr/lib/libQtCore.so.4 #35 0xb6a950a2 in ?? () from /usr/lib/libQtGui.so.4 #36 0xb75762ca in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #37 0xb757648a in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #38 0xb757866d in QCoreApplication::exec () from /usr/lib/libQtCore.so.4 #39 0xb6a0ad47 in QApplication::exec () from /usr/lib/libQtGui.so.4 #40 0x0808369f in _start () #0 0xffffe430 in __kernel_vsyscall ()
Ok so today I looked into this. It seems that indeed the problem comes from samba 3.2 which by default disables access to servers which try to authenticate with LANMAN passwords. There's a huge bug thread on launchpad about the same problem with nautilus/gvfs: https://bugs.launchpad.net/ubuntu/+bug/209520 . (And https://bugs.launchpad.net/ubuntu/+bug/209520/comments/111 explains the problem perfectly.) So the problem is in the underlying libsmbclient that kio_smb uses, but kio_smb suffers from the same problem that nautilus/gvfs suffered in that thread: it doesn't give a clear error message. When you try to connect from the command-line, you get: ~> smbclient -L //ea_sir/share Enter knuckles's password: Domain=[REDE] OS=[Unix] Server=[Samba 3.0.24] Server requested LANMAN password (share-level security) but 'client lanman auth' is disabled tree connect failed: SUCCESS - 0 Which clearly tells you - authentication using lanman is disabled. With kio_smb, you only get that rather cryptic error "The file or folder smb://..... does not exist." So I'm changing the summary of the bug to reflect this, as this bug should be about giving a clear error message, so people don't think it's a bug or a kde 4 fault (as witnessed in the launchpad bug, in that case with ubuntu 8.04 and gvfs) and it's just a samba (mis)configuration issue.
*** Bug 150743 has been marked as a duplicate of this bug. ***
Please provide exact configurations for client/server to replicate this.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. 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. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!