After a recent update (I think a week or so ago) SMB4K stopped working properly. I am unable to scan my workgroup and see a message saying ‘failed to init messaging context’ on each time I try. I am able to use the smb:// protocol in dolphin to access an shares but unable to use SMB4K in the normal way. This is on Tumbleweed KDE Plasma 5 btw. The problem does not exist on Laep 42.2.
Anyone else seen this? Anyone any ideas please?
Stuart
By what do you mean “the normal way?”
Mounting a SMB network share in a command line console?
Something else?
If from a command line, would want to see the command syntax you’re using, and what the Share permissions are (local machine? network security like AD or LDAP, and what type of DC are you using?)
TSU
By the normal way I mean (as I said ) using SMB4k as it is intended, double click on workgroup and it shows the computers, then double click on the computer and it shows the shares which can then be mounted by SMB4K. None of that works because of the error message from SMB4K. I’d expect a mount from a console to work as well since the smb:// protocol works in Dolphin, however I like to use SMB4k and cannot currently.
Stuart
I’d take issue with any description that accessing SMB network shares “normally” is by using a GUI client.
To troubleshoot your issue,
You need to “go back to basics” using the command line to execute each step of functionality you describe in your Dolphin client…
Recommend you start with what is described in the MAN pages, eg
https://www.samba.org/samba/docs/man/manpages-3/smbclient.1.html
If you can verify the functionality exists from the command line, then you might say that suggests the problem is in the application client you’re using.
HTH,
TSU
You may take issue with what I say, however using a GUI client is not a problem and I can see no reason to suggest otherwise. All I was doing was attempting to see if any other users here were experiencing the same issue with SMB4K, no more and no less. I fail to see why you are taking this attitude when all I am asking for is a little information. Obviously no one else is seeing this which is fine. I dont need to go into details about what works from either Dolphin or the commandline - IT ALL WORKS.
So as far as I am concerned this thread and be locked as I have no desire to continue discussing this with anyone who is not interested in my issue.
Mods please lock this now.
Stuart
I think you are mis-reading my comment. I was referring to the normal way to use SMB4K to mount shares. I was not trying to suggest using a GUI client was ‘normal’ although I see nothing wrong in using it. I happen to prefer GUI ways of doing things although I am perfectly capable of doing it via a console.
As far as I can tell it is indeed SMB4K which has a problem and I was trying to see if anyone else here might be using it and have this issue. Obviously from the lack of other replies no one else seems to have this problem which is fine. I need to debug SMB4K.
Stuart
Hi Stuart,
yes - we’re two … I also cannot access my Samba-shares with Smb4k. I renamed all Smb4k confi files and so on, removed and re-installed Smb4k, but it does not work. It started a week ago or so, obviously with an update. I can access the Samba shares via Dolphin, but that does not work e.g. for digiKam.
Did you get any help or solved the problem meanwhile?
Cheers,
Bogislav
No it is still failing for me here. I have asked for help of the SMB4K author but nothing yet.
Stuart
I can access my NAS through Dolphin (under networks, smb:), but this does not help because DigiKam does not support this. I can also mount the NAS but I cannot get RW access as normal user (I even set SUID to mount.cifs …).
I suppose - but this is just a guess - that the issue might not be smb4k but rather a security setting of opensuse in one of the latest updates, e.g. a firewall setting or so. smb4k keeps trying to connect and ends in a dead loop.
Cheers,
Bogislav
Exact;y what do you see? With my problem I get the notification message saying ‘failed to init messaging context’. Do you get the same message? If not then I suspect it could be a dfferent issue.
Stuart
Mounting with SMB4K doesn’t work currently because of a security issue. See also https://forums.opensuse.org/showthread.php/524960-Multiple-issues-after-recent-updates-(May-2017)?p=2823808#post2823808
FYI, smb4k 2.0.1 (with the fixed mount helper) is now available in the KDE:Extra repo, for Tumbleweed and Leap 42 (.1, .2, and .3).
http://software.opensuse.org//downlo…&package=smb4k
So people who want/need to use it to mount shares can install it from there for now.
It will enter Tumbleweed after a (hopefully) successful new security review, which we requested today, but that may of course take some time.
I did install that today on TW but still have an issue scanning the workgroup where I get ‘Failed to init messaging context’ message, I can mount from bookmarks OK though.
Stuart
As mentioned in the other thread, this might be an issue in Samba 4.6.
And regarding mounting: unfortunately the security team immediately declined the new review with the words “this can never be secure”.
http://bugzilla.suse.com/show_bug.cgi?id=1041511
So, it seems there never will be a working smb4k in the distribution again.
TBH, I’m fed up.
Well thanks for trying anyway. I am going to discuss with the author to see if anything can be done.
Stuart
FYI, this is likely related to https://bugzilla.opensuse.org/show_bug.cgi?id=1043115 I think.
Should be fixed soon then.
Well my system now has 4.6.6+git.36.67c8c47724e-1.1 and I still have the issue. I am unable to tell if this is the release which contains the fix, if it does the fix does not work.
Stuart
Obviously not:
Mon Jul 24 13:34:55 UTC 2017 - ddiss@suse.com
- fix cephwrap_chdir(); (bsc#1048790).
- Update to 4.6.6
+ CVE-2017-11103: Orpheus' Lyre KDC-REP service name validation;
(bsc#1048278).
Apparently 4.6.6 was just a critical security update…
Note that the comment in the mentioned bug report says that the fix is planned for 4.6.6, and the bug report is still open as well.
The 4.6.7 update that has been submitted to the devel project and forwarded to Tumbleweed 6 hours ago does refer to the updstream bug report though (12828 – net command fails due to incorrectly return code), so that should have the fix…
Request 517193: Submit samba - openSUSE Build Service
Wed Aug 16 11:33:36 UTC 2017 - ddiss@suse.com
- Update to 4.6.7; (bsc#1054017)
...
+ net command fails due to incorrectly return code; (bso#12828).
...
I had similar problems in Leap 42.3, smb4k 2.0.1 works fine for me. I wonder if not there is a “1-click install” as well (still getting it from KDE:Extra).
regards
There is:
https://software.opensuse.org/package/smb4k
Just click on “Show other versions” and “Show possibly unstable packages” (or whatever it’s called in other languages) and choose the one from KDE:Extra.
But there’s no point in using a 1-click install if you already added the KDE:Extra repo anyway.