The error I get from 2k is "Unable to display security information".
This is bad, we should still display the ACLs here, and just show the things we
can't resolve as unmappable SIDs. This can happen very easily if somebody
deletes a user from the local SAM and the local SAM UIDs/GIDs are not in the
The easiest way to do this is to create a new file under a share and do a chown
that file to some ID that's not in /etc/passwd and is not in the idmap range.
Created attachment 148 [details]
log.smbd of this failing
This is the log.smbd when we get the "Unable to view security information"
Created attachment 149 [details]
A .jpg of the security tab in this state
This is a .jpg of the security tab when this bug is in effect
Created attachment 150 [details]
Marc, please test this proposed fix.
Jerry - do you agree with this being added into SAMBA_3_0_RELASE ?
This caused a segfault for me and it still didn't display the info. I'm trying
to figure out where the segfault was. I'll probably look at it tomorrow though.
Created attachment 151 [details]
The backtrace of the segv when using jra's patch
This is the backtrace that I got when doing the same operation the bug
describes after applying jra's patch
Sorry, bad patch. I've checked in a proper fix (fingers crossed) to SAMBA_3_0
and HEAD. Still awaiting Jerry confirmation for check into SAMBA_3_0_RELEASE.
Fix is working great! Thanks.
Jerry, I'd like to mark this closed, I just want to make sure that you want this
change in the release first.
Integrated with SAMBA_3_0_RELEASE.
originally reported against one of the 3.0.0rc[1-4] releases.
Cleaning up non-production versions.
sorry for the same, cleaning up the database to prevent unecessary reopens of bugs.