For info: here our sepolicytype=1400 audit(1455258470.343:25): avc: denied { open } for pid=4138 comm="Thread-277" name="smbd.pid" dev="mmcblk0p27" ino=103560 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=ubject_r:app_data_file:s0 tclass=file permissive=0
Thanks for reporting :good:@berserker_devel
Regarding Marshmallow, where sharing won't start.
I and few other users in thread faced this problem.
I discovered, that at least on CyanogenMod 13 problem in "enforcing" SELinux.
If switch it off ("permissive") all works fine.
Here what in audit log:
For info: here our sepolicy
Thank you for attention.
@berserker_devel
Regarding Marshmallow, where sharing won't start.
I and few other users in thread faced this problem.
I discovered, that at least on CyanogenMod 13 problem in "enforcing" SELinux.
If switch it off ("permissive") all works fine.
Here what in audit log:
For info: here our sepolicy
Confirmed that this works with Nexus 6P stock build MMB29M
I used SELinuxModeChanger from here -> http://xdaforums.com/showthread.php?t=2524485
@berserker_devel
Regarding Marshmallow, where sharing won't start.
I and few other users in thread faced this problem.
I discovered, that at least on CyanogenMod 13 problem in "enforcing" SELinux.
If switch it off ("permissive") all works fine.
Here what in audit log:
For info: here our sepolicy
It appears that it doesn't work on Android 6.0.1. Can someone else confirm?
Install SELinuxModeChanger and set permissions to passive and it will work.Verified it does not work on the Rooted Nvidia Shield TV after the most recent Marshmallow 6.0 update from 5.1.
Anyone having an issue with backup/sync type programs not seeing some of the files on large (400+ files), flat directories? I just started using this this weekend, and on multiple devices and multiple OS's and multiple backup programs, the next time I sync, it shows a few files missing. These files are there, and it shows the same files missing on all devices. On directories with lots of files, but broken into many sub-directories, it sees them all just fine.
Install SELinuxModeChanger and set permissions to passive and it will work.
Sent from my XT1096 using Tapatalk
Translated line:<string name="ftp_user_invalid_password">Invalid password</string>
Please do not translate anything inside the "name" attribute:<string name="ftp_user_invalid_password">My translation of Invalid password</string>
But only:
I already implemented a fix for this situation in the 1.0.2 betaYou figured out a solution on your own by re-installing it, but if I pointed you in the right direction, you're welcome. Another solution, if Berserker's hunch is right, would've been to change the owner of the "nmbd" folder to "root" via Solid Explorer (on the same page as the "Change" button that I mentioned earlier) or other file manager. Anyways, the problem was even simpler than realized. I take it that you had Android 4.1 (CM10) with SambaDroid installed, backed everything up with Titanium Backup, flashed Android 4.2 (CM10.1), then restored your backup. Like you said, it could be an issue with Titanium Backup not restoring ownership rights or permissions correctly for SambaDroid's folders and files. If so, it doesn't sound like a huge, huge problem, but, maybe, as a workaround for users' sakes, SambaDroid could check for and fix incorrect permissions (or, at least, somehow detect a problem and recommend a re-installation).