This morning I updated my openSUSE Tumbleweed to the latest fix level and now when I try to use SMB4K I see 'Failed to init messaging context' on scanning the workgroup, which was working prior to the update. SMB/NMB are running OK and I can see my shares using the smb:// protocol on Dolphin. SMB4K is v1.2.3 and Samba is v4.6.2. Do you have any ideas why this might be happening please?
Stuart
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Since I am running Tumbleweed which has Plasma 5 etc I compiled SMB4K V2 to see what if any thing different happens and I am getting the exact same error message using V2.
Stuart
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Done a bit more testing this morning and search finds one of my PCs on the network but a right click on it and selecting Mount fails with the same message.
Stuart
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I don't have any idea at the moment, why this problem occurs. I'll install OpenSUSE in VirtualBox and try to reproduce the problem... Maybe I find out, what's wrong.
Alexander
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Aparently openSUSE have now removed SMB4k be4cause of a bug in the mounthelper code and want it fixed before they allow SMB4K back into their repos. Does this bug exist in SMB4K V2?
Stuart
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Stuart, sorry for not answering for such a long time. I was too busy in the last few weeks...
There was indeed a bug in the mounthelper code that basically allowed the execution of any binary passed to it, since no check was performed which executable was passed.
This logic flaw has been fixed and patches for Smb4K 1.2.3 and 2.0.0 are available (see here). Smb4K 2.0.1 has been released in the meantime which also contains the fix.
Alexander
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for the update Alexander. Hopefully SMB4K will be working on openSUSE 42.2 again as soon as they update the code.
As for my Tumbleweed issue with the messaging context I am still having that and dont believe it is related to the mount fix. Is there anyway I can help to debug this?
Stuart
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm not sure. Due to the lack of time I was unable to look at this issue at all. Hopefully, this weekend I can install Tumbleweed in VirtualBox and play around a bit...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
After having had a look at Samba 4.6 under Tumbleweed, I found out that the net command runs without problems when you use sudo. When run unprivileged, it errors out. That is strange. I haven't found any indication yet, that the Samba team made that change, but I'm still investigating...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This morning I updated my openSUSE Tumbleweed to the latest fix level and now when I try to use SMB4K I see 'Failed to init messaging context' on scanning the workgroup, which was working prior to the update. SMB/NMB are running OK and I can see my shares using the smb:// protocol on Dolphin. SMB4K is v1.2.3 and Samba is v4.6.2. Do you have any ideas why this might be happening please?
Stuart
Since I am running Tumbleweed which has Plasma 5 etc I compiled SMB4K V2 to see what if any thing different happens and I am getting the exact same error message using V2.
Stuart
Done a bit more testing this morning and search finds one of my PCs on the network but a right click on it and selecting Mount fails with the same message.
Stuart
Hi Stuart,
I don't have any idea at the moment, why this problem occurs. I'll install OpenSUSE in VirtualBox and try to reproduce the problem... Maybe I find out, what's wrong.
Alexander
Thanks Alexander, if there is anything you would like me to test please let me know. So far it's only on Tumbleweed, the LEAP versions are still OK.
Stuart
I have started to see a few other comments about this issue which might be something in Samba 4.6 which is what I have seen the issue for. One report is https://src.fedoraproject.org/cgit/rpms/samba.git/commit/?id=563829e681b9845325e7223c13c2e7b517f7e0df which is a Fedora patch but not sure if it fixes this issue but was linked from https://github.com/KaOSx/apps/issues/108
If anyone can suggest how I might debug this I'd appreciate it.
Stuart
Aparently openSUSE have now removed SMB4k be4cause of a bug in the mounthelper code and want it fixed before they allow SMB4K back into their repos. Does this bug exist in SMB4K V2?
Stuart
Stuart, sorry for not answering for such a long time. I was too busy in the last few weeks...
There was indeed a bug in the mounthelper code that basically allowed the execution of any binary passed to it, since no check was performed which executable was passed.
This logic flaw has been fixed and patches for Smb4K 1.2.3 and 2.0.0 are available (see here). Smb4K 2.0.1 has been released in the meantime which also contains the fix.
Alexander
Thanks for the update Alexander. Hopefully SMB4K will be working on openSUSE 42.2 again as soon as they update the code.
As for my Tumbleweed issue with the messaging context I am still having that and dont believe it is related to the mount fix. Is there anyway I can help to debug this?
Stuart
Could this bug at https://bugzilla.samba.org/show_bug.cgi?id=12828 possibly be the issue here?
Stuart
I'm not sure. Due to the lack of time I was unable to look at this issue at all. Hopefully, this weekend I can install Tumbleweed in VirtualBox and play around a bit...
After having had a look at Samba 4.6 under Tumbleweed, I found out that the net command runs without problems when you use sudo. When run unprivileged, it errors out. That is strange. I haven't found any indication yet, that the Samba team made that change, but I'm still investigating...