-
Notifications
You must be signed in to change notification settings - Fork 413
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
1.7.1 SMB ECONNREFUSED for Debian Samba (Regression from 1.6.2) #1181
Comments
Hi @SokolInTheCloud, I had similar issues with my SMB shares in Materials Files 1.7.1. Addendum: The error message I saw, was not exactly the same, but it also pertained to java8.nio. |
Hi @LevonTostig |
Hey, I just found that on Google Play the latest version is 1.6.2 (the latest working with SMB) |
It seems that you are not assuming a positive intent for me. I'm experiencing back and forth with Play Developer Support about getting the new version released on Play this time, and filing appeals isn't fun. Play version will be updated once they are approved. That was usually within 12 hours in the past and I haven't heard of any Play user complaining them being the free beta-testers for F-Droid users. Well, in terms of "free" I don't have any paid users anyway... The ECONNREFUSED errno usually means the remote server rejected the socket connection (usually a low level thing). I don't have a good guess of why either. |
@SokolInTheCloud I am almost sorry, that I tried to help you. I am not sure, that you appreciate what FOSS means. And no, the smiley and the end of the sentence about beta-testers does not help. Somebody (in this case @zhanghai) is providing you with a software free of charge and you choose to complain in this very odd way. Perhaps you can still try to check the connection to your SMB share from another device. It might also help to now, what is providing the SMB share. Last, but not least: LineageOS 18.1 is old and has finally when put to rest (https://lineageos.org/Sunsetting-LineageOS-18.1/). This means, that more and more software might stop working on your phone in the not so distant future. |
@zhanghai Hi, and thank you for your answer. I wish you the good luck with google bureaucracy. I saw what I saw - that F-Droid has versions 1.7.0 and 1.7.1 for several days, both versions have some issues, and it's just my guess about beta testing :) I don't mind being a free beta tester to make any FOSS project better. So I also spend my time for feedback on the issues described above. I suppose this could be more useful than just a bunch of negative reviews on Google Play. Previously I used some other paid app from Google Play for my SMB. I'll try to find and install it to check if the problem on my side (maybe it's lineageos security issue or Debian samba config could be updated). Anyway I like Material Files 1.6.2 and I just trying to help make it better. |
@LevonTostig I thanked you for your answer, it can really help someone else. And I would be glad if it worked in my case too. Unfortunately, this is not the case. What else can I do? I have a bunch apps on my phone, all of them work pretty good. As I wrote above Material Files 1.6.2. works with all my SMB shares with no issues. So I suppose the reason is new code in new version of Material Files. |
@zhanghai I found this app on F-Droid https://github.com/wa2c/cifs-documents-provider |
@zhanghai I also tried this app https://play.google.com/store/apps/details?id=com.cxinventor.file.explorer |
What I can tell is that SMBJ was updated from However I personally don't even use SMB myself (I only read some SMB spec to implement it) so I can't debug a specific configuration somehow broken either. After all, everything is open-source so anyone can debug it and propose fixes and I'll be happy to apply in that case. I'll also update the issue title to make it clear this is about Debian Samba and 1.6.2 to 1.7.1 so that if there's anyone else encoutering it they may find this bug and try to further debug it. |
@zhanghai I have played with samba and app settings. Samba log was useless. But it seems that the error Attempt to invoke interface method 'byte[] java.security.Key.getEncoded()' on a null object reference appears only in Anonymous authentication mode, while in Guest or Password modes everything works fine. |
Sounds like hierynomus/smbj#792 |
To work around regression in SMB anonymous authentication. See also hierynomus/smbj#792 This reverts commit d9ce4e6. Bug: #1181
Could you try the APK in https://github.com/zhanghai/MaterialFiles/actions/runs/8591504511 's artifacts? |
@zhanghai Hi! The debug version works nice with SMB in all three modes (Anonymous, Guest, Password). |
Thanks for confirming, the rollback of SMBJ will be in the next release. |
Having problem with SMB (linux samba), which worked nice with version 1.6.2 and prior.
I'm using firewall, Material Files is allowed (any in any out). But maybe newer versions require some additional permissions?
The text was updated successfully, but these errors were encountered: