New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
smb4k Fails to Retreive List of Hosts #108
Comments
When did this start? Update of samba to 4.6.1? Since you use the build repo (and should disable kde-next, not in use), please check if the issue is resolved by using samba from main:
|
I'm not sure when it started. I haven't used smb4k in a bit. Yesterday was when I first noticed it. I reverted to the samba in main and same thing. How do I remove 4.6.1? If I try to uninstall it doesn't just remove samba. |
Once you install Samba from main it replaces 4.6.1 (from build), you don't remove it.
|
I shut two of my three platforms down and tested on the third which is running SAMBA 4.6.1. It is working. I have seen this before. The NETWORK gets out of sync somehow and I have to reboot all platforms in a particular sequence, which one of these days I'll get around to writing down so I don't forget the sequence. I think it has to do with more than one Master Browser, but I have yet to figure out why. I don't think you have an issue. I think this is a long standing thing that has been there for years and across multiple distros. I may even have read about this in the SAMBA documentation somewhere. I am going to,bring up the other two platforms now and see what hapens. I think the sequence is to bring up the platform that I want as the Master Browser first (My Desktop PC) and then the other two (laptops) in any sequence. I'll let you know what happens. REPO order: build, core, main, and apps; correct? On this laptop where smb4k works I only have core, main, and apps. Should I leave build out? |
Yes, repo order as correct, but best to only have kde-next enabled when it is announced in the forum as being active. |
After messing around with what I thought was the issue (thick-heade3d you know :))) ) with no luck. I did what you asked pacman -U https://sourceforge.net/projects/kaosx/files/packages/samba-4.5.5-2-x86_64.pkg.tar.xz And yeah smb4k is not compatible with the 4.6 series. |
Then this probably needs to be taken upstream at smb4k. Not much I can do to make it compatible with new Samba. |
Agreed. I'm ignoring samba in pacman.conf for the time being and using
the sourceforge version.
…On 03/30/2017 03:49 PM, demmm wrote:
Then this probably needs to be taken upstream at smb4k. Not much I can
do to make it compatible with new Samba.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#108 (comment)>, or
mute the thread
<https://github.com/notifications/unsubscribe-auth/AVEUuYrbQ7m5RtbcsUcRIRRv1Ivkdd8yks5rrAdigaJpZM4MtsK1>.
|
It might actually be an issue in Samba, see this patch used in Fedora: |
I downloaded it and extracted it to my Build folder. I will reinstall
SAMBA 4.6.0.1 in the morning. How do I install the patch?
…On 03/30/2017 04:48 PM, demmm wrote:
It might actually be an issue in Samba, see this patch used in Fedora:
https://src.fedoraproject.org/cgit/rpms/samba.git/commit/?id=563829e681b9845325e7223c13c2e7b517f7e0df
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#108 (comment)>, or
mute the thread
<https://github.com/notifications/unsubscribe-auth/AVEUuYW0cKDkY4z8TLXaH2w6s3SYo3s8ks5rrBU0gaJpZM4MtsK1>.
|
There is no reference that this fixes smb4k. |
Yeah, I'm happy either way. 4.5 is working fine, and I may decide to go
bnack to 4.6 because I kind of like using Dolphin places over smb4k.
How's your immigration status going? Are you going to be able to stay
here in the US and keep your farm?
Tom
…On 03/30/2017 09:25 PM, demmm wrote:
There is no reference that this fixes smb4k.
You state too, Dolphin works fine with Samba 4.6.1, otherwise I would
have already applied the patch.
I will check upstream both smb4k & samba for bug reports regarding
this. Will leave report open in the meantime.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#108 (comment)>, or
mute the thread
<https://github.com/notifications/unsubscribe-auth/AVEUueykhjCjiXswEX1Xner3Cc3Pivzmks5rrFYPgaJpZM4MtsK1>.
|
Please report back if samba 4.6.2 fixes any, just uploaded to the build repo. |
No. Same. I had already tried it last night. I downloaded it from
samba.org, but I retried with the build version just to double check.
…On 03/31/2017 11:47 AM, demmm wrote:
Please report back if samba 4.6.2 fixes any, just uploaded to the
build repo.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#108 (comment)>, or
mute the thread
<https://github.com/notifications/unsubscribe-auth/AVEUuZvn3WrVPwbuoRAr6B2id7ggdNPaks5rrR_9gaJpZM4MtsK1>.
|
Please report back if this still is an issue. |
No longer an issue. I closed it |
Submission type
Package name & version you are having issues with or have a request for
Used repositories
Expected behaviour
Actual behaviour
Steps to reproduce the problem
System info link created by Octopi > Tools > SysInfo
The text was updated successfully, but these errors were encountered: